EYUTSnnnn messages

EYUTS0001I
Topology event for sysname Initiated - APPLID (applid) CICSplex (plexname)
Explanation:

Topology Services has begun processing a communications endpoint event for the specified CICS® system, where:

event
Identifies the event as one of the following:
Connect
A physical connection between the MAS (CICS system) and its maintenance point CMAS.
Join
A logical connection between the MAS (CICS system) and another CMAS.
Disconnect
A disconnection of the MAS (CICS system) from its maintenance point CMAS.
sysname
Identifies the MAS name for the CICS system.
applid
Identifies the APPLID of the CICS system.
plexname
Identifies the CICSplex the CICS system is being processed for.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSSC, EYU0TSSE, EYU0TSSJ.

EYUTS0002E
Topology event for sysname Failed - APPLID (applid) CICSplex (plexname)
Explanation:

A communications endpoint event that Topology Services was processing for the specified CICS system failed to complete, where:

event
Identifies the event as one of the following:
Connect
A physical connection between the MAS (CICS system) and its maintenance point CMAS.
Join
A logical connection between the MAS (CICS system) and another CMAS.
Disconnect
A disconnection of the MAS (CICS system) from its maintenance point CMAS.
sysname
Identifies the MAS name for the CICS system.
applid
Identifies the APPLID of the CICS system.
plexname
Identifies the CICSplex the CICS system is being processed for.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0TSCI, EYU0TSMJ, EYU0TSSC, EYU0TSSE, EYU0TSSJ

EYUTS0003I
Topology event for sysname Complete - APPLID (applid) CICSplex (plexname)
Explanation:

Topology Services has completed a communications endpoint event for the specified CICS system, where:

event
Identifies the event as one of the following:
Connect
A physical connection between the MAS (CICS system) and its maintenance point CMAS.
Join
A logical connection between the MAS (CICS system) and another CMAS.
Disconnect
A disconnection of the MAS (CICS system) from its maintenance point CMAS.
sysname
Identifies the MAS name for the CICS system.
applid
Identifies the APPLID of the CICS system.
plexname
Identifies the CICSplex the CICS system is being processed for.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSSC, EYU0TSSE, EYU0TSSJ

EYUTS0004I
Topology found sysname Already Active.
Explanation:

Topology Services could not process a communications endpoint event for the specified CICS system because the MAS agent was already active.

System action:

Processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0TSSC, EYU0TSSJ, EYU3TSIM

EYUTS0005E
Topology type Data Structures Compromised.
Explanation:

The Topology Services data cache structures for a CICSplex or CICS system are no longer reliable, where:

type
Identifies the type of data structures that are in error as either CICSplex or Scope.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0TSFD

EYUTS0006I
Topology event of CICSPlex plexname Initiated.
Explanation:

Topology Services has begun processing a CICSplex Change event for a CMAS, where:

event
Identifies the event as one of the following:
  • Add
  • Update
  • Remove
plexname
Identifies the affected CICSplex.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSPA, EYU0TSPD, EYU0TSPU

EYUTS0007E
Topology event of CICSPlex plexname Failed.
Explanation:

A CICSplex Change event that Topology Services was processing for a CMAS failed to complete, where:

event
Identifies the event as one of the following:
  • Add
  • Update
  • Remove
plexname
Identifies the affected CICSplex.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0TSPA, EYU0TSPD, EYU0TSPU

EYUTS0008I
Topology event of CICSPlex plexname Complete.
Explanation:

Topology Services has completed a CICSplex Change event for a CMAS, where:

event
Identifies the event as one of the following:
  • Add
  • Update
  • Remove
plexname
Identifies the affected CICSplex.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSPA, EYU0TSPD, EYU0TSPU

EYUTS0009E
CICS System Group grpname Not Found.
Explanation:

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.

System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0TSFD, EYU0TSGR, EYU0TIBS

EYUTS0010E
Unable to event sysname. CICSPlex plexname Unknown.
Explanation:

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:

event
Identifies the event as one of the following:
Connect
A physical connection between the MAS (CICS system) and its maintenance point CMAS.
Join
A logical connection between the MAS (CICS system) and another CMAS.
Disconnect
A disconnection of the MAS (CICS system) from its maintenance point CMAS.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0TSSC, EYU0TSSJ, EYU0TSST

EYUTS0011E
Unable to event sysname. CICS System sysname Unknown.
Explanation:

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:

event
Identifies the event as one of the following:
Connect
A physical connection between the MAS (CICS system) and its maintenance point CMAS.
Join
A logical connection between the MAS (CICS system) and another CMAS.
Disconnect
A disconnection of the MAS (CICS system) from its maintenance point CMAS.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0TSSC, EYU0TSSJ, EYU0TSST

