Specifications

#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.
KAVT0413-E
Execution of a job at a destination that does not permit execution was suppressed according to the settings specified
in the execution agent profile. (logical-host:scheduler-service-name:target-host:maintenance-information)
The execution agent specified for a job is not permitted to be a target host in its execution agent profile.
(S)
Ends the job abnormally in failed to start status.
(O)
The probable causes are as follows:
• An incorrect execution host name is specified in the detailed definition of the job.
• A permitted execution host is specified incorrectly in the execution agent profile.
If the execution agent name is wrongly specified in the detailed definition of the job, specify the correct name and
then re-execute the job.
If the execution agent profile is wrongly specified, correct the settings and then execute the ajsprofalter
command to apply the corrected profile to the scheduler service. Then, re-execute the job.
2. Messages
Job Management Partner 1/Automatic Job Management System 3 Messages 1
529