Setting the JCL options for permanent data sets

To define or modify the values in your ISPF profile and a user POF, use the Options panels of the JCL Generation Update - Main Menu component.

To set the JCL options for permanent data sets

Use the following menu selections to display the panels for permanent work data sets:

From this menu	Select this item and press Enter
ALTER or BMC AMI Change Manager for Db2 Main Menu	Options
ALTER or Change Manager Main Options Menu	JCLGEN options
JCL Generation Update - Main Menu	Individual Data Set Options
JCL Generation Individual Data Set Options	Type of data set (SORTOUT, SYSUT, or COPY)

Important

Not all of the options are available on all of the data set options panels.

If you choose to dynamically allocate your copy or unload data sets, any changes that you make to the copy (SYSCOPY), unload (SYSREC), and baseline recovery (BLRP – for Change Manager only) data set options in the JCL Generation override panels do not take effect.

----------- JCL GENERATION DATA SET OPTIONS FOR SORTOUT UPDATE ---------------
COMMAND ===>

Type data and press Enter. Press PF3 or END to return to the main panel.

  Enter Data Set Prefix below:
    . . &PREFIX..&WKID..&STEPN
  Unit Name . . . . . . . . . . . SYSDA    (SYSDA, TAPE, etc)
  Primary Space . . . . . . . . . 10       (Cylinders)
  Secondary Space . . . . . . . . 2        (Cylinders)
  Tape EXPDT. . . . . . . . . . .          (Blank or YYDDD or YYYY/DDD)
  Tape RETPD. . . . . . . . . . .          (Blank or 1 - 9999 days)
  SMS Data Class. . . . . . . . .          (Blank or Data Class)
  SMS Storage Class . . . . . . .          (Blank or Storage Class)
  SMS Management Class . . . . .          (Blank or Management Class)

  Threshold Value . . . . . . . . 0        (Cylinders, 0 means no Threshold)
  Alternate Unit Name . . . . . .          (SYSDA, TAPE, etc)
  Alternate SMS Data Class. . . .          (Blank or Data Class Name)
  Alternate SMS Storage Class . .          (Blank or Storage Class Name)
  Alternate SMS Management Class           (Blank or Management Class Name)

Specify the prefix for the data set.Consider the following items when you specify the prefix:

The suffix in the name of an unload (SYSREC) or image copy data set varies, depending on whether the data set is dynamically allocated:

For data sets that are not dynamically allocated, JCL Generation appends the ddname to the prefix to create the name of the data set.To suppress the ddname, specify Y for the appropriate keyword in the POF.

Data set	POF keyword
Local primary copy	PCPY1_SUPPRESS_SUFF
Local backup copy	PCPY2_SUPPRESS_SUFF
Recovery primary copy	RCPY1_SUPPRESS_SUFF
Recovery backup copy	RCPY2_SUPPRESS_SUFF
File reference	UNLD_FREF_SUPPR_SUFF
Primary SYSREC	UNLD1_SUPPRESS_SUFF
Backup SYSREC	UNLD2_SUPPRESS_SUFF

To specify a GDG for the local and recovery image copy data sets, add the &GDG symbolic variable to the end of the data set prefix.
----------- JCL GENERATION DATA SET OPTIONS FOR LOCAL PRIMARY COPY UPDATE ----
COMMAND ===>

Type data and press Enter. Press PF3 or END to return to the main panel.

  Enter Data Set Prefix below:
    . . &PREFIX..&OBNOD(&GDG)
  Unit Name . . . . . . . . . . . SYSDA    (SYSDA, TAPE, etc)
  Primary Space . . . . . . . . . 10       (Cylinders)
  Secondary Space . . . . . . . . 2        (Cylinders)
  Tape EXPDT. . . . . . . . . . .          (Blank or YYDDD or YYYY/DDD)
  Tape RETPD. . . . . . . . . . .          (Blank or 1 - 9999 days)
  SMS Data Class. . . . . . . . .          (Blank or Data Class)
  SMS Storage Class . . . . . . .          (Blank or Storage Class)
  SMS Management Class . . . . .          (Blank or Management Class)

  Threshold Value . . . . . . . . 0        (Cylinders, 0 means no Threshold)
  Alternate Unit Name . . . . . .          (SYSDA, TAPE, etc)
  Alternate SMS Data Class. . . .          (Blank or Data Class Name)
  Alternate SMS Storage Class . .          (Blank or Storage Class Name)
  Alternate SMS Management Class           (Blank or Management Class Name)
