Installing on the workstation

This document provides information you need to install VisualAge PL/I Version 2.1.10 on your workstation. For information on installing the host components required for remote ECD, see Installing on the host.

Before you start the installation, be sure you have done the following:

You have read the readme.htm file for late-breaking information or other information that supplements the VisualAge PL/I online help.
Your workstation meets the hardware and software requirements for the components of VisualAge PL/I that you choose to install, and for the applications you want to operate with VisualAge PL/I. Also make sure that your workstation has enough virtual memory. Your paging file should be 128 MB.
If the contents of the Windows CD are not already on your workstation, you have a Windows CD for installing and configuring the MS Loopback Adapter.
If you have IBM AntiVirus installed on your workstation, you have V3.02 or greater. Remove any earlier versions from your workstation before you install.
If you plan to use IBM VisualAge C++ Version 3.5 for Windows, you have installed it before you install IBM VisualAge PL/I.

After the installation, be sure to configure your browser so you can access VisualAge PL/I online help.

RELATED REFERENCES
Required hardware
Required software
Optional software

Installing VisualAge PL/I Version 2.1.10 Refresh over a VisualAge PL/I Version 2.1.6 or earlier product

This section provides instructions for installing IBM VisualAge PL/I Version 2.1.10 Refresh over a VisualAge PL/I Version 2.1.6 or earlier VisualAge PL/I Version 2.1 product installation. You must have administrator authority to complete the installation.

Warning: Applying this FixPak will remove the Application Understanding and Program Understanding components of this product. If you wish to further utilize these functions, please do not proceed with the installation of this FixPak.

Basic installation: installing on your local hard drive

To install VisualAge PL/I on your local hard drive, do the following steps:

Remove any files that you want to retain from the product directories (for example, ibmpliw) and save them elsewhere on your workstation before uninstalling.

The following are files created by IBM VisualAge PL/I components that you might want to save:

Component	File name	Directory where located	Comments
PL/I project environment	Project (.wfp and .wfo) files and source directories Files if you used Tools Setup to modify any actions	ibmpliw directories ibmpliw\mainproj	If you put the project files in a directory outside ibmcpli when you created a project, no action is needed.

Insert the IBM VisualAge PL/I CD in the CD-ROM drive.
Select Start -> Run, and type x:\setup.exe, where x is the CD-ROM drive.
Reply Yes when asked if you would like the previous version of VisualAge PL/I removed.
At this point the Uninstall Dialog will be started.
Reply Yes when asked if you would like to uninstall VisualAge PL/I.
Reply Yes when asked if you would like to restart the system.
After the system has rebooted, the IBM VisualAge PL/I V2.1.10 Setup Dialog will be started.
Follow the prompts to complete the installation.

Important: The default installation directory for VisualAge PL/I Version 2.1.10 is c:\Program Files\IBM\VAPLI. However, you can install VisualAge PL/I in the c:\ibmpliw directory, which was the default installation directory in previous versions, or another directory of your choosing.

Important: The estimates for the amount of space required are too low for FAT file systems (but correct for NTFS and HPFS formatted target drives). The cluster size has not been rounded up. Allow approximately 400 megabytes for a basic installation if you selected all of the components. If you selected only some of the components, multiply by 1.7 the space that the installation program says is required. This factor may be a little lower on a smaller disk where the FAT cluster size is smaller.

Shut down and restart your computer.
If you had any shortcuts, associations, or links to a previous installation of IBM VisualAge PL/I on your workstation, you should verify or update them now.
Configure your browser for online help.

Configuring components after installation

The following components require configuration or setup after you install. Instructions are provided in the Information Center.

Your browser (for online help)
Remote edit-compile-debug (remote ECD)
Remote DL/I
SMARTdata UTILITIES (SdU)

For more information on the product or to report problems, refer to the IBM PL/I Web site.

After completing the Year 2000 transition successfully, we have shifted our focus in the product by providing updates to our remote connectivity components. In doing so, we have removed the Application Understanding and Programming Understanding components from the base install of the product. If you require subsequent use of these components and functionality, please contact your IBM rep for further information on obtaining these tools.

Installing VisualAge PL/I Version 2.1.10 Refresh if Version 2.1.7 or later is already installed

To install IBM VisualAge PL/I Version 2.1.10 Refresh on a workstation with VisualAge PL/I Version 2.1.7 already installed, do the following steps:

