Naming conventions for Db2 library names

You need to modify the Db2 library data set names in the SMP/E jobs.

These data sets are listed in What you produce: Db2 distribution and target libraries. Their names are composed of three parts:

  • A user-defined prefix
  • A fixed base name: for example, SDSNLOAD
  • An optional user-defined suffix

The Db2 13 default prefix (prefix) is used in this information; the default suffix is null. You need to edit each of the Db2 SMP/E jobs and follow the directions in the header notes of each job to specify the names of the SMP/E data sets. If you want to add a suffix, edit the SMP/E procedures and allocation jobs. The prefix cannot exceed 18 characters. The suffix cannot exceed 17 characters, minus the length of the prefix. In addition, any data set names that exceed eight characters must be in groups of no more than eight characters, separated by periods. The qualified data set name cannot exceed 44 characters.

You can also change the base name of these libraries or load them into another data set. If you do this, however, you might need to do additional editing of the installation or migration jobs.

The DSNTINST CLIST, which you use later to tailor the installation and migration jobs, uses the following default data set names:

  • prefix.SDSNCLST
  • prefix.SDSNEXIT
  • prefix.SDSNLINK
  • prefix.SDSNLOAD
  • prefix.SDSNMACS
  • prefix.SDSNDBRM
  • prefix.SDXRRESL
  • prefix.SDSNSAMP
  • prefix.DBRMLIB.DATA
  • prefix.RUNLIB.LOAD
  • prefix.SRCLIB.DATA
  • prefix.SDSNIVPD
  • prefix.SDSNC.H

For best results, use the supplied naming convention, and be sure to document any changes that you make to the library names in the SMP/E jobs. You must specify these library names again during the ISPF tailoring session.

Remember: If you copy Db2 library data sets from one system to another, such as for installing a related test or production subsystem, ensure that you copy all of the Db2 library data sets to the same location. For example, if you copy the SDNSLOAD data set from one system to another but omit the DBRMLIB data set, the resulting mismatch can cause job DSNTIJRT to fail with SQLCODE -812.