6.1 Status levels of jobnets, jobs, and jobnet connectors

Not sched. to exe.

(no plan)

Y

Y

Y

Y

No execution schedule is defined.

Wait for start time^#1

(time-wait)

Y

Y

N

N

Waiting for the execution start time to arrive.^#2

If synchronized with a jobnet connector, the jobnet is waiting for the start time of the jobnet connector.

Wait for prev. to end

(term-wait)

N

Y

Y

Y

Waiting for the preceding job or jobnet to end.

Even if no preceding unit exists, the unit will be placed in this status if any of the following conditions applies:

• The upper-level jobnet is in wait state.

• The scheduler service is suspended.

• The execution process for the unit has not started even though the start condition of the upper-level jobnet has been satisfied.

Being held^#1

(holding)

Y

Y

Y

N

The job or jobnet is being held.

Waiting to execute

(exec-wait)

N

N

Y

N

Waiting for the job's submit process to complete.

This status applies after a job has been submitted by scheduler control, until it is queued by job execution control.

Not executed + Ended (not scheduled)^#3

(unexec)

N

Y^{#4, #5}

Y^{#4, #5}

Y

The job or jobnet was not executed because the preceding unit ended abnormally^#11.

--

(unexec-W)

N

Y

Y

N

The job or jobnet ended with a warning, and the attempted rerun was unsuccessful.

Bypassed^#1

(bypass)

N

Y

Y

Y

The job or jobnet was not executed because the schedules of the nested jobnet and the upper-level jobnet did not match, or execution was prohibited, for example.

Now running^#1

(running)

Y

Y

Y

Y

The job or jobnet is being executed.

The jobnet connector is waiting for the connection-destination jobnet to end.

Now queuing^#1

(queuing)

N

N

Y

N

The start condition has been satisfied and the job is waiting to be executed.

Running + Abend^#1

(AB-cont)

Y

Y

N

Y

Jobs or nested jobnets running concurrently in the same jobnet ended abnormally^#11.

An error^#12 occurred in the connection-destination jobnet of the jobnet connector.

Running + Warning^#1

(WA-cont)

Y

Y

N

Y

Jobs or nested jobnets running concurrently in the same jobnet ended with a warning.

In the case of a jobnet connector, the status of the connection-destination jobnet is also Running + Warning.

Ended normally^#1

(normal)

Y

Y

Y

Y

All jobs and jobnets ended normally.

The connection-destination jobnet of the jobnet connector ended normally.

Normal end + False

(normal-false)

N

N

Y

N

The judgment job ended normally, although the result of the preceding unit did not match the judgment condition.

Ended with warning^#1

(warning)

Y

Y

Y

Y

The job ended with a warning.

The jobnet contains a job that ended with a warning.

The connection-destination jobnet of the jobnet connector ended with a warning.

Ended abnormally^#1

(abnormal)

Y

Y

Y

Y

The job ended abnormally.

The jobnet contains a job or a nested jobnet that ended abnormally^#11.

The jobnet connector could not connect to the connection-destination jobnet due to an invalid definition or a communication error.

--

(abnormal-WR)

Y

Y

Y

N

The job or jobnet ended with a warning, and the subsequent rerun ended in the Ended abnormally status.

Skipped so not exe.^#3

(exec-deffer)

Y

Y

N

N

The jobnet was not executed because, for example, the JP1/AJS3 - Manager service was not active at the job's scheduled start time, or the base time passed while the root jobnet was being held.^#4,#6

A jobnet enters Skipped so not exe. status in the following cases:

• The jobnet's timeout period elapses while the root jobnet is in Wait for start time or Being held status.^#7

• Schedule skip is selected in Schedule option, and the start time of the next generation arrives before termination of the preceding generation.

• Schedule skip is selected in Schedule option, and a jobnet that is running in immediate execution mode is again registered for immediate execution.

• Multi-schedule is selected in Schedule option, but concurrent execution is not enabled for the jobnet. The current generation fails to end, and the root jobnet's timeout period expires before the next generation starts.

• There are tasks scheduled to be executed on a day when the OVERSCHEDULE environment setting parameter of the scheduler service is set to plan and the scheduler service starts by warm start or disaster recovery start.

• There are tasks scheduled to be executed before the scheduler service starts by warm start or disaster recovery start when the OVERSCHEDULE environment setting parameter of the scheduler service is set to skip or when registering the jobnet for execution in the Register for Execution dialog box, Execute from next time is selected for Planned time passed when daemon starts.

• When Do not start monitoring is set for Concurrent exec. of monitoring gen, it is time to start the next monitoring generation, but there is still a generation in the Now monitoring status.

• When Does not stay with skip is set for Pause exec. gen. for start cond. and concurrent execution is disabled, a generation is already running and the condition for starting the next generation is met.

--

(invalid-seq)

Y

Y

N

N

The execution sequence is in a loop and there is job or jobnet that cannot be executed.

Interrupted^#1

(interrupt)

Y

Y

N

N

Execution of the jobnet has been interrupted. There are no abnormally terminated^#8 units in the jobnet, but there is a unit that has not been processed (in Not executed + Ended status).

A unit is placed in Not executed + Ended status in the following cases where the preceding unit has not terminated abnormally:^#8

• The jobnet is interrupted from JP1/AJS3 - View or by using the Web GUI, the API, or a command.

• A queued job is killed and not executed.

• A queueless job is not executed due to a communication error or other problem.

• An abnormally terminated^#8 job in a jobnet is no longer in abnormally terminated^#8 status because it has been re-executed or a status change has been performed.

• The scheduler service was stopped by executing the ajsstop command with the -j option specified. For the command syntax, see ajsstop in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Note that if the scheduler service is started in warm-start mode or disaster-recovery-start mode, root jobnets in Now running, Running + Abend, or Running + Warning status are placed in Interrupted status regardless of the status of the subordinate units.

Killed^#1

(kill)

Y

Y

Y

Y

The job or jobnet was killed for one of the following reasons:

• An error occurred which prevented the end status of the job or jobnet from being determined (for example, the end result could not be written to the file at job execution).

• The JP1/AJS3 - Manager service stopped while a job was being executed.

• The system stopped while a job was being executed.

• The active job was killed.

• Processing was cancelled because the active job exceeded its specified job execution time.

In the case of a jobnet connector, the root jobnet was killed during execution of the jobnet connector.

--

(kill-WR)

Y

Y

Y

N

The job or jobnet ended with a warning, and the attempted rerun was killed.

Failed to start^#1

(fail)

N

N

Y

N

Process creation failed when the job started, or the environment settings for the process could not be set.

--

(fail-WR)

N

N

Y

N

The job ended with a warning, and the attempted rerun failed to start.

Unknown end status^#1

(unknown)

N

N

Y

Y

The end status is unknown for either of the following reasons:

• An error occurred which prevented the end status of the job from being determined. For example, the end result could not be written to the file at job execution.

• The JP1/AJS3 - Manager service stopped and the system shut down while the job was being executed.

In the case of a jobnet connector, a warm start or disaster recovery start mode was performed during execution.

--

(unknown-WR)

N

N

Y

N

The job ended with a warning, and the end status of the attempted rerun is unknown.

Shutdown

(shutdown)

Y

Y

Y

Y

A jobnet was registered for planned execution, but a non-existent unit is specified in the jobnet's exclusive schedule or in the calendar referenced in the jobnet's schedule information.

Wait for start cond.

(condition-wait)

Y

Y^#9

N

N

The jobnet is waiting for the start condition to be satisfied. If concurrent execution is disabled and another jobnet is running, the jobnet keeps waiting for the start condition even if it has already been satisfied.

Now monitoring

(monitoring)

Y

Y^#9

N

N

The jobnet is monitoring for the events defined in the start condition.

Unmonitored + Ended

(unexec-monitor)

Y

Y^#9

N

N

The operation time expired before the start condition was satisfied.

Monitor terminated^#10

(monitor-close)

Y

Y^#9

N

N

The jobnet that was monitoring for a start condition to be satisfied was interrupted or killed.

Interrupted monitoring^#10

(monitor-intrpt)

Y

Y^#9

Y^#9

N

Monitoring by a jobnet with a start condition was interrupted by the process that stops the scheduler service. The scheduler service was stopped either in restricted mode (job control, jobnet control, or schedule control option specified) or by forced termination (killing active jobs first).

In this case, when the scheduler service is started the next time by hot start or warm start, or when suppression of job execution is canceled after disaster recovery start is performed, monitoring is restarted based on the latest definition of the event job specified in the start condition.

Monitor-end normal^#10

(monitor-normal)

Y

Y^#9

N

N

The start condition was satisfied within the valid range (specified execution count or monitoring period).

End delay

(end-delay)

Y

Y

Y

N

An end delay has occurred.

Start delay

(start-delay)

Y

Y

N

N

A start delay has occurred.

Nested jobnet delayed end

(nest-end-delay)

Y

Y

N

N

An end delay has occurred in a lower-level unit.

Nested jobnet delayed start

(nest-start-delay)

Y

Y

N

N

A start delay has occurred in a nested jobnet.