You can get a listing of environment variables from your own server with the following two-line Perl program:

Save it with any name and run it on your browser. The script returns the default Environment variables. Five important environment variables are available to your CGI script to help in identifying the end user. HTTP_FROM This environment variable is, theoretically, set to the email address of the user. However, many browsers do not set it at all, and most browsers that do support it allow the user to set any value for this variable.

In general, there is no need to use environment variables with MIMIC. MIMIC is highly configurable in several ways (configuration files, command line options, etc), and environment variables are a convenient way to override default behavior for highly specialized circumstances. The references below contains details for the user-configurable environment variables:

Read the manual page on predefined variables as it includes a partial list of predefined variables available to your script. A complete list of available variables (and much more information) can be seen by calling the phpinfo() function. Be sure to read the manual section on variables from outside of PHP as it describes common scenarios for external variables, like from a HTML form, a Cookie, and the URL. register_globals: important note: Since PHP 4.2.

Starting in maven 2.0.1, you can reference windows and unix environment variables inside your pom.xml or settings.xml using an expression of the form:

However, SLIB provides getenv. Particular implementations may provide functions, e.g. Guile provides getenv.

Alpha systems have a variety of variables with values set up within the SRM system console. These environment variables control the particular behaviour of the console program and the system hardware, the particular console interface presented to the operating system, various default values for the operating system bootstrap, and related control mechanisms---in other words, "the environment variables provide an easily extensible mechanism for managing complex console state.

For Jim Hall's Help program, you need to set the PAGER and HELPPATH environment variables in Autoexec.bat. Reasonable values are: Note that Joe Cosentino has written an html Help program, and we will switch to that when we have enough support for it. Unless otherwise stated, FD-DOC HOWTO documents are copyrighted by their respective authors.

CMake names environment variables using an ENV prefix and surrounding the names in curly braces. Here is an example: MESSAGE("$ENV{PATH}") Reading variables will work in any version of CMake. Writing to them works in CMake 2.2 and higher using the following syntax: SET(ENV{HELLO} "World") Note that there is currently no way to tell apart an empty environment variable value from a variable that is not set at all.

Altering the global environment is platform dependent, and there are limits no matter what you do. In Windows NT, all environment variables are actually registry entries. The system initializes the process environment block based of the registry, and also the environment block of the process that creates the process. Applications can choose to be aware of changes to environment variables by paying attention to the WM_SETTINGCHANGE message.

A complete variable list is provided in the online Sources documentation. It can be accessed from the left navigation bar by clicking on the link titled Sources and then using the link to "information on all sources in the system." Click on the "Complete Variable List" in the Sources documentation Table of Contents to see variables arranged by Group and Sub-Group. Source documentation may also be reached directly.

Not all variables on the New York State Cancer Registry are available in NYSPACED. The variables available in the NYSPACED are listed below. You can also find which variables are available, along with the specific values of these variables, by choosing the dataset from the Data tab in SEER*Stat, then clicking on the data dictionary button.

The service fault management resource identifier (FMRI) of the instance for which the method is invoked.