Applicable versions and levels
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: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action
Points to check
Is there any difference in the startup method with the previous Systemwalker Operation Manager startup? (For example, the environment variable that is effective when the soperationmgr command is executed.)
Cause
Because of differences in the environment variable when Systemwalker Operation Manager is started, a change has occurred in the environment variable inherited to the job, therefore the job behavior changes. For example, when the user becomes superuser with the su command to execute the soperationmgr command, the inherited environment variable changes depending on whether the su command "-" option is set or not.
Action method
The environment variable that is required to operate the job must be set in the login shell or shell before it is required.
Remarks
The methods to read the environment variables referenced by the job are as follows:
When the job is submitted
Environment variable that takes effect when the soperationmgr command is executed
Job directory path (PATH environment variable)
Path defined in the PATH statement (only when JCL is used)
When the job is executed
Environment variable set when the job is submitted
Environment variable set in Environment variables in the Detail information tab of the Add/Change - Job window
Environment variable set in the login shell
