Environment variables

In some specific cases, you must specify environment variables for the ASM server. These variables are required in these cases:

• An instance started by the ASM server can require an LN environment variable. An environment variable can be set system wide. All LN environments that are installed on the system, and using the same environment variable are forced to use the same, value for this, variable. For example, a bshell must load a shared library for a third-party product, such as the database driver. In this case you must set the appropriate environment variables. On a Windows platform, you must set the environment variable as a system environment variable. A user environment variable is not recognized by ASM. If you have set a system wide environment variable, then you must reboot your system to activate the variable. Any subsequent process that is started by an ASM instance is assumably accessible by the PATH variable if not qualified with a full path name. At default, the ASM instances do not inherit system environment variables, of the user that starts the ASM server. Use the -inherit flag to inherit system or service environment variables by ASM instances.
• On Windows, the ASM Server runs in the context, and with the same environment, in which the server was started. Therefore, on Windows ASM Server runs in system context, and has the variables of that specific system environment.
• On UNIX, no environment variables are defined if the ASM Server was started from, for example, boot time. Environment variables are only available on UNIX after you start working from a shell, such as korn shell or bourne shell and so on. To overcome these problems, start the ASM Server from a shell with the correct environment variables defined. Remember that the shell may affect argument passing. Use for ksh for example; "$@",with quotes, instead of $*. Check the manual page of ksh for more information.
• We do not recommend that you use a system wide set environment variable. Use a shell script or batch file to set the variable. For LN Environments, you can also set variables per LN environment with the Infor Manager snap-in.