The VisualAge C++ Environment (OS/2, Windows)

VisualAge C++ uses a number of operating system environment variables to record system information such as the location of files used by the product. The VisualAge C++ environment is designed for security, and stores its settings separate from the environment of the operating system. This eliminates the potential for conflicts with other software that may be installed on the same workstation, and minimizes the impact on the environment space of the operating system.

When you start a component of VisualAge C++ by selecting any of the icons in the VisualAge C++ folder on the OS/2 desktop, the VisualAge C++ environment is automatically loaded.

When you start a component of VisualAge C++ from the Windows Start menu or by clicking on a shortcut, the VisualAge C++ environment is automatically loaded.

To work from the command line, you should use the VisualAge C++ command line window. Other command line sessions do not provide the VisualAge C++ environment. The VisualAge C++ command line windows is one of the selectable components set up when you install the product.

To install process stores the full path of the root directory in which all VisualAge C++ files reside in the environment variable VACPPMAIN. The rest of the environment is set by a batch file that resides in the subdirectory bin of the VisualAge C++ root directory. Selecting a product icon on the desktop runs setenv.bat automatically so you do not have to run it manually. However, you can load the VisualAge C++ environment in any command line window by entering the command:

 %vacppmain%\bin\setenv.bat

The file setenv.bat is an ordinary DOS command file. Do not modify or delete the commands in setenv.bat because they are needed by the components of the VisualAge C++ However, you can add additional settings to save a customized development environment. Alternatively, you can create a second batch file that records your personal setting then chains to setenv.bat.

Because VisualAge C++ runs in a protected environment, it can coexist with previous versions of VisualAge C++ and predecessor products, other IBM software products, and non-IBM software. It does not interfere with the environment setting of other software and is protected from changes that other software may make to the operating system environment. This is particularly helpful if you are migrating projects from other application development environments.

You cannot run tools from two different versions of VisualAge C++ in the same environment. Use the VisualAge C++ command line window for tools supplied with the current version of VisualAge C++. If a previous version is also installed on your workstation, you can run tools supplied with that version from other command line windows. Some tools, such as ilib, have the same name in more than one version of the product. When this happens, the environment settings determine which version is used.



Application Run-Time Environment Variables
Migration Tools