Specifying naming conventions

You can set up Db2 Admin Tool to use your local naming conventions for items such as data sets, utility IDs (UIDs), and plan names. The default settings are provided in skeleton ADB2UCUU. Update skeleton member SADBSLIB(ADB2UCUS) to override any of the variable default settings in SADBSLIB(ADB2UCUU) to site-specific standards. Do not update SADBSLIB(ADB2UCUU).

Review SADBSLIB(ADB2UCUU) and use skeleton member SADBSLIB(ADB2UCUS) to override any variable default settings to site-specific standards. Over 250 variable settings are provided. Each variable setting is documented in member ADB2UCUU. For example, you can set the default plan name for sample programs DSNTIAD and DSNTIAUL.

To customize these values, modify the ADBU002 usermod, which resides in the SADBSAMP library. Copy the desired lines from the ADB2UCUU skeleton to the ADBU002 usermod and modify as needed. All customization in skeleton ADB2UCUS should be done after it imbeds skeleton ADB2UCUU, unless otherwise noted.

When you subsequently run SMP/E to receive and apply SMP/E usermod ADBU002, the updated ISPF JCL skeletons are added to the SADBSLIB library.

The following list includes some of the variables that you can use in the specified naming conventions. For a complete list of variables, see skeleton member ADB2UCUT.

Variable:

Description:

&AJDATE

Julian date (YYDDD)

&AJDAY

Julian day (DDD)

&AYEAR4

4-digit year (YYYY)

&AGDATE

Gregorian date (YYMMDD)

&ANMON

Numeric month (MM)

&ADAY

Day (DD)

&AYEAR

2-digit year (YY)

&ACMON

3-character month (XXX)

&ATIME

Time (HHMMSS)

&ATIME7

Time with tenths of seconds (HHMMSST)

&ATIME4

Time without seconds (HHMM)

&AHOUR

Hour (HH)

&AMIN

Minute (MM)

&ASEC

Seconds (SS)

All lines that might require tailoring are preceded by SET statements (indicated by )SET).

Example: This example demonstrates several different types of data set naming changes using the variable ASYCPY1:

The variable ASYCPY1 is shipped as:

)SET ASYCPY1 = &PREFIX..&DB2SYS..IC.&DBNAME..&NAME.(+1)

To change the high-level qualifier from the current TSO PREFIX to MYHLQ, specify:

)SET ASYCPY1 = MYHLQ.&DB2SYS..IC.&DBNAME..&NAME.(+1) /* CHANGE HLQ TO FIXED STRING

To change the second-level qualifier from the Db2 subsystem ID to TEST, specify:

)SET ASYCPY1 = &PREFIX..TEST.IC.&DBNAME..&NAME.(+1)  /* CHANGE SUBSYSTEM TO 'TEST'

To insert a high-level qualifier of MYHLQ in front of the current TSO PREFIX and to remove the Db2 database name, specify:

)SET ASYCPY1 = MYHLQ.&PREFIX..&DB2SYS..IC.&NAME.(+1) 
               /* CHANGE HLQ TO FIXED STRING, 
               /* INCLUDE PREFIX, REMOVE DBNAME

To use sequential data sets rather than a GDG data set, specify a data set name that contains date and time values to generate unique data set names:

)SET ASYCPY1 = &PREFIX..IC.&DBNAME..&NAME..D&AJDATE..T&ATIME

Example: This example demonstrates several different types of utility ID (UID) naming changes using the variables PREFXUID, LOADUID, and UNLODUID.

The variables PREFXUID, LOADUID, and UNLODUID are included as:

)SET PREFXUID = &Z
)SET LOADUID = &PREFXUID
)SET UNLODUID = &PREFXUID

To change the LOAD and UNLOAD UIDs such that they contain the TSO user ID, a time stamp, and a utility type identifier, specify:

)SET PREFXUID = &ZUSER.&ATIME
)SET LOADUID = &PREFXUID.LD
)SET UNLODUID = &PREFXUID.UL

This specification sets the value of LOADUID to &ZUSER.&ATIME.LD and UNLODUID to &ZUSER.&ATIME.UL. So, if the user ID is 'JOE' and the JCL for the LOAD utility is generated at time '095344', the UID in the JCL for the LOAD utility is set to 'JOE095344LD'.

The maximum size of &ZUSER is 8 bytes, the size of &ATIME (HHMMSS) is 6 bytes, and the size of the literal is 2 bytes. The total maximum size is 16 bytes, which is the maximum UID size.

To change the LOAD and UNLOAD UIDs such that they contain the TSO user ID and a time stamp with tenths of seconds (USERID.HHMMSST), specify:

)SET PREFXUID = &ZUSER..&ATIME7
)SET LOADUID = &PREFXUID
)SET UNLODUID = &PREFXUID

This specification sets the value of LOADUID and UNLODUID to &ZUSER..&ATIME7. So, if the user ID is 'JOE' and the JCL for the LOAD utility is generated at time '0953446', the UID in the JCL for the LOAD utility is set to 'JOE.0953446'.

The maximum size of &ZUSER is 8 bytes, the size of a period is 1 byte, and the size of the &TIME7 (HHMMSST) is 7 bytes. The total maximum size is 16 bytes, which is the maximum UID size.

For testing purposes, copy the ADB2UCUS skeleton to a private skeleton library and make your changes. This private skeleton library must first be allocated in the ISPSLIB concatenation (using the USERADD parameter of the ADBL CLIST).

After testing is complete, you can use an SMP/E USERMOD to update the Db2 Admin Tool product libraries. A sample SMP/E USERMOD is provided in member ADBU002 in the SADBSAMP library. Instructions for completing this step are provided in sample job ADBU002.