EYUTS0012E
CICSPlex plexname Not Found.
Explanation:

A requested topology action could not be processed because the specified CICSplex, which is the current context, is not known to Topology Services.

System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0TSFD, EYU0TSGA, EYU0TSGR, EYU0TSPR, EYU0TSPU, EYU0TSSA, EYU0TSSR, EYU0TSSU

EYUTS0013E
CICS System sysname Not Found.
Explanation:

A requested topology action could not be processed because the specified CICS system, which is the current scope, is not known to Topology Services.

System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0TSGR, EYU0TSSR

EYUTS0014E
Unable to Connect sysname. No Resource Topology Collected.
Explanation:

An attempt to connect the specified CICS system failed because the required resource topology data was not provided by the MAS.

System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0TSRA

EYUTS0015I
Topology event of CICS System sysname Initiated.
Explanation:

Topology Services has begun processing a CICS system Change event for a CMAS, where:

event
Identifies the event as one of the following:
  • Add
  • Update
  • Remove
sysname
Identifies the affected CICS system.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSSA, EYU0TSSD, EYU0TSSU

EYUTS0016E
Topology event of CICS System sysname Failed.
Explanation:

A CICS system Change event that Topology Services was processing for a CMAS failed to complete, where:

event
Identifies the event as one of the following:
  • Add
  • Update
  • Remove
sysname
Identifies the affected CICS system.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0TSSA, EYU0TSSD, EYU0TSSU

EYUTS0017I
Topology event of CICS System sysname Complete.
Explanation:

Topology Services has completed a CICS system Change event for a CMAS, where:

event
Identifies the event as one of the following:
  • Add
  • Update
  • Remove
sysname
Identifies the affected CICS system.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSSA, EYU0TSSD, EYU0TSSU

EYUTS0018I
Topology event of System Group grpname Initiated.
Explanation:

Topology Services has begun processing a CICS system group Change event for a CMAS, where:

event
Identifies the event as one of the following:
  • Add
  • Remove
grpname
Identifies the affected CICS system group.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSGA, EYU0TSGD

EYUTS0019E
Topology event of System Group grpname Failed.
Explanation:

A CICS system group Change event that Topology Services was processing for a CMAS failed to complete.

event
Identifies the event as one of the following:
  • Add
  • Remove
grpname
Identifies the affected CICS system group.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0TSGA, EYU0TSGD

EYUTS0020I
Topology event of System Group grpname Complete.
Explanation:

Topology Services has completed a CICS system group Change event for a CMAS, where:

event
Identifies the event as one of the following:
  • Add
  • Remove
grpname
Identifies the affected CICS system group.
System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0TSGA, EYU0TSGD

EYUTS0021E
Topology event of CICS System sysname failed due to a type Time-Out.
Explanation:

An attempt to connect or join the specified CICS system has failed, where:

event
Identifies the event being attempted as either Connect or Join.
sysname
Identifies the CICS system.
type
Identifies the type of time-out condition that occurred as one of the following:
Start of change
Resource Topology Collection
A request for resource topology timed out during the connection of a local MAS.
Topology Resource Map Get
A request to get topology resource maps from a CMAS timed out during the joining of a MAS.
End of change
System action:

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.

User response:

Shut down the affected CICS system and then restart it.

Destination:

Console, job log, EYULOG

Module:

EYU0TSMJ, EYU0TSRA, EYU0TSSC

EYUTS0023E
Topology connect of CICS system sysname not initiated. CSYSDEF and MAS SysIds mismatch. APPLID (applid) CICSplex (plexname)
Explanation:

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:

sysname
Identifies the MAS name for the CICS system.
applid
Identifies the APPLID of the CICS system.
plexname
Identifies the CICSplex the CICS system is being processed for.
System action:

Processing continues, however the CICS system cannot be managed by CICSPlex SM.

User response:

Either update the CICS system definition, or specify the correct SYSIDNT in the SIT.

Destination:

Console, job log, EYULOG

Module:

EYU0TIST

EYUTS0024I
Topology connect for mas waiting for BAS to complete initialization for CICSplex plexname
Explanation:

During Topology connect processing for a MAS, where:

mas
is the name of the MAS.

it was determined that resources need to be installed by BAS, but BAS has not yet initialized data structures for the CICSplex, where:

plexname
is the name of the CICSplex.
System action:

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).

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0TSCI

Start of change
EYUTS0025I
Topology Connect|Join for mas terminated due to Disconnect request - APPLID (applid) CICSplex (plexname)
Explanation:

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.

System action:

The Connect or Join request is terminated.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0TSCI , EYU0TSMJ , EYU0TSSC , EYU0TSSJ

End of change
Start of change
EYUTS0026I
User userid has issued the FORCEDISCON action for MAS masname - APPLID (applid) CICSplex (plexname).
Explanation:

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.

