Tailoring the installation jobs

You might want to tailor several items in the installation jobs, such as data set names or library names, to meet the requirements of your site.

To prepare the installation jobs for your site:

1. Tailor the jobs to suit the needs of your site.
   You should edit the jobs to conform to any unique requirements that you might have. Also, you might want to make any minor JCL changes for items that the ISPF panels did not handle.
2. If you specified volume serial numbers on installation panel DSNTIPA3, examine the volume serial numbers that are used in the various jobs.
   The volume serial number fields of installation panel DSNTIPA3 enable you to specify up to five volumes for the data sets that are defined during installation or migration. If you want to use more than five volumes, specify them before continuing with installation or migration tasks.

   If you specified volume serial numbers on installation panel DSNTIPA3, the DSNTINST CLIST spreads the data sets across these volumes. If you use explicit volume serials instead of SMS, adding more volumes to provide more separation of data sets can help improve system performance and recoverability. Many of the log data sets are large and easy to place on separate volumes. The CLIST produces a series of messages that estimate space for each type of data set that is created during the installation or migration process.

3. Edit the DSNH CLIST if needed.
   The DSNH CLIST allows you to precompile, compile, prelink-edit, link-edit, bind, and run an application by issuing a single command. You might need to edit the DSNH CLIST to change values for some of the entries. Verify that DSNH keyword parameters for all Db2-supported compilers that your applications use.
   1. Check the default data set names for the licensed programs that you have installed.
      These defaults are in the parameter definitions at the beginning of each program. If the names and prefixes are not correct for your site, change them.
   2. Check default library names.
      If the names and prefixes are not correct for your site, change them. Ensure that the data sets exist and are cataloged for BLIB, CLIB, LLIB, and PLIB. When the DSNH CLIST runs, it creates DBRMLIB and LOAD data sets if they do not already exist. The DBRMLIB data set is created only if the DBRMLIB(DEFAULT) is set. The following are the default library names:

      • BLIB(NONE)
      • DBRMLIB(DEFAULT) - The DBRM library must be allocated exclusively when the precompiler writes to it.
        Recommendation: Set up a temporary library, or one per user, rather than trying to share libraries.
      • CLIB(NONE)
      • LLIB(NONE)
      • LOAD(RUNLIB.LOAD) - This library is allocated exclusively when it is being written.
        Recommendation: Set up a temporary library, or one per user, rather than trying to share libraries.
      • PLIB(NONE)
   3. Check default processor options.
      If you prefer other default options, change them. The default processor options follow:

      • CICSOPT(NONE)
      • LOPTION(NONE)
      • COPTION(NONE)
      • PASS(DEFAULT)
   4. Check print and work space defaults.
      If the default allocation sizes are not acceptable for your site, change them. The print and work space defaults follow:

      • PSECSPAC(20)
      • PSPACE(20)
      • WORKUNIT(DEFAULT)
      • WSECSPAC(20)
      • WSPACE(20)
4. Examine the data set names for other products.
   Many data set names for other products appear in the jobs. These names are shown in the table on panel DSNTIPU. Change them if they are different at your site.