6.2.21 Settings for enabling an environment variable in a job definition when the name is the same as a system environment variable name
If an environment variable#2 specified in a job#1 definition contains lower-case alphabetic characters and a system environment variable uses the same spelling but the use of case is different, an environment variable containing lower-case alphabetic characters might not take effect.
- #1
-
A PC job (except a queueless job) or a submit job to be executed by the jpqjobsub command.
- #2
-
One of the following applies:
-
An environment variable specified in the Environment variables field in the JP1/AJS3 - View Define Details - [PC Job] dialog box, or specified for the -env option of the jpqjobsub command.
-
An environment variable in the environment variable file specified either in the Environment variable file field in the JP1/AJS3 - View Define Details - [PC Job] dialog box, or specified for the -ev option of the jpqjobsub command.
-
The following table describes the relationship between the presence of lower-case alphabetic characters and the environment variables that take effect.
|
Environment variable defined in the job definition |
System environment variable |
Environment variable setting that takes effect |
|
|---|---|---|---|
|
Example when there are lower-case alphabetic characters |
Aa=www AB=yyy |
AA=xxx AB=zzz |
AA=xxx AB=yyy |
|
Example when there are no lower-case alphabetic characters |
AA=www AB=yyy |
AA=xxx AB=zzz |
AA=www AB=yyy |
In the table, in the first-row example, environment variable Aa contains lower-case alphabetic character a. The system environment variable AA has the same spelling but its case is different. As a result, the system environment variable AA takes effect but the environment variable Aa in the job definition does not.
To enable the specification of environment variables containing lower-case alphabetic characters in job definitions, enable the setting described here according to the procedure below. Note, however, that this setting need not be enabled if there are no environment variables that duplicate the spelling of system environment variables, with upper or lower cases.
This setting must be specified on the host on which the jobs will be executed.
- Organization of this subsection
(1) Definition procedure
-
In Windows Control Panel, open the Services administrative tool, and stop the following service:
-
JP1/AJS3 service
- Cautionary note:
-
For a cluster system, check the cluster settings and stop the JP1/AJS3 service on the logical host.
-
-
Execute the following command to set the environment setting parameters described in (2) below:
jajs_config -k definition-key "parameter-name"=value
-
Restart JP1/AJS3.
The contents of the configuration file are applied to the system.
(2) Environment setting parameter
|
Definition key |
Environment setting parameter |
Explanation |
|---|---|---|
|
[{JP1_DEFAULT|logical-host}\JP1NBQAGENT\Job]# |
"MergeEnvMode"= |
Specifies whether to enable an environment variable in a job definition when its name duplicates a system environment variable name. |
- #:
-
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.
For details about the definition of this environment setting parameter, see 20.5.2(86) MergeEnvMode.