Previous Topic

Next Topic

Book Contents

Book Index

Job Statuses

The following job statuses can appear in the Active Environment screen:

Table 59 Job Statuses for the Active Environment screen

Status

Description

ACTIVE

The job is a dummy job that has not yet reached the post-processing phase.

BUT NOT FOUND n TIMES

If a job is not found at least once, this status displays the number of times (n) Control-M has looked for the job. If the job is still not found after 10 times, the status is changed to DISAPPEARED.

Example

JOB SUBMITTED BUT NOT FOUND 5 TIMES

The job was submitted, but may have been purged. After checking 10 times, Control-M changes the status to DISAPPEARED.

Note: This default number can be changed by your INCONTROL administrator.

§Restart§ CLEANUP

Job is being run for Cleanup.

DELETED

The job order was deleted by an authorized user.

DISAPPEARED

Job disappeared completely. This status only occurs after a NOT FOUND status.

ENDED NOT "OK"

Job ended NOT OK.

ENDED NOT "OK" – ABENDED

Job abended.

ENDED NOT "OK" – DUE TO CC

Condition code that is not defined as OK has occurred.

ENDED NOT "OK" – FAILED – REASON UNKNOWN

This usually occurs following a system crash.

ENDED NOT "OK" – JCL ERROR

Job failed due to JCL error.

ENDED NOT "OK" – RERUN NEEDED

Rerun is needed for the job.

ENDED NOT "OK" – RERUN WAS NEEDED

Rerun was required for the previous execution of the job.

ENDED NOT "OK" – TERM ON NCT2

The job was terminated by Control-M due to a NOT CATLGD 2 error.

ENDED "OK"

Job finished executing OK.

ENDED "OK" FORCED OK

Job ended OK due to a Force OK request.

EXECUTING

Job is executing.

EXECUTING (SYSOUT IN HOLD STATUS)

Job was placed in HOLD status by an operator issued JES HOLD command before Control-M could read the job’s output.

GOING TO START

Started task is eligible to be run and is about to be activated.

(TBL HELD)

The SMART Table Entity of which the job is part is in Held status, and as a result, the job itself is being logically held. (While the job’s SMART Table Entity is being held, actions that require a Held status, such as Delete, Zoom, and Save, can be performed against the job. In addition, the Control-M monitor does not handle the job. For example, if the job is in WAIT SCHEDULE status it is not selected for submission.)

HELD

Job is in hold status.

LATE

Job did not finish executing by the time specified in a SHOUT WHEN LATE statement.

LATE EXECUTION

The elapsed runtime of the job is outside the acceptable limits defined in a SHOUT WITHIN EXECTIME statement.

LATE SUBMISSION

Job was not submitted by the time specified in a SHOUT WHEN LATESUB statement.

NJE JOB

The job is not currently found in either Remote or Host node, but is in the process of transmission between nodes. (Either the job is being transmitted to the Remote node for execution, or the sysdata output of the job is being transmitted to the Host node.) Control-M continues to search for the job until it is located on one of the nodes.

BMC recommends that you do not purge jobs on the Remote node. However, if you do purge a job on the Remote node, you must notify Control-M of the event by changing the value in the NJE field in the Active Environment Zoom screen (Screen 3.Z) to '  ' (Blank). After a short time, the job status changes to Disappeared.

NJE JOB (ID CHANGED)

The job ID of the NJE job has changed. When the job’s sysdata output was transmitted back to the Host NJE node, the Control-M monitor detected that the original job ID of the NJE job is occupied by another job. The Control-M monitor continues to search for a job to match the new job ID.

NOT FOUND

Job not found in the queue. Check that the job or its sysout has not been accidentally deleted. This status may also appear when JES is very busy. In such a case, Control-M waits for JES until it confirms that the job is lost.

NOT STARTED

Starting of the started task failed.

NOT SUBMITTED

Submission of the job failed.

NOTE

A Note has been added to the job, through the Zoom screen.

ON HST FILE

Job is currently in the History file. If the job is included in the flow of jobs being rerun, it will be restored to the Active Jobs file before being rerun.

Note: This option appears only in the Rerun Flow Job List window.

ON OUTPUT QUEUE

Job is on the output queue of the remote NJE node or on the output queue of the host node with a changed job ID.

PRIOR RUN

Termination status of the previous job (or cyclic task) execution (for jobs that have been rerun).

PROBLEMS READING SYSOUT

Usually means that problems prevent the Control-M monitor from reading the job’s output.

PSEUDO

At the time when the job was ordered, Control-M automatically converted it to a DUMMY job.

RELEASED

On Spool job has been released and is waiting to be executed.

REQUESTED CHANGE

Job parameters were changed using the Zoom option, but the request has not yet been performed by the Control-M monitor.

REQUESTED FORCE OK

A Force OK request was issued for a held job, but the request has not yet been performed by the Control-M monitor.

REQUESTED FREE

A free request was issued for a held job, but the request has not yet been performed by the Control-M monitor.

REQUESTED HELD

A hold request was issued for the job, but the request has not yet been performed by the Control-M monitor.

REQUESTED REACT

An activate request was issued for a job, but the request has not yet been performed by the Control-M monitor.

REQUESTED RERUN

A rerun request was issued for the job, but the request has not yet been performed by the Control-M monitor.

§Restart§ RESTARTED)

Job has run (executed) with the restart step under Control-M/Restart (that is, a restart has been performed).

RESTORED

This job was restored from the History file.

If this status is displayed in the History Environment screen, the job has been restored, rerun, and then copied to the History file as part of the New Day or a User Daily procedure.

RUN n

Run number. Incremented each time a cyclic task is executed or a job is rerun.

STARTED

Started task started, but is not yet in the operating system’s job queue.

SUBMITTED

Job submitted, but is not yet in the operating system’s job queue.

WAIT CONFIRMATION (FOR SCHEDULE)

Job is waiting for manual confirmation before it can be scheduled.

§Restart§ WAIT CONFIRMATION (WITH RESTART)

Job is waiting for manual restart confirmation.

WAIT EXECUTION

Job is in the operating system’s job queue waiting to be executed.

WAIT RELEASE

On Spool job is eligible to be run and is about to be released.

WAIT SCHEDULE

Job is waiting to be scheduled.

WAIT SCHEDULE ON SPOOL

Job is waiting to be scheduled but is already in input queue on spool.

WAIT SCHEDULE (PIPE)

For MAINVIEW Batch Optimizer (MVBO) users. Job is waiting to be scheduled and is a participant in a Pipe (Collection).

WAIT SUBMISSION

Job is eligible to be run and is about to be submitted.

§Restart§ (WITH RESTART)

The restart step under Control-M/Restart will be added to the JCL of the job when the job is submitted (that is, a restart will be performed).

Parent Topic

Active Environment Screen