Enabling variable support

Support for variables must be enabled in each runtime environment in which variables are used. To enable variable support, the RTE_SYSV_SYSVAR_FLAG parameter in the LPAR configuration profile for each runtime environment must be set to Y. If user-defined variables are referenced, those variables and their resolved values for the target system must be defined in the system variables profile, GBL_USER_JCL(%RTE_NAME%) .

About this task

Enabling variable support involves the following steps:
  1. Enabling variable support in the RTE by setting the RTE_SYSV_SYSVAR_FLAG to Y.
  2. Defining user variables, if any, and specifying resolution values for system and KCIPARSE-extracted variables if these values cannot be determined automatically from the IPL PARMLIB.

If you are using the PARMGEN Workflow interface, you can set the RTE_SYSV_SYSVAR_FLAG on the third panel of the Set up PARMGEN work environment for an RTE option ( KCIP@PG3), or in the RTE configuration profile itself.

After you have enabled variable support, you can customize other parameters within the profile to use the system and user-defined variables. For example, you can modify the runtime environment name by using a system variable:
RTE_NAME 				OMXE&SYSNAME.
You can also customize parameters to employ user-defined variables. In the following example, the z/OS® UNIX® System Services directory used can be represented by a variable:
RTE_USS_RTEDIR 	"&RTE_USS_DIR."
If you are referencing user-defined symbols, you must also customize the GBL_USER_JCL(%RTE_NAME%) variables resolution profile to define the variables and their resolved values for this runtime environment. You can edit the member directly, or access it from the Customize PARMGEN Configuration Profile Members panel (KCIP@PG6), by selecting option 8 on the PARMGEN Workflow main menu. Figure 1 shows an example of the member where the resolved symbols are defined.
Figure 1. Pre-defined and user-defined symbolics
======================================================================
000284 * *********************************************************************
000285 * SECTION: PRE-DEFINED / USER-DEFINED SYMBOLICS *
000286 * *********************************************************************
000287 * ----------- BEGIN - USER SECTION: PRE-DEFINED SYMBOLICS ----------- *
000288 * ====================== 			  ===============
000289 * User-defined symbolic: 			  Resolved value:
000290 * ====================== 			  ===============
000291 AGT_TEMS_BKUP1_NAME_NODEID		     PLB1SP22:CMS
000292 AGT_TEMS_BKUP1_TCP_HOST 			  SP22
000293 AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD	  CANCTDCS
000294 AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR	  TS1DSLB
000295 AGT_TEMS_BKUP1_VTAM_NETID 			  USCACO01
000296 * ----------- END - USER SECTION: PRE-DEFINED SYMBOLICS ----------- *
000297 * ----------- BEGIN - USER SECTION: USER-DEFINED SYMBOLICS ---------- *
000298 * ====================== ===============
000299 * User-defined symbolic: Resolved value:
000300 * ====================== ===============
000400 * ----------- END - USER SECTION: USER-DEFINED SYMBOLICS ---------- *
008300 * ----------- BEGIN - USER SECTION: USER-DEFINED SYMBOLICS ---------- *
008400 * ====================== 			  ===============
008500 * User-defined symbolic: 			  Resolved value:
008600 * ====================== 			  ===============
008700 * ----------- END - USER SECTION: USER-DEFINED SYMBOLICS ---------- *
008800 * Type 1: Static symbol override
008900 SYSNAME 									  SYSG
009000 SYSPLEX 									  LPAR400J
009010 SYSALVL 									  2
009011 SYSCLONE 									  SG
009100 * Type 2: KCIPARSE-extracted symbols
009200 SYSVTAMNETID 							  USCACO01
009300 SYSIPHOSTNAME 							  WLAG
009400 * Type 3: User defined symbols
009500 RTE_USS_RTEDIR 							  /tstest
009600 SDA_CICS_FLAG 							  N
009710 KDS_HUB_TEMS_NAME_NODEID			  "PLB1SP22:CMS"
009711 KDS_HUB_VTAM_APPL_GLB_BROKER		  TS1DSLB
009720 KDS_HUB_VTAM_NETID 					  USCACO01
009730 KDS_HUB_TCP_HOST 						  SP22
009780 KDS_HUB_TCP_PIPE_PORT_NUM 			  14731
009790 KDS_HUB_TCP_UDP_PORT_NUM 			  14731
****** **************************** Bottom of Data ****************************

What to do next

After you enable variable support, run the jobs appropriate to the configuration scenario you are enacting.