PM27632: EYUXL0905E CPSM ASRA IN XDNR TASK IN A CMAS, METHOD XDP6, S0C4

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You are running an API program and receive an ASRA abend, for
  which the CMAS takes a dump with the following title:
  .
  TITLE=EYU9XLRV Dump,jobname,applid,PRPC,CMAS,XDNR,#######,ASRA,
        EYU0XDP6,dd/mm/yyyy,hh:mm:ss
  .
  Using IPCS command  VERBX EYU9D### 'TASKS' will show the
  following Kernel Linkage Summary for the task in error
  .
  Kernel linkage summary for component - DAT / Data Definition
   Task Meth Load-Pt  OSSB     Stack    Mal      MODB     MOEB
  20938 XLOP 000B5940 33401740 33401768 00000000 31E70E60 31CB9140
  20938 XDNR 32C26BA0 33401740 334018B0 333BE05C 31E76360 3323A060
  20938 XDP3 32CEEA00 33401740 334023B8 33402270 31E76360 3323A060
  20938 XDP4 32C2C298 33401740 33403020 33402618 31E76360 3323A060
  20938 XDP6 32C2ED88 33401740 334039C0 33403320 31E76360 3323A060
  .
  Looking in the trace using VERBX EYU9D### 'TRC' you will see a
  number of trace entries with debug text of BADVER and/or INVVER
  .
  The problem is that you have PK98569/UK58389 on your system, and
  CPSM has made a request for MASQRYER records at a level that it
  does not understand those records. We then try to reference
  storage in the DAT dataspace but are not in Access Register mode
  (bit 17 of the PSW is not on) and therefore we're accessing
  storage in the CMAS private area, which may not be accessible.
  Thus the S0C4 / ASRA.
  .
  Additional Keywords:
  Debug:BADVER Debug:INVVER SCODE=S00C4 TRAN=XDNR MASQRYER DETAIL
  INVALID INVALID_VERSION EXCEPTION METHOD_FAILED
  Methods=XDP6,XDP4,XDP3,XDNR,XLOP
  KIXREVJXD
  

Local fix

• Ensure that your API programs are CONNECTing at the currently
  installed CPSM level.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:    After applying PTF UK59430 for APAR  *
  *                      PM19338 you execute a CPSM API program  *
  *                      which passes VERSION(0140) on the API   *
  *                      CONNECT command.  Later in the same     *
  *                      program, a PERFORM SET command returns  *
  *                      RESPONSE=FAILED, REASON=EXCEPTION.  In  *
  *                      the CMAS to which the API program con-  *
  *                      nected, an ASRA (S0C4) abend occurred   *
  *                      in module EYU0XDP6 (XDP6 - Refresh API  *
  *                      Result Set Status).                     *
  ****************************************************************
  * RECOMMENDATION:    After applying the PTF that resolves this *
  *                 APAR, all CMASes must be recycled to pick up *
  *                 the new code.  Note that the restarts do not *
  *                 need to be done at the same time.            *
  ****************************************************************
     The MASQRYER resource table was introduced by PTF in V3.2 of
  CPSM.  If an API program passed a version earlier than 0320 on
  the CONNECT command, CPSM will be unable to build a result set
  of MASQRYER resources because the resource table is not known
  at the version of CPSM identified by the CONNECT.  In response
  to the invalid version, module EYU0XDP6 leaves AR mode and calls
  module EYU0XZPT (XZPT - Put Trace record) to log the exception.
  However EYU0XDP6 does not return to AR mode after writing the
  trace, so an abend ASRA (S0C4) occurred trying to modify storage
  in the DAT cache data space.
  

Problem conclusion

•    Module EYU0XDP6 was modified to return to the addressing
  mode which was in effect when the trace subroutine was called.
  In addition, the call to trace invalid version exceptions was
  removed from EYU0XDP6 and EYU0XDP1 (XDP1 - API GET Command),
  as a trace was written when the exception was first detected.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

• None.
  ž**** PE11/06/30 FIX IN ERROR. SEE APAR PM42796  FOR DESCRIPTION
  

APAR Information

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

  PM27664

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

  UK62860

Modules/Macros

•    DYU0MOXT DYU0VAFT DYU0VAGM DYU0VAGT DYU0VAGW
  DYU0VAST DYU0VASU DYU0VBRP DYU0VHDT DYU0VHLK DYU0VHPL DYU0VHTT
  DYU0VHVD DYU0VIFM DYU0VISE DYU0VISI DYU0VISP DYU0VISZ DYU0VMPR
  DYU9VKEC EYUA2639 EYUBVAPI EYUBVISS EYUBVIST EYUBXDEN EYUBXDRD
  EYUCXXRS EYUC2639 EYUEVGAR EYUE2639 EYUKVGAR EYUK2639 EYUL2639
  EYUP2639 EYUQACCK EYUQXXRC EYURVGAR EYURXDEQ EYUR2639 EYUSVGAR
  EYUS2639 EYUTACMD EYUTAEYU EYUTBNRC EYUTMOMI EYUTMOSD EYUTRDIR
  EYUTVOSX EYUTVTHE EYUTVTHK EYUTVTHS EYUT2639 EYUUACMD EYUUAGBL
  EYUUXXFI EYUUXXRS EYUUXXTC EYUY2639 EYU0ABAA EYU0ABAF EYU0ABAJ
  EYU0ABA4 EYU0ABA7 EYU0ABA9 EYU0ABM0 EYU0CRCK EYU0CTEX EYU0DXRC
  EYU0MOXT EYU0TICT EYU0TSRA EYU0VAFT EYU0VAGC EYU0VAGM EYU0VAGP
  EYU0VAGT EYU0VAGW EYU0VAST EYU0VASU EYU0VBRB EYU0VBRF EYU0VBRS
  EYU0VHDA EYU0VHDB EYU0VHDF EYU0VHDH EYU0VHDI EYU0VHDK EYU0VHDT
  EYU0VHLB EYU0VHLF EYU0VHPL EYU0VHTD EYU0VHTH EYU0VHTM EYU0VHTT
  EYU0VHVB EYU0VHVC EYU0VHVD EYU0VHVH EYU0VHVS EYU0VHVT EYU0VIFB
  EYU0VIFC EYU0VIFM EYU0VIFR EYU0VISE EYU0VISI EYU0VISP EYU0VISZ
  EYU0VKED EYU0VMNR EYU0VMPD EYU0VMPR EYU0XDER EYU0XDH3 EYU0XDH4
  EYU0XDH7 EYU0XDNR EYU0XDP1 EYU0XDP2 EYU0XDP4 EYU0XDP5 EYU0XDP6
  EYU0XDQA EYU0XDQB EYU0XDQR EYU0XDQ2 EYU0XDW1 EYU0XDW2 EYU0XDW3
  EYU0XDW8 EYU0XDW9 EYU0XDY1 EYU0XDY2 EYU0XDY3 EYU0XDY4 EYU0XDY5
  EYU0XDY7 EYU0XLSD EYU0XL80 EYU0XQGQ EYU0XXRC EYU7VISS EYU7VIST
  EYU9XDF1 EYU9XMAL JCI650MJ MASQRYER
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R50M PSY UK62860

     UP10/12/16 P F012

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.