This section outlines the basic operation procedures for the Job Execution Control function.
1) Designing and setting up the job environment
Design the job environment so that a reliable and efficient job execution environment can be created. The design content can be set up using either the Define Operating Information window or an initialization file.
For more information, refer to the Systemwalker Operation Manager Installation Guide or the Systemwalker Operation Manager Online Help.
2) Executing jobs
Jobs can be executed once they have been created. If job execution is automated, job submission is mainly managed by the Jobscheduler. However, the Job Execution Control function is used when jobs are submitted without being scheduled.
Jobs submitted by the Jobscheduler are called "scheduled jobs," and jobs submitted by Job Execution Control are called the "demand jobs." For information about executing demand jobs, refer to the Systemwalker Operation Manager User's Guide.
3) Checking the status of jobs and queues
The status of scheduled jobs can be viewed in the Jobscheduler window, and the status of demand jobs can be viewed in the Job Execution Control window.
If an execution delay occurs with either a scheduled job or a demand job, check the operational status of queues.
4) Operating jobs and queues
If job execution does not proceed smoothly, perform operations (such as changing execution queues, changing job priorities, suspending execution, or deleting jobs) as necessary.
For information about job and queue operations, refer to the Systemwalker Operation Manager User's Guide.
5) Saving job execution histories and operation records
The following files can be saved as history information about job execution.
For multi-subsystem operations, this file can be collected for each subsystem.
Log (execution history) files
Achievement record files
These files can be used to analyze the job submission status on servers where Systemwalker Operation Manager has been installed. To collect these files, make specifications in the Logging sheet of the Define Operating Information window.
For more information about log files and achievement record files, refer to the Systemwalker Operation Manager User's Guide and the Systemwalker Operation Manager Reference Guide.
Information
Example of how to create a job execution environment (with a limited number of executable jobs)
As an example of how to create an efficient job execution environment, the following figure shows the advantages of limiting job multiplicity within the system. Specifically, limiting multiplicity makes it possible to prevent increases or decreases in the number of batch jobs submitted from influencing the response times for online jobs.
