PH02301: CEE0374C ABEND0C4 DFHTRPX DFHSO0001 ABEND422 AKEX DFHSOSO5 WITH SO LEVEL 2 TRACE ACTIVE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Running CICS 5.4 with fix for APAR  PI89854 applied, and
  have SO level 2  tracing active. When receiving an error
  on RECEIVE_SSL_DATA processing, you receive the following
  error messages:
  CEE0374C CONDITION=CEE3204S TOKEN=xxxxx
           WHILE RUNNING PROGRAM DFHSIP AT THE TIME OF INTERRUPT
  
  The PSW associated with this error points to DFHTRPX.
  This is followed by
  DFHSO0001 An abend (code 422/AKEX) has occurred at
            offset X'FFFF' in module DFHSOS05.
  
  The first error is an abend0c4 at offset x'586' into DFHTRPX
  on an MVCL instruction. DFHSOCK is trying to put out
  trace point id x'029D' or trace point tid_sock_buffer_cont.
  .
  In CICS trace level 1 you will see many of the following trace
  entries:
  .
  task S800G SO 029D SOCK  DATA  BUFFER_CONTINUED
  .
  DFHSOCK is using incorrect values for writing out trace, until
  it hits a page boundary it does not have access to, causing the
  program check .
  Additional Symptom(s) Search Keyword(s): KIXREVxxx
  abend422-1A0 in BPXNSDLV (signal delivery) while in a
  takesocket call
  

Local fix

• turn off SO level 2 tracing
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Using CICS with SSL may result in an    *
  *                      abend0C4 in DFHTRPX if SO level 2       *
  *                      tracing is active.                      *
  ****************************************************************
  CICS is setup with SSL enabled and SO level 2 trace active.
  DFHSOCK is called to receive SSL data. There is a variable to
  save the length of the received SSL data. DFHSOCK set this
  variable to -1 if there is an error during the receive. The
  -1 value will be treated as a large positive value when tracing
  the data buffer. That causes many SO 029D continuation trace
  entries to be produced.  If the data being traced crosses a page
  boundary into unallocated storage then an 0C4 will occur in
  DFHTRPX.
  

Problem conclusion

• DFHSOCK has been changed to not trace the data buffer if an
  error happened during the socket receive.
  

Temporary fix

Comments

APAR Information

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

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

  UI59162

Modules/Macros

• DFHSOCK
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R100 PSY UI59162

     UP18/10/18 P F810

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.