Migration step 17: Start DB2 10

During migration to DB2® 10, start the DB2 subsystem after you run job DSNTIJMV and IPL z/OS®.

Procedure

To start DB2:

  1. Start the IRLM. If you have not requested that DB2 automatically start the IRLM, you should start it before you start DB2. Use the following command, where irlmproc is the name that you assigned to the IRLM startup procedure:
    START irlmproc
    The irlmproc is the value that you specified for the PROC NAME option on installation panel DSNTIPI.

    If you specified YES for the AUTO START option on installation panel DSNTIPI, DB2 starts the IRLM automatically.

  2. Start DB2 from the z/OS console with the following command, where -DSN1 is the subsystem command prefix that you defined for DB2, and DSNZPxxx is the name of the DB2 initialization parameter module: 
    -DSN1 START DB2 PARM(DSNZPxxx)
    Start of changeIf you omit the PARM parameter, and you specified a value in the PARAMETER MODULE field on installation panel DSNTIPO3, that value is used as the parameter module name. If you did not specify a parameter module on panel DSNTIPO3, DB2 uses the default, DSNZPARM.End of change

    Start of changeIf you have not run job DSNTIJRT, and the administrative task scheduler 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.End of change

    Start of changeIf 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.End of change

    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

    In the next migration step, you migrate the DB2 catalog. Before the catalog is migrated, some catalog or directory table spaces are restricted.

    The following messages might occur during startup of DB2 because the catalog and directory table spaces are restricted:

    • DSNT501I with reason code 00C900A6
    • DSNL700I with reason code 00C900A6 (if DDF is auto-started)
    • Abend 04E with reason code 00E70014 (during DDL registration)

    These restrictions can cause failure of processes that are started as part of normal DB2 startup, such as collection of real-time statistics, until catalog tailoring is completed. Possible actions to restart such processes are explained in the discussion of job DSNTIJTC.

    You can determine existing restrictions by issuing this command after you start DB2: 
    -DSN1 DISPLAY DATABASE(*) SPACENAM(*) RESTRICT

    The preceding command might also generate message DSNT501I with reason code 00C900A6.

    If DB2 does not start properly, 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. A common cause of startup failure is that the BSDS does not match the subsystem parameter values; ensure that the correct job was run for DSNTIJUZ. Also, check that the subsystem parameter member that you specified (or used by default) when you started DB2 is the one that the DSNTIJUZ job built. Check the JCL for the DB2 startup procedure.

  3. If you want to use the TSO SUBMIT command to do housekeeping and migration verification, start TSO (if it is not already started).
  4. If you did not enable primary user IDs to issue DB2 commands from the z/OS console or TSO SDSF when you first installed the subsystem, take one of the following actions:
    • Grant SYSOPR authority to all primary user IDs that issue DB2 commands from the z/OS console or TSO SDSF. Issue the following command: 
      GRANT SYSOPR TO userid
    • Define RACF® classes to authorize DB2 commands. Use the following statements: 
      SETR CLASSACT(DSNADM)
RDEFINE DSNADM DSN1.SYSOPR UACC(NONE)                        
SETR RACLIST(DSNADM) REFRESH
PERMIT DSN1.SYSOPR CLASS(DSNADM) ID(userid) ACCESS(READ)    
SETR RACLIST(DSNADM) REFRESH