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).