KAVS1153-E

Scheduler service stops because database access error occurred while JP1/AJS3 is operating with the external database.

One of the following information items is displayed as the unit-name:

• unit-name

• unit-ID

• hyphen (-)

If unit-ID is displayed, you can check the full name of the unit by using the ajsname command. For details on the ajsname command, see ajsname in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(S)

Scheduler service stops and restarts in hot start mode.

The restart setting depends on extended startup process definition file (jp1ajs_service_0700.conf).

If the scheduler service is restarted, the scheduler service inherits the state from before it was restarted. The scheduler service obtains information about jobs whose statuses are Now running from the server where a job is to be executed, and automatically changes the status of a job to its actual status where possible.

If the scheduler service is able to obtain the actual status of a job, the scheduler service automatically continues execution of the job according to the jobnet definition. If the scheduler service is unable to obtain information from the server where a job is to be executed, the status of the job changes to Ended abnormally.

(O)

If a job cannot be restarted, see 2.15 Troubleshooting problems related to the external database in the manual JP1/Automatic Job Management System 3 Troubleshooting and resolve the problem. Then, restart the scheduler service.

After restarting the scheduler service, perform the following actions.

• If the job ends abnormally, check the job status, and manually execute the job again.

• Check the handling number in the message that was output.

  The following describes how to take action for each handling number.

Handling number: 1

No action is needed.

Handling number: 2

An error occurred during creating the generations.

Check the jobnet displayed in the unit name. The workaround differs according to the method by which a jobnet was registered for execution. Of the following workarounds, perform the one that is applicable to the method by which the jobnet in question was registered.

• Fixed execution registration with the period specified (including the case in which a schedule information file is used):

  Make sure that the generations have been created in the specified period, and then add the generations that have not been created. If many generations have not been created yet, cancel all registrations of the relevant jobnet, and then re-register them.

• Fixed execution registration with the number of future generations specified, or planned execution registration:

  No generations will be created after the generation whose creation is canceled. Cancel all registrations of the relevant jobnet, and then re-register them.

• Fixed execution registration with a specific date and time, or immediate execution registration:

  If the generations have not been created, re-register them.