Insert the IBM VisualAge PL/I 2.1.10 CD in the CD-ROM drive.
Select Start -> Run, and type x:\setup.exe, where x is the CD-ROM drive. The IBM VisualAge PL/I Setup window opens.
Select Repair and click Next.
Follow the prompts to complete the installation. Your original installation directory is retained.
Shut down and restart your computer.
If you had any shortcuts, associations, or links to a previous installation of IBM VisualAge PL/I on your workstation, you should verify or update them now.
Configure your browser for online help.

Installing and configuring the MS Loopback Adapter on Windows NT

You must install and configure the MS Loopback Adapter to be able to connect to an MVS system. You can install the MS Loopback Adapter after you install VisualAge COBOL, but it must be installed before you start the MVS connections manager for the first time

To install the MS Loopback Adapter on Windows NT, follow these steps:

Right-click the Network Neighborhood icon on your Windows NT desktop. Click Properties and select the Adapters tab.
On the Adapters page, click the Add button.
In the Select Network Adapter window, select MS Loopback Adapter from the Network Adapter list. Click OK.
In the MS Loopback Adapter Card Setup window, click OK to accept the frame type.
In the Windows NT Setup window, specify the location of the installation files for the adapter. If the installation files are on your workstation, the directory where they reside is indicated. If not, the directory where they reside on the Windows NT CD-ROM is indicated, and you will need to insert the CD-ROM.
Click Continue. The MS Loopback Adapter will be added to the Network Adapter list. Click Close.

To configure the MS Loopback Adapter, do these steps:

In the Microsoft TCP/IP Properties window, select the MS Loopback Adapter from the Adapter list.
Click the button for specifying an IP address and enter the IP address, 192.168.2.1. Do not click the button to obtain an IP address from a DCHP server.
Move the cursor to the Subnet Mask field. This field should contain 255.255.255.0. Leave the Default Gateway blank. Click OK.
Reboot your workstation.

To verify that the MS Loopback Adapter was installed and configured, do these steps:

Right-click Network Neighborhood, then click Properties.
Click the Services tab. On the Services page of the Network window, click NetBIOS Interface, then click Properties.
In the NetBIOS Configuration window, you will see that a Lana number with the value NetBT->NDISLoop has been added.

In some cases, you can increase the speed of bringing up certain tasks by placing the Loopback Adapter last in the protocol bindings. To do this:

Right-click Network Neighborhood, and then click Properties.
Click the Bindings tab. On the Bindings page in the Network window, select all protocols in the box next to Show Bindings for.
Expand each protocol option by clicking the + sign.
For each protocol where MS Loopback Adapter appears, click MS Loopback Adapter and then click Move Down until each occurrence of MS Loopback Adapter is last in the list of bindings for each protocol.

Installing and configuring the MS Loopback Adapter on Windows 2000

To install the MS Loopback Adapter on Windows 2000, follow these steps:

Click Start -> Settings -> Control Panel.
In the Control Panel window, click Add/Remove Hardware.
Click Next at the welcome screen.
Click Add/Troubleshoot a device in the task list, then click Next.
Click Add a new device in the list of hardware devices, then click Next.
Click No, I want to select the hardware from a list when prompted to search for the new hardware, then click Next.
Click Network adapters in the list of hardware types, then click Next.
Click Microsoft in the Manufacturers list and Microsoft Loopback Adapter in the Network Adapter list, then click Next.
Click Next again to start the hardware installation, then click Finish after the hardware is installed.

To configure the MS Loopback Adapter, do these steps:

In the Control Panel window, click Network and Dial-up Connections.
In the Network and Dial-up Connections window, right-click the appropriate Local Area Connection for the Loopback Adapter and then click Properties.
In the Local Area Connection Properties window, select Internet Protocol (TCP/IP). Clear all other boxes so that no other components in the list are selected; if other components are selected, the connection to an MVS system will not work. Click the Properties button.
In the Internet Protocol (TCP/IP) Properties window, click the button for specifying an IP address and enter the IP address, 192.168.2.1. Do not click the button to obtain an IP address from a DCHP server.
Move the cursor to the Subnet Mask field. This field should contain 255.255.255.0. Leave the Default Gateway blank. Click OK.
Reboot your workstation.

Configuring your browser for online help

