Jobs that are executed on servers other than the schedule server are referred to as network jobs. ("Servers other than the schedule server" can be any servers that have Systemwalker Operation Manager installed and are connected via the network.)
This section explains the items to be considered when executing job nets or jobs as network jobs.
Items to be considered
Network jobs can be specified as individual jobs or as individual job nets (jobs within a job net).
To specify individual jobs, select the Submit the job as a network job check box in the Add/Change - Job window.
To specify individual job nets, select the Submit the jobs of the job net as a network job check box in the Standard information tab of the Job Net Properties window.
Determine which servers will execute network jobs.
For multi-subsystem operations, network job requests can be sent to a subsystem of the local host.
It is possible to reject network jobs coming from unexpected servers.
For execution servers, determine which servers they will accept job execution requests from. Immediately after Systemwalker Operation Manager is installed, the default settings are to accept requests from all servers.
Refer to "Defining a Trust Host" in the Systemwalker Operation Manager Installation Guide for details.
Consider code conversion when executing network jobs between servers with different character encodings.
To perform code conversion, create definitions in the Define Operating Information window on the server from which jobs are submitted (server where Systemwalker Operation Manager has been installed).
Refer to "Definition of Job Execution Control" in the Systemwalker Operation Manager Installation Guide for details.
When network jobs are executed between Windows and UNIX platforms, the execution priority will be converted. Ensure that there are no problems with priorities after conversion.
Refer to "Controlling Job Execution Environments" in the Systemwalker Operation Manager Technical Guide for details.
