COF in OPSMVS upgrade from 13.5 to 14.0

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

We are using COF( CICS Operational Facility ) as part of OPS/MVS 13.5 .

While upgrading OPS/MVS from 13.5 to 14.0, should we follow any additional steps apart from below notes :

1.Copy load module OPCITDCN from <hlq>.OPS.CCLXLOAD to a library in the CICS DFHRPL concatenation.
The module is linked AMODE=31 and RMODE=ANY.

2. Define the transaction and program to CICS using the CICS RDO facility:
DEFINE GROUP(OPXTDOUT) PROGRAM(OPCITDCN)
DATALOCATION(ANY) EXECKEY(CICS)
LANGUAGE(ASSEMBLER) RESIDENT(YES)
DESCRIPTION(OPS/MVS XTDOUT GLOBAL EXIT)
DEFINE GROUP(OPXTDOUT) TRANSID(OPTD) PROGRAM(OPCITDCN)
TASKDATAKEY(CICS) TASKDATALOC(ANY)
DESCRIPTION(OPS/MVS XTDOUT EXIT CONTROL)
INSTALL GROUP(OPXTDOUT)
ADD GROUP(OPXTDOUT) LIST(DFHLIST)
The XTDOUT exit code is contained in the OPCITDCN program, and it is enabled as an entry point address in this
module using the name OPCITDEX. The exit program does not need to be defined to CICS.
3. Enable the XTDOUT exit by invoking OPTD from a CICS terminal or with a MODIFY command from a z/OS console.
OPCITDCN may be added to the CICS PLTPI stage 3 for automatic exit enablement at CICS initialization when
desired.

 

Environment

Release : 14.0

Resolution

As you already has this interface working with OPS 13.5 you don't need to redo the CICS definitions.

You can just execute the step 1 of the instructions so that you have the new version of the module OPCITDCN.