A fix is available
APAR status
Closed as program error.
Error description
After implementing Sysplex Omtimized Workload management within some workloads for certain target AOR regions, any WUI workload views (ie. WLMAWAOR, WLMATARG, etc) received message: . EYUVC1278E unable to obtain data for requested View. 'GET' (GET) request failed (Failed, Exception). . None of the routing regions have been set optimized yet. The APIGET failure was the result of an RSSR failure occurring in WABA / WABB on a RSSR_INQUIRE_TARGET_STATUS function with a response of 02 RSSR_EXCEPTION and a reason of 0A RSSR_TARGET_NOT_KNOWN. The region that received the RSSR failure was located on a different plex then the region where the request was executed. . The trace may show either of the following exception: WABA XLSD XLST WLM EXCP. 14 DFHRSSR EUI G333297 CMAS . where the WABA entry trace point id 14 indicates DFHRSSR failed and around x'580' in the STAK, the RSSR structure shows the MAS having the problem at +2C. . Or... WABB XLSD XLST WLM Lv-13 13003 RSSRRESP Ext B326599 CMAS . where the RSSR parm list (RSSRplst) shows the MAS having the problem at +34. . Additional Keyword(s) and Symptom(s): KIXREVPAD
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R1M0 Users * **************************************************************** * PROBLEM DESCRIPTION: You activate Sysplex Optimized Work- * * load for a CPSM workload in a CICSplex * * which spans multiple z/OS SYSPLEXes. * * You attempt to view your active target * * regions through the EYUSTARTWLMAWAOR or * * EYUSTARTWLMATARG WUI views and receive * * the following message: * * . * * EYUVC1278E unable to obtain data * * for requested View. 'GET' * * (GET) request failed * * (Failed, Exception). * * . * * Examination of the CMAS AUXTRACE shows * * that an RSSR_INQUIRE_TARGET_STATUS * * request returned response 02 * * (RSSR_EXCEPTION) and reason 0A * * (RSSR_TARGET_NOT_KNOWN). The target * * region which was being processed is * * executing in a different SYSPLEX than * * the CMAS in which the request is being * * processed. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and MASes 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. * **************************************************************** When Sysplex Optimized Workload is active for target regions, status is maintained by the RS Domain in a Coupling Facility Data Table. Because a coupling facility can only be accessed by one sysplex, region status information will only be available to regions executing in the same sysplex as the target region. When a target region is activated in a CMAS which manages an active workload, the optimization state is set from attributes of the CICS System Definition (CSYSDEF) resource for the region, without considering whether Region Status is available in the local coupling facility. Modules EYU0WABA (WABA - Browse Active AORs) and EYU0WABB (WABB - Browse Active Target Regions) call the RS Domain to retrieve Region Status information. If the target region is in a different SYSPLEX, the RS Domain will return a response of 02 (RSSR_EXCEPTION), and a reason of 0A (RSSR_TARGET_NOT_KNOWN). WABA and WABB interpret this as a failure, and erroneously re- turn a response of EXCEPTION and a reason of METHOD_FAILED.
Problem conclusion
Modules EYU0WABA and EYU0WABB were modified to detect reason 0A (RSSR_TARGET_NOT_KNOWN) and set the reported Optimization Status for the target region to INACTIVE. Several modules which initialize or update the WLM AOR Descriptor (WAOR) in a CMAS were modified to compare the local SYSPLEX with the SYSPLEX in which the target regions executes, and to set the local optimi- zation state to INACTIVE if they are different. This prevents TORs which connect to the CMAS from attempting to use region status information which is not available in the local SYSPLEX, in making routing decisions.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM97125
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
80M
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-16
Closed date
2014-01-15
Last modified date
2015-03-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI14243
Modules/Macros
EYU0WABA EYU0WABB EYU0WABT EYU0WABU EYU0WARS EYU0WMAA EYU0WMAM EYU0WMTJ EYU0WPUD
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R80M PSY UI14243
UP14/01/20 P F401
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:
05 March 2015