You can set any kind of environment variable you like and you can define environment variables for all Remote System Explorer connection types (IBM® i, Windows, Linux, and UNIX). If you change an environment variable while the Remote System Explorer is connected to a remote server, the change does not take effect until you disconnect and reconnect. Although environment variables are set in subsystem properties pages, the Remote System Explorer stores them globally by connection.
When you need to specify different environment variables, initial library lists, or user IDs, you can do so by defining multiple connections to your server. For example, you can set your class path variable, used by the Java™ Virtual Machine to locate class files, with a value of /home/your userid:/QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar. You could also write a program that uses any environment variable that you define.
Environment variables are set for the remote job process when you first connect to a remote system. This means that the results of the variables are shown in the Commands view. For example, the Commands view shows the ADDENVVAR CL command that is run for each variable. If the system type you are using is case sensitive (UNIX for example), then the environment variables will also be case sensitive. Spaces and equals signs (=) are only allowed in the Value for the environment variable. When setting environment variables for IBM i connections, the variables apply to all jobs (interactive, batch, and normal) associated with the connection.
To configure environment variables: