Starting the Db2 subsystem

During the process of adding a data sharing member, start the Db2 subsystem after you define Db2 to z/OS.

To start the Db2 member:

1. Start Db2 from the z/OS® console.
   Use the following command:

   -DSN1 START DB2

   where (-DSN1) is the subsystem command prefix that you defined for Db2.

   Db2 uses the subsystem parameter module that is specified in the start-up JCL procedure in SYS1.PROCLIB:

   //IEFPROC EXEC PGM=DSNYASCP,PARM='ZPARM(DSNZPxxx)', ...

   where DSNZPxxx is the value that you specified for the PARAMETER MODULE field on installation panel DSNTIPO3.

   If you need to change the name of the DSNZPxxx module, you can edit SYS1.PROCLIB. Alternatively, you can override the DSNZPxxx name by using the PARM option as follows:

   -DSN1 START DB2,PARM(DSNZPxxx)

   If you have not run yet job DSNTIJRT on any member of the group, and the administrative task scheduler for this member starts, the administrative task scheduler issues error message DSNA679I to report SQLCODE -805 until you run job DSNTIJRT. The administrative task scheduler starts if you specified an address space procedure name in the ADMIN SCHEDULER field on installation panel DSNTIPX.

   If Db2 starts successfully, two to five address spaces also start. These address spaces are ssnmMSTR and ssnmDBM1, possibly ssnmDIST, possibly ssnmADMT, and irlmproc, where ssnm is the Db2 subsystem name, ssnmADMT is the Db2 administrative task scheduler procedure name, and irlmproc is the IRLM procedure name.

   If Db2 starts successfully, the series of RESTART messages that you receive concludes with these two messages:

   DSNR002I   RESTART COMPLETED
   DSN9022I   DSNYASCP '-DSN1 START DB2' NORMAL COMPLETION

   After you start Db2, identify unusual conditions for databases with the command:

   -DSN1 DISPLAY DATABASE(*) SPACENAM(*) RESTRICT

   If Db2 does not start successfully, it usually abends with a reason code that indicates where the error occurred. To find the error, check the set of definitions for the associated resource. Ensure that the DSNTIJID, DSNTIJIN, and DSNTIJUZ jobs ran correctly. Also, verify that the subsystem parameter member that you specified (or allowed by default) when you started Db2 is the one that is built by job DSNTIJUZ. Check the JCL for the Db2 startup procedure.

   If you use distributed data facility, you must define VTAM® before DDF can start. However, you do not need to have TCP/IP configured to start DDF. In addition, transactions such as those from DDF or CICS® may fail because work files have not yet been defined.

2. Optional: Start TSO.
   After Db2 starts, it is available to TSO. If you want to use the TSO SUBMIT command to do housekeeping and installation verification, you must start TSO (if it is not already started).