When you use the &GDG variable, JCL Generation resolves the data set name using the symbolic variable, and the name includes the GDG number (see the following figure).
//*--------------------------------------------------------------------
//* UTILITY COPY DD STATEMENTS
//*--------------------------------------------------------------------
//SYCL0001 DD DSN=RDACRJ.DEMOCJ.S9(+1),
//         DCB=(SYS1.MODEL),
//         DISP=(NEW,CATLG,CATLG),
//         SPACE=(CYL,(10,2),RLSE),
//         UNIT=SYSDA
//SYCL0002 DD DSN=RDACRJ.DEMOCJ.S3(+1),
//         DCB=(SYS1.MODEL),
//         DISP=(NEW,CATLG,CATLG),
//         SPACE=(CYL,(10,2),RLSE),
//         UNIT=SYSDA
//SYCL0003 DD DSN=RDACRJ.DEMOCJ.S2(+1),
//         DCB=(SYS1.MODEL),
//         DISP=(NEW,CATLG,CATLG),
//         SPACE=(CYL,(10,2),RLSE),
//         UNIT=SYSDA
//         DISP=(NEW,CATLG,CATLG),
//         SPACE=(CYL,(10,2),RLSE),
//         UNIT=SYSDA
//SYCL0004 DD DSN=RDACRJ.DEMOCJ.S11(+1),
//         DCB=(SYS1.MODEL),
//         DISP=(NEW,CATLG,CATLG),
//         SPACE=(CYL,(10,2),RLSE),
//         UNIT=SYSDA
//*--------------------------------------------------------------------
//* SORT WORK DD STATEMENTS
//*--------------------------------------------------------------------
//SORTWK01 DD UNIT=SYSDA,
//         SPACE=(CYL,(10,2)),
//         DISP=(NEW,DELETE)
//SORTWK02 DD UNIT=SYSDA,
//         SPACE=(CYL,(10,2)),
//         DISP=(NEW,DELETE)
//SORTWK03 DD UNIT=SYSDA,
//         SPACE=(CYL,(10,2)),
//         DISP=(NEW,DELETE)
//SORTWK04 DD UNIT=SYSDA,
//         SPACE=(CYL,(10,2)),
//         DISP=(NEW,DELETE)
//SORTWK05 DD UNIT=SYSDA,
//         SPACE=(CYL,(10,2)),
//         DISP=(NEW,DELETE)
//*--------------------------------------------------------------------
If you specify a GDG for a dynamically allocated data set, Analysis does not append the two-character abbreviation and the six-digit number to the prefix.
Important
ALTER and Change Manager use data set prefixes for unload (SYSREC) and image copy data sets. These prefixes ensure the uniqueness of the name of the data set when the data set is dynamically allocated. The POF that is generated in the HLQ.UBMCCNTL data set includes the new prefixes, unless you copy an existing POF during installation. If you copy an existing POF during installation to the HLQ.UBMCCNTL data set, you might need to modify the data set prefixes.
The SRnnnnnn unload data set can contain the &MSSID symbolic variable, which identifies the Db2 subsystem ID (SSID) on the sending subsystem for a two-phase migration. The Analysis component also generates the -JCLP worklist command with the &MSSID variable and a value that refers to the sending SSID.
The prefixes for copy data sets can contain the &TSSID symbolic variable, which identifies the receiving (or target) Db2 subsystem ID (SSID). If you specify the name of the Db2 SSID as the target SSID for a migrate-type work ID, the Analysis component generates a -JCLP worklist command with the TSSID parameter. The TSSID parameter specifies the name of the receiving (or target) SSID. JCL Generation uses the name of the receiving SSID to build the Execution JCL. For example, if the following command is in the worklist, JCL Generation Update - Main Menu uses the DEBA SSID for the receiving subsystem:
-JCLP 000700 MIGR TSSID DEBA
If you do not specify the name of an SSID as the target, or you specify an asterisk, JCL Generation Update - Main Menu uses the value of the &SSID symbolic variable as the value for the &TSSID variable.
Important
If the copy data set is dynamically allocated, JCL Generation Update - Main Menu substitutes the &SSID variable for the &TSSID variable in the COPY OUTPUT descriptor. The copy utility resolves the &SSID variable.
Tip
To specify the target SSID, see Defining-migrate-options-for-a-migrate-type-work-ID .
During a table space or index reorganization, the reorg utility might make an image copy of the objects. When the utility makes a copy, you cannot specify substrings with symbolic variables in the data set prefix. The products do not support using substrings in this situation.

