Start of change

Converting from using UXTABLE to using the defaults table

The UXTABLE is a table that is created during conversion to DFSMSrmm and is used together with the EDGCVRSX sample for the EDG_EXIT100 installation exit. It functions like the defaults table, and you can move away from using the UXTABLE by converting it to the defaults table. To convert, you need to have the source of the UXTABLE that is used on your system. The following UXTABLE option is not available in the defaults table: ACL1OPT.

Use the EDGJDEF sample JCL, which is available in SYS1.SAMPLIB, to convert the UXTABLE to the defaults table. EDGJDEF expects the UXTABLE source to be specified in the //VRSTABLE DD statement and saves the defaults table to the data set specified in the //EDGDEF DD statement. The EDGJDEF job uses the EDGRDEF script to do the conversion. This script is also located in SYS1.SAMPLIB. The EDGRDEF script expects one parameter, which is the global retention period default on your system. If not changed, this parameter has a value of 5: PARM='%EDGRDEF 5'. See the EDGRDEF script for more information about this parameter. The defaults table is different from the UXTABLE as follows:
  1. Additional options present in the defaults table, missing from UXTABLE:

    CONTINUE, EDM/NOEDM, LASTREF, NOKEYDATE, PGMNAME, RETAINBY, WHILECATALOG

  2. Unlike the UXTABLE, the defaults table allows you to combine selection criteria DSNAME and JOBNAME together with KEYDATE. All entries of the defaults table are processed together, while the UXTABLE processes KEYDATE entries separately from the DSNAME/JOBNAME entries.
  3. The RO(YES) option of the UXTABLE, used to indicate that the retention period or expiration date that is specified in the JCL must be replaced, has the equivalent option OVERRIDE, a subparameter of RETPD, in the defaults table. An example of specifying OVERRIDE is RETPD(50,OVERRIDE). In the defaults table, OVERRIDE must be specified together with a retention period, unlike the UXTABLE where RO(YES) would clear the retention period that is specified in the JCL even if RETPD is not specified in the UXTABLE. Also, in the UXTABLE, KEYDATE entries have RO(YES) implied, which is not the case for the defaults table.
  4. The OVERRIDE option of the defaults table has no effect on the priority of the defaults table entry. This is unlike the UXTABLE, where RO(NO) and RO(YES) are also used to choose between a KEYDATE entry and a DSN/JOBNAME entry, when both match the data set. In the defaults table, the NOKEYDATE parameter can be used instead of RO(NO) to indicate that the current entry is not to be used if there exists a matching KEYDATE entry.
  5. The UXTABLE allows you to combine entries in such a way that a DSN/JOBNAME with RO(NO) is used to make a pooling decision while a KEYDATE entry is used to choose all the remaining retention settings. The same behavior might be achieved in the defaults table by using the CONTINUE keyword. The CONTINUE keyword allows you to make any pooling decisions in the beginning of the defaults table, and if CONTINUE is specified in the entries that choose the POOL. The rest of the defaults table is able to assign any other parameters.
End of change