Applicable versions and levels
Windows versions: V5.0L10 or later
Action
Points to check
Has the environment variable value been set for the system environment variable?
Cause
The only type of environment variables that can be referenced by applications started from Systemwalker Operation Manager is system environment variables. User environment variables, which are the user specific information, and environment variables set using autoexec.bat, cannot be referenced by applications started from Systemwalker Operation Manager.
Action method
If the application uses an environment variable registered as a user environment variable, one of the following actions is required:
Register the user environment variable that is required to execute the application as a system environment variable (this can be set using Control Panel >> System). Note that the system must be restarted in order for the system environment variable to take effect.
Create a batch file to start the application, and then register the environment variable that is required to execute the application at the start of the batch file.
In V10.0L20 or later, register the environment variable that is required to execute the application in Environment variables in the Detail information tab of the Add/Change - Job window.
Information
In the Windows versions Systemwalker Operation Manager, the job operates as part (child process) of the "Systemwalker MpMjes" service.
The service can only reference system environment variables, therefore, even if the environment variable required to operate the application has been set as a user environment variable, the service cannot see it. As a result, unintended behavior may occur, for example the executable file is not found, or the environment variables required to execute the job are insufficient.
