PI09866: ABEND ASRB S00E0 IN CPSM METHOD MOMS. TRANSACTION PEAD. INVALID ALET.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CPSM produces an ASRB abend with messages similar to the
  following:
  .
  .
  EYUXL0900I   Starting Environment Recovery
  
  EYUXL0905E <applid> ASRB IN MOMS, OFFSET 0000071A
             PSW=078D5000 A62590C2
  EYUXL0905E INTC=0028 ILC=4 TXCP=26E8D400 SCODE=S00E0
             TRAN=PEAD TASK=0012345
  
  EYUXL0905E Methods=MOMS,PEAD,XLOP
  
  .
  Access Register 2 is invalid. It was being used as part of the
  parms sent to a GETMAIN routine in EYUMOMS, MOCM_GETMAIN, but
  the register values are not correct.
  .
  .
  Additional Symptom(s) Search Keyword(s): KIXREVRJL
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V4R2M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:    You start two CMASes, one linked to  *
  *                      an APSPEC as the primary control point, *
  *                      and the other as a secondary control    *
  *                      point.  In the EYULOG for the secondary *
  *                      CMAS, you see message:                  *
  *                           EYUPP0003I  Analysis Point         *
  *                             Specification (apspec)           *
  *                             successfully installed for       *
  *                             Context(cicsplex).               *
  *                      followed by message:                    *
  *                           EYUPP0005I  Analysis Point         *
  *                             Specification (apspec)           *
  *                             successfully released in         *
  *                             CMAS(cmasname).                  *
  *                      as the APSPEC is installed in the       *
  *                      secondary CMAS, and then released when  *
  *                      the primary CMAS becomes available.     *
  *                      Some time later, you stop the primary   *
  *                      CMAS, and the following messages are    *
  *                      written to the EYULOG of the secondary  *
  *                      CMAS:                                   *
  *                           EYUPP0003I  Analysis Point         *
  *                             Specification (apspec)           *
  *                             successfully installed for       *
  *                             Context(cicsplex).               *
  *                           EYUPP0107E  Install of RTADEF      *
  *                             (rtadef) for APSPEC apspec in    *
  *                             Context(cicsplex) Scope(cicsgrp) *
  *                             failed.                          *
  *                      Message EYUPP0107E also appears in the  *
  *                      secondary CMAS's JES log.               *
  *                         When the sample interval for the     *
  *                      EVALDEF or EVALDEFs in the evaluation   *
  *                      expression for RTADEF rtadef expires,   *
  *                      you might see errors including, but not *
  *                      limited to, abend ASRA (S0C4), ASRB     *
  *                      (S0E0), or overlay of CICS or CPSM data *
  *                      space storage.                          *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all CMASes must be recycled to pick    *
  *                 up the new code.  Note that CMASes do not    *
  *                 need to be brought down and restarted at     *
  *                 the same time.                               *
  ****************************************************************
     When an APSPEC is installed or released, the appropriate
  method, running under the RTA/AP long running task (PPLT) adds
  a service request to the service queue for the RTA/EVAL long
  running task (PELT) to add or remove elements from the timer
  control lists, then POSTs PELT to have the request processed.
  Module EYU0PELT (PELT - RTA/EVAL Long Running Task) removes
  request elements from the service queue in LIFO sequence.  In
  normal circumstances, this causes no problem because there is
  only one request element on the service queue.  However if two
  or more service requests are added to the request queue in
  quick succession, and dispatch of the PELT task is delayed, a
  release request could be processed before the install request
  for the same APSPEC.
     If the APSPEC is installed again, for example in the sec-
  ondary CMAS, triggered by shutdown of the primary CMAS, the
  install of the RTADEF will fail because its EVALDEFs are still
  in the timer control lists.  As a result, the EVAL Descriptors
  will be released, but the timer control lists will still con-
  tain elements pointing to the freed EVAL Descriptors.  If the
  storage in the RTA data space is reused for another purpose,
  at the next expiration of the evaluation timer for an EVALDEF
  in the Evaluation Expression of the failed RTADEF, this will
  result in failures as described above, in module EYU0PEAD
  (PEAD - RTA/EVAL Asynchronous Data Collector) or in other
  modules called by PEAD.
  

Problem conclusion

•    Module EYU0PELT was modified to remove the queue of incoming
  service requests and rechain in FIFO sequence, when POSTed by a
  service requestor.  Incoming request elements will be processed
  in the order in which they were added to the queue.  Module
  EYU0PESD (PESD - RTA Evaluation Scheduler) was modified to sus-
  pend execution after POSTing the service ECB for PELT, to allow
  PELT to be dispatched.
  

Temporary fix

•             *********
              * HIPER *
              *********
  FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  PI09873 UI14835

Modules/Macros

•    EYU0PELT EYU0PESD
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R70M PSY UI14835

     UP14/02/10 P F402

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.