IBM Support

DFHAP0701 0C4 AKEA in OPCITDEX at startup after upgrading to CICS TS 5.3

Question & Answer


Question

Do you know why I would get an abend 0C4 AKEA in exit program OPCITDEX at CICS startup after upgrading my CICS Transaction Server for z/OS (CICS TS) V5.1 region to CICS TS V5.3? When I did a WARM start of CICS TS V5.3, shortly after "Control was given to CICS", the region crashed and captured a dump. These are the messages in the CICS log:

+DFHAP0701 CICSPROD An abend (code 0C4/AKEA) has occurred in exit program OPCITDEX at exit point XTDOUT.
+DFHME0001 CICSPROD An abend (code ---/AKEA) has occurred at offset X'0179E' in module DFHMEME
+DFHDS0001 CICSPROD An abend (code 0C4/AKEX) has occurred at offset X'3200' in module DFHDSTCB.

Looking at the messages from the log, the exit OPCITDEX is listed first with a 0C4/AKEA abend. This exit allows CA Ops/MVS automation from CA Technologies to scan MSGUSR for messages in addition to JESMSGLG.

No changes where made to the exit program OPCITDEX.

Answer

OPCIT* modules are from CA Technologies. The OPCITDEX program is defined to the CICS loader and program domains as OPCITDCN, which is defined as threadsafe. The stub in OPCITDCN indicates it was compiled for CICS TS V5.1, but this dump is for CICS TS V5.3.

I would contact CA Technologies. CA Technologies has a PTF that includes a version of this exit module compiled for CICS TS V5.3. Applying the PTF should resolve the abend 0C4 in OPCITDEX.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Startup","Version":"5.3","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
08 June 2016

UID

dwa1278072