System action:

The ESSS connection for the MAS is terminated and this message is issued to document the requester of the action.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0TSUM

End of change
EYUTS0030I
Topology RODM Manager registered with NetView.
Explanation:

The Topology Services long running task (LRT) task has successfully registered with NetView® as a sender and receiver program.

System action:

Processing continues.

User response:

None.

Destination:

Job log

Module:

EYU0TIRT

EYUTS0031I
Receiver program for rodmname is active.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Job log, EYULOG

Module:

EYU0TIRT

EYUTS0032I
NetView subsystem is inactive. Will query again in 5 minutes.
Explanation:

The NetView subsystem is not currently active. Topology Services continues to query NetView at 5 minute intervals until the subsystem becomes active.

System action:

Processing continues.

User response:

None.

Destination:

Job log, EYULOG

Module:

EYU0TIRT

EYUTS0033I
NetView release does not support user requests.
Explanation:

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.

System action:

Topology Services processing continues. However, no RODM-related requests are accepted.

User response:

If you want to use the CICSPlex SM interface to RODM, you must upgrade to NetView 2.4 or later.

Destination:

Job log, EYULOG

Module:

EYU0TIRT

EYUTS0034I
Receiver program for rodmname is inactive or undefined. Will query again in 5 minutes.
Explanation:

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:

rodmname
Is the name of the RODM subsystem to be populated.

Topology Services continues to query NetView at 5 minute intervals until the receiver program becomes active.

System action:

Processing continues.

User response:

None.

Destination:

Job log, EYULOG

Module:

EYU0TIRT

EYUTS0035E
Topology RODM Manager NetView PPI request failed. Request type=nnnn, RC=rcode.
Explanation:

A Topology Services request was sent to the NetView program-to-program interface, but the request failed, where:

nnnn
Is a numeric identifier for the topology request that was issued.
rcode
Is the NetView return code.
System action:

The Topology Services interface to NetView terminates.

User response:

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.

Destination:

Job log, EYULOG

Module:

EYU0TIRT

EYUTS0036E
CMAS cmas at incompatible CPSM version. RODM reporting negated.
Explanation:

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:

cmas
Identifies the CMAS that was trying to contact Topology Services.
System action:

The specified CMAS is not known to the Topology Services agent for NetView. The CMAS cannot report to RODM on its resources.

User response:

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.

Destination:

Job log, EYULOG

Module:

EYU0TIRT

EYUTS0050I
plexname/sysname restype: resname state <status>
Explanation:

The operational state of the specified resource is being reported, where:

plexname
Is the name of the CICSplex.
sysname
Is the name of the CICS system where the resource is defined.
restype
Is the type of resource.
resname
Is the name of the resource.
status
Is the current operational state of the resource.

Resource status messages such as this are issued when the CICSPlex SM system parameter RESSTATUS(MSG) is specified in the CMAS startup job.

System action:

Processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0TREH

EYUTS0051I
plexname/sysname restype: resname state <status>
Explanation:

The operational state of the specified resource is being reported, where:

plexname
Is the name of the CICSplex.
sysname
Is the name of the CICS system where the resource is defined.
restype
Is the type of resource.
resname
Is the name of the resource.
status
Is the current operational state of the resource.

Resource status messages such as this are issued when the CICSPlex SM system parameter RESSTATUS(CONMSG) is specified in the CMAS startup job.

System action:

Processing continues.

User response:

None.

Destination:

Job log, console, EYULOG

Module:

EYU0TREH

EYUTS0060I
Topology ResMap Hardening long running task Initialization Complete
Explanation:

The topology services resource map hardening long running task has completed initialization.

System action:

Processing continues

User response:

None.

Destination:

EYULOG

Module:

EYU0TSMH

EYUTS0061I
Topology ResMap Hardening long running task Termination Complete
Explanation:

The topology services resource map hardening long running task has ended.

System action:

Processing continues

User response:

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.

Destination:

EYULOG

Module:

EYU0TSMH

EYUTS0062E
Topology ResMap Hardening long running task error
Explanation:

The topology services resource map hardening long running task has detected an error.

System action:

The topology services resource map hardening long running task attempts to continue. Start of changeAfter recovering from ten errors, if another error occurs, the task is terminated.End of change

User response:

Collect the CMAS trace records, job log and EYULOG, and contact your IBM support center.

Destination:

EYULOG

Module:

EYU0TSMH

Start of change
EYUTS0063E
Topology encountered an error processing a change to a CICS system group
Explanation:

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.

System action:

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
User response:

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.

Destination:

Console, job log

Module:

EYU0TSEC

End of change [[ Contents Previous Page | Next Page Index ]]