Parameters eligible to use variables

Only a subset of parameters support variables as their parameter values.

Only the following PARMGEN profile parameters support variables as their parameter values. These parameter values are referenced in the started task PROC variables:
RTE_NAME
Used as the STC PROC SYS=symbol parameter.
RTE_HILEV
Used as the STC PROC RHILEV=symbol parameter.
RTE_VSAM_HILEV
Used as the STC PROC RVHILEV=symbol parameter.
RTE_X_HILEV_SHARING
Used as part of the STC PROC BASEHLEV=symbol parameter.
RTE_SHARE
Used as part of the STC PROC BASEHLEV=symbol parameter.
Any PARMGEN profile parameters that have VTAM® APPLIDs (Kpp_*_VTAM_APPL_*) are applicable to &stc_prefix.M2RC and &stc_prefix.TOM, as well as the STC PROC APPL=symbol parameter.
Note: Use caution when specifying user-defined variables (as opposed to static variables) for any of these configuration profile parameters. JCL rules that govern the use of system variables state that most system variables cannot be used in batch JCL. In started-task procedures, you will generate a startup JCL error if you issue the /START &stc command, as user variables referenced as part of the STC PROC statement are not recognized by the system. (Static variables like &SYSNAME. or &SYSCLONE. are defined system-wide).

There are ways to get around this JCL rule by overriding the value of these variables using the startup command or by using the PARMGEN sample composite STC startup member (IBMAPF, by default) and then defining your own PROC symbol overrides. For VTAM_APPL-related parameters, there are no exceptions; these must not use user-defined variables, as both the started tasks and the VTAM major node members will not work.