Types of variables supported

Parameter Generator (PARMGEN) configuration supports three types of variables: system variables, KCIPARSE extracted variables, and user-defined variables.

Typical static system variables
Typical static system variables are those defined in SYS1.IPLPARM, such as &SYSNAME and &SYSCLONE. You can use these variables as parameter values in the configuration profile so long as you specify their values using the following syntax:
```
& || VARNAME || .
```
For example, to use a static variable such as &SYSNAME for the RTE_NAME parameter, specify &SYSNAME., as shown in the following example:
```
         
   000002 ** ============================ ====================               
   000003 ** PARMGEN CONFIG Parameter     PARMGEN CONFIG Value               
   000004 ** ============================ ====================               
   000005 RTE_NAME                        "&SYSNAME."                        
```
KCIPARSE-extracted variables
The PARMGEN process has built-in application program interfaces (APIs) to extract system-related information such as IP network address, IP address, VTAM network ID, and so forth. Review and submit the $PARSEDV job to get a list of variables that you can use as PARMGEN configuration values.

For example, to use a KCIPARSE-extracted variable such as &SYSIPHOSTNAME for the RTE_TCP_HOST parameter, specify &SYSIPHOSTNAME., as shown in the following example:
```
   000012 ** ============================ ====================    
   000013 ** PARMGEN CONFIG Parameter     PARMGEN CONFIG Value          
   000014 ** ============================ ====================          
   000015 RTE_TCP_HOST                    "&SYSIPHOSTNAME."             
```
See the z/OS MVS™ Initialization and Tuning Reference (SA22-7592) for basic information on system variables.

User-defined variables

You may reference any variables that your site defines as long as the PARMGEN configuration profile parameter value is not used as any PROC symbol in a started task.

For example, to use a generic user variable such as &HUB_HOST. for the KDS_HUB_TCP_HOST parameter, specify &HUB_HOST., as shown in the following example:

   000021 KDS$    BEGIN *-- TIVOLI ENTERPRISE MONITORING SERVER         
   000022 ** ============================ ====================          
   000023 ** PARMGEN CONFIG Parameter     PARMGEN CONFIG Value          
   000024 ** ============================ ====================           
   000025 KDS_HUB_TCP_HOST                "&HUB_HOST."

The $PARSEDV job generates a $SYSVAR1 output member and stores it in the WCONFIG library. The $SYSVAR1 report provides a listing of the three types of symbols autodiscovered by PARMGEN processing. When executing any KCIPARSE job, (the KCIJPCFG, KCIJPUP1, and $PARSE* jobs, for example), review the SYSVROUT DDNAME output for a full listing.