PI17237: DFHAP0002 A SEVERE ERROR (CODE X'4E13') HAS OCCURRED IN MODULE DFHAPCR

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible.

Error description

• Region received several APCR02 abends followed by a DFHRZ0001
  (An abend (code ---/ARZE) has occurred at offset X'0388' in
  module DFHRZTA) abend.
  .
  Task 61509 detects a problem during IMPORT_ALL processing
  because the flattened channel has a container whose header
  lists a non-zero length but does not have any associated data
  following the header.
  .
  The DFHAP0002 A severe error (code X'4E13') happen because the
  CHANNEL data being IMPORTed by DFHAPCR running under
  transaction CPIH, contain an invalid CONTAINER.  CONTAINER
  DFHCONTENTTYPE has either an invalid CONTAINER length data
  or the CONTAINER data is missing.
  .
  The reason the data is incorrect is that the partner task 61522
  had a problem during its EXPORT_ALL processing.  While doing
  the GET CONTAINER INTO call for the DFHCONTENTTYPE container it
  got stuck on the SMLOCK.  The task was then purged out of the
  suspend for the lock.  The purged response was returned to
  DFHPGCR but it is not handled correctly.  Instead of DFHPGCR
  returning PURGED back to DFHAPCR it returns OK along with the
  number of bytes that were copied to the INTO area before the
  error, which was 0.  DFHAPCR then continues filling its buffer
  with the next container header without moving on the current
  buffer position.
  
  
  
  
  
  
  
  
  Additional Symptom(s) Search Keyword(s): KIXREVSLY
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHAP0002 A severe error                *
  *                      (CODE X'4E13') has occurred in module   *
  *                      DFHAPCR.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A GET_CONTAINER_INTO is being performed which becomes
  suspended due to a different task holding the SMLOCK lock. The
  task performing the GET_CONTAINER_INTO is then purged. A
  disaster response is returned to DFHPGCR, but this is not
  handled properly. Instead of passing the disaster response back
  to the caller, DFHAPCR in this scenario, it actually returns
  OK along with the number of bytes which have been copied into
  the return buffer, which was zero. Subsequently, during
  EXPORT_ALL processing, DFHAPCR will create an invalid
  flattened channel. Later when this is used for IMPORT_ALL
  processing, the import will fail because one of the containers
  is missing data. This is reported via a DFHAP0002 message
  with severe error code X'4E13'.
  
  The problem can also occur with GET_CONTAINER_SET.
  

Problem conclusion

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

• DFHPGCR has been changed so that if a disaster response is
  received, it is correctly propagated to the caller.
  

APAR Information

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

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

  UI18778

Modules/Macros

• DFHPGCR  DFHSMMG
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R700 PSY UI18778

     UP14/06/20 P F406

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.