EQQF000E EQQF004E
EQQF000E DATA ROUTER TASK HAS IGNORED AN INVALID QUEUE ELEMENT:
DQE
Explanation: A queue element did not contain the correct eye catcher or version number.
System action: The data router task does not process the invalid element, but continues normal processing.
User response: Contact your system programmer.
System programmer response: Save the TME 10 OPC message log and contact your IBM representative.
EQQF001I DATA ROUTER TASK INITIALIZATION IS COMPLETE
Explanation: The data router task has successfully completed initialization.
System action: Data router task processing starts.
User response: None.
EQQF002E DATA ROUTER TASK INITIALIZATION FAILED
Explanation: The data router task could not acquire the resources required for normal operation.
System action: Data router processing is terminated.
Problem determination: Review previous messages in the TME 10 OPC message log.
User response: Contact your system programmer.
System programmer response: Correct all errors and restart the data router task.
EQQF003E MEMBER
MEMBER
IS DEFINED AS A DESTINATION IN ROUTOPTS BUT IS STARTED AS A
STANDBY SYSTEM
Explanation: An XCF member has joined the same XCF group as the controller. This member was defined as a
tracker in the ROUTOPTS but has been started as an TME 10 OPC standby system.
System action: TME 10 OPC will not recognize the joined standby member as a destination. No communication
will take place between the controller and the standby member.
Problem determination: Check the ROUTOPTS initialization statement and the initialization statement defined for
the member.
User response: Contact your system programmer.
System programmer response: Restart the standby system as a tracker or update the controller ROUTOPTS
statement.
EQQF004E DATA ROUTER TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT
DQE
Explanation: An abend prevented the data router task from processing a queue element.
System action: MVS recovery/termination is requested to generate a dump. 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.
User response: Contact your system programmer.
System programmer response: Save the message log and dump datasets and contact your IBM representative.
Copyright IBM Corp. 1991, 1998 101