A fix is available
APAR status
Closed as program error.
Error description
You have a CICSplex which has multiple CMASes and a workload with TORs and AORs on different CMASes. You use CICSPlex Optimized Workloads and have a Region Status Server (usually DFHRSTAT) running on each LPAR where your regions run. . When you start your MASes, sometimes you receive messages similar to the following: . EYUWM0508I cmasname Target region (xxxxxxxx) optimization termination reason: (RS server failure). . This message appears in the JOINing CMAS, not the CONNECTing CMAS for a given MAS. . A timing issue exists whereby the JOINing CMAS may attempt to read a record from the Region Status Server Coupling Facility File for a given MAS before that MAS has gotten a chance to write it out there. This can lead to the above message. . If you format out the AUX trace file from the JOINing CMAS you will see an exception entry that looks like the following: . TASK:12345 METHOD:WMAA PRIOR:WMEV DEBUG:WMAARSSR POINTID: 22 TRANID:WMGR MAJOBJ:WLM ENVRN:CMAS TYPE:EXCEPTION TOD:hh:mm:ss.ttttt CLOCK:hh:mm:ss.ttttt UOW(CPSM): SYSTM:XXXX NAME:cmasname CICS-TASK: 12345 TASK-START:hh:mm:ss.ttttt MethName WMAA,WMEV,WMGR,XLOP . RSSR rsp LEN:000001 ALET:00000000 ADDR:16B9717A 0 - 02 RSSR rsn LEN:000001 ALET:00000000 ADDR:16B9717B 0 - 0A RSSRplst LEN:000068 ALET:00000000 ADDR:16B97160 .... The data for the MAS in question here .... RSBLOCK LEN:000040 ALET:01FF0023 ADDR:00058B20 0 - 00000000 00000000 00000000 00000000 LINES 10 - 20 Same as above 30 - 00000000 00000000 00000000 00000000 . . The RSSR Response of x'02' means RSSR_EXCEPTION EQU 002 . The RSSR Reason of x'0A' means RSSR_TARGET_NOT_KNOWN EQU 010 . . Additional Symptom(s) Search Keyword(s): KIXREVSVR
Local fix
Either recycle the MASes reported in the message or stop/restart the MAS agent code in them by logging onto them and issuing COSH followed by COLM.
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R1M0 and V5R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: A CMAS may invalidly report that a CPSM * * WLM target region that is connected to * * another CMAS in the same sysplex is not * * running optimized, even though the * * connected CMAS and the target region * * itself report that the region is * * running optimized. * * * * If this occurs, the CMAS in error will * * issue the following message: * * * * EYUWM0508I Target region (<targetnm>) * * optimization termination * * reason: (RS server * * failure). * * * * Additionally, examination of the * * auxtrace data sets for the CMAS in * * error will show an exception trace * * written by method EYU0WMAA (WMAA), with * * a debug text of "WMAARSSR" and a trace * * point ID of 22. In the trace record, * * the "RSSR rsp" will be x'02' * * (Exception) and the "RSSR rsn" will be * * x'0A' (Target not known). * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and MASes must be * * restarted. Note that the restarts do not * * need to occur at the same time. * **************************************************************** When a target region starts, if it is running optimized, it will write a region status block record to the coupling facility data table (CFDT) for the CICSplex the region is connected to. When a CMAS in the same sysplex issues a CPSM WLM workload join for the target region, it will issue a read for the CFDT record written by the target. If the record is not found in the CFDT, then the CMAS will report the target region as not optimized, issuing the EYUWM0508I message and exception trace documented above. If a CMAS attempts to workload join an optimized target region as it is starting up, it is possible it could attempt to read the CFDT record before the target region writes it. When that occurs, then the EYUWM0508I message and exception trace will be issued in error, and all routing regions connected to the CMAS will not use optimized data for the target region when making routing decisions.
Problem conclusion
To address the possible timing errors, the following changes have been made: - If the CFDT read issued by the CMAS fails during workload join processing, then method EYU0WMAA (WMAA) will store the failure reason in the WAOR control block for the target region. Additionally, if the reason is "Target not known" then WMAA will request that the EYUWM0508 message be issued with the new "Target record not found" reason. The text of the message will be similar to the following: EYUWM0508I Target region (<targetnm>) optimization termination reason: (Target record not found). - Method EYU0WNHD (WNHD), which runs in a MAS at heartbeat time (every 15 seconds) to provide information to its caller, method EYU0NLHD (NLHD), which builds the EMSTATUS record, will determine if the MAS is running as a CPSM WLM target region, and if so, will return to NLHD an indication of whether the MAS is running optimized. NLHD will add that indication to the EMSTATUS record as an internal attribute. - Method EYU0WMAM, which processes EMSTATUS records in a CMAS under the WMGR long running task, will determine if the current record is for a target region connected to another CMAS in the same sysplex. If so, it will check its WAOR control block for the target region to determine if the CFDT read issued by WMAA for the target region failed due to "Target not known". If that is the case, then WMAM will issue a read for the CFDT record, and process as follows depending upon the response and reason returned from the CFDT read: - if the response and reason is OK, then WMAM will activate the target region for optimization, clear the failed reason in the WAOR control block, and issue new message EYUWM0509, which will be similar to the following: EYUWM0509I Workload optimization has been activated for target region (<targetnm>). - if the response is Exception and the reason is "Target not known", then WMAM will exit, wait for the next EMSTATUS record to arrive for the target region, and if it still indicates that the region is an optimized target region, the CFDT read will be re-attempted. - if the response and reason is any other value, then the WAOR will be updated with the new reason, an exception trace will be issued documenting the new failure, and message EYUWM0508 will be re-issued with the appropriate reason. WMAM will not attempt to read the CFDT record for the target region on subsequent EMSTATUS cycles. - EYUZWNHD, which maps the parameter list for method WNHD, has been updated to allow WNHD to pass the optimization status to its caller, NLHD. - The WAOR control block, EYURWAOR, has been updated to include a new field to hold the reason code from CFDT reads issued by WMAA and WMAM. - The EMSTATUS resource table has been updated to include a new internal only attribute which will contain the optimization status of the MAS if it is a CPSM WLM target region. - The EYUMCWME message table has been updated to allow for and document new reason code "Target record not found" for message EYUWM0508, and to create and document new message EYUWM0509. The Kanji (EYUMCWMK) and simplified Chinese (EYUMCWMC) tables have also been updated. - Copybook EYUUWMEQ has been updated to contain an equate for the new EYUWM0509 message.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PI37711
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
80M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-03-24
Closed date
2015-10-23
Last modified date
2015-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI32336 UI32337
Modules/Macros
CJA0NLHD CJA0WNHD CJB0NLHD CJB0WNHD CJC0NLHD CJC0WNHD CJD0NLHD CJD0WNHD CJE0NLHD CJE0WNHD EYUE2507 EYUMCWMC EYUMCWME EYUMCWMK EYUT2507 EYUY2507 EYU0NLHD EYU0WMAA EYU0WMAM EYU0WMAT EYU0WNHD EYU9WMPU EYU9WMP3 EYU9WMP4
GC34288700 | GC34731000 |
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 November 2015