EQQF005E EQQF008I
EQQF005E DATA ROUTER TASK QUEUE POINTERS ARE DESTROYED, RTRQ IS LOST
Explanation: The data router task abended while processing elements on RTRQ because the queue chaining is
invalid.
System action: MVS recovery/termination is requested to generate a dump. All elements on RTRQ are skipped, but
the data router task attempts to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP dataset, and the
SYSMDUMP dataset to determine the cause of the problem.
TME 10 OPC administrator response: Save the message log and dump datasets and contact your IBM
representative.
EQQF006I UNKNOWN XCF MEMBER
MEMBER
HAS JOINED THE GROUP. IT IS IGNORED
Explanation: A member that is not defined in ROUTOPTS has joined the XCF group.
System action: The controller ignores the joined member. No workload or event communication between the
controller and the tracker will take place.
Problem determination: Check the XCFOPTS initialization statement of the TME 10 OPC tracker system and check
the ROUTOPTS initialization statement of the controller.
TME 10 OPC administrator response: Verify that the tracker system has been defined with an XCF member name
that corresponds to the definition in ROUTOPTS. Add the member name to ROUTOPTS and restart the controller.
EQQF007I XCF MEMBER
MEMBER
HAS JOINED THE GROUP. THE DESTINATION WILL BE REPORTED
ACTIVE
Explanation: An TME 10 OPC tracker system has joined the same XCF group as the controller. The member is
defined as an XCF destination in the ROUTOPTS initialization statement.
System action: The controller will report the destination as active. Work can be scheduled at workstations defining
this destination.
User response: None
EQQF008I XCF MEMBER
MEMBER
HAS JOINED THE GROUP AS STANDBY FOR THE OPC/ESA CONTROLLER
Explanation: An TME 10 OPC standby system has joined the same group as the controller.
System action: Controller processing continues as normal.
User response: None
102 TME 10 OPC Messages and Codes