In the Unit Name field, type the name of the unit.Consider the following items when you specify the unit:
- The value of the unit can be a name from 1 to 8 characters long, blank, or NONE. To omit the UNIT parameter from the JCL, specify NONE.
- If you use a tape unit, JCL Generation Update - Main Menu allocates the data sets before it opens them.
- For the Error data set (SYSERnnn) and Map data set (SYSMAP), specify SYSDA.
  If you specify TAPE and need to restart the IBM LOAD utility, you must uncatalog the existing data set. Then, you must change the DD statements to a disposition of (NEW,CATLG,CATLG).
- If you have large data sets and want to avoid extents or multiple data sets on DASD, specify a tape, virtual tape, or cartridge unit.
- If you are processing a worklist in parallel, you must specify a DASD unit for your permanent work data sets.
- Tape stacking is disabled if either of the following conditions exist. As a result, specifying tape for the unit might cause you to exceed the number of tape drives at your site.
  - You use tape for the sort input (SYSUT, SUT, WRK) or sort output (SORTOUT, SORTO, SORTP) data sets, or you use tape because the maximum threshold value for DASD for a data set is exceeded. Additionally, you specify a value for the maximum number of SYSUT temporary work data sets in Analysis that the LOADPLUS and REORG PLUS utilities use to build nonclustering indexes.
  - You use the UNLOAD PLUS and LOADPLUS utilities in Analysis, and you include partitioned table spaces in the scope.
- As an alternative to specifying tape for the unit, you can specify a DASD unit that will span multiple data sets. Return to the JCL Generation Static Data Set Options panel (see Setting-the-JCL-options-for-static-data-sets) and specify a value for Max cylinders and a value greater than 1 for Max unit count.
- BMC recommends that you specify SYSDA for the unit name for ROWID SYSREC unload data sets. (The ROWID SYSREC data set is used only by the UNLOAD PLUS utility in the Database Administration and BMC AMI Database Administration for Db2 solutions.) If the ROWID SYSREC is set to SYSDA, the performance of the worklist commands for unloading the ROWID data set can be improved when the worklist is executed in parallel.
If you typed N in the Data set sizing option field in Step 2, specify the default primary and secondary quantities:
1. In the Primary Space field, type the value for the primary quantity in cylinders.
2. In the Secondary Space field, type the value for the secondary quantity in cylinders.
This option is not applicable if you choose to dynamically allocate copy or unload data sets.
In the Tape EXPDT field, type the expiration date for a tape.
In the Tape RETPD field, type the retention date for a tape.
Specify the SMS definitions for the data set classes:
1. In the SMS Data Class field, type the name of the data class.
2. In the SMS Storage Class field, type the name of the storage class.
3. In the SMS Management Class field, type the name of the management class.
In the Threshold Value field, type, in cylinders, the primary quantity for the data set.If this value is exceeded, JCL Generation Update - Main Menu uses the alternate unit and the alternate SMS parameters. Zero indicates that a threshold is not specified for the unit. If you specify zero, JCL Generation Update - Main Menu does not use an alternate unit and the alternate SMS parameters.
When ALTER or Change Manager dynamically allocates the copy data sets for IBM COPY, it uses TEMPLATE descriptors in the worklist for local and recovery primary and backup copies. If you specify a value for Threshold Value, the product provides templates for a primary set of data set attributes and an alternate set of data set attributes. If the threshold is exceeded, the utility can perform template switching and use the alternate data set.
For more information about the TEMPLATE descriptors, see Copy-utilities-options. For more information about the -COPY worklist command, see COPY-IBM-COPY-utility .
When Change Manager dynamically allocates the unload data set for a baseline recovery point, it specifies a TEMPLATE descriptor of SYRC for the data set when the baseline recovery point threshold (BLRP_THRESH) is set to 0. When the baseline recovery point threshold is greater than 0, it also specifies a TEMPLATE descriptor of SYRCX. The SYRCX descriptor includes values for alternate SMS classes.
Important
If you are processing a worklist in parallel, do not specify a threshold value.
In the Alternate Unit Name field, type the alternate name of the unit to be used if the threshold value specified in Step 8 is exceeded.
Important
The alternate unit name must be a valid tape unit name. For more information, see Setting-the-JCL-options-for-tapes.
Specify the SMS definitions for the alternate data set classes:
1. In the Alternate SMS Data Class field, type the name of the data class.
2. In the Alternate SMS Storage Class field, type the name of the storage class.
3. In the Alternate SMS Management Class field, type the name of the management class.
Press END to save your changes and return to the ALTER or BMC AMI Change Manager for Db2 Main Menu.

