Change KCIPARSE to use the Configuration Manager RTEDEF defined variables

When using RTE_SYSV_SYSVAR_FLAG=Y, variables can be defined as System variable, or they may be defined in the RTEDEF(VAR$GLOB) and/or RTEDEF(VAR$lpar) members. When running the Configuration Manager (CM) GENERATE action, variables defined by the system and/or in RTEDEF(VAR$GLOB) and/or RTEDEF(VAR$lpar) members are then used. So far so good!

The CM generated started task JCL in the PROCLIB, will have a KCIPARSE step for each started task which is used to resolve the variables. However this is where it goes of track, the KCIPARSE step uses a CONFIG DD which point to the PARMGEN.JCL dataset. Not only does it not use the RTEDEF dataset, but is also uses different members in the PARMGEN.JCL dataset, namely members 1-KCI$RTEV, 2-lpar, 3-KCI$GBLV. Luckily CM will make sure that members KCI$RTEV and KCI$GBLV are empty, but nothing is done to the lpar member (right fully so). However this DOES mean that if the started task JCL is used as is, that one must make sure the variable defined in RTEDEF(VAR$GLOB) and/or RTEDEF(VAR$lpar) are transferred into the PARMGEN.JCL(lpar) member!

I suggest that with CM the KCIPARSE step is changed to use the 1-RTEDEF(VAR$GLOB) and 2-RTEDEF(VAR$lpar) members for variable resolution! This will reduce the number of places one has to make sure the proper variables are defined, and thus failures can occur. I do realize this may impact existing sites.