Order Number: AA-J179J-TM
This document contains instructions for installing Kednos PL/I on the OpenVMS VAX and OpenVMS Alpha operating systems. It also explains how to read the online release notes before installing the product.
Revision/Update Information: This revised manual supersedes the PL/I Installation Guide for VAX VMS, Order Number AA-J179F-TL.
Operating System and Version:
For Kednos PL/I for OpenVMS VAX: OpenVMS VAX Version 5.5 or higher
For Kednos PL/I for OpenVMS Alpha: OpenVMS Alpha Version 6.2 or higher
Kednos PL/I Version 3.8 for OpenVMS VAX
Kednos PL/I Version 4.4 for OpenVMS Alpha
Published by: Kednos Corporation, Pebble Beach, CA, www.Kednos.com
Kednos Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Kednos Corporation or an anthorized sublicensor.
No responsibility is assumed for the use or reliability of software on equipment that is not listed as supported in the Product Description.
Copyright Kednos Corporation, 1980-2003. All rights reserved.
The following are trademarks of Hewlett-Packard: Alpha, AXP, DEC, DECnet, DECtalk, DECUS, Digital, MicroVAX, OpenVMS, RMS, RMS-11, RX50, TK50, VAX, VAX Ada, VAX BASIC, VAX BLISS, VMScluster, VAX CDD/Plus, VAX COBOL, VAX DATATRIEVE, VAX DIBOL, VAX DOCUMENT, VAX FORTRAN, VAXinfo, VAX MACRO, VAX Pascal, VAX SCAN, VAXset, VAXTPU, and the DIGITAL logo.
This document was prepared using VAX DOCUMENT, Version V3.3.
This manual describes how to install Kednos PL/I for OpenVMS VAX and Kednos PL/I for OpenVMS Alpha on the OpenVMS VAX and OpenVMS Alpha operating systems respectively.
Keep this document with your distribution kit. You will need it to install maintenance updates or to reinstall this product for any other reason.
For more information about installing PL/I software on OpenVMS systems, see your processor-specific installation/operations guide.
This document is intended for system managers and applies to the current versions and all future maintenance-update versions to the current versions. A major version number is represented by the digits to the left of the decimal point, and a maintenance-update version number is indicated by the digits to the right of the decimal point.
In addition to this guide, the PL/I documentation set includes:
This guide contains cross-references to the following OpenVMS documentation:
Table 1 lists the conventions used in this guide:
|UPPERCASE TEXT||Uppercase letters indicate the name of a command, file, parameter, procedure, or utility.|
|$ @SYS$UPDATE:VMSINSTAL||In interactive examples, boldface type indicates user input. System output, such as prompts and messages, is not shown in boldface.|
|$||The dollar sign indicates the DCL prompt. The operating-system prompt may be different on your system.|
|[Ctrl/x]||In procedures, a sequence such as [Ctrl/x] indicates that you must hold down the key labeled Ctrl while you press another key or a pointing-device button.|
|[Return]||In procedures, a key name enclosed in a box indicates that you press a key on the keyboard.|
|Vertical ellipsis in an example indicates that information not directly related to the example has been omitted.|
|file-spec,...||Horizontal ellipsis indicates that the user can enter additional parameters, values, or information.|
|[logical-name]||Brackets in syntax diagrams indicate that the enclosed item is optional. (Brackets are required, however, as delimiters of a directory name in a file specification or in the syntax of a substring specification in an assignment statement. In addition, default responses appear in brackets () throughout the installation procedure.)|
The word PL/I applies to both Kednos PL/I for OpenVMS VAX and Kednos PL/I for OpenVMS Alpha unless otherwise indicated.
This chapter describes the preparations and requirements needed prior to installing Kednos PL/I Version 3.8 for OpenVMS VAX and Kednos PL/I Version 4.4 for OpenVMS Alpha.
This manual presumes the necessary installation kits have been obtained via FTP from Kednos Corporation and have been placed in a directory called SYS$SYSDEVICE:[KITS]. Adjust your commands to match the directory you use.
This product provides online release notes. Kednos Corporation strongly
recommends that you read the release notes before proceeding with the
installation. For information on accessing the release notes, see
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:
Kednos PL/I for OpenVMS VAX
Kednos PL/I for OpenVMS Alpha
Online help also directs you to the release notes file. After the installation, enter the following command:
$ HELP PLI RELEASE_NOTES [Return]
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:
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:
Note that VMSINSTAL turns off BYPASS privilege at the start of the installation.
Table 1-1 summarizes the disk space requirements for PL/I.
|Kit||Blocks During Installation1||Blocks After Installation|
|Kednos PL/I for OpenVMS VAX||8500||5000|
|Kednos PL/I for OpenVMS Alpha||30,000||27,500|
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]
Installing PL/I requires that certain system parameters be set at certain minimum values, as Table 1-2 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
(Kednos PL/I for OpenVMS VAX)
(Kednos PL/I for OpenVMS Alpha)
|GBLPAGES 1||n + 1500||n + 7776|
|GBLSECTIONS 1||n + 7||n + 3|
In Table 1-2, 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.
126.96.36.199 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:SYSGEN[Return] 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, 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 GBLPAGES[Return]
After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level.
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.
To determine the number of free global pages on your system, invoke the OpenVMS Install Utility, as follows:
$ INSTALL [Return] INSTALL> LIST/GLOBAL/SUMMARY [Return] Summary 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. If the number of free pages is less than the required minimum in Table 1-2, 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 [Return] SYSGEN> USE CURRENT [Return] SYSGEN> SHOW GBLSECTIONS [Return] Parameter 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). 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 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") [Return] 15848 $ WRITE SYS$OUTPUT F$GETSYI ("FREE_GBLSECTS")[Return] 24
If the values displayed by the system are greater than the values in Table 1-2, 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, increase the maximum values of the GBLPAGES and GBLSECTIONS system parameters.
Section 188.8.131.52 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.
184.108.40.206 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:
For example, to change the setting for the WSMAX system parameter, add to the file:
WSMAX = 1024
To change the setting for incremental SYSGEN parameters, add to the file:
ADD_GBLPAGES = 2000
Then run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt:
$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT[Return]
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
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.
|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)||
(optimally, 1024 to 2048 pages)
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 [Return] UAF> 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 and Section 2.2 show an example of this procedure.
Use one of the following commands to invoke the VMSINSTAL procedure:
Kednos PL/I for OpenVMS VAX
$ @SYS$UPDATE:VMSINSTAL PLI038 location [OPTIONS N]
Kednos PL/I for OpenVMS Alpha
$ @SYS$UPDATE:VMSINSTAL DPLI044 location [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 NIs 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: