TDQs do not automatically register in COF after OPS/MVS restart

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

When configuring the CICS Operations Facility (COF) for persistence in OPS/MVS, Transient Data Queues (TDQs) fail to register automatically following an OPS/MVS restart. 

• Manual registration via 'ADDRESS OPSCTL' works successfully.
• Parameters 'INITCOF YES' and 'CICSAOF YES' are set in 'OPSSPA00'.
• The `ADDRESS OPSCTL "COF DEFINE..."` command is present in 'OPSSPA00' but does not result in registered queues.
• OPSLOG may show message: 'OPS4600I ADDRESS OPSCTL COMMAND REJECTED - SUBSYSTEM OPSS IS NOT ACTIVE'.

 

Environment

OPS/MVS Event Management & Automation 14.0 and above.
CICS Transaction Server.

Cause

The issue is caused by a timing conflict during the OPS/MVS startup sequence. The `OPSSPA00` member is processed very early in the initialization phase, before the OPS/MVS subsystem (SS) is fully active. Because the `ADDRESS OPSCTL` host command environment requires an active subsystem, any COF or MSF definition commands issued within `OPSSPA00` are rejected.

Resolution

To ensure persistent and automatic registration, move the COF definition statements from the parameter initialization member to the startup REXX program that executes after subsystem initialization.

1. **Modify OPSSPA00:**
      Ensure the following parameters are set to enable the interfaces, but remove any `ADDRESS OPSCTL` commands:
   
      T = OPSPRM_Set("INITCOF","YES")
      T = OPSPRM_Set("CICSAOF","YES")
      ```
2. **Update OPSTART2:**
      Add your COF definition statements to the 'OPSTART2' REXX program. 'OPSTART2' is the first OSF transaction executed once the subsystem is fully initialized. 
      Example:
   
      /* Define COF TDQs for automation */
      address OPSCTL "COF DEFINE JOBNAME(DEFAULT) DESTIDS(CSMT,CSSL)"
      ```
      *Note: If you do not have a customized 'OPSTART2', copy the sample from the `CCLXSAMP` library to your user REXX library before editing.*
3. **Automate CICS Enablement:**
      To ensure the COF interface is enabled automatically when CICS regions start, add the program 'OPCITDCN' to the CICS Post Initialization Program List Table (PLTPI) at Stage 3.
4. **Verification:**
      After restarting OPS/MVS, verify the registration using OPSVIEW option 4.11 (COF Display) to confirm the DestIDs are active and associated with the expected jobnames.