Job Management Partner 1/Automatic Job Management System 3 Command Reference 2

Appendix A.1 Notes on defining environment variables

This section describes the notes on defining environment variables for job execution.

For a list of environment variables, see the environment variable list in Chapter 1.4 Environment variables.

Use the environment-variable-name=value format to specify an environment variable. To specify more than one environment variable, use a line-feed character to separate each entry, as shown in the following example.

Example:

environment-variable-name-1=ABCD<line-feed character>

environment-variable-name-2=EFGH<line-feed character>

You can separate each entry only by using a line-feed character. Do not use a delimiter such as a semicolon (;) or a colon (:).

Make sure that you specify all entries in the environment-variable-name=value format. If you specify an entry that is not in this format, the job could terminate abnormally depending on the OS of the host on which the job is executed.

You cannot use environment variables that start with AJS (for example, AJSxxxx, where xxxx is any string) regardless of whether you specify them in uppercase or lowercase. These variables are reserved in the system.

You cannot use environment variables that start with JP1 (for example, JP1xxxx, where xxxx is any string) regardless of whether you specify them in uppercase or lowercase. These variables are reserved in the system.

You cannot set the following environment variables for Environment variables of a job definition or in a file you specify for Environment file of a job definition:

AJSENV=YES

AJSPRE_ST= termination-status-of-preceding-job-or-jobnet{n|w|a}

AJSPRE_RC=return-value-of-preceding-job (-2147483648 to 2147483647)

AJSNETNAME=root-jobnet-name

AJSJOBNAME=job-name

AJSHOST=name-of-manager-host-requesting-job-execution

AJS_AJSCONF=scheduler-service-name-on-manager-host-requesting-job-execution

AJSEXDATE=scheduled-date-of-execution (yyyy/mm/dd)

AJSEXECID=job-execution-ID

AJSEXECPID=execution-ID-of-generation-for-which-start-condition-is-monitored

JP1JobName=job-name

JP1JobID=job-number (1 to 999999)

JP1UserName=name-of-user-who-submitted-job

HOME=home-directory

SHELL=execution-shell

LANG=language-type

LOGNAME=login-name

MAIL=mail-user-name

PATH=search-path-name

Usually, environment variables are set in JP1/AJS3 and they refer to those listed in Table 1-7 in 1.4 Environment variables, as well as those specified for job definition, and those contained in files specified as environment files for job definition. In addition, environment variables may also be set in the command statements, script files, local login scripts, and system login scripts specified for job definition. If the same environment variables are found in these, they will have the following levels of priority (with the value of 1 as the highest level).

Windows

1. Environment variables specified for Environment variables^#1

2. Environment variables specified for Environment file^#2

3. System environment variables

UNIX

1. Definitions in the commands or script files specified for job definition

2. Definitions contained in local login scripts

3. Definitions contained in system login scripts

4. Environment variables specified for Environment variables^#1

5. Environment variables specified for Environment file^#2

#1

Variables specified for Environment variables in the JP1/AJS3 - View window or those specified with the -env option for the jpqjobsub command.

#2

Variables specified for Environment file in the JP1/AJS3 - View window or those specified with the -ev option for the jpqjobsub command.

When defining an environment variable in a dialog box of JP1/AJS3 - View or in the -env option of the jpqjobsub command, you cannot use a reference to an environment variable. In the following example, the xyz variable is assigned the character string %abc%, and not the value of the abc environment variable.

Example:

abc=1

xyz=%abc%

If you want to use a reference to an environment variable, specify the reference in the batch file or script file for the job to be executed.

Cautionary note

In Windows, normally, JP1/AJS3 is started as the JP1/AJS3 service. Thus, JP1/AJS3 does not read the user environment variables. When a job is executed from JP1/AJS3, the system environment variables read at the start of the JP1/AJS3 service are set for the job. When a cluster system is set up, however, the user environment variables will be valid in the JP1/AJS3 service (logical hosts only) started by MSCS. This is because MSCS reads user environment variables according to the MSCS specifications. For any non-MSCS cluster software, refer to the relevant specifications.

Note that the environment variables that are read when the JP1/AJS3 service is started include not only the system environment variables but also the environment variables that are set at OS startup. Also note that the environment variables specified in the login script are not read.

[Contents][Back][Next]

[Trademarks]