How to Define DB2 and Its Accompanying Address Spaces in STCTBL and STCTBL_ACT?

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Properly defining IBM DB2 address spaces in the OPS/MVS System State Manager (SSM) STCTBL and STCTBL_ACT tables ensures that automation does not conflict with DB2's internal management. This article describes the recommended MODE configuration for DB2 Master and dependent tasks.

DB2 is composed of a master started task and some dependent tasks. The names of the tasks are composed by the DB2 subsystem name and a suffix:

ssnmMSTR: System Services address space (sample default: DSN1MSTR)

ssnmDBM1: Database Services address space (sample default: DSN1DBM1)

ssnmDIST: Distributed Data Facility (DDF) address space (sample default: DSN1DIST)

irlmproc: Intersystem Resource Lock Manager procedure (sample default: IRLMPROC)

 

 

Environment

• OPS/MVS Event Management & Automation
• IBM DB2 for z/OS

Resolution

When incorporating DB2 into SSM, only the Master address space should be under direct SSM control. The dependent tasks are managed internally by the DB2 subsystem.

Configure the STCTBL entries as follows:

• ssnmMSTR (Master Task):
  
  
  • Set MODE to ACTIVE.
    
    
  • Map startup and shutdown actions (e.g., SHUTDB2 REXX exec) to this resource in STCTBL_ACT.
    
    
  • SSM manages the DESIRED_STATE for this task.
    
    
• Dependent Tasks (ssnmDBM1, ssnmIRLM, ssnmDIST):
  
  
  • Set MODE to PASSIVE.
    
    
  • In PASSIVE mode, SSM monitors the CURRENT_STATE (UP/DOWN) for visibility in the OPSVIEW panels.
    
    
  • SSM does not issue START or STOP commands for these tasks, as the DB2 Master initiates them internally.