PH63035: ABEND0C1 OCCURS IN EYU0XLSJ TRYING TO WRITE A JOURNAL ENTRY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An abend 0C1 occurred in CICSplex environment.  At the time of
  the abend, the XDNR task had the following task stack:  XDP6,
  XDP4, XDP3, XDNR, XLOP
  
  The trace shows the exception abend entries:
  12345 XLSJ           XDNR          Abend          *Abend*
  12345 XLSD XLSI XDNR KNL Excp      9     XLSDXLSJ     Ext
  12345 CRCK          XDNR         Abend           *Abend*
  12345 XDP6          XDNR         Abend           *Abend*
  
  The psw for this 0C1 abend points x'A92' into EYI9XLMC.  It is
  not pointing to a valid instruction.
  
  The 0C1 occurred due to being incorrectly in AR mode while
  trying to write a trace record when locating a bad entry in a
  name list during processing to create a new Action/Command
  journal entry. The name list error was detected in XLSJ which
  was called to record the action to the configured journal,
  however the error processing, to trace and exit  was incorrectly
  called while in AR mode needed to address the name list entry.
  As such, as this is not expected, this resulted in an 0C1 due to
  this not being allowed (due to calls and instructions made not
  being allowed). Some of this bad call can be seen in the job
  logs with :
    +EYUXL0904I CALL IN AR MODE, DISPLAYING FROM CALL
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM Users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend S0C1 may occur in EYU0XLSJ in a   *
  *                      CMAS region when using CMAS journaling, *
  *                      when XLSJ attempts to write an          *
  *                      exception trace record.                 *
  ****************************************************************
  * RECOMMENDATION: After applying the PTFs addressing this      *
  *                 APAR, all CMAS regions should be restarted.  *
  *                 Restarts can be performed in any order.      *
  ****************************************************************
  CMAS journaling enabled through EYUPARM values JRNLDEFCH/
  JRNLOPACT/JRNLRTAEV enabled the writing of CICS journal records
  to track CICSplex activities. EYU0XLSJ is called to write
  records for Create/Command actions. If multiple records are
  affected by an action, the namelist from the request is passed
  in. If a namelist passed in from the API action has incorrect
  entries, XLSJ writes an exception trace record with debug text
  of 'BadNameE'. However, this may incorrectly be attempted while
  still in AR addressing mode, which results in this operation
  failing with abend 0C1.This also results in the trace record not
  being written.Message EYUXL0904I is also produced due to the
  0C1 / AR mode scenario :
    +EYUXL0904I CALL IN AR MODE, DISPLAYING FROM CALL
  

Problem conclusion

• The logic for the bad namelist entry path has been corrected
  to restore addressing to primary mode prior to writing the
  trace record.
  

Temporary fix

Comments

APAR Information

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

  PH62849

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

  UI98366 UI98367

Modules/Macros

• EYU0XLSJ
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R40M PSY UI98367

     UP24/09/19 P F409

• R50M PSY UI98366

     UP24/09/19 P F409

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.