Top
Systemwalker Operation Manager Troubleshooting Guide
FUJITSU Software

4.2.4 A Job Net that Waits for Message Events and the Execution Time is not Started, even if a Message Event was Generated and the Execution Time was Exceeded

Applicable versions and levels

Action 1

Points to check

Was the scheduled start (startup day) or job net information changed after the message event was generated?

Cause

If the following changes were performed after the message event was generated but before the execution time arrived, Jobscheduler will create the scheduled start of the job net again (rescheduling processing).

The generated message event is cleared as a result of this rescheduling processing. For this reason, the job net is not started even if the execution time arrives.

*1: If Another job net is used as Another base job net on the Startup Days tab in the Job Net Properties window, the scheduled start will also be created again when the execution condition for the selected base job net is changed. The execution condition for the selected base job net is changed in the following cases:

Action method

Change the job net information at a time that will not affect the job net operation.

Action 2

Points to check

Was the message event cleared using the jobschmsgclear command?

Action method

Execute the jobschmsgclear command at a time that will not affect the job net operation.

The message event can also be generated again using the jobschmsgevent command, however consideration should also be given to the effect on other job nets.

Action 3

Points to check

Was the server stopped at the point when the execution time arrived?

Cause

If Startup on power-on if power is off during scheduled execution is not selected in Job Net Properties, the scheduled start for that day will be skipped at the point when the server starts.

Action method

If the Startup on power-on if power is off during scheduled execution check box is selected in Job Net Properties, the job net will start the next time Jobscheduler starts.