Generating tailored installation, migration, or function level activation jobs by running the Db2 installation CLIST in interactive mode

The Db2 installation CLIST displays a series of ISPF panels that prompt you to supply parameter values or accept the supplied default values. In most cases, the fields on the ISPF panels correspond with Db2 subsystem parameters.

Before you begin

You must use SMP/E to load the required Db2 13 libraries, as described in Making the Db2 product code available. At minimum, generating Db2 installation, migration, or function level activation jobs requires the following Db2 load libraries:
  • prefix.SDSNCLST
  • prefix.SDSNSPFM
  • prefix.SDSNSPFP
  • prefix.SDSNSAMP
  • prefix.SDSNIVPD (only if generating z/OSMF artifacts)
Tip: Start of changeIf you are preparing to migrate to Db2 13 or to activate a Db2 function level, you can avoid working through the Db2 installation CLIST panels in interactive mode by running a batch job with valid input files to generate required JCL jobs and other artifacts with a background process. See Generating tailored Db2 migration or function level activation jobs in the background.End of change

About this task

The values that you enter or accept on the ISPF panels describe the operating characteristics of your Db2 system. If you change the default values when you install Db2 or when you migrate to a newer release, the CLIST verifies that the values that you enter are within the allowable ranges.

The Db2 installation CLIST allocates several data sets for input and output. From your TSO user ID, you should be able to allocate these data sets to the permanent or temporary unit names that are provided on installation panel DSNTIPA2. These devices can be defined by an esoteric device group.

The values that you specify configure the subsystem parameter module and application defaults load module for the Db2 subsystem.

Subsystem parameter module
The subsystem parameter module is generated by job DSNTIJUZ each time that you install, migrate, or update Db2. Six macros expand to form this data-only subsystem parameter load module. The load module contains the Db2execution-time parameters that you selected using the ISPF panels. These six macros are DSN6ARVP, DSN6FAC, DSN6LOGP, DSN6SPRM, DSN6SYSP, and DSN6GRP. By default, this load module has the name that you specify in the PARAMETER MODULE field in panel DSNTIPO3. For more information, see PARAMETER MODULE field.
Application defaults load module
The application defaults load module, sometimes called the DSNHDECP, is generated by job DSNTIJUA. This module contains the application programming defaults. By default, this load module has the name that you specify in the APPL DEFAULTS field of installation panel DSNTIPO3. For more information, see APPL DEFAULTS field.

Running the Db2 installation CLIST also prepares the jobs that are required for installation, migration, or function level activation. The CLIST tailors each installation or migration job according to the values that you specify on the ISPF panels.

After a successful installation or migration, you can also update these values later to improve your operations. For more information, see Updating subsystem parameter and application default values.

Tip: You can capture most settings of an existing Db2 subsystem by running the DSNTIJXZ job, which invokes the DSNTXAZP tool. Running this job reduces the effort to manually compare settings in the current DSNTIJUZ job with the values that are defined in the defaults input member. For details, see Updating the CLIST defaults input member: job DSNTIJXZ and DSNTXAZP tool.
Important: If you use the Db2 installation CLIST, do not change any members in your prefix.SDSNSAMP library. If you do, the Db2 installation CLIST can fail or produce unpredictable results when tailoring the installation or migration jobs.

Procedure

