KAVT0412-W

One half (30 minutes^#2) of the waiting time for acquisition of the branch execution ID (one hour^#1) has passed.

30 minutes^#2 later, the status of the jobnet with start conditions might change to Monitor terminated.

#1

For the compatible ISAM configuration, 30 minutes.

#2

For the compatible ISAM configuration, 15 minutes.

(S)

Continues processing.

(O)

Startup of a jobnet with start conditions takes a long time due to heavy loading on the schedule control.

The probable causes are:

• Many events being monitored by the jobnet with start conditions have occurred.

• Many jobnets in a batch or a jobnet containing many jobs was registered for execution or terminated forcibly.

• A jobnet with many logs to keep was unregistered.

• A jobnet with many fixed generations was unregistered.

• Many jobnets set in the schedule have reached the start time at the same time.

• A jobnet with start conditions having many generations whose start conditions (AND) are partially satisfied is terminated forcibly, or is placed in Monitor terminated status due to the valid range of start condition.

• The system loading is heavy due to a program other than JP1/AJS3.

If any of the above problems occurred and JP1/AJS3 caused the load, wait until processing terminates. If a program other than JP1/AJS3 caused the load, terminate that program as required.

To determine the name of the delayed jobnet with start conditions, you can use the unit ID displayed by executing the ajsname command with the -I option specified.