EQQX366E EQQX369E
EQQX366E A PREDECESSOR TO OPERATION
WS
OP
DOES NOT EXIST
Explanation: One predecessor for the indicated operation could not be found in the application description record.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX367E THERE IS A LOOP IN THE APPLICATION NETWORK
Explanation: The application network contains a loop.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX368E ALL OPERATIONS NOT IN NETWORK IN AD
AD
Explanation: All operations are not in the network in the indicated application description.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. If you cannot find a
valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
EQQX369E JOBNAME MISSING FOR OPERATION
WS
OP
Explanation: The indicated job setup, processor, or print operation has no job name.
System action: The request to write the record is rejected.
Problem determination: Look in the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Enter a valid job name and if the error occurred in batch, resubmit the job. If you cannot find a valid
reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative.
Chapter 31. EQQXnnn Messages 359