If your organization uses a proxy server for connecting to the Internet, the proxy configuration for your browser must include the following exceptions for the VisualAge PL/I help system to work: localhost:49213,127.0.0.1. These proxy exceptions allow your browser to bypass the proxy and access the help system directly. The installation program for VisualAge PL/I checks your browser's proxy configuration and will update it for you. However, in the following cases you may need to manually update your browser's proxy configuration:

If you are using VisualAge PL/I from a user ID other than the one from which PL/I was installed.
If your browser's proxy exception settings have been changed after installation (for example, the IE setup wizard was run).
If you declined to have your proxy settings updated during the installation.

Configuring Netscape

To check that your browser configuration for Netscape 4.x is correct, do the following steps:

In Netscape, click Edit -> Preferences.
In the Preferences window, click Advanced -> Proxies.
If the Direct connection to the Internet button is selected, no action is required.
If the Automatic proxy configuration button is selected, contact your system administrator to ensure that 127.0.0.1 is included in your proxy exceptions.

If the Manual proxy configuration button is selected, do the following steps:
1. Click View (next to the Manual proxy configuration button).
2. In the Manual Proxy Configuration window, add localhost:49213,127.0.0.1 to the list of proxy exceptions at the bottom.
3. Click OK on both the Manual Proxy Configuration window and the Preferences window to have your changes take effect.

If you use VisualAge PL/I without a TCP/IP connection to a network, and you use Netscape for viewing the online help, you must click the Direct connection to the Internet button for the online help to work.

Configuring MS Internet Explorer

To check that your browser configuration for Internet Explorer 5.x is correct, do the following steps:

In Internet Explorer, click Tools -> Internet Options.
In the Internet Options window, click the Connections tab.
Click the LAN settings button at the bottom of the Connections page.
If the Use a proxy server box is not checked, no action is required.

If the Use a proxy server box is checked, do the following steps:
1. Click Advanced (next to the Use a proxy server box).
2. In the Proxy Settings window, add localhost:49213;127.0.0.1 to the list of proxy exceptions at the bottom.
3. Click OK on both the Proxy Settings window and the Local Area Network (LAN) Settings window to have your changes take effect.

Resetting environment variables

To reset environment variables, follow these steps:

Click Start -> Settings -> Control Panel.
In the Control Panel window, double-click the System icon, and then click the Environment tab.
On the Environment page, set the variables to the appropriate values (as discussed in the sections below). That is, for each variable, do as follows:
- Type the name of the variable (for example, IPF_PATH32) in the Variable box.
- Type the value of the variable (for example, c:\ibmpliw, where c:\ibmpliw is the path where VisualAge PL/I was installed) in the Value box.
- Click the Set button.
Click OK after setting all the variables.

After uninstalling PL/I or C++

VisualAge PL/I Version 2.1 and VisualAge C++ Version 3.0 use the same names for environment variables for some components. If you have VisualAge C++ already on your system when you install VisualAge PL/I, VisualAge PL/I will reset these variables for PL/I usage.

If you install VisualAge C++ after VisualAge PL/I, uninstalling VisualAge C++ will not restore your PL/I values. You will need to reset the following environment variables for IBM VisualAge PL/I, where c:\ibmpliw is the path where IBM VisualAge PL/I was installed:

Variable	Value
IPF_PATH32	c:\ibmpliw

If you uninstall IBM VisualAge PL/I, you may need to manually reset the environment variables for VisualAge C++ to their original settings, where c:\ibmcppw is the path where IBM VisualAge C++ was installed:

Variable	Value
IPF_PATH32	c:\ibmcppw

Using your own macros for the editor

Before you installed IBM VisualAge PL/I, you may have had your own macros for the language-sensitive editor, which the LPATH or LPATH2 environment variable pointed to. If so, you need to append the contents of the LPATH or LPATH2 environment variable to the contents of the environment variable that VisualAge PL/I created, PLILPATH4.

For example, suppose that before you installed IBM VisualAge PL/I, LPATH or LPATH2 contained d:\MYMACROS. During the installation of VisualAge PL/I, the PLILPATH4 environment variable was set to e:\Program Files\IBM\VAPLI\MACROS. To make your macros available, you would update the PLILPATH4 environment variable to be e:\Program Files\IBM\VAPLI\MACROS;d:\MYMACROS.

