Network job names
The job names on an execution server that is used to run network jobs will become the job name on the submitting server + "_" (an underscore character).
Job name on submitting server: Job1
Job name on execution server: Job1_
Job names can be verified using the following methods:
Open the View Job Status/Operate window
Run the qjstat command
View the job execution history information
View the operation result data
Privileges required when a Windows server sends a network job request to a UNIX server
When both of the following conditions are satisfied, jobs will run in a UNIX server with administrator (root) privileges:
The network job request is sent from a Windows server to a UNIX server.
The project owner (the effective user of the job) is a member of the Administrators group on the Windows server.
Notes when the submitting server and execution server are both running Windows
If the submitting server and the execution server are both running Windows and the user name of the job submitter is "root", network jobs may not be able to be executed. You cannot execute network jobs in case a or b below, regardless of whether the job submitter "root" is a system administrator.
To execute network jobs, specify a user other than "root" as the job submitter.
You cannot execute network jobs if all the following conditions are met:
The execution server is V5.0L20 - V13.3.1.
Execute jobs under the respective job owner's authority is specified on the execution server.
The password of the "root" user (job submitter) and the password of the "Systemwalker MpMjes" service logon account user on the execution server are different.
You cannot execute network jobs if all the following conditions are met:
The execution server is V13.8.0 or later.
Define Job Owner's Information is being used on the submitting server.
The combination of whether Execute jobs under the respective job owner's authority is specified on the submitting server or execution server, and whether it is specified on both servers is irrelevant.
The term "job submitter" refers to the following:
The owner of a project executed from the Jobscheduler
(However, if an effective user name has been specified for a job, the effective user name is the job submitter.)
The client user name specified in the -cu option of the qsub command
If the option is not specified, then it refers to the submitting user.
The user who ran the application that uses the job submission API
Notes on sending a network job request from a HP-UX or Linux server to an AIX server
Do not specify Transmission of execution command when sending a network job request from a HP-UX or Linux server to an AIX server. If Transmission of execution command is specified, the following error may be output:
|
To send a network job request from a HP-UX or Linux server to an AIX server, do not specify Transmission of execution command. Instead, either use the AIX resources or send resources (such as commands) to the AIX server beforehand.
Notes on requesting a network job that shuts down or reboots another server
After a network job that shuts down or reboots another server terminates, the following processes that run before the execution result is obtained may generate an error and terminate abnormally:
Processes that establish a network connection from the schedule server to the execution server (Error message: MJS881S)
User authentication processes on the execution server (Error message: MJS819E)
These processes generate an error because they run while the execution server is shutting down or when the system is beginning to start up. The errors are the result of normal shutdown or reboot operations and do not affect the operation of Systemwalker Operation Manager.
If network jobs that shut down or reboot another server are to be used, consider selecting the Ignore completion code check box in the Standard Information sheet of the Add/Change - Job window to ignore all completion codes.
Jobs that cannot be submitted as network jobs
The Network Job function cannot be used in the following situations:
If the job uses Job Control Language (JCL)
If the following jobs and commands are used:
Backup linkage command
"Systemwalker for Systems Management Server" commands (for SMS commands)
