This section explains several points to take into account when designing and creating jobs.
Appendix A, "Important Notes" in the Systemwalker Operation Manager User's Guide also explains points you should note when creating jobs. Refer to the following:
"Cautions on Jobs"
"Notes on Network Jobs"
"When Registering a Backup Command as a Job [Windows version]"
"When Registering the lfmt Command as a Job [UNIX version]"
Commands that cannot be executed for jobs
Design a job so that the following commands are not executed as jobs. If these commands are executed, the behavior of Systemwalker Operation Manager and Systemwalker Centric Manager cannot be guaranteed.
Start commands for Systemwalker Centric Manager and Systemwalker Operation Manager
Stop commands for Systemwalker Centric Manager and Systemwalker Operation Manager
Backup commands for Systemwalker Centric Manager and Systemwalker Operation Manager (unless you specify options to prevent the service or daemon from stopping)
Restore commands for Systemwalker Centric Manager and Systemwalker Operation Manager
qsub command for Job Execution Control
Commands that cause a cluster system to stop if Systemwalker Operation Manager has been registered on the cluster system
Other commands that cause Systemwalker Operation Manager to start
Note that if the system includes Systemwalker Centric Manager, commands that cause Systemwalker Centric Manager to start (-a option of the scentricmgr command and the swstart command of Systemwalker Centric Manager) will also start Systemwalker Operation Manager.
Jobs that cannot be submitted as network jobs
The following jobs and commands cannot be submitted as network jobs:
If a job is a Job Control Language (JCL) file
If the following jobs and commands are used:
Wait for Message Event job
Determine Job Net Variable job
for SMS commands