Installing by using a response file

With a normal (nonsilent) installation, you provide the necessary input in the form of responses to requests for information. With a silent installation, the response file for InstallShield Silent contains the input and no messages are displayed. Instead, a log file captures the installation information, including whether the installation was successful.

A response file is a text file that contains information similar to what an end user would enter as responses to requests for information when running a normal installation. InstallShield Silent reads the necessary input from the response file at run time. The format of a response file resembles that of an .ini file, but a response file has the .iss extension.

You might want to use a response file when you have many workstations on which to install the product and do not need to observe each install process.

To install IBM VisualAge PL/I by using a response file, follow these steps:

Create a response file. You can have InstallShield create the response file for you, or you can write the response file, perhaps using the response file setup.iss, which is provided, as a template. To have InstallShield create the response file for you, enter:
```
setup -r
```
As you do a normal installation, InstallShield records your installation choices in setup.iss and then puts the file in the Windows folder (c:\WINNT on most systems). If you have the system restarted at the end of the installation when you record the response file, the silent installation will also restart the system when it finishes. You may want to copy the response file to a diskette or network drive to use it later.
Run the installation in silent mode using InstallShield Silent. Enter, for example:
```
d:\setup -s -f1a:\setup.iss -f2a:\vad3.log
```
The -s parameter requests a silent installation, the -f1 parameter gives the location and name of the response file to use, and the -f2 parameter gives the location and name of the log file to use.
Review the log file, especially the return values, to verify that the silent installation succeeded.

Setup parameters for silent installation

You can pass setup parameters directly to the setup program (setup.exe) or put them into a setup.ini file. If you use the parameters, observe these guidelines:

Put a slash (/) or a dash (-) in front of each parameter.
Put a space between parameters but not inside a parameter. For example, the following command is valid:
```
/s /f1a:\setup.iss
```
The following command is not valid:
```
/s/f1 a:\setup.iss
```
When you use long path and file name expressions with parameters, enclose the expressions in double quotation marks. These quotation marks tell the operating system not to treat the spaces within the quotation marks as delimiters.
You can use uppercase or lowercase letters for all of the parameters except -SMS.

The command-line parameters are:

Parameter	Purpose	Comments
-f1	To specify the location and name of the response file	InstallShield Silent will read the response file that you specify.
-f2	To change the location and name of the log file that InstallShield Silent creates	By default, setup.log is created and stored in the same folder as setup.exe.
-m	To cause InstallShield to generate a management information format (.mif) file at the end of installation	Do not include a path. The .mif file is always placed in the Windows folder. If you do not specify a file name, the file is called status.mif.
-r	To cause the setup program to generate a file (.iss) for silent installation	The response file is a record of the installation input that you use as you step through a normal installation. It is stored in the Windows folder.
-s	To have InstallShield Silent run a silent installation
-SMS	To prevent a network connection and keep the setup program from closing before the installation is complete	You can use this parameter when installing from a Windows NT server over a network. SMS must be uppercase.

RELATED TASKS
Installing by using a response file

RELATED REFERENCES
Setup log file for silent installation

Setup log file for silent installation

Setup.log is the default name for the log file that results from the silent installation. Its default location is Disk1 in the same folder as setup.exe. You can specify a different name and location for setup.log by using the -f1 and -f2 parameters with the setup program..

Setup.log has three sections:

Section	Name	Identifies:
1	[InstallShield Silent]	Version of InstallShield used in the silent installation File as a log file
2	[Application]	Name and version of the installed application Company name
3	[ResponseResult]	Result code indicating whether or not the silent installation succeeded

InstallShield puts one of the following return values after the ResultCode keyname:

Value	Meaning
0	Success
-1	General error
-2	The mode is not valid.
-3	The required data was not found in the setup.iss file.
-4	Not enough memory is available.
-5	The file does not exist.
-6	Cannot write to the response file.
-7	Cannot write to the log file.
-8	The path to the InstallShield Silent response file is not valid.
-9	The list type (string or number) is not valid.
-10	The data type is not valid.
-11	Unknown error during setup.
-12	The dialogs are out of order.
-51	Cannot create the specified folder.
-52	Cannot access the specified file or folder.
-53	The option selected is not valid.

RELATED TASKS
Installing by using a response file

RELATED REFERENCES
Setup parameters for silent installation