Chapter 1
Preparing to Install PL/I
This chapter describes the preparations and requirements needed prior to installing Endless PL/I V3.9 for OpenVMS VAX and Endless PL/I V5.0 for OpenVMS Alpha.
Distribution media must be mounted in numerical order. The installation procedure prompts you to mount the volumes. For more information on how to mount distribution media, see your processor-specific installation/operations guide, which also details several options to the installation procedure.
This product provides online release notes. Endless Software Solutions strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the release notes, see Section 1.1, “Accessing the Online Release Notes”.
1.1. Accessing the Online Release Notes
The prompt to display or print the release notes during the installation appears in step 4 of the installation procedure, when you invoke VMSINSTAL with the OPTIONS N parameter.
To obtain the release notes after the installation, type or print one of the following files depending on the OpenVMS operating system you are using:
Endless PL/I V3.9 for OpenVMS VAX
SYS$HELP:PLI$038.RELEASE_NOTES
Endless PL/I V5.0 for OpenVMS Alpha
SYS$HELP:DPLI050.RELEASE_NOTES
Online help also directs you to the release notes file. After the installation, enter the following command:
$HELP PLI RELEASE_NOTES Return
1.2. Prerequisite Software
To install PL/I, you must have OpenVMS VAX Version 5.5 (or a later version) or OpenVMS Alpha Version 6.2 already installed on your system.
1.3. License Registration
The OpenVMS License Management Facility (LMF) is available with all supported versions of the OpenVMS operating systems. To install this product on OpenVMS, first register your PL/I software license. This section contains all the information you need to register your PL/I license.
The Product Authorization Key (PAK), a certificate shipped with PL/I, contains the license-registration information you need to install and run individual software products.
The installation procedure asks if you have registered the PL/I license and loaded the appropriate authorization key. To run the Installation Verification Procedure (IVP), register and load your PL/I license before you begin the installation.
To register a license, first log in to the system manager's account, SYSTEM. You have a choice of two ways to perform the registration:
Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your PAK.
Enter the LICENSE REGISTER command, at the DCL prompt, with the qualifiers that correspond to information on the PAK.
For complete information on using LMF, see the manual on the License Management Utility in the OpenVMS documentation set.
1.4. Installation Procedure Requirements
The following sections describe requirements for installing PL/I.
The installation requires approximately 5 to 30 minutes to complete, depending on your system configuration and the type of media you use. Before you begin, ensure that you have adequate privileges and system resources to support the installation.
1.4.1. Privileges and Disk Space
To install PL/I, you must be logged in to an account that has SETPRV or at least the following privileges:
CMKRNL
WORLD
SYSPRV
Note that VMSINSTAL turns off BYPASS privilege at the start of the installation.
Table 1.1, “Disk Space Requirements” summarizes the disk space requirements for PL/I.
To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt:
$ SHOW DEVICE SYS$SYSDEVICE Return
1.4.2. System Parameters
Installing PL/I requires that certain system parameters be set at certain minimum values, as Table 1.2, “Required Minimum Values for System Parameters” indicates. Depending on the kinds of programs and applications running at your site, you may need to set higher values for some parameters.
| System Parameter |
Minimum Value (Endless PL/I V3.9 for OpenVMS VAX) |
Minimum Value (Endless PL/I V5.0 for OpenVMS Alpha) |
|---|---|---|
| GBLPAGES[a] | n + 1500 | n + 7776 |
| GBLSECTIONS[a] | n + 7 | n + 3 |
| PQL_DASTLM[a] | 24 | 24 |
| PQL_DBIOLM[a] | 18 | 18 |
| PQL_DDIOLM[a] | 18 | 18 |
[a] The values listed are the minimum required on a permanent basis. After the installation, you may raise but not lower these values. | ||
Note
In Table 1.2, “Required Minimum Values for System Parameters”, the values for GBLPAGES and for GBLSECTIONS are the numbers of unused global pages and unused global sections needed on your system to install PL/I successfully.
The values shown for GBLPAGES and GBLSECTIONS apply when the currently installed compiler is a known image or when you plan to install the compiler as a known image after the installation. If the compiler is not currently installed as a known image, the requirement is 1 free global section and 400 free global pages (enough to replace DCLTABLES.EXE).
The following sections describe how to check and change the values of the system parameters.
1.4.2.1. Checking System Parameter Values
To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility (SYSGEN):
$ RUN SYS$SYSTEM:SYSGENReturn
SYSGEN>
At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 1.2, “Required Minimum Values for System Parameters”, unless the compiler is not currently installed as a known image or to be installed as a known image after the installation. The following example displays the current value of the GBLPAGES system parameter:
SYSGEN> SHOW GBLPAGESReturn
After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level.
Note
You must ensure that your system has the necessary SYSGEN quotas for global pages and global sections for the installation. Failure to do so could cause the DCL tables to be corrupted.
1.4.2.2. Calculating the Values for GBLPAGES and GBLSECTIONS
To determine the number of free global pages on your system, invoke the OpenVMS Install Utility, as follows:
$INSTALL ReturnINSTALL>LIST/GLOBAL/SUMMARY ReturnSummary of Local Memory Global Sections 309 Global Sections Used, 28866/13134 Global Pages Used/Unused INSTALL>EXIT Return
When you enter these commands, the system displays a summary of the number of global sections used and the number of global pages used and unused (free). To exit from the OpenVMS Install Utility, use the EXIT command.
PL/I requires the minimum number of free global pages indicated in Table 1.2, “Required Minimum Values for System Parameters”. If the number of free pages is less than the required minimum in Table 1.2, “Required Minimum Values for System Parameters”, you can use the OpenVMS Install Utility to delete an existing known image. You also can increase the maximum value of the GBLPAGES system parameter, a parameter that establishes the limit on the total number of global pages that can be created. To increase this limit, use the OpenVMS System Generation Utility (SYSGEN) to edit the file SYS$SYSTEM:MODPARAMS.DAT. Then invoke the AUTOGEN command procedure, SYS$UPDATE:AUTOGEN.COM. For more information on the AUTOGEN command procedure, see your processor-specific installation/operations guide.
To determine the number of free global sections, first invoke SYSGEN as follows:
$RUN SYS$SYSTEM:SYSGEN ReturnSYSGEN>USE CURRENT ReturnSYSGEN>SHOW GBLSECTIONS ReturnParameter name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections SYSGEN>EXIT Return
The last number displayed is the maximum number of global sections that can be made known to the OpenVMS operating system (the maximum number of global sections that you can set). Use the OpenVMS Install Utility to determine the number of global sections that are in use. Add the number that are in use to the minimum that must be free to install PL/I (indicated in Table 1.2, “Required Minimum Values for System Parameters”). If the sum exceeds the maximum number of global sections that you can set, then increase the number of free global sections until you have enough free to install PL/I. To increase the maximum value of the GBLSECTIONS system parameter, use SYSGEN to edit the file SYS$SYSTEM:MODPARAMS.DAT. Then invoke the SYS$UPDATE:AUTOGEN.COM procedure. For more information on the AUTOGEN.COM procedure, see your processor-specific installation/operations guide.
If the number of global sections used plus the number provided in Table 1.2, “Required Minimum Values for System Parameters” is less than the maximum number of global sections, you can exit from SYSGEN and continue.
A simpler method of finding the number of free global sections and pages available on your system is to use the WRITE command with the F$GETSYI lexical function. The following example shows how to display this information at your terminal (the default device for SYS$OUTPUT):
$WRITE SYS$OUTPUT F$GETSYI ("FREE_GBLPAGES") Return15848$WRITE SYS$OUTPUT F$GETSYI ("FREE_GBLSECTS")Return24
If the values displayed by the system are greater than the values in Table 1.2, “Required Minimum Values for System Parameters”, you need not increase the values for these parameters. If the value of free global pages or global sections is less than the value in Table 1.2, “Required Minimum Values for System Parameters”, increase the maximum values of the GBLPAGES and GBLSECTIONS system parameters.
Section 1.4.2.3, “Changing System Parameter Values with AUTOGEN” describes the procedures for increasing these values as well as those of other system parameters. See the OpenVMS documentation on system management and operations for more information.
1.4.2.3. Changing System Parameter Values with AUTOGEN
Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the ones you reset manually. To change system parameters with AUTOGEN, edit the following file:
SYS$SYSTEM:MODPARAMS.DAT
For example, to change the setting for the WSMAX system parameter, add to the file:
WSMAX = 1024To change the setting for incremental SYSGEN parameters, add to the file:
ADD_GBLPAGES = 2000Then run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt:
$ @SYS$UPDATE:AUTOGEN GETDATA REBOOTReturn
AUTOGEN performs an automatic system shutdown and reboots when it has finished. Rebooting your system makes the new parameter values active. You may also wish to add the [NO]FEEDBACK parameter to the AUTOGEN command line.
1.4.3. Process Account Quotas and Privileges
To use PL/I, each process account must have TMPMBX and NETMBX privileges and the requirements shown in Table 1.3, “Process Account Quotas”.
| Account Quotas | Minimum |
|---|---|
| AST limit (ASTLM) | 24 |
| Buffered I/O quota (BIOLM) | 18 |
| Buffered I/O byte count quota (BYTLM) | 18,000 |
| Direct I/O quota (DIOLM) | 18 |
| Enqueue quota (ENQLM) | 30 |
| Open file limit (FILLM) | 20 |
| Paging file quota (PGFLQUOTA) | 4096 pages |
| Subprocess creation quota (PRCLM) | by user requirement |
| Working set size (WSDEF) |
500 pages (optimally, 1024 to 2048 pages) |
Note
The quotas listed (the paging file in particular) are only the minimum required to compile small programs. Compiling larger modules can require larger values for BYTLM and PGFLQUO. When compiling large modules you should also set WSDEF to at least 2048 pages to prevent excessive page faulting.
Use the OpenVMS Authorize Utility (AUTHORIZE) to compare the current values of these quotas with the requirements for PL/I. For example, the account used in the following example is the SYSTEM account:
$SET DEFAULT SYS$SYSTEM Return$RUN AUTHORIZE ReturnUAF>SHOW SYSTEM Return
To change the values of these quotas, use the OpenVMS Authorize Utility's MODIFY command. For more information, see the VMS Authorize Utility Manual.
1.4.4. Using VMSINSTAL
After you log in to a privileged account to install PL/I, invoke VMSINSTAL, the command procedure that installs these products. Steps 1 and 2 of the installation procedure in Section 2.1, “Installation Procedure for Endless PL/I V3.9 for OpenVMS VAX” and Section 2.2, “Installation Procedure for Endless PL/I V5.0 for OpenVMS Alpha” show an example of this procedure.
Use one of the following commands to invoke the VMSINSTAL procedure:
Endless PL/I V3.9 for OpenVMS VAX
$@SYS$UPDATE:VMSINSTAL PLI039 ddcu: [OPTIONS N]
Endless PL/I V5.0 for OpenVMS Alpha
$@SYS$UPDATE:VMSINSTAL DPLI050 ddcu: [OPTIONS N]
ddcu:Represents a device name where the distribution volumes will be mounted for the PL/I installation media, where dd is the device code, c is the controller code, and u is the unit number. It is not necessary to use the console drive to install PL/I. If use the console drive, you should replace any media you removed from the drive. MUA0: is the device name used in examples in this manual.
- OPTIONS N
Is an optional parameter you should provide if you want to be prompted to display or print the release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you if you wish to display or print the release notes. VMSINSTAL permits the use of several other options. For more information on the other options, see your processor-specific installation/operations guide.
If you do not supply product and device names, VMSINSTAL prompts you for them. To be prompted for the product and device names and to display or print the release notes, enter the following command:
$ @SYS$UPDATE:VMSINSTAL Return
When you invoke VMSINSTAL, it checks to determine:
If you are logged in to a privileged account. ESS recommends that you install software from the system manager's account with your default device and directory set to SYS$UPDATE.
If you have adequate quotas for installation. VMSINSTAL checks for the following quota values:
ASTLM = 24
BIOLM = 18
BYTLM = 18,000
DIOLM = 18
ENQLM = 30
FILLM = 20
If users are logged in to the system. If VMSINSTAL detects that users are logged in to the system, it asks if you want to continue the installation. To continue, enter YES. To stop the installation, press Return.
1.4.5. Backing Up Your System Disk
At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. ESS recommends that you back up your system disk before installing any software. Use the backup procedures that are established at your site. For information on using the OpenVMS Backup Utility to perform a system backup, see the OpenVMS System Manager's Manual.