Additional considerations for permanent data set names

Consider the following items when you specify the prefix for data sets that are dynamically allocated. In addition to any suffixes that JCL Generation appends to the prefix, Analysis can also append suffixes to the prefix.

Analysis appends a period, a two-character abbreviation, and a six-digit number to the prefix to create the name of the data set.

Data set	Prefix
Baseline recovery	&PREFIX..&OBNOD.BLnnnnnn
Discard	&PREFIX..&OBNOD.SDnnnnnn
Local primary copy^{6 7 8}	&PREFIX..&OBNOD.LPnnnnnn
Local backup copy^{7 8}	&PREFIX..&OBNOD.LBnnnnnn
Recovery primary copy^{7 8}	&PREFIX..&OBNOD..P&PART.RPnnnnnn
Recovery backup copy^{7 8}	&PREFIX..&OBNOD..P&PART.RBnnnnnn
EXPORT data set¹	&PREFIX..&WKID.EXnnnnnn
Punch	&PREFIX..&WKID..&STEPN.PUnnnnnn
SYSUT	&PREFIX..&WKID..&STEPN.SUnnnnnn
Primary SYSREC²	&USERID..&MSSID..&WORKID8.SRnnnnnn
LOB SYSREC³	&USERID..&MSSID..&WORKID8.SRnnnnnn
XML file reference⁴	&USERID..&MSSID..&WORKID8.SRnnnnnn.Xnn
LOB file reference⁵	&USERID..&MSSID..&WORKID8.SRnnnnnn.Lnn

^{1 The EXPORT data set is used by the Copy Migration feature of the Recovery Management, BMC AMI Recovery for Db2 , Next Generation Technology Database Administration for DB2 , BMC AMI Database Administration for Db2 , and Database Administration solutions. The Copy Migration feature includes the BMC AMI Copy EXPORT command and BMC AMI Recover IMPORT command.}

^{2 If you are using the UNLOAD PLUS and LOADPLUS utilities to separate data sets for each table space partition and multitask the unloading and loading of data, Analysis also appends the P&PART variable to the prefix to create the name of the primary SYSREC data set (&USERID..&MSSID..&WORKID8.SRnnnnnn.P&PART).}

^{3 For the LOB SYSREC data set (LOBDSN), Analysis also appends .Cnnn to the prefix, where nnn is the number of the LOB column in the table (&USERID..&MSSID..&WORKID8.SRnnnnnn.Cnnn).}

^{4 The file reference data set is used in the SYXCnn OUTPUT descriptor for the BMC UNLOAD PLUS utility and in the SYXCnn TEMPLATE descriptor for the IBM UNLOAD utility. The utilities dynamically allocate the XML file reference data set. Assume that you are using the unload and load utilities to separate data sets for each table space partition and to multitask unloading and loading data. In that case, Analysis also appends the P&PART variable to the prefix to create the name of the primary SYSREC data set (&USERID..&MSSID..&WORKID8.SRnnnnnn.Xnn.P&PART).}

^{5 The file reference data set is used in the SYXBnn OUTPUT descriptor for the BMC UNLOAD PLUS utility and in the SYLBnn TEMPLATE descriptor for the IBM UNLOAD utility. The utilities dynamically allocate the LOB file reference data set. Assume that you are using the unload and load utilities to separate data sets for each table space partition and to multitask unloading and loading data. In that case, Analysis also appends the P&PART variable to the prefix to create the name of the primary SYSREC data set (&USERID..&MSSID..&WORKID8.SRnnnnnn.Lnn.P&PART).}

