Starting Db2
You must start Db2 to make it active and available to Db2 subsystem is active and available to TSO applications, and other subsystems such as IMS and CICS.
Before you begin
Important: Do not attempt to start Db2 at a code level that is lower than the catalog level or highest ever activated function level. For more information, see Function levels and related levels in Db2 13.
About this task
When Db2 is installed, it is defined as a formal z/OS subsystem. Afterward, the following message appears during any IPL of z/OS:
DSN3100I - DSN3UR00 - SUBSYSTEM ssnm READY FOR -START COMMAND
where ssnm is the Db2 subsystem name.
Procedure
To start a Db2 subsystem:
Issue the START DB2 command by using one of the following methods:
- Issue the START DB2 command from a z/OS console that is authorized to issue system
control commands (z/OS command group
SYS).
The command must be entered from the authorized console and cannot be submitted through JES or TSO.
Starting Db2 by a JES batch job or a z/OS START command is impossible. The attempt is likely to start an address space for Db2 that will abend (most likely with reason code X'00E8000F').
- Start Db2 from an APF-authorized program by passing a START DB2 command to the MGCRE (SVC 34) z/OS service.