Usage Note 17298: How to create a user or system level environment variable outside scope
of the command or cmd session that it is created in
Environment variables created by a set command within a Command or CMD
session are not available as user or system level environment variables
outside the scope of the session that they are created in. Applications
that run outside of the command or cmd session do not have access to
environment variables created within the command or cmd session. Once
the command or cmd session is exited, the environment variables created
during the session no longer exist.
To address this issue Microsoft created a utility that can create global
user and system environment variables from within a command or cmd
session called SETX.
Information about downloading and using this utility is available:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs
/en-us/ntcmds_shelloverview.mspx
Operating System and Release Information
| SAS System | Base SAS | Microsoft Windows 2000 Server | 9.1 TS1M0 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M0 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M0 | |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M0 | |
| Microsoft Windows NT Workstation | 9.1 TS1M0 | |
| Microsoft Windows XP Professional | 9.1 TS1M0 | |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M0 | |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M0 | |
| Microsoft Windows 2000 Professional | 9.1 TS1M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2006-05-01 10:09:50 |
| Date Created: | 2006-03-20 12:12:20 |
