PM38706: DFHZC0001 ABEND 0C4 AKEA OFFSET 2C72 INTO DFHZGRP AFTER A VTAM FAILURE

APAR status

• Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)

Error description

• You are running CICS TS 3.1 and VTAM goes down.
  You receive the following messages:
  DFHZC3443  VTAM has been cancelled or the ACB has been
             forceclosed . VTAM sessions terminated.
  DFHZC2316  VTAM ACB is closed
  DFHZC0200  An attempt by the COVR transaction to OPEN VTAM has
             failed with return code X'0000005C'; CICS will retry.
  DFHZC0001  An abend (code 0C4/AKEA) has  occurred at offset
             offset X'2C72'
             in module DFHZGRP.
  DFHME0116  CICS symptom string for message DFHZC0001 is
             PIDS/5655M1500 LVLS/640 MS/DFHZC0001 RIDS/DFHZGRP
             PTFS/UK19600 AB/S00C4 AB/UAKEA ADRS/00002C72
  DFHZC2316  VTAM ACB is closed.
  .
  The failing instruction was a move character- MVC
  D25A B000 E000
  Register RB contained zeros causing the ABEND0C4.
  RB was loaded from the TCTTE+22C or field TCTE_PRSS_CV29_PTR.
  The CICS internal trace showed this field was getmained
  by the COVR transaction from shared storage remark PRSSCV29.
  But there was a task still associated with this particular
  terminal that was not cleaned up yet when VTAM went away.
  It freemained this storage- TCTE_PRSS_CV29_PTR, causing
  the field to contain zeros. Later when the COVR task tried
  to restore this terminal, it received the 0C4 abend when
  referencing this field.
  KIXREVEPH
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is being closed with a code of RET/AU. This closing
  indicates that the Change Team has been unable to test the
  proposed fix for this APAR and that no Customer was able to test
  the fix and provide feedback within a reasonable amount of time.
  
  To ensure that only high quality fixes are distributed to all
  Customers, we require every fix to be tested either internally
  or at a Customer site which is experiencing the problem. This
  will minimize any exposure to a possible PTF error which could
  later be more detrimental to the Customer.
  
  The APAR fix is available upon application to the Change Team
  via PMR. Once the fix has been satisfactorily tested by a
  Customer experiencing the reported problem, the Change Team will
  accept a NO-DOC APAR (which must refer to this returned APAR) in
  order to provide the appropriate PTFs.
  
  If the fix does not correct the reported problem, please contact
  the Change Team via PMR with full details of the failure.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM45506

Fix information

Applicable component levels