EYUTRnnnn messages are issued by the Topology Services agent code that provides an interface to the NetView® Resource Object Data Manager (RODM) facility. These messages are issued to the destination defined by the NetView DEFAULTS or OVERRIDE command. The destination can be the NetView network log, the MVS™ system log, or both, depending on how the NETLOG= and SYSLOG= options are specified on those commands. For more information on the DEFAULTS and OVERRIDE commands, see the NetView Operation book.
The Topology Services agent for NetView is in the specified phase of initialization or termination, where:
Processing continues.
None.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView could not be initialized, where:
This message is preceded by other EYUTRnnnn messages that indicate why the initialization process failed.
The Topology Services interface to NetView terminates.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, and contact your IBM® Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView was contacted by the specified CMAS and the connection is in the specified phase, where:
When contact is initiated by a CMAS, Topology Services builds RODM data objects for the CMAS. When contact is terminated with a CMAS, Topology Services deletes all the RODM data objects it built for the CMAS.
None.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView was contacted by the specified CMAS, but was not able to establish communications, where:
This message is preceded by other EYUTRnnnn messages that indicate why the CMAS contact processing failed.
RODM data objects are not built for the specified CMAS.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, and the CMAS log. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView issued a program-to-program call, but NetView returned an abnormal response, where:
The Topology Services interface to NetView terminates.
For a description of the NetView return code, see the NetView Customization: Using Assembler book. If the cause of the problem is not apparent, collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, and contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView issued a NetView service call, but NetView returned an abnormal response, where:
The Topology Services interface to NetView terminates.
For a description of the NetView return code, see the NetView Customization: Using Assembler book. If the cause of the problem is not apparent, collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, and contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView issued an Environment Services System Services (ESSS) call, but ESSS returned an abnormal response, where:
The Topology Services interface to NetView terminates.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, and contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView made initial contact with the specified CMAS. However, the CMAS is running a different release of CICSPlex SM than the Topology Services agent, where:
RODM data objects are not built for the specified CMAS.
If you want the specified CMAS to participate in the RODM interface, it must be running the same release of CICSPlex SM as the CMAS that has a connection to RODM.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services agent for NetView made initial contact with the specified CMAS. However, the Topology Services agent can communicate with only 16 CMASs at a time and it has reached that limit, where:
RODM data objects are not built for the specified CMAS.
None.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
During initialization, the Topology Services agent for NetView detected a problem with the NetView startup parameter member, where:
The Topology Services interface to NetView does not initialize.
Make sure the NetView startup parameter member name is correctly specified and that the member exists in a library in the DSIPARM data set concatenation. Then, you must stop the Topology Services interface to NetView by issuing these NetView commands:
STOP OP=autotask,FORCE
STOP UNCOND=autotask
You can restart the interface by issuing this NetView command:
AUTOTASK OPID=autotask
In both cases, autotask is the name you assigned to the automation task for CICSPlex SM.
For more information about specifying a startup parameter member, see the NetView Installation and Administration Guide.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
During initialization, the Topology Services agent for NetView detected a problem with the contents of the NetView startup parameter member, where:
The Topology Services interface to NetView does not initialize.
Make sure the NetView startup parameter member is correctly defined. Then, you must stop the Topology Services interface to NetView by issuing these NetView commands:
STOP OP=autotask,FORCE
STOP UNCOND=autotask
You can restart the interface by issuing this NetView command:
AUTOTASK OPID=autotask
In both cases, autotask is the name you assigned to the automation task for CICSPlex SM.
For more information about specifying a startup parameter member, see the NetView Installation and Administration Guide.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
During initialization, the Topology Services agent for NetView detected that a required keyword is not specified in the NetView startup parameter member, where:
The Topology Services interface to NetView does not initialize.
Make sure the NetView startup parameter member is correctly defined and that all required keywords are specified. Then, you must stop the Topology Services interface to NetView by issuing these NetView commands:
STOP OP=autotask,FORCE
STOP UNCOND=autotask
You can restart the interface by issuing this NetView command:
AUTOTASK OPID=autotask
In both cases, autotask is the name you assigned to the automation task for CICSPlex SM.
For more information about specifying a startup parameter member, see the NetView Installation and Administration Guide.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
During initialization, the Topology Services agent for NetView could not find the required trace file, EYUTRTC, where:
The Topology Services interface to NetView does not initialize.
Allocate the EYUTRTC trace file to the NetView startup job. Then, you must stop the Topology Services interface to NetView by issuing these NetView commands:
STOP OP=autotask,FORCE
STOP UNCOND=autotask
You can restart the interface by issuing this NetView command:
AUTOTASK OPID=autotask
In both cases, autotask is the name you assigned to the automation task for CICSPlex SM.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services REXX EXEC, EYU#0001, detected that the specified RODM subsystem is not available, where:
The Topology Services interface to NetView terminates.
Make sure the specified RODM subsystem is available. Then, you must stop the Topology Services interface to NetView by issuing these NetView commands:
STOP OP=autotask,FORCE
STOP UNCOND=autotask
You can restart the interface by issuing this NetView command:
AUTOTASK OPID=autotask
In both cases, autotask is the name you assigned to the automation task for CICSPlex SM.
For a description of the RODM return and reason codes, see the NetView RODM Programming Guide.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services REXX EXEC, EYU#0001, received an unexpected response from the last MultiSystem Manager access to RODM, where:
The Topology Services interface to NetView terminates.
For a description of the RODM return and reason codes, see the NetView RODM Programming Guide. If the cause of the problem is not apparent, collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, the CMAS log, and the EYUTRTC trace data set. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services REXX EXEC, EYU#0001, received invalid data from the NetView agent code, where:
The Topology Services interface to NetView terminates.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, the CMAS log, and the EYUTRTC trace data set. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU#0001
The Topology Services REXX EXEC, EYU#0001, attempted to use the REXX EXECIO function to write data to the EYUTRTC trace file, but the request failed, where:
The EYU#0001 REXX EXEC was attempting to write trace entries to EYUTRTC for the diagnosis of another problem. Additional EYUTRnnnn messages are produced. In addition, REXX messages are produced that may explain the problem.
Review the messages produced by REXX to determine the cause of the problem. For a description of the REXX return code, see the TSO/E Version 2 REXX/MVS Reference.
If the problem persists, collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, the CMAS log, and the EYUTRTC trace data set. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU#0001
The Topology Services REXX EXEC, EYU#0001, issued the NetView GETTOPO HOSTONLY command during initial contact with a CMAS, but the command returned a nonnormal response, where:
The Topology Services interface to NetView terminates.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, the CMAS log, and the EYUTRTC trace data set. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services REXX EXEC, EYU#0001, could not locate the specified CMAS after issuing the GETTOPO HOSTONLY command, where:
The Topology Services interface to NetView terminates.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, the CMAS log, and the EYUTRTC trace data set. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU9T140
The Topology Services REXX EXEC, EYU#0001, issued the NetView WAIT command, but the command returned a nonnormal response, where:
The Topology Services interface to NetView terminates.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, the CMAS log, and the EYUTRTC trace data set. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU#0001
The Topology Services REXX EXEC, EYU#0001, issued a REXX command that caused a syntax error, where:
The Topology Services interface to NetView terminates.
For a description of the REXX return code, see the TSO/E Version 2 REXX/MVS Reference.
Collect the NetView network log or MVS system log, depending on where the EYUTRnnnn messages appear, the CMAS log, and the EYUTRTC trace data set. Then, contact your IBM Support Center.
As defined by NetView DEFAULTS or OVERRIDE command.
EYU#0001