Having scripts in multiple languages - Kix, Bat, & perl - the environment variable(s) allow me to place all scripts & utilities in one folder, and config files in another. Also allows me to apply different permissions to each folder, allowing authorized people to manipulate the config files but not the scripts.
On all servers and admin workstations at every client site, I create (via script) a /local and /local/bin folder structure. S_CONFIG defines the actual location of /local and S_BIN defines the /local/bin path. These are usually on C:. Kix32, some other utilities, and all kix/perl/bat scripts are in the /local/bin folder. Any config file is in /local. Scripts that need to call other scripts can reference $S_BIN%\scriptname, and config files are referenced by %S_CONFIG%\configfile.
A minor clarification of Mart's reply - the environment variable names are "S_BIN" and "S_CONFIG" - you can verify this by typing "set" at a command prompt. You reference or define the variable name by "VARNAME", but you reference its CONTENTS by "%VARNAME%".
Glenn
PS - the Customize script on my web site can be used to define these environment variables, create the folders, populate the folders with standard scripts, utilities, and script engines, and perform other basic configuration processes. It's all controlled by an ini file, so easily customized. I run it on all servers, and on the workstations of any system/network admin that needs access to the admin tools that it installs.
_________________________
Actually I
am a Rocket Scientist!
