Topology Services has begun processing a communications endpoint event for the specified CICS® system, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSSC, EYU0TSSE, EYU0TSSJ.
A communications endpoint event that Topology Services was processing for the specified CICS system failed to complete, where:
Processing continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSCI, EYU0TSMJ, EYU0TSSC, EYU0TSSE, EYU0TSSJ
Topology Services has completed a communications endpoint event for the specified CICS system, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSSC, EYU0TSSE, EYU0TSSJ
Topology Services could not process a communications endpoint event for the specified CICS system because the MAS agent was already active.
Processing continues.
None.
EYULOG
EYU0TSSC, EYU0TSSJ, EYU3TSIM
The Topology Services data cache structures for a CICSplex or CICS system are no longer reliable, where:
Processing continues. A user trace record is written to the CICS trace data set.
Shut down the affected CMAS and then restart it. Examine the exception trace records to determine the cause of the problem. If the problem persists, collect the trace records and any related messages and contact your IBM® Support Center.
Console, job log, EYULOG
EYU0TSFD
Topology Services has begun processing a CICSplex Change event for a CMAS, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSPA, EYU0TSPD, EYU0TSPU
A CICSplex Change event that Topology Services was processing for a CMAS failed to complete, where:
Processing continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSPA, EYU0TSPD, EYU0TSPU
Topology Services has completed a CICSplex Change event for a CMAS, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSPA, EYU0TSPD, EYU0TSPU
A requested topology action could not be processed because the specified CICS system group, which is the current scope, is not known to Topology Services.
Processing continues. A user trace record is written to the CICS trace data set.
Make sure the CICS system group name was correctly specified. If the CICS system group is known to exist, examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSFD, EYU0TSGR, EYU0TIBS
A communications endpoint event for the specified CICS system could not be processed because the specified CICSplex, which is the context for the event, is not known to Topology Services, where:
Processing continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSSC, EYU0TSSJ, EYU0TSST
A communications endpoint event for the specified CICS system could not be processed because the CICS system, which is the scope for the event, is not known to Topology Services, where:
Processing continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSSC, EYU0TSSJ, EYU0TSST
A requested topology action could not be processed because the specified CICSplex, which is the current context, is not known to Topology Services.
Processing continues. A user trace record is written to the CICS trace data set.
Make sure the CICSplex name was correctly specified. If the CICSplex is known to exist, examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSFD, EYU0TSGA, EYU0TSGR, EYU0TSPR, EYU0TSPU, EYU0TSSA, EYU0TSSR, EYU0TSSU
A requested topology action could not be processed because the specified CICS system, which is the current scope, is not known to Topology Services.
Processing continues. A user trace record is written to the CICS trace data set.
Make sure the CICS system name was correctly specified. If the CICS system is known to exist, examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSGR, EYU0TSSR
An attempt to connect the specified CICS system failed because the required resource topology data was not provided by the MAS.
Processing continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSRA
Topology Services has begun processing a CICS system Change event for a CMAS, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSSA, EYU0TSSD, EYU0TSSU
A CICS system Change event that Topology Services was processing for a CMAS failed to complete, where:
Processing continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSSA, EYU0TSSD, EYU0TSSU
Topology Services has completed a CICS system Change event for a CMAS, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSSA, EYU0TSSD, EYU0TSSU
Topology Services has begun processing a CICS system group Change event for a CMAS, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSGA, EYU0TSGD
A CICS system group Change event that Topology Services was processing for a CMAS failed to complete.
Processing continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0TSGA, EYU0TSGD
Topology Services has completed a CICS system group Change event for a CMAS, where:
Processing continues.
None.
Console, job log, EYULOG
EYU0TSGA, EYU0TSGD
An attempt to connect or join the specified CICS system has failed, where:
The CICS system continues to execute, but it is not known to CICSPlex® SM. MAS agent code is active in the CICS system; however, because of the specified time-out failure, CICSPlex SM cannot manage the CICS system.
Shut down the affected CICS system and then restart it.
Console, job log, EYULOG
EYU0TSMJ, EYU0TSRA, EYU0TSSC
Topology services could not process a connect for the specified CICS system because the SYSIDNT specified in the CICS system definition does not match that specified for the SYSIDNT SIT parameter, where:
Processing continues, however the CICS system cannot be managed by CICSPlex SM.
Either update the CICS system definition, or specify the correct SYSIDNT in the SIT.
Console, job log, EYULOG
EYU0TIST
During Topology connect processing for a MAS, where:
it was determined that resources need to be installed by BAS, but BAS has not yet initialized data structures for the CICSplex, where:
Connect processing for the MAS will wait until BAS completes initialization of the CICSplex (EYULOG message EYUBI0005I) or the MAS initialization time expires (as specified by the MASINITTIME EYUPARM).
There should not be a need for user response unless the MAS connect fails. If the connect process fails because BAS initialization for the CICSplex (bracketed by EYULOG messages EYUBI0004I and EYUBI0005I) extends beyond the time allowed for the MAS to initialize (as specified by the MAS's MASINITTIME EYUPARM), then it may be necessary to increase the MASINITTIME EYUPARM for the MAS. If the connect process fails because BAS initialization for the CICSplex failed (message EYUBI0102E), the BAS failure should be pursued according to the comments for message EYUBI0102E.
Console, job log, EYULOG
EYU0TSCI
A Topology Connect or Join request is being terminated because a Disconnect request has been received for the MAS during the Connect or Join process.
The Connect or Join request is terminated.
The Disconnect request is due to the MAS being shutdown or the MAS agent being terminated. If this is not expected, review the job log for the MAS to determine the reason.
Console, job log, EYULOG
EYU0TSCI , EYU0TSMJ , EYU0TSSC , EYU0TSSJ
The specified user has successfully issued the MAS resource table FORCEDISCON action against the specified MAS. If the userid is *Internal*, then the action was generated as the result of internal CICSPlex SM processing.
The ESSS connection for the MAS is terminated and this message is issued to document the requester of the action.
None, unless the user is *Internal*. If so, to determine why the action was issued, collect the complete job output and auxtrace datasets from the MAS and the CMAS that issued this message, along with any dumps that might have been produced at this time by the MAS or CMAS, and contact your local IBM Support Center.
Console, job log, EYULOG
EYU0TSUM
The Topology Services long running task (LRT) task has successfully registered with NetView® as a sender and receiver program.
Processing continues.
None.
Job log
EYU0TIRT
Topology Services has determined that the CICSPlex SM NetView OS task receiver program (EYU9Tnnn) for the specified RODM subsystem is active, where rodmname is the name of the RODM subsystem to be populated.
Processing continues.
None.
Job log, EYULOG
EYU0TIRT
The NetView subsystem is not currently active. Topology Services continues to query NetView at 5 minute intervals until the subsystem becomes active.
Processing continues.
None.
Job log, EYULOG
EYU0TIRT
The release of NetView that was found to be active in the MVS™ image does not support the CICSPlex SM interface to NetView RODM. The CICSPlex SM interface requires NetView Version 2.4 or later.
Topology Services processing continues. However, no RODM-related requests are accepted.
If you want to use the CICSPlex SM interface to RODM, you must upgrade to NetView 2.4 or later.
Job log, EYULOG
EYU0TIRT
The CICSPlex SM OS task receiver program (EYU9Tnnn) for the specified RODM subsystem is either not currently active or is not defined to the NetView program-to-program interface (PPI), where:
Topology Services continues to query NetView at 5 minute intervals until the receiver program becomes active.
Processing continues.
None.
Job log, EYULOG
EYU0TIRT
A Topology Services request was sent to the NetView program-to-program interface, but the request failed, where:
The Topology Services interface to NetView terminates.
For a description of the NetView PPI return code, see the NetView Application Programming Guide. If the cause of the problem is not apparent, collect the CMAS job log and either the NetView network log or the MVS system log, depending on where NetView messages are issued. Then, contact your IBM Support Center.
Job log, EYULOG
EYU0TIRT
The specified CMAS attempted to make contact with the Topology Services agent for NetView. However, the CMAS is running a different release of CICSPlex SM than the Topology Services agent, where:
The specified CMAS is not known to the Topology Services agent for NetView. The CMAS cannot report to RODM on its resources.
If you want the specified CMAS to participate in the RODM interface, it must be running the same release of CICSPlex SM as the Topology Services agent.
Job log, EYULOG
EYU0TIRT
The operational state of the specified resource is being reported, where:
Resource status messages such as this are issued when the CICSPlex SM system parameter RESSTATUS(MSG) is specified in the CMAS startup job.
Processing continues.
None.
EYULOG
EYU0TREH
The operational state of the specified resource is being reported, where:
Resource status messages such as this are issued when the CICSPlex SM system parameter RESSTATUS(CONMSG) is specified in the CMAS startup job.
Processing continues.
None.
Job log, console, EYULOG
EYU0TREH
The topology services resource map hardening long running task has completed initialization.
Processing continues
None.
EYULOG
EYU0TSMH
The topology services resource map hardening long running task has ended.
Processing continues
None if CMAS is being shut down. If the CMAS is not being shut down, take the actions described by message EYUTS0062E, which should have been issued before this message.
EYULOG
EYU0TSMH
The topology services resource map hardening long running task has detected an error.
The topology services resource map hardening long running task
attempts to continue. After recovering from ten errors,
if another error occurs, the task is terminated.
Collect the CMAS trace records, job log and EYULOG, and contact your IBM support center.
EYULOG
EYU0TSMH
During the processing of an Add or Remove command, to add a CICS region to or remove a CICS region from a CICS system group, the CMAS encountered an error while performing the topology update for the change.
The data repository update is complete, but the topology updates, and any changes that the monitor, RTA, WLM, and BAS components need to make to support the change, have not been made.
A dump is also taken with a dump title similar to the following:
EYU0XZPT Dump,cmasjobn,cmasname,lpar,CMAS,TIST,
tasknum,TRAC,EYU0TSEC,date,time
Collect the dump, complete job output, and auxtrace data sets for the CMAS, and contact your IBM support center.
Message EYUXD0002E should be issued prior to this message, in the CMAS's job log, indicating which change was aborted by topology. If this change is required during the current run of the CMAS, the CMAS must be restarted. Topology will then properly process the request during CMAS initialization.
Console, job log
EYU0TSEC