With Systemwalker Operation Manager, a sequence of scripts, commands and execution programs can be registered and executed. These scripts, commands and execution programs are referred to as "jobs." A sequence of jobs is referred to as a "job net."
Systemwalker Operation Manager can process the following jobs.
Batch files [Windows version] and shell scripts [UNIX version]
Execution programs (or commands)
The Job Control Language (JCL) provided by Systemwalker Operation Manager
Systemwalker scripts
Systemwalker Operation Manager Task Link commands
"Systemwalker for Systems Management Server" commands (for SMS commands) [Windows version]
Interstage WorkUnits
The following Interstage WorkUnits can be processed:
TD (Transaction Director) WorkUnits (Windows x86/Solaris 32bit/Linux x86)
EJB (Enterprise JavaBeans) WorkUnits (Windows x86/Solaris 32bit/Linux x86)
Utility WorkUnits (Solaris/Linux)
CORBA WorkUnits (Windows/Solaris/Linux)
Note that the WorkUnits that can be handled vary depending on the operating system and the Interstage version and level. For more information, refer to "3.2 Software Resources".
PowerAIM WorkUnits (only if the connection detection server is running UXP/DS) [UNIX version]
The Interstage WorkUnits and PowerAIM WorkUnits are jobs supported by other products. To link to Interstage refer to "2.16 Linking to Other Products".
All jobs handled by Systemwalker Operation Manager are basically executed by Job Execution Control. However, if the connection destination server is running the UNIX version, Job Execution Control may not be used for the following kinds of jobs.
For PowerAIM WorkUnits provided by UXP/DS PowerAIM, the Jobscheduler links directly to PowerAIM. Queue Control and other Job Execution Control functions are disabled.
The following jobs can be executed only by the Jobscheduler because of compatibility issues with earlier versions of the Jobscheduler.
Shell scripts
Commands
Execution programs
Jobs and file extensions
The following table lists the jobs that can be handled by Systemwalker Operation Manager, the file extensions that are assigned when jobs are stored in files, and how each job is handled by Job Execution Control.
[Windows version]
Jobs | File extension | Recognition by |
|---|---|---|
Job Control Language (JCL) | filename.jcl | Recognized as the Job Control Language (JCL). |
Systemwalker | filename.swt | Recognized as a Systemwalker script. |
Batch file | filename.bat | Recognized as a batch file. |
Executable file | filename.exe | Recognized as an executable file. |
[UNIX version]
Jobs | File extension | Recognition by |
|---|---|---|
Job Control Language (JCL) | filename.jcl | Recognized as the Job Control Language (JCL). |
Systemwalker | filename.swt | Recognized as a Systemwalker script. |
Other jobs | Any extension | Recognized as a command if a binary file is used |
Files with the "inf" extension are created by Job Execution Control for job data control. Do not create shell script files with the "inf" extension.
Scheduled jobs and demand jobs
Jobs submitted from Systemwalker Operation Manager can be divided into the following two types:
Scheduled jobs
Demand jobs
Scheduled jobs can be executed automatically, and are monitored and operated by the Jobscheduler. Scheduled jobs are executed automatically by registering them in job nets.
Demand jobs are not scheduled, and are submitted separately when necessary. These jobs can be submitted directly, or they can be stored in a job folder and submitted when necessary. Once demand jobs have been stored in a job folder, jobs or commands need not be entered each time jobs are submitted.
Online jobs and batch jobs
Systemwalker Operation Manager can schedule all jobs, including batch jobs and online jobs.
Batch jobs are executed in the background process when their startup event, such as the preset time or message, occurs. Batch jobs (and job nets) end when the job processing that has been running ends (except for when jobs are cancelled due to their execution time expiring).
If job nets have Interstage attributes, their end times can be scheduled, as well as their start times. These jobs are referred to as "online jobs."
If online jobs are developed using Interstage, the start and end time of each WorkUnit can be automated by Systemwalker Operation Manager. Any combination of batch jobs can be scheduled before or after online jobs.
Jobs where windows are displayed
Using the Task Link client application startup commands makes it possible to execute applications that display windows on clients. This kind of application can be scheduled by registering client application startup commands as "jobs" in job nets.
Job net execution attributes
Before a scheduled job can be registered, a job net must be registered first. When the job net is registered, the function that will execute the job net can be selected by specifying "Job net execution attributes." These attributes are explained below.
Specify this attribute when jobs are submitted to the Job Execution Control function.
Almost all jobs handled by Systemwalker Operation Manager can be registered by specifying the Job Execution Control attribute. Not only can many different types of jobs be registered with this attribute, the following kind of detailed execution control is also possible. For these kinds of operations, job nets must be registered with the Job Execution Control attribute.
Managing jobs using queues, and controlling the execution priority of jobs and the number of jobs that can be executed concurrently.
Executing jobs on other servers connected via the network.
For more information about using Job Execution Control, refer to "2.3 Job Execution Control".
Specify this attribute to perform startup/shutdown control and monitoring for Interstage WorkUnits.
Interstage WorkUnits that have been registered with this attribute can be controlled via Job Execution Control. This means that Queue Control and other Job Execution Control functions can be used. Job nets with the Interstage attribute are restricted to job nets controlled by Interstage, and only Interstage WorkUnits can be registered with this attribute. Ordinary jobs cannot be registered with this attribute.
Note that WorkUnits that have been started using the Interstage isstart command cannot be managed by Systemwalker Operation Manager. WorkUnits started by Systemwalker Operation Manager are checked by Systemwalker Operation Manager every five minutes. Note that it may take up to five minutes to detect errors that occur.
Specify this attribute to submit WorkUnits to PowerAIM for execution. To execute PowerAIM WorkUnits, job nets must be registered with the PowerAIM attribute. Only PowerAIM WorkUnits can be registered in job nets with the PowerAIM attribute.
Specify the earlier version compatibility attribute to control job execution using the Jobscheduler. The jobs that are registered in job nets with this attribute must be able to be executed by the Jobscheduler alone.
Jobs that cannot be executed by Systemwalker Operation Manager
Systemwalker Operation Manager cannot execute the following jobs. Do not register these jobs with the Jobscheduler.
Windows system commands (such as Notepad)
However, these commands can be executed if the Task Link client application startup command is used with Windows systems.
Interactive commands (such as edlin[Windows version], and more or pg [UNIX version])
Commands or shell scripts that request data entry (such as format and backup)
Jobs registered with the Jobscheduler are executed in background mode. Therefore, if a job that requests input is registered with the Jobscheduler, job execution is stopped when the job requests input and the job continues to be displayed in the Jobscheduler as "executing".
Applications that are not processed correctly when their execution is requested by the AT command [Windows version]
Note that commands that start resident programs do not terminate even after the command processing has completed. (The command is displayed as "Executing".)
If the connection destination server is running UNIX, the following jobs cannot be executed.
Commands that require a control terminal (such as ps and passwd )
Full-screen commands (such as vi and sysadm)
Commands and shell scripts that run in the background
Internal shell commands
