S_CONFIG is what I use - it represents "System Config Folder" (which makes sense to me and my team). I also use S_LIB, which is where some external UDFs are kept - I don't use that too often now that I use KGen to generate my scripts. S_BIN is also defined, which represents the location for binaries - scripts, executables, and such that are not part of the core O/S.
This was meant to illustrate one method for defining a physical location for storage of config data, and a process for informing all scripts / programs of any language where their config files could be found. You can use any name that suits you, just be consistent.
When you install your utilities, you create the folder where they will be stored, along with the config subfolder, and then you define the SYSTEM environment variable(s) that identify the location(s). 99% of the time, it will be the same place (which might lead you to hard-code the path into your scripts - very bad!). The use of the environment var lets you easily handle the exceptions - Citrix servers come to mind, since they usually have no C: or D: drives themselves.
Glenn
_________________________
Actually I
am a Rocket Scientist!
