Job execution directory [UNIX version]
In UNIX system, when a job is registered to a job net without specifying the directory and the job net has the "Compatible with the earlier versions (old and standard)" attribute, the job will be executed in the home directory of the user who has registered it. In case of the " Job Execution Control" attribute, the job will be executed in the home directory of the owner of the project where the job net has been registered.
Environment variables
In UNIX system, the environment variables (HOME, SHELL, LOGNAME, USER, MAIL and PWD) are specified from the password file before the job is started. The directory name is set as the PWD environment variable. The home directory name is set as the HOME environment variable. The value of the SHELL environment variable is set according to "Considering the shell strategy" described later.
With network jobs, the environment variables shown in "Environment variables set by the Jobscheduler" and "Environment variables set by the Job Execution Control" are not inherited.
Information
If both schedule server and execution server of Systemwalker Operation Manager V10.0L20/10.1 or later are used for network jobs, the environment variables which have been set by Environment variables on the Detail information sheet of Add/Change - Job window are inherited to the network jobs. However, if both schedule server and execution server are not Systemwalker OperationMGR V10.0L20/10.1 or later, these environment variables are not inherited.
Environment variables set by the Jobscheduler
Prior to starting jobs, the Jobscheduler assigns values to the following environment variables. Use these environment variables to change processing procedure for the succeeding job depending on the type or the completion code of the preceding job.
USERNAME environment variable [Windows]/ USER environment variable [UNIX]
Stores the owner of project.
PWD environment variable [UNIX]
Stores the job directory name. If it is not specified, this variable stores the home directory name of the project owner.
HOME environment variable [UNIX]
Stores the home directory name of the project owner.
LOGNAME environment variable [UNIX]
Stores the owner name of project.
MAIL environment variable [UNIX]
Stores "/usr/mail/owner name of project". For AIX, stores "/usr/spool/mail/owner name of project". For Linux, stores "/var/spool/mail/owner name of project".
USERDOMAIN environment variable
When connecting to a Windows server, the domain name of the project owner is stored as the USERDOMAIN environment variable. If the domain name is not specified, the value of this environment variable will be omitted.
When connecting to a UNIX server, the value of this environment variable will be omitted, too.
JOBSCH_SUB_SYSTEM environment variable
Stores the subsystem number in an environment where multiple subsystems operate.
JOBSCH_PROJECT environment variable
Stores the name of the project where the job net is registered.
JOBSCH_JOBNET environment variable
Stores the name of the job net.
JOBSCH_JOBNAME environment variable
If the job name to be passed to the Job Execution Control is registered in the job registration information, this variable stores that job name. If the job name is not registered, this variable stores the execution file information (including the qsub command options and the execution file parameters) registered in the Add/Change - Job window.
JOBSCH_JOBNET_DATE environment variable
Stores the value indicating the date of the configuration with which the job net is started up. The value is stored in the "yyyymmdd" format.
JOBSCH_ENVIRONMENT environment variable
Stores the character string "BATCH."
In addition, values are set for the following environment variables when any preceding job exists. If there are multiple preceding jobs, however, the information on the job that triggers the startup of these jobs (the most recently executed preceding job) will be stored.
JOBSCH_PRE_JOBNAME environment variable
If the job name to be passed to the Job Execution Control is registered in the preceding job registration information, this variable stored that job name. If the job name is not registered, this variable stores the execution file information (including the qsub command options and the execution file parameters) registered in the Add/Change - Job window. If there are multiple preceding jobs, however, the information on the job that triggers the startup of these jobs (the most recently completed preceding job) will be stored.
JOBSCH_PRE_JOBCODE environment variable
Stores the completion code of the preceding job.
If there are multiple preceding jobs, however, the information on the job that triggers the startup of these jobs (the most recently completed preceding job) will be stored.
JOBSCH_ROOT_JOBNET environment variable
If the job net is nested, this variable stores the name of the job net in the first layer. If the job net is not nested, this variables store the job net name (the value will be the same as the JOBSCH_JOBNET environment variable).
If the job net has the " Job Execution Control" attribute and the job execution is to be requested to another host (for network jobs) and the job net has the "PowerAIM" execution attribute, this environment variable will not be set.
Environment variables set by the Job Execution Control
Prior to starting jobs, the Job Execution Control assigns values to the following environment variables. Use these environment variables to change processing procedure for the succeeding job depending on the type or the completion code of the preceding job.
JC_CHOST environment variable
Stores the client host name. This is set when submitted from the Edit/Submit Job Information window or the Select/Submit Jobs window.
JC_CUSER environment variable
Stores the name of the job owner.
JC_COMMENT environment variable
Stores the job comment.
JC_EXHOST environment variable
Stores the execution host name.
JC_JOBID environment variable
Stores the job number.
JC_JOBNAME environment variable
Stores the job name.
JC_QUEUE environment variable
Stores the queue name.
QSUB_WORKDIR environment variable
Stores the name of the job submission directory.
JC_SUBSYSID environment variable
Stores the subsystem number in an environment where multiple subsystems operate.
If I/O file transfer has been performed in network jobs and distributed execution jobs, the directory in which the files sent/received on the execution server have been stored is set in the environment variable for the job process that is executed on the execution server.
For network jobs and distributed execution jobs, the host name of the schedule server is set in the environment variable for the job process that is executed on the execution server.
Environment variables that can be browsed by applications [Windows version]
In the following, the environment variables that can be browsed by applications started from Systemwalker Operation Manager are listed according to the job submission method (scheduled jobs, qsub command or Mp_SubmitJob API).
Scheduled jobs
Environment variables registered in the Detail information sheet of the Add/Change - Job window.
Environment variables enumerated in "Environment variables set by the Jobscheduler".
Environment variables enumerated in "Environment variables set by the Job Execution Control".
System environment variables at the moment of startup by the OS.
If an environment variable name exists in more than two of a to d above, the first-enumerated environment variable can be browsed.
Jobs started with the qsub command
Environment variables of the application or batch file executing the qsub command.
They can be browsed only when the -x option is specified in the qsub command.
Environment variables enumerated in "Environment variables set by the Job Execution Control"
System environment variables at the moment of startup by the OS.
If an environment variable name exists in more than two of a to c above, the first-enumerated environment variable can be browsed.
Jobs started by the Mp_SubmitJob API
Environment variables of the application calling the Mp_SubmitJob API.
They can be browsed only when the -x option is specified for the qsub command in the second argument of the Mp_SubmitJob API.
Environment variables enumerated in "Environment variables set by the Job Execution Control".
System environment variables at the moment of startup by the OS.
If an environment variable name exists in more than two of a to c above, the first-enumerated environment variable can be browsed.
The user environment variables which include individual information of the user and the environment variables set in "autoexec.bat" cannot be browsed by applications started from Systemwalker Operation Manager.
When an application uses an environment variable registered as the user environment variable, any of the following actions must be taken to execute the application from Systemwalker Operation Manager.
Register the user environment variables required to execute the application to the system environment variables (in System of the Control Panel).
Create a batch file to start the application, and set the environment variables required to execute the application at the beginning of the batch file.
Register the environment variable in the Detail information sheet of the Add/Change - Job window.
If an application uses environment variables that have been set by either the Jobscheduler or Job Execution Control, the following action must be taken to execute the application from Systemwalker Operation Manager:
Create a batch file for starting the application and pass environment variables to the application from the batch file.
For network jobs, the following environment variables set by the Jobscheduler cannot be browsed.
USERNAME
USERDOMAIN
JOBSCH_PROJECT
JOBSCH_JOBNET
JOBSCH_JOBNAME
JOBSCH_ENVIRONMENT
JOBSCH_PRE_JOBNAME
JOBSCH_PRE_JOBCODE
JOBSCH_ROOT_JOBNET
Up to 512 environment variables can be browsed.
When the number of environment variables exceeds 512, certain undetermined environment variables may become unable to be browsed. To prevent this, delete the unnecessary environment variables from the following so that the total number of environment variables is no more than 512.
Scheduled jobs
Environment variables registered in the Detail information sheet of the Add/Change - Job window.
System environment variables
The system should be rebooted after updating of the system environment variables.
Jobs started with the qsub command
Environment variables of the application or batch file executing the qsub command.
These environment variables need not be deleted because they are not adopted if the -x option was omitted with the qsub command.
System environment variables
The system should be rebooted after updating of the system environment variables.
Jobs started by the Mp_SubmitJob API
Environment variables of the application calling the Mp_SubmitJob API.
These environment variables need not be deleted because they are not adopted if the -x option was omitted with the qsub command in the second argument of the Mp_SubmitJob API.
System environment variables
The system should be rebooted after updating of the system environment variables.
Storage location of temporary files created by application [Windows version]
Many applications create temporary files during execution in the following paths specified in the environment variables.
It is recommended to register these environment variables as the system environment variables.
Environment variable name | Example of value set as an environment variable |
|---|---|
temp | c:\temp (Note) |
tmp | c:\temp (Note) |
This is the path generally used as a directory where temporary work files are created. Create in a drive with a sufficient disk space and register the path name in the TEMP and TMP environment variables.
Updating the system environment variables [Windows version]
Systemwalker Operation Manager starts an application using the registered system environment variables at the system startup. Therefore, to browse added, updated or deleted environment variables from an application, the system must be restarted.
Value of umask [UNIX version]
The Job Execution Control daemon functions by setting the value of umask to "0000". As a result, the application runs with "0000" set as the value of umask if no value is specified for umask in the startup file in the shell of the job executing user (Note) or in the application.
To set a desired access right mode in the directory and files created by the application, set the desired value for umask in the startup file of the shell or the application.
[When the login shell of the executing user is sh or ksh]
/etc/profile, or ".profile" in the executing user's home directory
[When the login shell of the executing user is csh]
/etc/.login, ".login" in the executing user's home directory and ".cshrc" in the same directory.
