Symbolic variables
This topic describes the symbolic variables for DASD MANAGER PLUS and for all of the BMC Administrative Products.
Symbolic variables for DASD MANAGER PLUS
This topic includes a table that lists symbolic variables that relate only to DASD MANAGER PLUS.
You can use the symbolic variables in the following table only in the following items:
- Service DD statements
- User-defined service syntax
- Service parameters
Use && to specify that DASD MANAGER PLUS should not substitute the variable but rather should remove one & and generate the remaining syntax. If DASD MANAGER PLUS encounters an & with a symbol that it does not recognize, it generates the symbolic variable in the text.
Symbolic variables specific to DASD MANAGER PLUS
Symbolic variable | Description |
|---|---|
ALID | Same as WKID |
CR CREATOR | Creator |
DA | Date, same as DD |
DATE | Date in YYMMDD format |
DATEJ | Date in YYYYDDD format |
DB | Database |
DBNAME | Database name |
DD | Day of month |
DDD | Julian day |
DDSEQ DSQ | DD sequence number |
DOPTS | Default options module, for full automation mode only |
DSNUM | Same as PART |
DT | Date in YYMMDD format |
HH | Hour |
HMS | Same as TIME |
HO | Hour |
IX | Index |
IXCR | Index creator |
IXNAME | Index name |
JD | Date in YYDDD format |
JDATE | Date in YYYYDDD format |
JDAY | Julian day |
JOBTYP | Job type, for online generation only |
JQID | Same as WKID |
JUL4Y | Date in YYYYDDD format |
JULIAN | Date in YYDDDD format |
MEMBER | For online generation only |
MI | Minutes |
MM MO | month |
OBJKW | Object keyword |
OBJNAME | Object name |
OBJT | Object type |
OBJTYPE | Object type |
OBNAM | Object name |
PART | Partition ID |
PART2 | Partition ID, at least 2-digits |
PART3 | Partition ID, at least 3-digits |
PART4 | Partition ID, is 4-digits |
PGMR | For online generation only |
PREFIX | Same as USERID, for online generation only |
RUNTYP | Run type, for online generation only |
SC SS | Seconds |
SPNAME | Either table space name or index space name |
SSID | Subsystem ID |
TIME | Time in HHMMSS format |
TS | Table space |
TSNAME | Table space name |
UID | Same as USER, for online generation only |
USER | For online generation only |
USERID | For online generation only |
UTILID UTID | Utility ID, for full automation mode only |
VCAT | VCAT name |
WKID | Action name |
WKID8 | First 8 characters of WORKID or action |
WORKID | Same as WKID |
YEAR | Year in YYYY format |
YY | Year in YY format |
YYYY | Year in YYYY format |
ZPREFIX | Same as PREFIX, for online generation only |
ZUSER | Same as USERID, for online generation only |
You can use symbolic variables in the installation options module, in the POF, and on several of the options panels. The symbolic variables are used in job cards and data set names. On product panels, an ampersand (&) must precede the symbolic variable. In the JCL of the installation options module, two ampersands (&&) must precede the symbolic variable. For information about the use of symbolic variables, see the customization guide.
Symbolic variables for BMC Administrative products
You can use symbolic variables in the installation options module, the product options file (POF), and on several of the options panels. The symbolic variables are used in job cards and data set names.
The following table lists all of the symbolic variables that the JCL Generation and Execution components use. Some of these variables are not applicable to each of the BMC Administrative products. The table indicates which products resolve the variables in job cards and data set names. The table also lists the related skeleton library (SLIB) (or ISPF) variable and the corresponding OUTPUT and TEMPLATE descriptor variables.
On product panels, an ampersand (&) must precede the symbolic variable. In the JCL of the installation options module, two ampersands (&&) must precede the symbolic variable. For information about the use of symbolic variables, see the Installation System and Customizing BMC Products and Solutions for DB2.
1 ALTER and Change Manager resolve this variable for job cards and data set names.
2 DASD MANAGER PLUS resolves this variable for job cards and data set names.
3 This variable is incremented each time any image copy is taken for a specific table space. Consider the following items if you use the GDG variable:
a JCL Generation does not verify that the GDG base definitions already exist.
b No GDG numbers are built for invalid or incomplete table space names. JCL Generation builds the &AJXDB, &AJXTS, and &OBNOD variables by parsing the utility commands in the worklist. An alter-type worklist might contain incomplete table space names for implicit table spaces because these names will not be known until the worklist is executed.
4 This value truncates after eight characters when used by JCL Generation.
5 This value is determined at runtime (same as SSID).
6 For the Compare component of Change Manager, this variable indicates the outbound migrate profile name.
7 Leave this variable blank for NOPREFIX (same as PREFIX).
Related topic