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. Use the individual data set options panels to specify information about the following permanent work data sets and image copy data sets:

  • Sortout (WORKDDN or LOADDN)
  • Sysut (WORKDDN)
  • Copy (COPYDDN, RECOVERYDDN, RECOVERDDN, ICDDN, RECOVERYICDDN, OUTCOPYDDN, FCOPYDD, or EXPORTDDN)
  • Sysrec (UNLDDN, INDDN, or UNLOADDN)
  • Archive (ARCHDDN)
  • Cntl file (CNTLDDN)
  • (Change Manager only) Baseline recovery
  • Discard (DISCARDDN)
  • Error (ERRDDN)
  • Map (MAPDDN)
  • Report
  • Punch (PUNCHDDN)
  • Filter (FILTERDDN)

The permanent work data sets, which contain data, allow restarts. They are defined by using DISP=(NEW,CATLG) or DISP=SHR for restart or startover JCL. Examples include input (SYSUT), output (SORTOUT), discard (SYSDISC), map (SYSMAP), error (SYSERR), and punch (SYSPUNCH).

Other permanent data sets are used for restart and recover purposes. They use the same dispositions as the permanent work data sets. Examples include unload (SYSREC), copy (SYSCOPY).

The LOB SYSREC data sets is used only by the UNLOAD PLUS utility to unload and load data contained in LOB columns.

The BMC AMI Reorg  product uses only the copy, punch, and discard data sets.

To set the JCL options for permanent data sets

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

    From this menu

    Select this item and press Enter

    DASD MANAGER PLUS Main Menu

    User Options

    User Options

    JCL generation options

    JCL GENERATION UPDATE - MAIN MENU

    Individual Data Set Options

    JCL Generation Individual Data Set Options

    Type of data set (SORTOUT, SYSUT, or COPY)

    Warning

    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 panel

    ----------- 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)
  2. Specify the prefix for the data set.

    Consider the following items when you specify the prefix:

    • JCL Generation automatically 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.

      POF keywords used to suppress the ddname

      Data set

      POF keyword

      (Catalog Manageronly) flashcopy

      FCPY_SUPPRESS_SUFF

      Local primary copy

      PCPY1_SUPPRESS_SUFF

      Local backup copy

      PCPY2_SUPPRESS_SUFF

      Recovery primary copy

      RCPY1_SUPPRESS_SUFF

      Recovery backup copy

      RCPY2_SUPPRESS_SUFF

      Primary SYSREC

      UNLD1_SUPPRESS_SUFF

      Backup SYSREC

      UNLD2_SUPPRESS_SUFF

    • 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

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

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

      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

      1 Suppressing the suffix omits .LP nnnn , .LB nnnn . The P&PART variable element of the suffix is included .

      If you use the &GDG symbolic variable (see below, Using the &GDG symbolic variable ), then .LP nnnn , .LB nnnn , .RP nnnn and .RB nnnn 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

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

      2 When 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

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

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

      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

    • 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 (see below).

      Using the &GDG symbolic variable

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

    Data set names resolved with the &GDG symbolic variable

    //*--------------------------------------------------------------------
    //*  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)
    //*--------------------------------------------------------------------
  3. 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.
    • If you have very large data sets and want to avoid extents or multiple data sets on DASD, specify one of the following:
      • Tape
      • Virtual tape
      • Cartridge unit
    • 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 do the following:

      1. Uncatalog the existing data set
      2. Change the DD statements to a disposition of (NEW,CATLG,CATLG)
      Success

      Tip

      As an alternative to specifying tape for the unit, you can specify a DASD unit that spans multiple data sets, by doing the following:

      1. Return to the JCL Generation Static Data Set Options panel (see the figure in Setting-the-JCL-options-for-static-data-sets)
      2. Specify a value for Max cylinders and a value greater than 1 for Max unit count
      Warning

      Best Practice

      We recommend that you specify SYSDA as 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 Object Administration for DB2 solutions.) If the ROWID SYSREC is set to SYSDA, you can improve the performance of the worklist commands for unloading the ROWID data set when the worklist is run in parallel.

  4. If you typed N in the Data set sizing option field in Step 2 when Setting-the-JCL-options-for-static-data-sets, 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.

  5. In the Tape EXPDT field, type the expiration date for a tape.
  6. In the Tape RETPD field, type the retention date for a tape.
  7. 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.
  8. 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 Creating OUTPUT or TEMPLATE descriptors for copiesandErrorExcerpt named Use of -COPY to dynamically was not found in document xwiki:Mainframe.Data-for-Db2.DASD-MANAGER-PLUS-for-DB2.ASU13100._inclusions_library_dasdmanagerplus._links_DASD.WebHome..

    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.

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

    Warning

    Important

    The alternate unit name must be a valid tape unit name. For more information, see Setting-the-JCL-options-for-tapes.

  10. 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.
  11. Press END to save your changes and return to the DASD MANAGER PLUS Main Menu.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

DASD MANAGER PLUS for DB2 13.1