EQQF013I EQQF015I
EQQF013I EXIT EQQUX009 IS NOT LOADED OR HAS BEEN DISABLED
Explanation: User exit EQQUX009 has not been loaded, or has abended previously. The operations scheduled to
run on a workstation which specifies a user-defined destination will not be routed.
System action: The operation status is set according to what is specified in the SUBFAILACTION keyword on the
JTOPTS initialization parameter.
User response: Issue a WSSTAT command, or use the workstation dialog, to vary the destination workstations
offline.
System programmer response: Investigate why EQQUX009 is not loaded. If a previous abend caused the exit to
be disabled, correct the error and stop/start the TME 10 OPC subsystem to get the exit reloaded.
EQQF014E THE EXTERNAL ROUTER QUEUE IS FULL. USER DESTINATION WILL BE SET TO OFFLINE
STATUS
Explanation: The external router queue is full. TME 10 OPC will set the destination to offline status and set the
corresponding operation to the status specified in the SUBFAILACTION keyword value in the JTOPTS initialization
statement.
System action: The current operation status is set according to what is specified in the SUBFAILACTION JTOPTS
parameter.
System programmer response: Investigate why the EQQUX009 exit is not processing.
EQQF015I XCF
TYPE
MEMBER
MEMBER
HAS LEFT THE GROUP.
REASON:
REASON
Explanation: The XCF link to
TYPE
with member name
MEMBER
has been disconnected. The
REASON
is either
that the linked TME 10 OPC address space terminated or the entire MVS/ESA system terminated.
System action: The transmission of data (such as event records) through the XCF link is postponed. The
transmission of data will resume when the XCF member rejoins the group.
Problem determination: If this message is not expected, review the message log (EQQMLOG) and the SYSLOG of
the linked TME 10 OPC
MEMBER
to determine the cause of the outage.
User response: Contact your system programmer.
System programmer response: This is an TME 10 OPC informational message.
If this message was expected and:
The
TYPE
indicated
CONTROLLER
and message EQQW070I was also issued when the controller was restarted,
you should consider increasing the size of the tracker's event data set.
The
TYPE
indicated
TRACKER
and message EQQZ035I was also issued when the tracker was restarted, you
should consider increasing the size of the ECSA buffer (SYS1.PARMLIB(IEFSSN
xx
)).
104 TME 10 OPC Messages and Codes