5.5 Shell variables
Shell variables are variables whose values are inheritable once they are defined until a job definition script terminates. JP1/Advanced Shell enables you to specify and use shell variables. You can customize an environment for executing job definition scripts by referencing and changing the values of shell variables.
In Windows, the names of environment variables set when the job controller starts, such as environment variables specified as system properties, are converted to uppercase, and then the environment variables are imported as shell variables if the VAR_ENV_NAME_LOWERCASE parameter is specified as described in the following:
|
VAR_ENV_NAME_LOWERCASE parameter value |
Conversion of environment variable names set when the job controller starts |
|---|---|
|
ENABLE |
Only environment variable names HOME, PATH, and SHELL are converted to uppercase; all other environment variable names are imported as is as shell variables. |
|
DISABLE |
All environment variable names are converted to uppercase and then imported as shell variables. |
If the name of an environment variable set when the job controller starts is not consistent with the naming conventions for variables supported by JP1/Advanced Shell, that environment variable is imported but cannot be used. For details about the naming conventions for variables, see 5.1.2(1) Naming conventions for variables.
In JP1/Advanced Shell, some shell variables cannot be used as variable names. If these shell variables are used, an error message is displayed. The following are the shell variables that are not supported:
COLUMNS, EDITOR, EXECSHELL, FCEDIT, HISTFILE, HISTSIZE, KSH_VERSION, MAIL, MAILCHECK, MAILPATH, POSIXLY_CORRECT, SH_VERSION, TMOUT, VISUAL
You must also not use the shell variables shown below, because they are used internally by JP1/Advanced Shell (however, no error message will be displayed if these shell variables are used):
PS1, PS2, PS3