Applicable versions and levels
Windows versions: V5.0L20 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 10.0 or later
AIX versions: 10.0 or later
A
The following explains the rights required for executing jobs using Systemwalker Operation Manager.
Job execution rights
Execution rights for network jobs and load distribution [Windows versions]
Job execution rights
Systemwalker Operation Manager jobs are executed using the rights explained below.
Windows versions
Jobs are executed using the rights of the service logon account (the default is "systemwalker" on V13.3.1 or earlier, and the local system account on V13.8.0 or later) specified when Systemwalker Operation Manager was installed.
However, jobs are executed using the following rights if the Execute jobs under the respective job owner's authority check box is selected in the Options tab of the Define Operating Information window:
Project owner in the case of scheduled jobs (jobs managed by the Jobscheduler)
However, the rights of the specified user are used if Effective user name is specified in the Detail information tab of the Add/Change - Job window (can be specified on V10.0L20 or later).
User who submitted the job in the case of demand jobs (jobs submitted using the qsub command, job submission API, Edit Job Information/Submit dialog box or window, or Select/Submit Job window)
However, the rights of the user specified in the -cu option are used if this option is specified in the qsub command or the job submission API.
UNIX versions
Jobs are executed using the following rights:
Project owner in the case of scheduled jobs (jobs managed by the Jobscheduler)
However, the rights of the specified user are used if Effective user name is specified in the Detail information tab of the Add/Change - Job window (can be specified on 10.1 or later).
User who submitted the job in the case of demand jobs (jobs submitted using the qsub command, Edit Job Information/Submit dialog box or window, or Select/Submit Job window)
However, the rights of the user specified in the -cu option are used if this option is specified in the qsub command.
Execution rights for network jobs and load distribution [Windows versions]
Execution rights for network jobs and distributed execution jobs vary depending on the status of the schedule server and execution server. Jobs are executed using the rights explained below.
If the schedule server is Windows version
If the execution server is Windows version
If the Execute jobs under the respective job owner's authority check box is not selected in the Options tab of the Define Operating Information window on the schedule server or execution server
On the execution server, jobs are executed using the rights of the service logon account (the default is "systemwalker" on V13.3.1 or earlier, and the local system account on V13.8.0 or later) specified when Systemwalker Operation Manager was installed. The logon account of the Job Execution Control service must be the same on the schedule server and execution server (the password does not need to be the same, and if the execution server is V13.2.0 or later, the logon accounts do not need to be the same either).
In addition, on the execution server, you must register an account with the same name as the following account on the schedule server:
Project owner in the case of scheduled jobs (jobs managed by the Jobscheduler)
However, the rights of the specified user are used if Effective user name is specified in the Detail information tab of the Add/Change - Job window (can be specified on V10.0L20 or later).
User who submitted the job in the case of demand jobs (jobs submitted using the qsub command, job submission API, Edit Job Information/Submit dialog box and window, or Select/Submit Job window)
However, the rights of the user specified in the -cu option are used if this option is specified in the qsub command or the job submission API.
If the Execute jobs under the respective job owner's authority check box is selected in the Options tab of the Define Operating Information window on the schedule server and execution server
Jobs are executed using the same rights as explained for "Windows versions" under "Job execution rights". The account and password must match on the schedule server and execution server.
If the execution server is UNIX version
Jobs are executed using the rights explained for "UNIX versions" under "Job execution rights".
On the execution server, you must register an account with the same name as the following account on the schedule server (the password does not need to be the same):
Project owner in the case of scheduled jobs (jobs managed by the Jobscheduler)
However, the rights of the specified user are used if Effective user name is specified in the Detail information tab of the Add/Change - Job window (can be specified on V10.0L20 or later).
User who submitted the job in the case of demand jobs (jobs submitted using the qsub command, job submission API, Edit Job Information/Submit dialog box and window, or Select/Submit Job window)
However, the rights of the user specified in the -cu option are used if this option is specified in the qsub command or the job submission API.
If the user is a member of the Windows Administrators group on the schedule server, jobs on the execution server are executed using system administrator (superuser) rights.
If the schedule server is UNIX version
If the execution server is Windows version
If the Execute jobs under the respective job owner's authority check box is not selected in the Options tab of the Define Operating Information window on the execution server
On the execution server, jobs are executed using the rights of the service logon account (the default is "systemwalker" on V13.3.1 or earlier, and the local system account on V13.8.0 or later) specified when Systemwalker Operation Manager was installed.
On the execution server, you must register an account with the same name as the following account on the schedule server (the password does not need to be the same). If the account on the schedule server is for the system administrator (superuser), the account you register on the execution server must be a member of the Administrator group.
Project owner in the case of scheduled jobs (jobs managed by the Jobscheduler)
However, the rights of the specified user are used if Effective user name is specified in the Detail information tab of the Add/Change - Job window (can be specified on V10.0L20 or later).
User who submitted the job in the case of demand jobs (jobs submitted using the qsub command, Edit Job Information/Submit dialog box or window, or Select/Submit Job window)
However, the rights of the user specified in the -cu option are used if this option is specified in the qsub command.
If the Execute jobs under the respective job owner's authority check box is selected in the Options tab of the Define Operating Information window on the execution server
Network jobs cannot be executed. Do not specify network jobs because they terminate abnormally.
If the execution server is UNIX version
Jobs are executed using the rights explained for "UNIX versions" under "Job execution rights".
If the schedule server or execution server is running 10.1 or earlier, on the execution server, you must register an account with the same name as the following account on the schedule server (the password does not need to be the same):
Project owner in the case of scheduled jobs (jobs managed by the Jobscheduler)
However, the rights of the specified user are used if Effective user name is specified in the Detail information tab of the Add/Change - Job window (can be specified on 10.1 or later).
User who submitted the job in the case of demand jobs (jobs submitted using the qsub command, Edit Job Information/Submit dialog box or window, or Select/Submit Job window)
However, the rights of the user specified in the -cu option are used if this option is specified in the qsub command.
Point
If you specify an effective user to execute a job when using network jobs and the Distributed Execution function, the possibility of executing the job is determined by whether the specified user has been registered in the job submitting server and the execution server, as indicated below.
Network jobs [UNIX versions]
Execution server | |||
|---|---|---|---|
User is registered | User is not registered | ||
Submitting server | User is registered | Y | N |
User is not registered | Y (*1) | N | |
Y: The job is executed normally. N: The job is NOT executed because an error occurs when the execution request is processed.
*1: The job is NOT executed if the execution server or the submitting server is running on V10.1 or earlier.
Network jobs [Windows versions] with the Distributed Execution function
Execution server | |||
|---|---|---|---|
User is registered | User is not registered | ||
Submitting server | User is registered | Y | N |
User is not registered | N | N | |
Y: The job is executed normally. N: The job is NOT executed because an error occurs when the execution request is processed.
