Specifications

KAVS4971-E
A job (name: unit-full-name:execution-ID) cannot finish waiting because the unit whose end is to be waited for
(name: unit-full-name:execution-ID) is in a state for which waiting is not possible. (cause number: cause-number)
The status of the unit whose end is being waited for has prevented the job with wait conditions indicated in the message
from finishing the waiting process.
The message outputs the execution ID of the jobnet that cannot finish waiting if yes is specified for the LOGINFOALL
environment setting parameter.
(S)
Continues processing.
(O)
Take action according to the cause number output in the message.
The appropriate action for each cause number is as follows:
Cause number: 1
The wait condition (wait method AND) was not satisfied because the status of the unit whose end is being waited
for indicated in the message does not allow the wait condition to be satisfied. The probable causes are as follows:
• The unit finished executing in a status that does not allow waiting to finish
• A jobnet with start conditions whose end is being waited for is in a status that does not allow waiting to
finish.
• The unit is suspended
• The unit has not been registered
If the unit in the message terminated in a status that does not allow waiting to finish, re-execute the unit or change
the status so that waiting can finish. Also take this action if a jobnet with start conditions whose end is being
waited for is in a status that does not allow waiting to finish. For details about the statuses that allow waiting to
finish, see 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the Job
Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
If the unit in the message whose end is being waited for is suspended, check the following points. Then, release
the unit whose end is being waited for from the suspended state.
• Does the unit whose end is being waited for exist?
• Is the unit a type that can be waited for?
If the unit in the message whose end is being waited for has not been registered, register the unit for execution.
If this approach fails to resolve the problem, perform a temporary change operation to disable waiting for the
unit to be waited for indicated in the message.
Note that if the unit whose end is being waited for has not been registered, asterisks (***) appear as the execution
ID in the message.
Cause number: 2
The wait condition (wait method AND) was not satisfied because there are no applicable generations of the unit
whose end is being waited for, and the system is configured not to execute the jobnet in these circumstances.
The probable causes are as follows:
1. There are no generations of the unit whose end is being waited for.
2. The number of generations of the unit with wait conditions does not match that of the unit whose end is being
waited for.
2. Messages
Job Management Partner 1/Automatic Job Management System 3 Messages 1
476