A fix is available
APAR status
Closed as program error.
Error description
After a CICSplex is FORCEd for one or more non-MP CMASes which are unavailable, subsequent WUI views, CICS Explorer views, and API program lookups for CPLEXDEF on each CMAS can produce inconsistent results. The EYUSTARTCICSPLEX.TABULAR view may display no CICSplexes or may display only a subset of the CICSplexes. The CICS Explorer CICSplex tab may also not display all CICSplexes or only a subset. . The CONN_MY_PLEX and CONN_CPLEX_DIR cache lists in the non-MP CMASes will still show the CICSplexes that have been FORCEd from the MP CMAS. Method CPBI issues an XCLV call to view each entry in the CONN_MY_PLEX cache list and then issues an XDGT method call to read the associated CMASCPLX record from its EYUDREP. If the CMASCPLX record is not found, processing terminates in method CPBI and returns to the caller with a CPBI_CONTEXT_NOT_FOUND status and CPBI_RESPONSE of OK. . Additional Symptom(s) Search Keyword(s): eyu0cpbi eyu0xdgt XDGT_RECORD_NOT_FOUND kixrevwjb
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V3R2M0 Users * **************************************************************** * PROBLEM DESCRIPTION: A GET request of CMASPLEX or CICSPLEX * * resource table records for a CMAS * * through the API or WUI may show * * CICSplexes for which no maintenance * * point CMAS exists. * * * * Additionally, in the case of the * * CICSPLEX resource table, a GET request * * may be missing all or some of the * * CICSplexes that the CMAS manages. When * * this occurs, if a CICS Explorer session * * is issued through a WUI server * * connected to the CMAS, the CICSplex * * list displayed by CICS Explorer will be * * null or incomplete. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all CMASes, MASes and WUI servers must * * be restarted. * * * * - 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 CMASes must be * * restarted before non Maintenance point * * CMASes, MASes and WUI Servers. * * * * If you have more than one Maintenance * * point CMAS and those Maintenance point * * CMASes are connected directly or * * indirectly, then these maintenance point * * CMASes must be restarted at the same * * time. * * * * - Before a MAS or WUI server is restarted, * * the CMAS to which the MAS or WUI server * * connects must be restarted. * * * * - Before a CPSM V3R2M0 CMAS running with * * the PTF that resolves this APAR connects * * to a CPSM V4R1M0 CMAS, the V4R1M0 CMAS * * must be restarted so that it is running * * with the PTF that resolves CPSM V4R1M0 * * APAR PM28230. * * * * - If a GET for CMASPLEX records is issued * * to a CMAS which has not been restarted, * * the new CMASPLEX attributes will not be * * set correctly. * * * * - If the new CMASPLEX actions REMPLEX or * * FORCEREMPLEX are issued to a CMAS that * * has not been restarted, a * * Response/Reason of Failed/Exception will * * be returned. * * * * * * - All API programs that access the CMASPLEX * * resource table should be reassembled or * * recompiled pointing to the appropriate * * copybook library distributed by the PTF. * * * * * * - Once a WUI server has been restarted, then * * users of the CICSPlex SM supplied starter * * set viewsets and menus must re-import the * * updated starter set CMASPLEX viewset into * * the WUI server's repository in order to * * pick up the changes. * * * * The viewset can be re-imported either via * * the AUTOIMPORTDSN and AUTOIMPORTMEM WUI * * server initialization parameters or the * * IMPORT (from a dataset) function of the * * COVC WUI transaction. * * * * If COVC is used to re-import the viewset, * * ensure that the TYPE operand is set to ALL * * or VIEWSET, and that the Import option is * * set to OVERWRITE. * * * * Users who have copied the IBM supplied * * starter set viewsets and menus to another * * name will have to manually apply the * * changes made by the PTF that resolves this * * APAR to those copies. * * * * For details on the AUTOIMPORTDSN and * * AUTOIMPORTMEM WUI server initialization * * parameters see 'Specify the Web User * * Interface server initialization * * parameters' in the "CICS Transaction * * Server for z/OS Version 3 Release 2 * * Installation Guide" (GC34-6812). * * * * For details on the COVC IMPORT function * * see 'The CICSPlex SM Web User Interface * * transaction (COVC)' in the "CICS * * Transaction Server for z/OS Version 3 * * Release 2 CICSPlex SM Web User Interface * * Guide" (SC34-6841). * * * * The updated starter set viewset name that * * needs to be imported is: * * * * CMASPLEX ViewSet : EYUxA1W4 * * * * Replace x with the required language * * version to be imported: * * * * E - English, K - Japanese, S - Chinese * * * * Insure that the import references the * * SEYUVIEW dataset that was updated by the * * PTF that resolves this APAR. * **************************************************************** When an inactive CMAS is removed from management of a CICSplex through the CPLEXDEF or CPLXCMAS UNASSIGN action using the FORCE option, and the CICSplex is subsequently deleted from the maintenance point CMAS through the CPLEXDEF REMOVE action, the CICSplex records will never be deleted from the data repository of the CMAS which was UNASSIGN FORCEd. In effect, this causes the CICSplex to be "orphaned". This can result in invalid control blocks existing in the CMAS network if the CMAS becomes active. The CPLEXDEF or CPLXCMAS UNASSIGN action with the FORCE option was intended to only be used when the CMAS being removed from management of the CICSplex was not active and would never again be active. However, there is no way to ensure this, allowing the possibility that this can occur. And once this does occur, there is no mechanism for removing the CICSplex from the CMAS's data repository. Additionally, when the invalid control blocks exist in the CMAS network, GET requests for CICSPLEX records may cause method EYU0CPBI (CPBI) to stop processing when it encounters an invalid control block. When this occurs, either no records or a partial subset of the records will be returned to the caller. Note that the CICS Explorer issues a GET for CICSPLEX records to build its CICSplex list.
Problem conclusion
The CMASPLEX resource table has been updated to identify and allow removal of "orphaned" CICSplexes: - Two new attributes have been added to the CMASPLEX table: MPCMAS - This names the maintenance point CMAS as defined to the CONTEXT CMAS. MPSTATE - This indicates the state of the reported maintenance point CMAS. This attribute can have one of the following three values: VALID - The maintenance point CMAS is connected to the CONTEXT CMAS and has confirmed it is the maintenance point CMAS. INVALID - The maintenance point CMAS is connected to the CONTEXT CMAS and has confirmed it is not the maintenance point CMAS. NOTCONNECTED - The maintenance point CMAS is not connected to the CONTEXT CMAS, therefore it cannot be determined if the named MP CMAS is actually the MP CMAS. - Two new actions have been added to the CMASPLEX table: REMPLEX - Remove the CONTEXT CMAS from a CICSplex definition when the MPSTATE is INVALID. FORCEREMPLEX - Remove the CONTEXT CMAS from a CICSplex definition when the MPSTATE is NOTCONNECTED. Note that if a connection is established to the MP at a future date, and the MP is valid, then the MP will reinstall the CICSplex into the CONTEXT CMAS. Additionally, CPBI has been updated to issue an exception trace if it encounters invalid control blocks when processing a GET for CICSPLEX resource table records. The trace will have a debug text of "BCPXXCP" and a trace point ID of 8. After issuing the trace, CPBI will continue processing, ensuring that all valid CICSPLEX records are returned to the caller.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM26587
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
50M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-11
Closed date
2011-01-21
Last modified date
2011-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM28230 UK64126
Modules/Macros
CMASPLEX DYU0MOMB EYUA2452 EYUCCPBP EYUC2452 EYUEA1W4 EYUE2452 EYUKA1W4 EYUL2452 EYUP2452 EYUQCCPD EYUQCPBP EYURCCPD EYURCPBP EYUR2452 EYUSA1W4 EYUTRCOM EYUT2452 EYUYCCPD EYUYCPBP EYUY2452 EYUZCCPD EYUZCPBP EYU0CCPD EYU0CPBI EYU0CPBP EYU0MOMB EYU9CMPU EYU9CMP3 EYU9CMP4 EYU9CMRU EYU9CMR3 EYU9CMR4
SC34685003 | SC34684203 | SC34683903 |
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R50M PSY UK64126
UP11/02/16 P F102
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":"3.2","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":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 March 2011