KAVS0218-E

Since the scheduler service for which a cold start was attempted was still accessing the database, database registration information could not be deleted and the cold start of the scheduler could not be performed. The possible causes are:

• JP1/AJS3 - View is connected to the object scheduler service.

• JP1/AJS3 - Web Console is connected to the object scheduler service.

• A JP1/AJS3 command is executing on the object scheduler service.

You can use the ajsstatus or jajs_status command to check the connection status of JP1/AJS3 - View and JP1/AJS3 - Web Console. For details about each command, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(S)

Cancels processing.

(O)

• If JP1/AJS3 - View is connected:

  Execute the jajs_hstd_stop command to stop the ajsinetd process temporarily, and then execute the jajs_hstd command to start the ajsinetd process. For details on the jajs_hstd and jajs_hstd_stop commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

• If JP1/AJS3 - Web Console is connected:

  Execute the jajs_hstd_stop command to stop the ajscdinetd process temporarily, and then execute the jajs_hstd command to start the ajscdinetd process. For details on the jajs_hstd and jajs_hstd_stop commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

• If a JP1/AJS3 command is executing:

  Wait for the command to terminate or cancel the processing.

Remove the process that is accessing the database. Then, use the jajs_spmd command with the -cold and -n jajs_schd options specified to perform a cold start of the object scheduler service again.