Parameters ineligible to use variables
Several parameters in the LPAR configuration profile currently do not support variables or should not be used with variable values due to either products' architecture requirements or z/OS® rules governing variables. System variables may be used in started task JCL (for both jobs and procedures) and in TSO logon procedures, but most may not be used in a batch JCL.
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 variable overrides. For VTAM_APPL-related
parameters, there are no exceptions; both the started tasks and the VTAM® major node members will get
JCL errors at startup if variables are used.
- Common parameters (RTE_*) not eligible to specify a variable value
on the PARMGEN panels or RTE configuration profile:
- RTE_SMS_*
- Any variation of the VOLUME, UNIT, STORCLAS, and MGMTCLAS parameters.
- RTE_STC_PREFIX
- Global runtime environment product started task prefix. (See Post-configuration steps for variables in started tasksif you choose to use variables for this parameter).
- RTE_NAMESV
- For use in the KCIJV* jobs in WKANSAMU when system variables mode is enabled (RTE_SYSV_SYSVAR_FLAG=Y).
- RTE_PLIB_HILEV
- High level qualifier for the PARMGEN work library specified on the
Parameter Generator (PARMGEN) Workflow
panel (KCIP@PG0).
- Product-specific parameters not eligible to specify a variable
value in the LPAR profile:
- Kpp_*_STC
- Any variation of the product started task prefixes. (See Post-configuration steps for variables in started tasks if you choose to use variables for these parameters).
- OMEGAMON® for CICS®
- KC2_CCnn_CLASSIC_STC
- KC2_CCnn_CUA_STC
- OMEGAMON for Db2® on z/OS Performance Expert and Performance Monitor
- KD2_DBnn_DB2_SSID
- KD2_DBnn_DB2_PROFID
- KD2_PFnn_PROFID
- KD2_CLASSIC_DB2ID_DEFAULT
- OMEGAMON for IMS on z/OS
- KI2_I1nn_CLASSIC_STC
- KI2_I1nn_CLASSIC_MPREFIX
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 (&OMXESYM., for example)
referenced as part of the STC PROC statement are not recognized by
the system.