Job startup can be triggered by a particular file creation, update (update time or size is changed), or deletion. This section explains how to use these changes in the file status as triggers for starting jobs.
The table below lists the changes in file status and the corresponding job type. Depending on the job type, you may be able to specify multiple changes in file status at one time.
Operation that changes the file status | Name of corresponding job |
|---|---|
Determine the existence of the file | Determine File Existence job |
Wait for file creation |
|
Wait for file deletion | |
Wait for file update (update time or size) |
To start a job by using a change in its status, define a Determine File Existence job or Wait for file job as the preceding job of the job you want to start.
You can use a wildcard character (*) when specifying the file name of a Wait for file job.
The Determine File Existence job and Wait for file job correspond to the chkfile command in the Windows version and the jobschchkfile command in the UNIX version respectively.
Refer to the Systemwalker Operation Manager Reference Guide for details such as the synopsis of the chkfile and jobschchkfile commands.
Using a change in file status as a trigger to execute jobs
To use a change in file status as a trigger to execute jobs, register a Determine File Existence job or Wait for file job as the first job in the job net. When the job net meets the execution conditions, the existence, creation, update, or deletion of a file can be used as a startup trigger for processing the succeeding job net.
By combining this type of trigger with the jobschmsgevent command, you can automatically start other job nets after they have waited for a file to be created, updated, or deleted.