^{6 For the IBM REORG utility under the following circumstances, Analysis also appends the P&PART variable to the end of the data set name:}

^{You are converting a table space to or performing online schema changes to a partition-by-range table space that uses relative page numbering.}
^{The entire table space, or some of the partitions in the table space, must be reorganized.}

^{The utility requires that the DCPYLOCP TEMPLATE must allocate a separate data set for each partition.
If the P&PART variable is already appended to the data set prefix, you might receive an error because the length of the data set name is too long. To resolve the problem, remove the variable from the data set prefix.}

^{7 For the IBM REORG utility under the following circumstances, Analysis also appends the &SN variable to the end of the data set name. With this variable, IBM REORG generates a copy for each affected table space.}

^{When a base table space for a partition-by-growth table space includes a table with a LOB column and the REORG includes AUX YES}
^{When Analysis uses the ALTER TABLESPACE MOVE TABLE statement to move tables from multi-table spaces to partition-by-growth table spaces}

^{(PTF BQU4259) If the &SN variable is already included in the data set prefix, Analysis does not append the variable to the prefix.}

^{8 If the MOVETB option is enabled, Analysis appends the ".&SN" variable to the end of the data set name in the OUTPUT descriptor for copies in the worklist.}

Important

You must ensure the uniqueness of the name of the data set.

In a worklist, BMC AMI Reorg always dynamically allocates data sets. Analysis adds the following suffixes to image copies that BMC AMI Reorg creates. You can suppress the suffix by specifying *_SUPRESS = Y in the POF.

Nonpartitioned objects without LOBs

Data set	Suffix^{1 2}
Local primary copy	.LPnnnn
Local backup copy	.LBnnnn
Recovery primary copy	.RPnnnn
Recovery backup copy	.RBnnnn

^{1Suppressing the suffix omits .LPnnnn, .LBnnnn, .RPnnnn and .RBnnnn.}

^{2Using the &GDG symbolic variable (Using the &GDG symbolic variable) omits .LPnnnn, .LBnnnn, .RPnnnn and .RBnnnn.}

The following symbolic variables can be added by Analysis:

Symbolic variable	Details
&UNIQ	Resolves to a unique eight-character string
P&PART	Resolves to a number that is from two to five digits long, depending on the length of the partition number
(+1)	Resolves to an eight-character string in the format G000nVooo

Partitioned objects without LOBs

Data set	Suffix ^{1 2}
Local primary copy	.LPnnnn..P&PART
Local backup copy	.LBnnnn..P&PART
Recovery primary copy	.RPnnnn..P&PART
Recovery backup copy	.RBnnnn..P&PART

^{1Suppressing the suffix omits .LPnnnn, .LBnnnn. The P&PART variable element of the suffix is included.}

^{2If you use the &GDG symbolic variable (Using the &GDG symbolic variable), then .LPnnnn, .LBnnnn, .RPnnnn and .RBnnnn are omitted. The P&PART and (+1) symbolic variable are included.}

Nonpartitioned objects with LOBs and AUX YES in reorganization

Data set	Suffix^{1 2}
Local primary copy	.&UNIQ
Local backup copy	.&UNIQ
Recovery primary copy	.&UNIQ
Recovery backup copy	.&UNIQ

^{1The value of *_SUPRESS_SUFF does not affect the suffix.}

^{2When you use the &GDG symbolic variable, the suffix is always .&UNIQ.(+1)}

Partitioned objects with LOBs and AUX YES in reorganization

Data set	Suffix^{1 2}
Local primary copy	.&UNIQ..P&PART
Local backup copy	.&UNIQ..P&PART
Recovery primary copy	.&UNIQ..P&PART
Recovery backup copy	.&UNIQ..P&PART

^{1The value of *_SUPRESS_SUFF does not affect the suffix.}

^{2When you use the &GDG symbolic variable, the suffix is always .&UNIQ..P&PART.(+1)}

Setting the JCL options for permanent data sets

To set the JCL options for permanent data sets

Additional considerations for permanent data set names

On this page