To tailor Db2 13 installation and migration jobs, complete the following steps:

  1. Make the Db2 ISPF libraries available to TSO by taking one of the following actions:
    • To prepare for running only the Db2 installation CLIST, issue the following commands:
      PROFILE WTP MSGID
      ALLOCATE DDNAME(SYSEXEC) DSN('prefix.SDSNCLST') SHR REUSE
      ALLOCATE DDNAME(ISPMLIB) DSN('prefix.SDSNSPFM' + 
          'ISP.SISPMENU') SHR REUSE
      ALLOCATE DDNAME(ISPPLIB) DSN('prefix.SDSNSPFP' + 
          'ISP.SISPPENU') SHR REUSE
      
    • To prepare for running the Db2 installation CLIST and the Db2 Interactive (DB2I) facility, issue the following commands. If you use Kanji DB2I panels, concatenate SDSNPFPK to ISPPLIB instead of SDSNPFPE.
      PROFILE WTP MSGID 
      ALLOCATE DDNAME(SYSPROC) DSN('prefix.SDSNCLST') SHR REUSE
      ALLOCATE DDNAME(ISPMLIB) DSN('prefix.SDSNSPFM' + 
          'ISP.SISPMENU') SHR REUSE 
      ALLOCATE DDNAME(ISPPLIB) DSN('prefix.SDSNSPFP' 'prefix.SDSNPFPE' + 
          'ISP.SISPPENU') SHR REUSE 
      ALLOCATE DDNAME(ISPSLIB) DSN('prefix.SDSNSPFS' + 
          'ISP.SISPSLIB' 'ISP.SISPSENU') SHR REUSE 
      

    The PROFILE command provides complete error messages.

    The ALLOCATE command uses the default names of the libraries that contain the ISPF panels. These ISPF library names might be different at your site. To concatenate or merge existing libraries with them, put the library names in the list of names in parentheses after DSN with the largest block size first. (If two or more libraries have the same block size, you can list either one first.)

  2. If you are running the Db2 installation CLIST to migrate to Db2 13 update an existing Db2 13 subsystem, or install a new Db2 13 based on the settings of existing installation, configure and run job DSNTIJXZ to update the defaults input member. For details, see Updating the CLIST defaults input member: job DSNTIJXZ .
  3. If your z/OS system has multiple procedure libraries, ensure that the installation jobs access the appropriate set of procedures by specifying the order in which procedure libraries are searched. You can use the following JCLLIB statement to specify the order in which procedure libraries are searched.
    //ddname JCLLIB ORDER=(library[,library...])
    The JCLLIB statement must follow the JOB statement and precede the first EXEC statement in the job. You can have Db2 insert this statement in your JCL for you by entering the statement on installation panel DSNTIPY. For more information on the JCLLIB statement, see JCLLIB statement .
  4. Establish system affinity to ensure that the installation jobs run on the z/OS system where the appropriate Db2 subsystem is running. The following methods are examples of several z/OS installation-specific methods for establishing system affinity:
    • For JES2 multi-access spool (MAS) systems, use the following JCL statement:
      /*JOBPARM SYSAFF=cccc

      Where cccc is the JES2 name. You can specify an asterisk (SYSAFF=*) to indicate that the job should run on the system from which it was submitted.

    • For JES3 systems, use the following JCL statement:
      //*MAIN SYSTEM=(main-name)

      The main-name is the JES3 name.

    You can edit the jobs manually, or you can enter the preceding statements on installation panel DSNTIPY and have Db2 insert these statements for you. For more information, see JES2 Control Statements (MVS JCL Reference) and JES3 Control Statements (MVS JCL Reference).

  5. Invoke the CLIST:
    1. Check that your TSO logon region size is sufficient.
      Usually 2 MB is enough.
    2. Invoke ISPF.
    3. Select option 6 on the main ISPF panel.
    4. Run the Db2 installation CLIST by entering one of the following specifications:
      • EXEC 'prefix.SDSNCLST(DSNTINST)' 
      • If you want to receive the messages that trace the progress of the CLIST, use the following specification:
        EXEC 'prefix.SDSNCLST(DSNTINST)' 'CONTROL(LIST)'
      • If you want to use the CLIST but skip the verification of output data sets, use the following specification:
        EXEC 'prefix.SDSNCLST(DSNTINST)' 'CHKOUTDS(NO)'
        By default, the CLIST verifies the following information when installation panels DSNTIPT and DSNTIPA1 are displayed:
        • The CLIST verifies that the TEMP CLIST LIBRARY and SAMPLE LIBRARY that you specify on DSNTIPT can be allocated and opened for output.
        • If you specify a value for OUTPUT MEMBER NAME on DSNTIPA1, the CLIST verifies that the data set prefix.SDSNSAMP can be allocated and opened for output.
    The CLIST reads a set of default values and displays them on the panels. The values can be the original default values that are supplied by IBM®, values that you specified in a previous run of the CLIST, or values that were generated when you ran the DSNTXAZP tool.
  6. Use the CLIST panels to verify or adjust the values in the panel fields.
    For instructions for working with CLIST panels and descriptions of the panels and fields, see The Db2 installation CLIST panel session.
    Tip: You can save your progress as you work through the CLIST panel session. To save your changes at any point during the panel session, enter the SAVE command, and select option 1 in panel DSNTIPSV. The changes are saved in the output member that is specified in the OUTPUT MEMBER NAME field on panel DSNTIPA1. You can continue working after you save, and if you decide to quit or an error occurs, you can use the output member when you restart the panel session.
  7. On the last panel that displays, CLIST calculations (DSNTIPC1 for installation or DSNTIPC for migration), press Enter to complete the CLIST processing.
    A series of messages provide details about the CLIST processing:
    1. DSNT478I BEGINNING EDITED DATA SET OUTPUT
    2. If the CLIST detects a problem when it checks the parameter values that you entered, you receive an error or warning message indicating the name of the parameter and the type of problem.
      • If you receive an error message, the CLIST cannot edit the installation or migration jobs properly.
      • If you receive a warning message, check the conditions. A warning message can sometimes be issued even when the conditions are normal or acceptable.
      • If you specify several large numbers in the panels, the CLIST might send a message indicating an overflow in CLIST arithmetic.

      The CLIST displays the Main Panel again. You can proceed through the panels, rechecking or changing parameter values.

    3. If the CLIST does not find any errors, you receive messages on DSNTIPC1 that indicate the amount of required disk storage and virtual storage.
    4. You might also receive some other information messages. For example, if you specified an existing data set for the TEMP CLIST LIBRARY field or the SAMPLE LIBRARY field on panel DSNTIPT, the following message is displayed:
      WARNING(S) ISSUED

Results

The Db2 installation CLIST tailors each installation or migration job according to the panel values that you specified. For a list of the tailored jobs, see Installation and migration jobs that the CLIST tailors. These jobs and other output from the CLIST panel session are stored in several output data sets. For more information, see CLIST panel session output.

For each edited job, you receive the following message:

 DSNT489I CLIST EDITING dsname(member), explanation
Important:

If an error occurs when the Db2 installation CLIST edits your jobs, you receive the following message:

IKJ52506I TEXT NOT FOUND

Enter END NOSAVE to prevent modification of the original copies of your installation or migration jobs.

You can rerun the CLIST with the trace control parameter set to CONTROL(SYMLIST) to learn what caused the problem. In some cases, specifying CONTROL(LIST) as the trace control parameter may provide enough information for you to find the source of the problem.

After the CLIST finishes tailoring the jobs, it displays the Main Panel (DSNTIPA1) again. If you need to continue your tailoring at another time, conclude this session. Then, when you start a new session, use the value that you specified for OUTPUT MEMBER NAME during this session as the value for INPUT MEMBER NAME during the new session. Enter these values on the Main Panel.

What to do next

If you are installing Db2, you might need to tailor several items in the installation jobs, such as data set names or library names, to meet the requirements of your site. For more information see Tailoring the installation jobs.

You can use the generated JCL jobs and input files to complete the following activities: