Filter
Top Products
EQQTT06E EQQTT09E
EQQTT06E A SEVERE ERROR IN THE TCP/IP COMMUNICATION TASK HAS CAUSED ONE OR MORE
REQUESTS TO BE LOST
Explanation: The TCP/IP communication task encountered an error processing elements on the TATQ. As a result,
at least one queue element has been lost.
System action: MVS/ESA recovery/termination is requested to generate a dump. The TCP/IP communication task
attempts to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
TME 10 OPC administrator response: Save the message log, dump and diagnostic datasets, and contact your IBM
representative.
EQQTT07E THE TCP/IP COMMUNICATION TASK ABENDED WHILE PROCESSING THE FOLLOWING
REQUEST:
REQUEST
Explanation: An abend prevented the TCP/IP communication task from processing a queue element.
System action: MVS/ESA recovery/termination is requested to generate a dump. The TCP/IP communication task
attempts to continue normal processing.
Problem determination: Review the TME 10 OPC message log dataset, the EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
User response: Contact your system programmer.
System programmer response: Save the message log, dump and diagnostic datasets, and contact your IBM
representative.
EQQTT08E THE TCP/IP COMMUNICATION TASK HAS IGNORED THE FOLLOWING QUEUE ELEMENT:
REQUEST
Explanation: The TCP/IP communication task has detected an invalid queue element on its queue.
System action: The element is discarded from the TCP/IP communication task queue. The task continues normal
processing.
Problem determination: Review the TME 10 OPC message log dataset.
User response: Contact your system programmer.
System programmer response: Save the message log (EQQMLOG) and the current plan (EQQCPxDS) and
contact your IBM representative.
EQQTT09E THE TCP/IP TASK CANNOT START, TRACKER FEATURE IS NOT INSTALLED
Explanation: The TCP/IP communication task could not locate a required load module.
System action: The TCP/IP communication task terminates.
System programmer response: If the AIX tracker feature is not installed, then the ROUTOPTS initialization
statement should not specify the TCP keyword. If the AIX tracker feature is installed, then make sure that the
TME 10 OPC subsystem can access corresponding load module libraries. After making appropriate corrections,
restart the TME 10 OPC subsystem.
272 TME 10 OPC Messages and Codes