A fix is available
APAR status
Closed as program error.
Error description
You run CPSM and have one or more of the following PTFs applied . CPSM 5.1 UI51093 CPSM 5.2 UI51048 CPSM 5.3 UI51183 CPSM 5.4 UI51267 . You may experience CMAS-to-CMAS or CMAS-to-MAS connectivity problems. Details and messages to be documented in this APAR's closing text. . . Additional Symptom(s) Search Keyword(s): KIXREVGJT
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V5R1M0, V5R2M0, V5R3M0 and * * V5R4M0 Users. * **************************************************************** * PROBLEM DESCRIPTION: MASes may fail to connect to CMASes * * and CMASes may fail to connect to * * other CMASes after applying any of * * the following PTF sets: * * * * V5R1M0 - UI51046 UI51047 UI51048 * * UI51049 UI51050 UI51051 * * * * V5R2M0 - UI51087 UI51089 UI51090 * * UI51091 UI51092 UI51097 * * * * V5R3M0 - UI51182 UI51183 UI51184 * * UI51185 UI51186 UI51187 * * * * V5R4M0 - UI51265 UI51266 UI51267 * * UI51268 * * * * * * The MAS-CMAS connection problems may be * * accompanied by messages similar to the * * following: * * * * - in the CMAS joblog: * * * * EYUXD0031E Capability mismatch (HIGH) * * for table 215/RULE * * (Service=<svclvl>) * * Local=<val>: Remote=<val>. * * * * EYUCL0130E Capability of MAS <masnm> * * is not lower or equal. * * * * EYUCL0131E Resource type mismatch 1 * * with MAS <masnm> is RULE. * * * * EYUCL0107E ESSS ICT attach to <masnm> * * failed, check capability * * failed. * * * * - in the MAS joblog: * * * * EYUCL0112E Protocol Services * * initialization unable to * * perform ICT Attach. * * * * EYUCL0124E A failure occurred while * * attempting to connect to * * CMAS <cmasnm>. * * * * EYUCL0101E Protocol Services * * initialization failed. * * * * * * The CMAS-CMAS connection problems can * * be of two different types, depending * * upon whether the CMASes are the same or * * different releases: * * * * - If the CMASes are the same release * * the problem will only occur if one * * CMAS is a maintenance point (MP) * * CMAS for a CICSplex, and the partner * * CMAS is a non-MP CMAS for the same * * CICSplex. The connection problems * * may be accompanied by messages * * similar to the following: * * * * - in the MP CMAS joblog: * * * * EYUXD0031E Capability mismatch (HIGH) * * for table 215/RULE * * (Service=<svclvl>) * * Local=<val> : Remote=<val>. * * * * EYUCP0022E Maintenance Point for * * CICSplex <plxnm> on CMAS * * <mpcmas> has a lower * * capability than CMAS * * <nonmpcmas>. CMAS * * <nonmpcmas> will be * * isolated from the CICSplex. * * * * - in the non-MP CMAS joblog: * * * * EYUCP0022E Maintenance Point for * * CICSplex <plxnm> on CMAS * * <mpcmas> has a lower * * capability than CMAS * * <nonmpcmas>. CMAS * * <nonmpcmas> will be * * isolated from the CICSplex. * * * * EYUXZ0910I EYU0XZSD Dump,<jobname>, * * <cmasname>,<lparid>,CMAS, * * XLST,<tasknum>,TRAC, * * EYU0CPRL,<date>,<time> * * * * EYUCP0033I Disconnect requested for * * CMAS <mpcmas>. Reason: * * CMAS isolated. * * * * EYUCP0011E Repository synchronization * * failed for one or more * * CICSplexes. This CMAS is * * being isolated at the * * request of CMAS (<mpcmas>). * * * * EYUCP0205S Repository Synchronization * * with CMAS <mpcmas> failed. * * * * - If the CMASes are different releases * * the problem can occur regardless of * * whether either CMAS is an MP CMAS. * * The connection problems may be * * accompanied by messages similar to * * the following: * * * * - in the higher release CMAS joblog: * * * * EYUXD0031E Capability mismatch (MIXED) * * for table 215/RULE * * (Service=<svclvl>) * * Local=<val> : Remote=<val>. * * * * EYUCP0017E Capability of CMAS * * <lowrelcmasnm> is not valid * * for this CMAS to connect. * * * * EYUCP0018E Resource type mismatch 1 * * with CMAS <lowrelcmasnm> is * * RULE. * * * * EYUCP0018E Resource type mismatch 2 * * with CMAS <lowrelcmasnm> is * * RULE. * * * * EYUCS0105E Unable to assign link set * * for <type> network * * connection * * <lowrelcmassysid>SEND. * * * * - in the lower release CMAS joblog: * * * * EYUCS0105E Unable to assign link set * * for <type> network * * connection * * <highrelcmassysid>SEND. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes and MASes, including MASes * * running as WUI servers, must be recycled to * * pick up the new code. * * * * The restarts need not be performed at the * * same time, however if systems are not * * restarted at the same time, the following * * rules apply: * * * * - Maintenance Point (MP) CMASes must be * * restarted with the updated code before * * non-MP CMASes. * * * * - If you have more than one MP CMAS and any * * of those MP CMASes are connected directly * * or indirectly, then those MP CMASes must * * be restarted with the updated code at the * * same time. * * * * - Before a MAS, regardless of whether it is * * running as a WUI server, is restarted with * * the updated code, the CMAS to which the * * MAS connects must be running with the * * updated code. * * * * - This fix is being provided to the * * following supported releases of CPSM as * * follows: * * * * - CPSM V5R1M0 - APAR PI89699 * * - CPSM V5R2M0 - APAR PI89699 * * - CPSM V5R3M0 - APAR PI89699 * * - CPSM V5R4M0 - APAR PI89699 * * * * Before a CMAS running with the PTF that * * resolves this APAR for its release * * connects directly or indirectly to a CMAS * * running a higher release of CPSM, the * * higher release CMAS must be restarted so * * that it is running with the appropriate * * PTF for its release. * * * * * * Additionally, all API programs that access * * the RULE resource table should be * * reassembled or recompiled pointing to the * * libraries updated by the PTF that resolves * * this APAR. * **************************************************************** The PTFs mentioned in the problem description above, make a change to the RULE resource table: - The V5R4M0 change was not compatible with the V5R1M0, V5R2M0 and V5R3M0 changes. - The change requires that CMASes and MASes, including MASes running as WUI servers, be restarted with the updated code in a specific order, but the APAR Recommendations did not document this, and ACT HOLD data was not included in the PTFs to indicate this. As a result of the above, errors can occur when connection attempts are made between CMASes and MASes, including MASes running as WUI servers, or between different CMASes.
Problem conclusion
To correct the possible connection problems: - The V5R4M0 code as been updated through this APAR to change the RULE resource table so that it is compatible with the changes to V5R1M0, V5R2M0 and V5R3M0. - An APAR Recommendation and ACT HOLD data have been added to this APAR, to document the correct method of restarting regions after applying the PTFs that resolve this APAR.
Temporary fix
Comments
APAR Information
APAR number
PI89699
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
80M
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-01
Closed date
2017-11-14
Last modified date
2017-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI51861 UI51862 UI51863 UI51864
Modules/Macros
CJC0NQPU CJD0NQPU CJE0NQPU CJF0NQPU CJG0NQPU EYU0NQPU EYUA0215 EYUC0215 EYUL0215 EYUP0215 EYUT0215 EYUTMOMI EYUTMOSD EYUTVOSX EYUY0215
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R00M PSY UI51864
UP17/11/21 P F711 {
R10M PSY UI51863
UP17/11/22 P F711 {
R80M PSY UI51861
UP17/11/21 P F711 {
R90M PSY UI51862
UP17/11/18 P F711 {
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:
02 December 2017