In attempting to connect the specified CMASs to each other, CICSPlex® SM determined that both CMASs were considered the maintenance point for the specified CICSplex. This occurs when the same CICSplex is manually created under two different CMASs. The CMAS under which a CICSplex is created becomes its maintenance point, and each CICSplex can have only one.
The communications link between the two CMASs is terminated.
If you want the CMASs to communicate with each other, the CICSplex must be defined to only one of them. Use the CPLEXDEF view to remove the CICSplex definition from one of the CMASs and then restart that CMAS.
Console, job log, EYULOG
EYU0CPSI
The Connection Services subcomponent was not able to import network topology information about the specified CMAS, where:
The network topology import process terminates.
Stop and restart the CMAS where the failure occurred, as indicated by the APPLID stamp that precedes the message.
Console, job log, EYULOG
EYU0CPTI
In attempting to connect the specified CMASs to each other, CICSPlex SM determined that a MAS of the same name was active for each CMAS. The names of CICS® systems to be managed by CICSPlex SM must be unique within a CICSplex. Because both CMASs are participating in the management of the specified CICSplex, duplicate MAS names are not allowed.
The duplicate MASs are terminated. The CICS systems continue to run normally, but they are not known to CICSPlex SM. The connection between the CMASs is completed.
Change one of the MAS names in the appropriate CICS system startup JCL. Then stop and restart both CICS systems.
Console, job log, EYULOG
EYU0CPMI
The Connection Services long running task (LRT) is being initialized.
Initialization of the LRT continues.
None
EYULOG
EYU0CPLT
The Connection Services long running task (LRT) has been successfully initialized.
The initialization of Connection Services subcomponent.
None
EYULOG
EYU0CPLT
The Connection Services long running task (LRT) is being terminated.
Termination of the LRT continues.
None
EYULOG
EYU0CPLT
The Connection Services long running task (LRT) has been terminated.
Termination of the Connection Services subcomponent continues.
None.
EYULOG
EYU0CPLT
The Connection Services long running task (LRT) encountered an error from which it could not recover.
The LRT terminates. CICSPlex SM may continue running without the services of the LRT.
Stop and restart the CMAS where the failure occurred, as indicated by the APPLID stamp that precedes the message. If the problem persists, collect any exception trace records, the job log, and CICS or MVS™ dump output, if available, and contact your IBM® Support Center.
Console, job log, EYULOG
EYU0CPLT
The Connection Services long running task (LRT) encountered an error, but was able to recover and continue processing.
Connection Services processing continues. A user trace record is written to the CICS trace data set.
If the problem persists, collect the exception trace records and the job log, and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CPLT
An attempt to perform repository synchronization for the specified CICSplex and CMAS failed, where:
This CMAS will issue an exception trace, request an SVCdump, and issue this message. The CMAS which could not be synchronized is then removed from the CMAS network.
Collect the CICS auxtrace data sets, the SVCdump, the job output from this CMAS, and a backup copy of this CMAS's data repository. Note that message EYUCP0011E is issued in the CMAS that was isolated. Refer to the description of that message for additional documentation to collect.
To recover from the problem, the isolated CMAS and all MASs connected to it should be terminated.Then restart the isolated CMAS. After it successfully performs repository synchronization with the other CMASs in the network (EYULOG messages EYUCP0203I and EYUCP0204I), its MASs can be restarted.
To determine the cause of the problem, contact your IBM Support Center with the documentation collected.
Console, job log, EYULOG
EYU0CPLT
The data repository of the CMAS that issued this message could not be synchronized for one or more CICSplexes, where:
This CMAS issues an exception trace, request an SVC dump, and issues this message. This CMAS is then removed from the CMAS network.
All the connections to the CMAS are terminated.
Collect the CICS auxtrace data sets, the SVCdump, the job output from this CMAS, and a backup copy of this CMAS's data repository. If the requesting CMAS is not the local CMAS, message EYUCP0010E is also issued in the requesting CMAS. Refer to the description of that message foradditional documentation to collect. If the requesting CMAS is the local CMAS, message EYUXD0029E is also issued in the local CMAS, and no additional documentation needs to be collected.
To recover from the problem, the local CMAS and all MASsconnected to it should be terminated. The local CMAS should then be restarted. After it successfully performs repository synchronization with the other CMASs in the network (EYULOG messages EYUCP0203I and EYUCP0204I), its MASs can be restarted.
To determine the cause of the problem, contact your IBM Support Center with the documentation collected.
Console, job log, EYULOG
EYU0CPRL
In attempting to connect the specified CMASs to each other, CICSPlex SM determined that the connecting CMAS is running a later release of the product than the maintenance point CMAS, where:
The maintenance point CMAS must always be running the most current release of any CMAS actively involved in managing the CICSplex.
The CMAS running the later release of CICSPlex SM is removed from active management of the CICSplex. All definitions related to the CICSplex are deleted from the later level CMAS's data repository.
Upgrade the maintenance point CMAS to the most current release of CICSPlex SM. Bring up both CMASs. When both CMASs have connected, re-add the non-maintenance point CMAS to the CICSplex.
For details on migrating from one release of CICSPlex SM to another, see CICS Transaction Server for z/OS® Migration from CICS TS Version 2.3.
Console, job log, EYULOG
EYU0CCPA, EYU0CPAI, EYU0CPSI
In attempting to connect the CMASs in a network, CICSPlex SM determined that the specified CMASs are running incompatible releases of the product, where:
The CMAS running the later release of CICSPlex SM shuts down.
If you want to include the CMAS identified as cmasid1 in a network with more current CMASs, you must upgrade that CMAS to a supported release of CICSPlex SM.
For a list of supported releases and details on migrating from one release to another, see CICS Transaction Server for z/OS Migration from CICS TS Version 2.3.
Console, job log, EYULOG
EYU0CPCI, EYU0CPDG
While attempting to remove a CICSPlex SM connection between this CMAS and another CMAS, a failure has occured, where:
The connection is terminated, but all appropriate cleanup may not have occured. This may result in errors when the link is re-established.
Collect all job output and AUXTRACE datasets from both CMASs. When the link is re-established, ensure that each CMAS JOINs the MASs of the other CMAS. If not, restarting either CMAS should correct the problem. If the problem persists, contact your IBM Support Center.
Console, job log, EYULOG
EYU0CPRL
A network topology exchange has occurred, but the definition of CMAS cmas, which was received, specifies an APPLID or SYSID that conflicts with an existing CMAS.
The CMAS cmas is not added to the issuing CMAS's network topology.
Check the CMTCMDEFs of other CMASs to ensure that the definitions are correct and that all CMAS names, APPLIDs and SYSIDs are unique.
Console, job log, EYULOG
EYU0CPCI
This CMAS is communicating with CMAS nodename which has one or more resource tables at an earlier version or level of service where:
The capability of a CMAS is determined by its service level or CICSPlex SM release and version.
This CMAS might perform additional processing during transmissions with CMAS nodename because of the need to convert one or more of its resource tables to the earlier version in use by CMAS nodename.
No action is needed. This message is for information only.
EYULOG
EYU0CPUC
CMAS nodename has at least one resource table at a later version or service level and at least one resource table at an earlier version or service level than this CMAS where:
The capability of a CMAS is determined by its service level or CICSPlex SM release and version.
This CMAS cannot determine whether it has the reponsibility to convert resource tables to an earlier version during transmissions between itself and CMAS nodename, or whether CMAS nodename will do so.
This message might be followed by mesage EYUCP0018E which can give more information.
The request to establish a communications link is denied.
Correct the startup JCL for either this CMAS or CMAS nodename. The service level or CICSPlex SM release and version should either be the same for both CMAS systems, or one of the CMAS systems should be at a later level of service or version of CICSPlex SM.
Console, job log, EYULOG
EYU0CPUC
CMAS nodename has a version of resource table objname that does not match the version in use by this CMAS where:
This message can be issued for up to two resource table types.
See message EYUCP0017E for more information.
See message EYUCP0017E for more information.
Console, job log, EYULOG
EYU0CPUC
This CMAS has had to convert one or more of its resource tables to an earlier version during trasmissions between itself and CMAS nodename where:
The additional processing is no longer performed.
Processing continues
No action is needed. The message is for information only..
EYULOG
EYU0CPUC
This CMAS is communicating with MAS nodename which has one or more resource tables at an earlier version or level of service where:
The capability of a MAS is determined by its service level or CICSPlex SM release and version.
This CMAS might perform additional processing during transmissions with MAS nodename because of the need to convert one or more of its resource tables to the earlier version in use by MAS nodename.
No action is needed. This message is for information only.
EYULOG
EYU0CPAM
This CMAS has had to convert one or more of its resource tables to an earlier version during trasmissions between itself and MAS nodename where:
The additional processing is no longer performed.
Processing continues
None. The message is for information only..
EYULOG
EYU0CPAM
In attempting to connect the specified CMASs CICSPlex SM determined that the maintenance point is at an earlier service level of CICSPlex SM than the connecting CMAS where:
The maintenance point CMAS must run at the same or a later service level of CICSPlex SM than a connecting CMAS for a particular CICSPlex. The capability of a CMAS is determined by service level.
The connecting CMAS, which is running a later service level of CICSPlex SM is isolated from the CICSPlex.
If you want to include the CMAS identified as cmasid1 in a network with more current CMASs you must upgrade that CMAS to the same or or a later service level of CICSPlex SM.
EYULOG
EYU0CPAI, EYU0CPSI
A communications error has occurred while this CMAS was performing repository synchronization with another CMAS, resulting in the isolation from the CMAS network of the other CMAS, where
This CMAS issues an exception trace, request an SVCdump, and issue this message. The CMAS which could not be synchronized is then removed from the CMAS network.
Collect the CICS auxtrace data sets, the SVCdump, and the job output from this CMAS. Note that message EYUCP0024E is issued in the CMAS that was isolated. Refer to the description of that message for additional documentation to collect.
To recover from the problem restart the isolated CMAS.
To determine the cause of the problem, contact your IBM Support Center with the documentation collected.
Console, job log, EYULOG
EYU0CPLT
A communications error has occurred while this CMAS was performing repository synchronization with another CMAS, resulting in the isolation from the CMAS network of this CMAS, where:
This CMAS issues an exception trace, request an SVC dump, and issue this message. This CMAS is then removed from the CMAS network.
Collect the CICS auxtrace data sets, the SVC dump, and the job output from this CMAS. Note that message EYUCP0023E is issued in the CMAS that requested the isolation. Refer to the description of that message for additional documentation to collect.
To recover from the problem restart this CMAS.
To determine the cause of the problem, contact your IBM Support Center with the documentation collected.
Console, job log, EYULOG
EYU0CPLT
While this CMAS was processing data repository updates that were shipped from the maintenance point CMAS for a CICSplex, an unrecoverable error was encountered, where:
This CMAS issues an exception trace, this message and message EYUCP0011E. This CMAS is then removed from the CMAS network.
Refer to the description of message EYUCP0011E for guidance.
Console, job log, EYULOG
EYU0XDRS
The local CMAS is now directly connected to a CMAS, where:
This message is issued.
None
EYULOG
EYU0CPDG
The local CMAS is now indirectly connected to a CMAS, where:
This message is issued.
None
EYULOG
EYU0CPDG
The local CMAS no longer has a connection, where:
This message is issued.
None
EYULOG
EYU0CPDG, EYU0CPSL
You are approaching the maximum number of Managed Region features allowed for the specified type. This message appears when you have exceeded 90 percent active, where:
None.
Check your IBM license agreement or a current billing statement for the number of copies of the Managed Region feature licensed by your enterprise. The number of CICS systems you intend to manage concurrently cannot exceed the number of Managed Region features you have licensed.
If the number of Managed Region features you have licensed appears to be sufficient, then make sure that their distribution among your CICSplexes matches your actual CICSplex configurations. Use the CPLEXDEF view (described in the CICSPlex System Manager Administration manual) to review the number of managed regions assigned to each CICSplex.
If you have not licensed a sufficient number of Managed Region features to support your enterprise, then do one of the following:
Console, EYULOG
EYU0CPCM
You have exceeded the maximum number of Managed Region features allowed for the specified type, where:
None.
Check your IBM license agreement or a current billing statement for the number of copies of the Managed Region feature licensed by your enterprise. The number of CICS systems you intend to manage concurrently cannot exceed the number of Managed Region features you have licensed.
If the number of Managed Region features you have licensed appears to be sufficient, then make sure that their distribution among your CICSplexes matches your actual CICSplex configurations. Use the CPLEXDEF view (described in the CICSPlex System Manager Administration manual) to review the number of managed regions assigned to each CICSplex.
If you have not licensed a sufficient number of Managed Region features to support your enterprise, then you should:
Console, EYULOG
EYU0CPCM
You have greatly exceeded the maximum number of Managed Region features allowed, where:
None.
Check your IBM license agreement or a current billing statement for the number of copies of the Managed Region feature licensed by your enterprise. The number of CICS systems you intend to manage concurrently cannot exceed the number of Managed Region features you have licensed.
If the number of Managed Region features you have licensed appears to be sufficient, then make sure that their distribution among your CICSplexes matches your actual CICSplex configurations. Use the CPLEXDEF view (described in the CICSPlex System Manager Administration manual) to review the number of managed regions assigned to each CICSplex.
If you have not licensed a sufficient number of Managed Region features to support your enterprise, then you should:
Console, EYULOG
EYU0CPCM
The CMAS known as cmas1 has been successfully identified to the CMAS known as cmas2. cmas1 can now participate in the CMAS network.
None.
None.
EYULOG
EYU0CPAC
A network topology change has been initiated by the specified CMAS. This message appears only if trace level 23 (for the Communications component) is set to YES in the CMAS.
None.
None.
EYULOG
EYU0CPTI
A network topology change that was initiated by the specified CMAS has been successfully completed. This message appears only if trace level 23 (for the Communications component) is set to YES in the CMAS.
None.
None.
EYULOG
EYU0CPTI
The data repository for the specified CMAS is being synchronized with the data repository of the CMAS that issued this message. The data repositories for all CMASs that participate in a network are synchronized to contain the same network topology information.
None.
None.
EYULOG
EYU0CPLT
The data repository for the specified CMAS has been successfully synchronized with the data repository of the CMAS that issued this message.
None.
None.
EYULOG
EYU0CPLT
The Connection Services long running task (LRT) encountered an error while trying to synchronize the repository of the CMAS that issued the message with the CMAS (cmasname).
The CMAS which issues the message continues processing. However the CMAS (cmasname) may no longer be able to accept Topology Joins or WLM requests.
Check if other EYUCPxxxx messages are issued, by the CMAS that issued this message or CMAS (cmasname), relating to reasons for the repository synchronization failure. For example, EYUCP0010E, EYUCP0011E, EYUCP0022E, EYUCP0023E, and EYUCP0024E. Perform the actions indicated by these additional messages. If no further information is available, collect any exception trace records and the job logs of both CMASs, and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CPLT
During repository synchronization processing between the current CMAS and another CMAS, the current CMAS determined that the data repository (EYUDREP) records were incomplete for a CICSplex for which it is the maintenance point (MP) CMAS, where:
This message and a trace record are issued. Repository synchronization continues without processing the CICSplex that is in error.
An error occurred when the CICSplex was either added or removed, resulting in incomplete EYUDREP records for the CICSplex. Check the current and previous job logs for this CMAS to determine if any error messages were issued. If any error messages are found, collect the messages, the unformatted auxtrace data sets from that run of the CMAS (if available), and a backup copy of the CMAS's EYUDREP, then contact your IBM support center.
To resolve the error message, enter the TSO end user interface (EUI) under the context of the CMAS, and use the CPLEXDEF view REMove action to remove the CICSplex. If the CICSplex is required, CREate it anew after removing it.If this does not resolve the problem, collect the job output, unformatted CICS auxtrace data sets from the current execution of the CMAS, and a backup copy of the CMAS's EYUDREP, then contact your IBM support center.
Console, job log, EYULOG
EYU0CPLT
The CMAS that issues this message is the maintenance point (MP) CMAS for CICSplex plexname.
During a data repository synchronization for CICSplex plexname with CMAS cmasname the maintenance point CMAS has determined that the CICSplex definition in CMAS cmasname must be deleted. The CICSplex delete was not possible as MASes within CICSplex plexname were directly connected (or were in the process of connecting) to CMAS cmasname at the time of the data repository synchronization attempt.
action may be 'deleted' or redefined':
Message EYUCP0010E will be issued and CMAS cmasname will be isolated.
The MAS agents that connect directly to CMAS cmasname need to be stopped and CMAS cmasname will need to be restarted in order for the data repository synchronization to complete.
To identify the MAS agents that were connected (or trying to connect), review the CMAS cmasname EYULOG for the following messages:
To stop the CICSPlex SM MAS agent in these MASes either use the COSH transaction in each MAS or if the MASes are connected to the non-MP CMAS, the MAS view STOp action (or WUI/API equivalent). Alternatively, shut down the MAS.
Once the MAS agents have been stopped, restart CMAS cmasname to retry the data repository synchronization.
When the data repository synchronization has completed, restart the previously stopped MAS agents with the COLM transaction, or restart the MASes.
Console, job log, EYULOG
EYU0CPLT