EQQM926E EQQM929W
EQQM926E PRINT OPERATION HAS MORE THAN 1 PREDECESSOR OPERATION:
APPL
,
IA
,
OPER
Explanation: A modify-current-plan request would have caused a print operation to have more than one
predecessor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM927E PRINT OPERATION HAS NO CPU PREDECESSOR OPERATION:
APPL
,
IA
,
OPER
Explanation: A modify-current-plan request would have caused a print operation to not have a computer operation
predecessor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM928E SETUP OPERATION HAS INVALID SUCCESSOR OPERATION:
APPL
,
IA
,
OPER
Explanation: A modify-current-plan request would have caused a job setup operation to not have a valid computer
operation successor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in
hexadecimal form. Use HEX ON when browsing the TME 10 OPC message log.
System action: The request is rejected, and message EQQM025E is issued to the dialog user.
Problem determination: Dependency data has probably been changed during the dialog session.
System programmer response: If the error occurs again, investigate the failing occurrence to see if any abnormal
activities have been associated with it. Then report the error to your IBM representative.
EQQM929W JOBLOG FOR
JOBN
(
JOBNUM
) NOT FOUND
Explanation: You have made a catalog management request or a browse-joblog request on an TME 10 OPC
system activated for step-level restart and where the required joblogs will be retrieved at the time of your request.
TME 10 OPC requested the tracker to retrieve the joblog, but the joblog could not be located.
System action: The message will be displayed as a TSO broadcast message to the requesting dialog user at the
first interaction after the message is sent out.
User response: Because no joblog was found, no step-level restart can be performed by TME 10 OPC If dataset
information exists, TME 10 OPC will display a dataset list for you that can be manually changed. If no dataset list
exists TME 10 OPC will accept a job-restart but will not change the JCL or make catalog updates. If you request
joblog browse, nothing will be displayed and an error message issued.
Check with your system programmer why the joblog could not be retrieved.
System programmer response: Check the tracker message log, EQQMLOG, for messages to help diagnose the
problem.
206 TME 10 OPC Messages and Codes
