EQQE102W EQQE104E
EQQE102W PULSE LOST FROM TRACKER
SUBS
AT DESTINATION
DEST
Explanation: This message indicates that handshake processing, the frequency for which is determined by the
PULSE keyword of the ROUTOPTS statement, has terminated for the indicated Tracker system. When handshake
processing is in use, each connected Tracker system sends an identification (ID) event to the controller at the
specified interval. If the controller detects that a Tracker system has missed two consecutive PULSE intervals, this
message is issued.
SUBS
is the name of the Tracker (the subsystem name for MVS/ESA trackers).
DEST
is the
destination for this system, as defined in the ROUTOPTS statement.
System action: If the destination
DEST
is defined using shared DASD (submit/release) dataset communication, this
destination is forced Offline by the TME 10 OPC controller. For other communication methods, no action is taken.
System programmer response: Check that the destination is active. If it is, check that the event writer at the
destination is active.
EQQE103W TRACKER
SUBS
AT DESTINATION
DEST
LOST THE
FUNC
Explanation: This message is issued for reporting purposes on the controller message log, EQQMLOG, when the
ROUTOPTS PULSE processing is active for Tracker systems on TME 10 OPC release 3 level or higher. The
message indicates that the
FUNC
subtask in the
SUBS
subsystem on the MVS/ESA system represented in TME 10
OPC by the
DEST
destination has abnormally terminated.
System action: No action is taken by the controller.
System programmer response: Check the message log for the indicated Tracker address space and take
appropriate actions to restart the failed subtask.
EQQE104E KEYWORD
KEYW
MISSING. IT IS REQUIRED FOR SUBRESOURCE
SUBRES
CHECKING AT
SUBSYSTEM
SUBSYS
Explanation: Authority checking for subresource
SUBRES
is specified in the AUTHDEF statement for subsystem
SUBSYS
. A valid subresource name cannot be built for protection of the operation when keyword
KEYW
is omitted.
System action: No event is created for the subsystem identified in the message text. The request is directed to the
next OPC subsystem if SUBSYSTEM(MSTR) was specified in the input. Return code 4 is set if event creation failed
for one or more subsystems. If it failed for all subsystems, or for a subsystem specifically identified in the input, return
code 8 is set.
System programmer response: Add the keyword and resubmit the EQQEVPGM job for the failing subsystem.
100 TME 10 OPC Messages and Codes