EQQE043W EQQE045E
EQQE043W JOB START OR JOB END EVENT RECEIVED FOR
JOBNAME
(
JOBNUM
) IS NOT CONSISTENT WITH
CURRENT OPC/ESA STATUS OF THIS JOB
Explanation: The Event Manager has received an event for a job on an automatically reporting computer workstation
that conflicts with the information already collected for this operation. For example, a job complete event can only
occur for a job that has started to execute.
System action: The status of the operation is not changed. The Event Manager continues normal operation with the
next queued event.
System programmer response: Use console messages in the MVS SYSLOG dataset, or records in an SMF log
dataset to determine what has happened to this job. If possible, try to locate the SYSMSG dataset for this job.
EQQE044W
JOBNAME
(
JOBNUM
) MAY HAVE BEEN STARTED OUT-OF-ORDER. IF REQUIRED, SET CORRECT
STATUS MANUALLY
Explanation: The Event Manager has received a job start event for an operation on an automatically reporting
computer workstation. However, this operation has predecessor operations that have not yet been reported complete.
System action: The status of the operation is not changed. The Event Manager continues normal operation with the
next queued event.
System programmer response: Determine if the job was submitted outside of TME 10 OPC or if it was held and
then released manually. Inform all people concerned about the reason for this message and take appropriate action
to make sure that operations are started only after all predecessors are complete.
Operator response: Determine if predecessors to the current operation have completed. If they have, change their
status to complete, and change the status of the current operation to started. If they have not, the current job should
be entered into hold status, and the job should be restarted. After predecessors have completed, the job should be
released from hold.
EQQE045E ERRORS OCCURRED READYING SUCCESSORS TO THE FOLLOWING OPERATION:
APPLICATION =
APPL
, INPUT ARRIVAL =

ARRTIME

, OPERATION NUMBER =
OPNUM
THE FAILURE
REASON WAS
REASON
. THE PROBLEM SUCCESSOR OPERATION: APPLICATION =

SAPPL

,
INPUT ARRIVAL =

SARRTIME

, OPERATION NUMBER =

SOPNUM

Explanation: OPC/ESA changed the status of an operation to Complete but encountered errors when attempting to
set the status to Ready for a successor of the complete operation.
System action: The status is not changed for any of the successor operations. Processing continues.
System programmer response: Review earlier messages in the TME 10 OPC message log to determine the exact
reason for this message. Some possible values for reason are:
RA VSAM I/O error was encountered when reading the successor operation. See the message reporting the I/O
error for more details.
NThe successor operation does not list the predecessor as a dependency.
WThe workstation name for the successor operation is not defined in the current plan.
CThe status of the successor operation is already complete.
MSetting the status of the successor operation to Ready failed. Check the message log for further messages
describing the error.
All of the reasons above indicate an internal OPC/ESA error. Save a copy of the active current plan, the job-tracking
archive, and the active job-tracking log. Contact your IBM representative.
Operator response: Check each successor operation to see if all its predecessors are complete. If they are
complete, change the status of the operation to ready using the MCP dialog.
Chapter 8. EQQEnnn Messages 89