Triggering execution when files are created, updated or deleted
Startup of jobs and job nets can be triggered when a certain file is created, updated, or deleted, or depending on whether a certain file exists. You can also specify a combination of these conditions and make jobs and job nets wait for any one of the specified conditions to be met. A wildcard character (*) can be used to specify the file names of files that will trigger execution.
Refer to the Systemwalker Operation Manager User's Guide for information on how to start jobs and job nets triggered when files are created, deleted, or updated. Refer to the Systemwalker Operation Manager Reference Guide for information on the chkfile and jobschchkfile commands.
Triggering execution when mail is received
In addition to using execution schedules based on startup days, job net execution can also be triggered by the receipt of mail. To do this, mail waiting conditions must be set up by defining startup parameters. For more information about defining startup parameters, refer to the Systemwalker Operation Manager Installation Guide.
The type of mail referred here is "e-Mail". For information about the format of mails that can be received, refer to the Systemwalker Operation Manager User's Guide.
The following figure illustrates the flow for starting job nets triggered by the receipt of mail.
Triggering execution when events are output to event logs [Windows version]
Job net execution can be triggered by events being output to event logs by the operating system or other products. In order for the event logs being used as startup triggers to be recognized by the Jobscheduler, the "source name" and "event ID" in the event log must match the message event that is the execution condition for the job net. In order to associate "source names" and "event IDs" with message events, a "message table" must be created.
For information about how to create the message table, refer to the Systemwalker Operation Manager Installation Guide.
Coordinating job times
Job times can be coordinated within job nets. To coordinate job times within a job net, schedule the Jobschchecktime command (time wait command) as the preceding job of the job that needs to wait until a certain time before executing. If the Jobschchecktime command is registered as a job, the job does not end until the specified time comes. The subsequent job can then be executed after the specified time. It is also possible to specify the maximum waiting time, so that if jobs are started after the maximum waiting time, the job completion code will be different, which can be used to change subsequent processing.
For more information about the Jobschchecktime command, refer to the Systemwalker Operation Manager Reference Guide.
Switching between subsequent jobs by analyzing character strings in files
Each line of a specified file can be analyzed to check whether it contains a specified character string. To analyze the file, use the Jobschchecklog command (log file analysis command). Because the completion code of the job varies depending on the result of the analysis, the Jobschchecklog command can be scheduled as a job, and the value of its completion code can be used to switch between alternative subsequent jobs.
Regular expressions can be used to specify the character string. If the specified character string is found, the line including the character string can also be output to the standard output.
The specified file can be analyzed from beginning to end, or analysis can start from the middle of the file. To analyze a file from the middle of the file, specify a key to store ending information. Ending information is stored based on the file name, the user name and the key. Therefore, the same file can be analyzed by multiple users or multiple jobs starting from the end point if the file name, user name and key are unique.
For more information about the Jobschchecklog command, refer to the Systemwalker Operation Manager Reference Guide.
Monitoring scheduled startup times for job nets
It is possible to monitor whether job nets start according to the designated schedule. If a job net does not started at the scheduled startup time, a notification message can be output to an event log [Windows version] or the SYSLOG [UNIX version]. In this case, the start of the job net will be delayed, and so the progress can also be checked using a Gantt chart.
Monitoring scheduled startup times for job nets applies to the following kinds of situations:
When the "Wait for startup time" option is used to start a job net when the conditions for a startup time and a message event are both met, and the message event has still not occurred when the schedule startup time arrives
When a job net belongs to a group and the preceding job net has not completed but the scheduled started time has passed
When a job net belongs to a group and the scheduled startup time has passed because the preceding job net has been canceled or has terminated abnormally
When a job net belongs to a group and the scheduled startup time passes without the message event that it is waiting for occurring
When the scheduled startup time for a job net has been defined with the Start only when message event has occurred option and the scheduled startup time passes without the message event that it is waiting for occurring
When a job net does not start even though the scheduled startup time has arrived, whether a notification message should be output can be defined using a startup parameter for the Jobscheduler service or daemon. For notes on startup parameters, including information about how to define them, refer to the Systemwalker Operation Manager Installation Guide.
If a job net has not started even though the scheduled startup time has arrived, custom processing can be executed using the "job net start delay exit." For more information about the "job net start delay exit," refer to the Systemwalker Operation Manager Reference Guide.
Monitoring scheduled end times for job nets
It is possible to monitor whether job nets have terminated according to the designated schedule. If a job net has not terminated at the scheduled end time, a notification message can be output to an event log [Windows version] or the SYSLOG [UNIX version]. If a job net has not terminated at the scheduled end time, this indicates that the status of the job net is either "executing", "warning" or "waiting." If a job net is still executing after its scheduled end time has passed, the status of the job net is "delayed termination", and so the progress can also be checked using a Gantt chart.
The scheduled end time can be specified either as an absolute time or as a relative time (relative to the time the job net started). Define the scheduled end times for job nets when job net information is registered. For information about how to make these definitions, refer to the Systemwalker Operation Manager User's Guide.
When a job net does not terminate even though the scheduled end time has arrived, whether a notification message should be output can be defined using a startup parameter for the Jobscheduler service or daemon. For notes on startup parameters, including information about how to define them, refer to the Systemwalker Operation Manager Installation Guide.
If a job net has not terminated even though the scheduled end time has arrived, custom processing can be executed using the "job net end delay exit." For more information about the "job net end delay exit," refer to the Systemwalker Operation Manager Reference Guide.
Monitoring the estimated processing time for jobs
If the execution attribute for a job net is "Job Execution Control", a message can be output to the event log [Windows version] or SYSLOG [UNIX version] if the job does not end within the estimated processing time. If a job net is still executing after its estimated finishing time (calculated based on the estimated processing time for the specified job net) has passed, the status of the job net is "delayed termination", and so the progress can also be checked using a Gantt chart.
When a job net does not terminate even though the estimated end time has arrived, whether a notification message should be output can be defined using a startup parameter for the Jobscheduler service or daemon. For information about how to define startup parameters, refer to the Systemwalker Operation Manager Installation Guide.
Define the estimated processing time when jobs are registered. For information about how to make these definitions, refer to the Systemwalker Operation Manager User's Guide.
Turning off the power to the System when job nets terminate [Windows version]
The shutdown exit of the end processing job net provided by the Jobscheduler can be used to turn the power to the system off when a job net terminates.
Specifically, replace the f3crheet end-of-wait notification command in the shutdown exit of the job net that performs the shutdown processing with the shutdown command provided by the operating system.
If the power to the system is turned off by calling the shutdown command from the shutdown exit of the end processing job net, the power will be turned off as soon as the job net terminates. The system will shut down even if the server shutdown time that has been set up in the power schedule has not arrived yet. If the server shutdown time that has been set up in the power schedule arrives before the end processing job net runs, server shutdown processing will be performed even if job nets are still executing. When setting up the server shutdown time in the power schedule, sufficient time must be allowed before the time when the end processing job net runs.
For more information, refer to "Shutting Down the System at Optional Times [Windows version]" in the Systemwalker Operation Manager User's Guide.
Note
Turning the system power off
In order to turn the system power off, the system must be equipped with a power control device (hardware).
Postponing system shutdown until job nets complete
System shutdown processing can be delayed until job nets have completed even if the shutdown time has arrived. This can be done by using the shutdown monitoring options (provided by the Power Control function) and the f3crheet end-of-wait notification command.
Specifically, set the shutdown monitoring options and register the f3crheet command as the last job to be started. This job must be registered so that it starts before the system shuts down.
After the shutdown processing completes, the system power will be turned off by the Power Control function.
For an explanation of the shutdown monitoring options and information about how to set them up, refer to the Systemwalker Operation Manager User's Guide. Also, for information about the f3crheet end-of-wait notification command, refer to the Systemwalker Operation Manager Reference Guide.
Note
Turning the system power off
In order to turn the system power off, the system must be equipped with a power control device (hardware).
Permitting access to projects
With the Jobscheduler, access rights can be set to specify which users are permitted to have access to which projects. For information about setting up access rights, refer to the Systemwalker Operation Manager User's Guide.
