-START DB2 (DB2)

The DB2® command START DB2 initializes the DB2 subsystem. When the operation is complete, the DB2 subsystem is active and available to TSO applications and to other subsystems (for example, IMS™ and CICS®).

The effect of restarting the system can be controlled by a conditional restart control record, which you create by using the DSNJU003 (change log inventory) utility. For more details about the effects, see Usage notes.

Abbreviation: -STA DB2

Environment

This command can be issued only from a z/OS® console. The name of the DB2 subsystem is determined by the command prefix. For example, -START indicates that the DB2 subsystem to be started is the one with '-' as the command prefix.

The command is rejected if the DB2 subsystem is already active. The restart recovery status of DB2 resources is determined from the prior DB2 shutdown status.

Data sharing scope: Member

Authorization

None is required. However, the command can be executed only from a z/OS console with the START command capability.

Syntax

>>-START DB2--+-------------------------+----------------------->
              '-PARM(---module name---)-'   

>--+-----------------------+--+---------------------+----------->
   |       .-DSNCDECP--.   |  |         .-*-----.   |   
   '-DECP(-+-----------+-)-'  '-ACCESS(-+-------+-)-'   
           '-decp-name-'                '-MAINT-'       

>--+-------------------------+--+------------------------+------>
   |        .-NO---------.   |  '-MSTR(jcl-substitution)-'   
   '-LIGHT(-+------------+-)-'                               
            +-YES--------+                                   
            '-NOINDOUBTS-'                                   

>--+------------------------+--+------------------------+------><
   '-DBM1(jcl-substitution)-'  '-DIST(jcl-substitution)-'   

Option descriptions

None of the following options are required.
PARM ( module-name )
Specifies the load module that contains the DB2 subsystem parameters.

The default is the name of the parameter module that was specified on panel DSNTIPO when the installation CLIST was run. The default can also be changed if you update ZPARM(default-module-name) in the ssnmMSTR DB2 subsystem startup procedure.

Start of changeDECPEnd of change
Start of changeStart of changeSpecifies the name of the load module that contains DB2 application parameter defaults.

decp-name is the name of a module that is provided by the installation. The default name is DSNHDECP. If the specified module is not found or cannot be loaded, an error is issued, and the DB2 subsystem does not start.

End of changeEnd of change
ACCESS
Specifies whether access to DB2 is to be general or restricted.
Abbreviation: ACC
(*)
Makes access general; all authorized users can connect to DB2.

The default is ACCESS( * ).

(MAINT)
Start of changeProhibits access to any authorization IDs other than installation SYSADM, installation SYSOPR, and SECADM. End of change

For data sharing, ACCESS(MAINT) restricts access on only the DB2 member on which you execute this command. Other members of the data sharing group are unaffected.

LIGHT
Specifies whether a light restart is to be performed in a data sharing environment.
(NO)
A light restart is not performed.
(YES)
Specifies that a light restart is to be performed. DB2 starts with reduced storage, waits for resolution of indoubt units of recovery, and terminates normally after freeing retained locks.
(NOINDOUBTS)
Start of changeSpecifies that DB2, during a light restart, does not wait for indoubt units of recovery to resolve before it terminates.End of change
MSTR ( jcl-substitution )
Gives parameters and values to be substituted in the EXEC statement of the JCL that executes the startup procedure for the system services address space.
DBM1 ( jcl-substitution )
Gives parameters and values to be substituted in the EXEC statement of the JCL that executes the startup procedure for the database services address space.
DIST ( jcl-substitution )
Gives parameters and values to be substituted in the EXEC statement of the JCL that executes the startup procedure for the distributed services address space.
( jcl-substitution )
One or more character strings of the form keyword = value , enclosed between apostrophes. If you use more than one character string, separate each string with a comma and enclose the entire list between a single pair of apostrophes.

Recommendation: Omit the keyword and use the parameters that are provided in the startup procedure.

Usage notes

Command prefix: If your installation has more than one DB2 subsystem, you must define more than one command prefix.

Conditional restart: A conditional restart control record can prevent a complete restart and specify current status rebuild only. In that case, the following actions occur during restart:
  • Log records are processed to the extent that is determined by the conditional restart control record.
  • The following values are displayed:
    • The relative byte address (RBA) of the start of the active log
    • The RBA of the checkpoint record
    • The status counts for units of recovery
    • The display table for restart unit of work elements
  • The restart operation terminates with an abend.

Light restart with ARM: To enable a light restart in an ARM environment, you must code an ARM policy for DB2 and IRLM.

The following example shows an ARM policy for DB2, where the element name is the DB2 data sharing group name and member name concatenated. For example, DSNDB0GDB1G.
ELEMENT(elementname)

   RESTART_METHOD(SYSTERM,STC,'cmdprfx STA DB2,LIGHT(YES)')
The following example shows an ARM policy for IRLM, where the element name is the IRLM group name and the ID concatenated. For example, DXRDB0GDJ1G001.
ELEMENT(elementname)

   RESTART_METHOD(SYSTERM,STC,'cmdprfx S irlmproc')

The element name that DB2 uses is the DB2 data sharing group name and member name concatenated. For example, DSNDB0GDB1G.F

Endless wait during start: The start operation might begin and fail to complete, if the system services address space starts and the database services address space cannot start. If a seemingly endless wait occurs, cancel the system services address space from the console, and check both startup procedures for JCL errors.

Starting members of a data sharing group: To start members of a data sharing group, you must enter a START DB2 command for each subsystem in the group. If it is the first startup of the group, you must start the originating member (the first DB2 that was installed) first.

Examples

Example 1: Start the DB2 subsystem.
-START DB2
Example 2: Start the DB2 subsystem, and provide a new value for the REGION parameter in the startup procedure for the system services address space.
-START DB2 MSTR('REGION=6000K')
Example 3: Start the DB2 subsystem. Assuming that the EXEC statement of the JCL that executes the startup procedure for the system services address space uses the symbol RGN, provide a value for that symbol.
-START DB2 MSTR('RGN=6000K')
Example 4: DB2 subsystems DB1G and DB2G are members of a data sharing group. Both were installed with a command prefix scope of STARTED. Start DB1G and DB2G by routing the appropriate commands to the z/OS system on which they are to be started, MVS1 and MVS2.
ROUTE MVS1,-DB1G START DB2
ROUTE MVS2,-DB2G START DB2
Start of changeExample 5: Start the DB2 subsystem, then provide the parameter module and a value for the DECP option. Enter either DSNCDECP or another decp-name
 -START DB2 PARM(VA1AZNS) DECP(DSNHDVA1)
End of change