EQQO001I EQQO006E
EQQO001I APPC TASK INITIALIZATION IS COMPLETE
Explanation: The APPC task has completed initialization processing.
System action: Processing continues.
Operator response: None.
EQQO002E APPC TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT
APP
Explanation: An abend prevented the APPC task from processing a queue element.
System action: MVS recovery/termination is requested to generate a dump. The APPC task attempts to continue
normal processing.
Problem determination: Review the TME 10 OPC message log dataset, EQQDUMP diagnostic dataset, and the
dump dataset to determine the cause of the problem.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: Save the MLOG, dump, and EQQDUMP datasets and contact your IBM
representative.
EQQO003E APPC TASK INITIALIZATION FAILED - XCF FAILURE
Explanation: The APPC task has ended due to an XCF failure or request denied by XCF
System action: The APPC task is not started.
Operator response: None.
System programmer response: Ensure the XCF destination names are defined correctly, restart the APPC task
when XCF is available.
EQQO004E APPC TASK INITIALIZATION FAILED - APPC/MVS FAILURE
Explanation: The APPC task has ended due to APPC/MVS failure
System action: The APPC task is not started.
Operator response: Restart the APPC/MVS address space before starting the TME 10 OPC APPC subtask.
EQQO005I INITIALIZATION FAILED - SUBSYSTEM STOP REQUESTED
Explanation: A stop subsystem command was issued while the APPC task was initializing. This caused the subtask
to end.
System action: The TME 10 OPC subsystem continues the shutdown sequence
Operator response: None.
EQQO006E APPC TASK TERMINATED - MVS/APPC SHUTTING DOWN
Explanation: The APPC task has ended due to APPC/MVS ending. All active conversations have been lost.
System action: The APPC task is shutdown.
Operator response: When APPC/MVS is available again, restart the TME 10 OPC APPC subtask.
Copyright IBM Corp. 1991, 1998 229