OPS/MVS Message OPS0041H OPS4600I ADDRESS OPSCTL COMMAND REJECTED - SUBSYSTEM OPSS IS NOT  ACTIVE. When setting up CICS Interface

book

Article ID: 209334

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

Setting up the OPS/MVS CICS Interface, following the instructions in the CA OPS/MVS EVENT MANAGEMENT AND AUTOMATION 14.0 documentation, section Integrating with CICS:

 

Activate the AOF processing of CICS messages by setting the INITCOF and CICSAOF parameters to YES and define, at the least, the default transient data queue name list.

 

X = OPSPRM('SET','INITCOF','YES')

X = OPSPRM('SET','CICSAOF','YES')

ADDRESS OPSCTL "COF DEFINE JOBNAME(DEFAULT)",

     "DESTIDS(CSMT,CSSL,CADL,...)"

 

The first 2 lines work but the OPSCTL gives error

OPS0041H OPS4600I ADDRESS OPSCTL COMMAND REJECTED - SUBSYSTEM OPSS IS NOT  ACTIVE

 

Have added the lines to SYS8.OPSMVS.MVSX.USER.CLIST(OPSSPA00)

Environment

Release : 14.0

Component : OPS/MVS

Resolution

The ADDRESS OPSCTL commands for the COF must be included in the OPSTART2 REXX. OPSTART2 is the default value of the the BEGINCMD parameter that indicates the name of a REXX program to be executed when the OSF servers are available.

https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/reference-information/parameter-reference/parameters-for-facilities/osf-parameters.html#concept.dita_170ffc54c774cb78ecb1e992b38e6afbec696df8_BEGINCMDParameter