Preparing a second Db2 subsystem for use

After you have installed a second Db2 subsystem on the same operating system, you must run some jobs that prepare the subsystem for use.

Procedure

To prepare your second Db2 subsystem for use:

  1. IPL z/OS®.
    This step is required for any SYS1.PARMLIB changes. Alternatively, you can use the SETSSI, SETPROG APF, and SETPROG LNKLST commands to define the subsystem to z/OS until the next IPL.
  2. Start Db2 by using the new command prefix (formerly called the subsystem recognition character) that you named during the installation process.
  3. Run job DSNTIJTC.
  4. Run job DSNTIJTM.
    If you use the same library prefix for both subsystems, change the name of the data sets listed below, unless you do not need them on the first subsystem. Subsequent jobs write information in these data sets and prevent use of the new load module DSNTIAD on the second subsystem with the previously bound plan DSNTIA91 on the first subsystem.
    • prefix.DBRMLIB.DATA
    • prefix.RUNLIB.LOAD
  5. Run job DSNTIJSG.
  6. Optional: Run job DSNTIJRW to define core WLM environments for Db2-supplied stored procedures and user-defined functions.
  7. Run job DSNTIJRT to install all Db2-supplied routines.
  8. Run job DSNTIJRV to validate the Db2-supplied routines after they have been installed.
  9. Optional: Run job DSNTIJIC to copy the catalog.
  10. Verify your installation process.
    See Verifying your installation process for a second Db2 subsystem for more information.