Post-configuration steps for variables in started tasks

There are MVS restrictions on starting up STC procedures when variables are used. If you use variables for the RTE_STC_PREFIX parameter or any of the product-specific Kpp_*_STC parameters, you must customize the started tasks outside the configuration software.

RTE_STC_PREFIX and *_STC-related parameter values are referenced inside PARMGEN-created product started tasks in the runtime environment's WKANSAMU library. The started task names are referenced in the started task members in two places as shown in the following Tivoli Enterprise Monitoring Server started task example.

Table 1 shows the LPAR profile for a sharing-with-base runtime environment named PLB1SYSG.

Table 1. Symbolic parameter values in LPAR profile
Parameter in WCONFIG(PLB3SYSG)	Symbolic Value	Resolved Value (system or user defined)
RTE_NAME RTE_STC_PREFIX RTE_HILEV RTE_VSAM_HILEV RTE_X_HILEV_SHARING RTE_SHARE	PLB&LEV.&SYSNAME. TSS&SYSALVL. &RHILEV. &RVHILEV. &BASEHLQ. BASE&SYSALVL.	PLB1SYSG TSS1 TSTEST.LPAR TSTEST.LPAR TSTEST BASE1

Table 2 shows the user-defined symbol in the variable configuration profile member PLB3SYSG in %GBL_USER_JCL%.

Table 2. User-defined symbol in system variable member
User-defined symbol	Resolved value at STC startup
LEV	1

The $PARSESV and KCIJVUPV jobs use the variable values in the started task for the monitoring server as shown in the following example:

PROC section:
000045 //TSS&SYSALVL.DSST  PROC RGN=0M,TIM=1440, 
000046 //				SYS=PLB&LEV.&SYSNAME.,                        
000047 //				RHILEV=&RHILEV.,                              
000048 //				BASEHLEV=&BASEHLQ..BASE&SYSALVL..R,           
000049 //				USERCMDU=&RHILEV..PLB&LEV.&SYSNAME..RKANCMDU, 
000050 //				USERPARU=&RHILEV..PLB&LEV.&SYSNAME..RKANPARU, 
000051 //				USERSAMU=&RHILEV..PLB&LEV.&SYSNAME..RKANSAMU, 
000052 //				DOUT=X,       DEBUGGING OUTPUT CLASS          
000054 //				RVHILEV=&RVHILEV.,                            
000055 //				STARTUP=KDSSYSIN             

EXEC section:
000155 //TSS&SYSALVL.DSST  EXEC PGM=KLV,REGION=&RGN,TIME=&TIM  
000156 //STEPLIB 	DD DISP=SHR,                                
000157 //				DSN=&RHILEV..&SYS..RKANMODU                 
000158 //				DD DISP=SHR,                                
000159 //				DSN=&BASEHLEV.KANMODL                       
000160 //				DD DISP=SHR,                                
000161 //				DSN=&BASEHLEV.KANMOD

When the $PARSESV and KCIJVUPV jobs build the STCs and VTAM major nodes in the environment's WKANSAMU library, PARMGEN system variables processing retains the variables inside the STC and VTAM members. Retaining the variables makes the proceduress and nodes shareable: they can be started on any LPAR without change. However, the reference to "//TSS&SYSALVL.DSST" on lines #45 and #155 in the preceding example started task does not work with MVS startup rules. MVS rules require these to be static values.

The workaround for this limitation is to change the two references to static values after PARMGEN copies the started tasks from WKANSAMU to the system procedure library (GBL_DSN_SYS1_PROCLIB value you supplied in WCONFIG profiles), by using the PARMGEN KCIJPSYS job. The following example shows a sample edit with the variable values changed to static values:

EDIT       SYS1.PROCLIB(TSS1DSST)                        
Command ===>                                             
PROC section:                                          
 000045 //TSS1DSST PROC RGN=0M,TIM=1440,                  
EXEC section:                                          
 000155 //TSS1DSST EXEC PGM=KLV,REGION=&RGN,TIME=&TIM