Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Messages


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

  • The status was changed by re-executing the succeeding unit

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 JP1/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 the status of the unit (indicated in the message) whose end is being waited for is Ended normally, Ended with warning, or Bypassed, the status was changed by re-executing the succeeding unit. Re-execute the unit whose end is being waited for.

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.

  3. The number of saved generations of the unit with wait conditions, the unit whose end is being waited for, or both is not sufficient to save the execution results from one day of operation.

Add an execution schedule that satisfies the waiting rule to the unit whose end is being waited for indicated in the message. Alternatively, in the case of 3. above, the system might have been unable to obtain generation information because generations were being deleted. Check whether the execution ID of the unit whose end is being waited for appears in the Wait Conditions Statuses window of JP1/AJS3 - View or in the -xw option of the ajsshow command. If the execution ID appears, the unit can be waited for and the problem is resolved. You can prevent this error message from appearing by ensuring that the number of saved generations allows the system to save one day's worth of execution results for the unit with wait conditions and the unit whose end is being waited for.

If you cannot take this approach, perform a temporary change operation to disable waiting for the unit to be waited for indicated in the message.

For this cause, asterisks (***) appear as the execution ID of the unit in the message whose end is being waited for.

Cause number: 3

The wait condition (wait method OR) was not satisfied because the unit with wait conditions indicated in the message cannot finish waiting for all units whose ends are being waited for.

The probable reasons are as follows. Check the statuses of all the units whose ends are being waited for, and take the appropriate action.

  1. A unit whose end is being waited for terminated in a status that does not allow waiting to finish, waiting cannot finish for a jobnet with start conditions and whose end is being waited for, or a unit is suspended.

    Take the action described for cause number 1.

  2. The unit whose end is being waited for is not registered for execution.

    Take the action described for cause number 1.

  3. The status was changed by re-executing the succeeding unit.

    Take the action described for cause number 1.

  4. There are no applicable generations of the unit whose end is being waited for, and the system is configured not to execute the unit in these circumstances.

    Take the action described for cause number 2.

For cause number 3, asterisks (***) appear as the full unit name and execution ID of the unit in the message whose end is being waited for.