A fix is available
APAR status
Closed as program error.
Error description
You are using CPSM Monitoring, either directly or through an RTA configuration, and experience ASRA / S0C9 abends in method PEPR. The abend message and methods traceback looks like . EYUXL0905E cmasname ASRA IN PEPR, OFFSET 00000598 PSW=07856000 97C55AD8 LEVEL=xxxxxxx PFX=yyy EYUXL0905E INTC=0009 ILC=4 TXCP=7EC44801 SCODE=S00C9 TRAN=PEAD TASK=0012345 EYUXL0905E Methods=PEPR,PEAD,XLOP EYUXL0905E BEAR=17C55AB0, OFFSET=00000570 . CPSM is building data incorrectly in a result set that ends up causing the ASRA / S0C9 later
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlexSM Users * **************************************************************** * PROBLEM DESCRIPTION: CICSPlex SM Monitoring table MLOCTRAN * * is generated with incorrect data. At * * release 5.6 or higher, when this table * * is used with RTA it may cause S0C9 * * abends to occur under the PEAD * * transaction ID. * **************************************************************** * RECOMMENDATION: Apply the PTF to all CMASes. This can be * * done in any order. * **************************************************************** The table data in EYUTMMDT was invalid due to differences between EYUQMMDT generated data and the EYURMMDT copy book used by programs to read it. Several table fields, AMAXTASKS, CURRAMAX, J8CPUC, J8CPUT, LASTRESET, PEAKAMAX, & TERMSTG that are no-longer used were being displayed with zero values instead of not being available in REXX. In external copybooks fields were marked with - * CURRAMAX * * Invalid CICSREL = M212 V220 E410PLUS * At v5.6 the fields in EYURMMDT were reordered but those generated by EYUQMMDT were not. Wrong data is used to populate the CURAVGRESP and CURAVGCPUT fields of the MLOCTRAN table with incorrect values. If either field was being checked by RTA this could cause the CMAS transaction to repeatedly abend S0C9.
Problem conclusion
The fixes in this APAR Ensure DSECT layouts from EYUQMMDT & EYURMMDT are identical. Ensure the "N/A ESA" bytes are contiguous at v5.4 & v5.5. Correcting the definition of PEAKAMAX at v5.4 & v5.5.
Temporary fix
Comments
APAR Information
APAR number
PH56434
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
30M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-08-18
Closed date
2023-10-05
Last modified date
2023-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PH56826 UI93893 UI93894 UI93895
Modules/Macros
EYU0DVNF EYU0MCCD EYU0MCCR EYU0MMAC EYU0MMCP EYU0MMEI EYU0MMIC EYU0MMIN EYU0MMKL EYU0MMQD EYU0MMRL EYU0MPRS EYU0MSBU EYU0MSIN EYU0MSRM EYU0MSRS EYUTMMDT
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R10M PSY UI93895
UP23/10/11 P F310
R20M PSY UI93894
UP23/10/10 P F310
R30M PSY UI93893
UP23/10/10 P F310
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.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.6","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
02 November 2023