EQQE037I EQQE042I
EQQE037I JOB
JOBNAME
(
JNUM
), IN APPLICATION
APPL
, IS LATE, WORK STATION =
WSID
, IA =
ARRTIME
Explanation: This message is issued when a job has reached its latest start time but has not yet started.
System action: Normal TME 10 OPC processing continues.
User response: Investigate what is keeping the job from starting and take appropriate actions to enable it to start.
EQQE038I LONG DURATION FOR JOB
JOBNAME
(
JNUM
), IN APPLICATION
APPL
, WORK STATION =
WSID
, IA
=
ARRTIME
Explanation: This message is issued when a job has been active longer than its estimated duration multiplied by the
feedback limit, divided by 100. For example, if the feedback limit is 200 and the estimated duration is ten minutes,
then the message will be issued if the job has been active longer than twenty minutes. The feedback limit specified
on the JTOPTS initialization statement is used in the calculation.
System action: Normal TME 10 OPC processing continues.
User response: Investigate why the job has been active so long. If possible, take corrective action to speed up the
processing of the job.
EQQE039I LONG TIME ON INPUT QUEUE FOR JOB
JOBNAME
(
JNUM
), APPL =
APPL
, WORK STATION =
WSID
,
IA =
ARRTIME
Explanation: This message is issued when a job has been waiting in a job input queue longer than ten minutes.
The message is only issued when the DURATION keyword is specified in the ALERTS statement.
System action: Normal TME 10 OPC processing continues.
User response: Investigate what is keeping the job from starting and take appropriate actions to enable it to start.
EQQE040W OPC/ESA CANNOT HANDLE JOB
JOBNAME
(
JOBNUM
). THE JOB MAY HAVE TO BE CANCELED
Explanation: TME 10 OPC job tracking has encountered an “add job to JES queue” event for a job whose job name
matches job names defined in the current plan. However, none of the operations with this job name has a status that
is consistent with an “add job to JES queue” event. This message indicates that jobs with TME 10 OPC job names
are being submitted by non-TME 10 OPC functions.
System action: TME 10 OPC assumes that the job is not an TME 10 OPC job and will not track the job. If the job
was held by an TME 10 OPC job tracking exit it will be released. Note that since this job is not handled by TME 10
OPC, any dependencies this job may have must be manually implemented.
System programmer response: Determine if TME 10 OPC and non-TME 10 OPC jobs are using the same job
names. Check that all jobs belonging to TME 10 OPC defined applications are defined in the current plan.
EQQE042I
JOBNAME
(
JOBNUM
) WAS NOT SUBMITTED BY OPC/ESA BUT WILL BE TRACKED ANYWAY
Explanation: The Event Manager has encountered an event for a job whose job name matches an operation defined
in the current plan. However, TME 10 OPC did not submit this job. This message indicates that jobs with TME 10
OPC job names are being submitted by non-TME 10 OPC functions.
System action: TME 10 OPC accepts current job as an TME 10 OPC job and will continue to track events for this
job.
System programmer response: Determine if TME 10 OPC and non-TME 10 OPC jobs are using the same job
names. If TME 10 OPC and non-TME 10 OPC jobs are using the same job names, take appropriate action to
minimize such name conflicts. Inform TME 10 OPC application owners that rerunning applications or adding
additional work to the job queue should be done using the TME 10 OPC Modify Current Plan dialog.
88 TME 10 OPC Messages and Codes