PI12305: THE EVENTDTL TABULAR AND DETAILED VIEWS DISPLAY INCORRECT INFORMATION FOR THE OUTSTANDING EVENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You have an RTADEF that includes multiple EVALDEFs on the
  evaluation expression (EVALEXPRTEXT).  When an event occurs and
  you view the event details (EVENTDTL), you notice the
  evaluation data is being displayed for the one (or more) of the
  other EVALDEFs.
  .
  As an example, there are 3 EVALDEFs:
    EVALDEF1 for CONNECT
    EVALDEF2 for MQCONN
    EVALDEF3 for TRANDUMP
  .
  On the RTADEF, EVALEXPRTEXT is:
    (EVALDEF1 | EVALDEF2 | EVALDEF3)
  .
  A CONNECT event occurs and when you view the
  EYUSTARTEVENTDTL.TABULAR view it shows the Resource Table name
  as MQCONN.  And the EYUSTARTEVENTDTL.DETAILED view displays a
  mix in the fields of the MQ connection data and the connection
  to IMS data.  This is due to the resource identification
  from the CONNECT event being merged with evaluation data
  from the EVALDEF based on MQCONN.
  .
  The definitions all work okay but the details do not.
  Additional Symptom(s) Search Keyword(s): KIXREVGJT
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V5R1M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:    You have an RTADEF that includes     *
  *                      multiple EVALDEFs in the Evaluation     *
  *                      expression (EVALEXPRTEXT).  When an     *
  *                      event occurs and you view the event     *
  *                      details (EVENTDTL), you notice that     *
  *                      records are displayed for all true      *
  *                      EVALDEFs associated with the RTADEF,    *
  *                      instead of the one EVALDEF associated   *
  *                      with the event.                         *
  *                                                              *
  *                      As an example, you have 3 EVALDEFs:     *
  *                        EVALDEF1 for MQCON                    *
  *                        EVALDEF2 for CONNECT                  *
  *                        EVALDEF3 for TRANDUMP                 *
  *                                                              *
  *                      On your RTADEF, EVALEXPRTEXT is:        *
  *                        (EVALDEF1 | EVALDEF2 | EVALDEF3)      *
  *                                                              *
  *                      A CONNECT event occurs and when you     *
  *                      view the EYUSTARTEVENTDTL.TABULAR view, *
  *                      it shows the Resource Table name as     *
  *                      MQCON.  The EYUSTARTEVENTDTL.DETAILED   *
  *                      view displays a mix of MQCON resource   *
  *                      data and CONNECT resource data.         *
  *                                                              *
  *                         You execute the REFRESH API command  *
  *                      against a result set of EVENTDTL or     *
  *                      EVENT resources and the REFRESH command *
  *                      returns response and reason of FAILED / *
  *                      EXCEPTION.                              *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all CMASes must be recycled to pick    *
  *                 up the new code.  Note that regions do not   *
  *                 need to be brought down and restarted at     *
  *                 the same time.                               *
  ****************************************************************
     The EVENTDTL resource contains fields derived from the EVENT
  resource, and from the EVALDEF that triggered the EVENT.  Module
  EYU0PNQN (PNQN - Query EVENT and EVENTDTL) retrieved the RTADEF
  Analysis Descriptor (PRRD) that generated the EVENT, scanned the
  Evaluation Expression, and generated an EVENTDTL resource for
  each EVALDEF in the expression.  This resulted (in the example
  above) in data for a specific EVENT being combined with EVALDEFs
  for multiple resource types.
     When a queue of raw resource records is added to a result set
  by module EYU0XDQA (XDQA - Add / Replace Records in result Set),
  the names of the CMAS and MAS (where appropriate) where the
  record originated are placed in the Object Status area for the
  record.  This information is copied to the NameList for actions
  and refresh requests to identify the destinations to which the
  request must be sent.  Module EYU0PNQN placed the name of the
  CICSplex against which a GET for EVENT or EVENTDTL was executed
  in the returned queue, but not the name of the CMAS in which it
  executed.  When a REFRESH command was executed against a result
  set of EVENT or EVENTDTL, CPSM's Single System Image component
  returned a method response and reason of KERNERROR and KERR_TARG
  (Target Unavailable).  This was exposed as an API response and
  reason of FAILED / EXCEPTION.
  

Problem conclusion

• Module EYU0PNQN was modified to retrieve the address of the
  specific EVALDEF Descriptor (PEED) whose state was reported in
  an EVENT, and to generate a single EVENTDTL resource for each
  EVENT containing data from the EVENT, and from the EVALDEF which
  triggered the EVENT.  It was also modified to place the name of
  CMAS in which it executed in the Queue Header (QUEHEAD) block
  for each queue buffer returned.
     Module EYU0XDQA was modified to copy the CMAS name to the
  Object Status area for EVENT and EVENTDTL resources.
  

Temporary fix

• 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:

  UI15715

Modules/Macros

• EYU0PNQN EYU0XDQA EYUA2519 EYUC2519 EYUE2519 EYUK2519 EYUL2519
  EYUP2519 EYUS2519 EYUT2519 EYUY2519
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R80M PSY UI15715

     UP14/03/07 P F403

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.