IBM Support

IEA995I 0C4 0000003B during CICS TS 5.2 or 5.1 startup after upgrading if using CA ENF

Question & Answer


Question

Why do I receive a system dump with a system completion code of 0C4 (S0C4) and reason code 0000003B during CICS Transaction Server for z/OS (CICS TS) V5.2 or V5.1 initialization? This started occurring the first time I tried to bring up CICS TS after upgrading to V5.2 or V5.1. I have run the DFHCSVCU job to dynamically install the SVC for the new release of CICS TS. I am using CA ENF.

These are the messages that I receive during CICS TS V5.2 startup:

 DFHDM0101I CICSAPPL CICS IS INITIALIZING.
 DFHXS1100I CICSAPPL SECURITY INITIALIZATION HAS STARTED.
 DFHW20100I CICSAPPL WEB2.0 DOMAIN INITIALIZATION HAS STARTED.
 DFHSI1500 CICSAPPL CICS STARTUP IS IN PROGRESS FOR CICS TRANSACTION SERVER VERSION 5.2.0
 IEA995I SYMPTOM DUMP OUTPUT  010
     010             SYSTEM COMPLETION CODE=0C4  REASON CODE=0000003B
     010             TIME=15.06.16  SEQ=01381  CPU=0000  ASID=00A6
     010             PSW AT TIME OF ERROR  078D1001   9DC701EC  ILC 6  INTC 3B
     010                ACTIVE LOAD MODULE           ADDRESS=1DC00000   OFFSET=000701EC
     010                NAME=DFHSIP
     010                DATA AT PSW  1DC701E6 - E36045C8  0004E3C0 10100004
     010                GR 0: 00000000_9DE82800   1: 00000000_9DE82908


 

Answer

I've seen the message IEA995I with abend0C4 RSN0000003B during CICS TS 5.2 or 5.1 startup when minimum CA maintenance requirements for CICS TS 5.1 or 5.2 have not been installed. You should make sure all CA maintenance relating to CICS TS 5.1 or 5.2 is applied. Recycle CA ENF after downloading, receiving, and applying the CA PTFs.

The following is from the CA website:


The minimum support requirements for CICS Transaction Server V5R2 are:

ACF2:
RO71103 - SUPPORT CICS TS (CTS) REL 5.2 FOR Z/OS

CA Common Services for z/OS:
Either v14.1 plus PTF RO64919
OR v14.0 plus PTF RO64920*

The minimum support requirements for CICS Transaction Server V5R1 are:

ENF/CICS

CA Common Services for z/OS r14.1 plus
PTFs RO53837, RO54378, RO55429, RO56477, RO59887, RO64763
or
CA Common Services for z/OS v14.0 plus
PTFs RO31927, RO52036, RO54279, RO55317, RO56475, RO59886, RO64766, RO66173*


I took a look at a CICS TS 5.1 dump of the 0C4 program check and it shows the abend is in DFHKESTX. This is the component responsible for handling abends in other areas of CICS. More than likely, the program check occurs when CICS is attempting to link to DFHLDLD. CICS must have been in AMODE 64 at the time, and DFHKESTX (still running AMODE 64) attempts to load information about the module that experienced the error. It loads the module header information address from the domain gate table.

The address loaded was x'00000000 94B80830', and this address can be seen at offset x'190' into the DFHLD domain table entry. Note that the high order bit for the bottom word is on. This makes the address invalid when in AMODE 64. Furthermore, CICS should have OR'd off this bit when adding the address to the table. Taking only the low order word it would be valid in AMODE 31 and and would be an address of x'14B80830'. Browsing this address, the storage looks a lot like the first x'60' or so bytes of module DFHLDLD, but the real load point for DFHLDLD is a long way from this (it is really at 14926DF8).

The abend is often due to a hook into CICS from CA product CA ENF when there is a bad address in the LD domain table, and the 'copy' of the first few bytes of DFHLDLD.

Contact CA Support if you need additional help.

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

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
23 February 2015

UID

dwa1176123