Runtime parts in variables mode

Edit online

If variables support is enabled in a runtime environment, a number of elements are involved during runtime processing.

Runtime members
When the $PARSESV job creates the runtime members and KCIJV* and KCIJP* jobs in the runtime environment’s WK* work libraries, the runtime members are created with a reference to the variables, where applicable.
KCIJV* PARMGEN jobs
After the $PARSESV job creates the runtime members and KCIJV* and KCIJP* jobs in the runtime environment's WK* work libraries, the KCIJV* jobs are ready for submission.
For example, the KCIJPALO RTE Build/Allocation job has an equivalent KCIJVALO job, which simply submits KCIJPALO after a KCIPARSE step is performed between KCIJPALO submissions. This processing is required because references in the KCIJPALO job may be using variables that need to be resolved before submitting the subsequent job. Otherwise, if variables are used for the RTE_HILEV or RTE_NAME parameters, the job will encounter a JCL error as these parameter values are used directly in the KCIJP* jobs. Thus, a preprocessor job that resolves all variables the job may contain is needed. The KCIJVALO equivalent job performs the variables substitution prior to submitting the processed KCIJPALO from a temporary dataset to the internal reader.
Product started tasks
The $PARSESV job generates the product started tasks in the WKANSAMU library with additional imbeds added to a typical product started task:
  • The KCIPARSE step imbed performs the variables substitution step.
  • The RKANPAR/RKANCMD DDNAME imbed concatenates either the physical runtime libraries (xKANCMDU, xKANPARU) when the runtime environment is not in variables mode, or the temporary libraries where the KCIPARSE step has resolved the variables referenced in the physical runtime libraries.
  • The RKPDIN DDNAME imbed concatenates either the physical xKANPARU Persistent Data Store command files (KppPG, KppPCTL) when the runtime environment is not in variables mode or the temporary libraries where the Persistent Data Store command files (KppPG, KppPCTL) have been processed for symbolics.
Post-KCIPARSE processing in the running started task
The RKLVLOG DDNAME of the started task gets passed the resolved values of the variables specified, whether this is a typical static variable, a KCIPARSE-extracted variable, or a user-defined variable.