jRCS Environment Variables
The table shows how jRCS interprets environment variables.
Needless to say, other jBASE variables can be set in the global system profile if a system-wide setting is desired. These variables will not be modified by jRCS, with exception of JBCPORTNO. On logon, jRCS sets the variable TERM to the term type of the user logging on, and REMOTEHOST to the IP address of the incoming connection.
Additional variables can be configured via the jRCS profile.
Although jRCS retains most environment variables it obtains from the system profile and loads the user's profile under Windows during authentication, it may be desirable for some users to execute a batch file setting additional environment variables on a per-user basis.
jRCS provides this functionality through the use of jRCS profiles. The profiles are stored in file jrcsrc.cmd under Windows and .jrcsrc under Unix. The profiles must be located in the user's home directory to be loaded on start-up.
The profiles follow the format of standard batch files under Windows or shell scripts under UNIX, with the following exceptions:
Limited expansion is performed on variables being set, although the full set of expansion capabilities is not provided under UNIX
In essence, jRCS profiles are similar to remote.cmd file used by jBASE telnetd under Windows. For example, if the system administrator wants to set the user's JEDI_FILEPATH variable during logon, he or she would create a jrcsrc.cmd file under Windows and place it in the user's home directory. The file would have the following content:
rem This is a sample jrcsrc.cmd demonstrating the
rem setting of JEDI_FILEPATH
The example above sets JEDI_FILEPATH to subdirectory FILES of the user's home directory.
To achieve the same result under UNIX, the administrator would create the file .jrcsrc in the user's home directory, with the following content:
# This is a sample .jrcsrc demonstrating the
# setting of JEDI_FILEPATH