PL/I_for_OpenVMS_Systems____________________________ Installation Guide Order Number: AA-J179J-TM June 1996 This document contains instructions for installing VAX PL/I on the OpenVMS VAX operating system and DEC PL/I on the OpenVMS AXP operating system. 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 VAX PL/I: VMS Version 5.4 and higher versions For DEC PL/I: OpenVMS AXP Version 6.1 or higher Software Version: VAX PL/I Version 3.5 DEC PL/I Version 4.1 UniPrise Systems, Inc., Irvine, CA ________________________________________________________________ June 1996 UniPrise Systems, Inc, 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 UniPrise 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 UniPrise Systems, Incorporated, 1980, 1983, 1985, 1987, 1992, 1993, 1995, 1996. All rights reserved. The following are trademarks of Digital Equipment Corporation: 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. The Reader's Comments form at the end of this manual requests your critical evaluation to assist in preparing future documentation. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Preparing to Install PL/I 1.1 Accessing the Online Release Notes............ 1-1 1.2 Prerequisite Software......................... 1-2 1.3 License Registration ......................... 1-2 1.4 Installation Procedure Requirements........... 1-3 1.4.1 Privileges and Disk Space................. 1-3 1.4.2 System Parameters......................... 1-4 1.4.2.1 Checking System Parameter Values........ 1-5 1.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS............................. 1-5 1.4.2.3 Changing System Parameter Values with AUTOGEN................................. 1-7 1.4.3 Process Account Quotas and Privileges..... 1-8 1.4.4 Using VMSINSTAL........................... 1-9 1.4.5 Backing Up Your System Disk............... 1-11 2 Installing PL/I 2.1 Installation Procedure for VAX PL/I........... 2-1 2.1.1 Error Conditions.......................... 2-7 2.1.2 Installing VAX PL/I as a Shared Image..... 2-7 2.2 Installation Procedure for DEC PL/I........... 2-8 2.2.1 Error Conditions.......................... 2-16 2.2.2 Installing DEC PL/I as a Shared Image..... 2-17 iii 3 After the Installation 3.1 Running the Installation Verification Procedure Separately.......................... 3-1 3.2 Installing PL/I on a VMScluster............... 3-3 3.3 Maintenance Updates........................... 3-4 3.4 Determining and Reporting Problems............ 3-4 A Sample Installation A.1 Installing VAX PL/I on OpenVMS VAX Systems.... A-1 A.2 Installing DEC PL/I on OpenVMS AXP Systems.... A-4 B Files Created During Installation Tables 1 Conventions Used in this Manual........... vi 1-1 Disk Space Requirements................... 1-3 1-2 Required Minimum Values for System Parameters................................ 1-4 1-3 Process Account Quotas.................... 1-8 B-1 Files Created During Installation......... B-1 B-2 Files Created During Installation......... B-3 iv _________________________________________________________________ Preface Purpose of This Guide This manual describes how to install VAX PL/I and DEC PL/I on the OpenVMS VAX and OpenVMS AXP 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. Intended Audience 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. Related Documentation In addition to this guide, the PL/I documentation set includes: o PL/I for OpenVMS Systems User Manual o PL/I for OpenVMS Systems Reference Manual This guide contains cross-references to the following OpenVMS documentation: o OpenVMS system messages documentation v Conventions Table 1 lists the conventions used in this guide: Table_1_Conventions_Used_in_this_Manual____________________ Convention_____________Meaning_____________________________ UPPERCASE TEXT Uppercase letters indicate the name of a command, file, parameter, procedure, or utility. $ In interactive examples, boldface @SYS$UPDATE:VMSINSTAL 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. In procedures, a sequence such as indicates that you must hold down the key labeled Ctrl while you press another key or a pointing-device button. 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. (continued on next page) vi Table_1_(Cont.)_Conventions_Used_in_this_Manual____________ Convention_____________Meaning_____________________________ [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.)_________________________ Terminological Conventions The word PL/I applies to both VAX PL/I and DEC PL/I unless otherwise indicated. vii 1 _________________________________________________________________ Preparing to Install PL/I This chapter describes the preparations and requirements needed prior to installing VAX PL/I Version 3.5 for OpenVMS VAX and DEC PL/I Version 4.1 for OpenVMS AXP. Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to check the contents of your kit against this information. If your kit is damaged or incomplete, please call your Digital service representative. 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. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the release notes, see Section 1.1. 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: VAX PL/I SYS$HELP:PLI$035.RELEASE_NOTES Preparing to Install PL/I 1-1 DEC PL/I SYS$HELP:DPLI041.RELEASE_NOTES Online help also directs you to the release notes file. After the installation, enter the following command: $ HELP PLI RELEASE_NOTES 1.2 Prerequisite Software To install PL/I, you must have OpenVMS VAX Version 5.4 (or a later version) or OpenVMS AXP Version 1.5 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: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your PAK. o 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-2 Preparing to Install PL/I 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: o CMKRNL o WORLD o SYSPRV Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. Table 1-1 summarizes the disk space requirements for PL/I. Table_1-1_Disk_Space_Requirements__________________________ Blocks During Blocks After Kit______________Installation[1]_______Installation________ VAX PL/I 8500 5000 DEC PL/I 30,000 27,500 [1]If_you_choose_to_decompress_the_PL/I_system_library_____ (PLI$STARLET) during the installation, you will need an additional 4500 blocks. ___________________________________________________________ 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 Preparing to Install PL/I 1-3 1.4.2 System Parameters 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. Table_1-2_Required_Minimum_Values_for_System_Parameters____ Minimum Value Minimum Value System_Parameter______(VAX_PL/I)_______(DEC_PL/I)__________ GBLPAGES[1] n + 1500 n + 7776 GBLSECTIONS[1] n + 7 n + 3 PQL_DASTLM[2] 24 24 PQL_DBIOLM[2] 18 18 PQL_DDIOLM[2] 18 18 [1]The_values_listed_represent_the_number_of_free_global___ pages and global sections required for the installation of PL/I, not the total number needed for your operating system and other software. [2]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, 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). ______________________________________________________ 1-4 Preparing to Install PL/I 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:SYSGEN 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 After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. _______________________ Caution _______________________ 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 INSTALL> LIST/GLOBAL/SUMMARY Summary of Local Memory Global Sections 309 Global Sections Used, 28866/13134 Global Pages Used/Unused Preparing to Install PL/I 1-5 INSTALL> EXIT 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 SYSGEN> USE CURRENT SYSGEN> SHOW GBLSECTIONS Parameter name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections SYSGEN> EXIT 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 1-6 Preparing to Install PL/I 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") 15848 $ WRITE SYS$OUTPUT F$GETSYI ("FREE_GBLSECTS") 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 1.4.2.3 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 = 1024 Preparing to Install PL/I 1-7 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 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. Table_1-3_Process_Account_Quotas___________________________ Account_Quotas_____________Minimum_________________________ AST limit (ASTLM) 24 Buffered I/O quota 18 (BIOLM) Buffered I/O byte count 18,000 quota (BYTLM) Direct I/O quota (DIOLM) 18 Enqueue quota (ENQLM) 30 Open file limit (FILLM) 20 Paging file quota 4096 pages (PGFLQUOTA) Subprocess creation quota by user requirement (PRCLM) 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 1-8 Preparing to Install PL/I 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 $ RUN AUTHORIZE UAF> SHOW SYSTEM 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: VAX PL/I $ @SYS$UPDATE:VMSINSTAL PLI035 ddcu: [OPTIONS N] DEC PL/I $ @SYS$UPDATE:VMSINSTAL DPLI041 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. Preparing to Install PL/I 1-9 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 When you invoke VMSINSTAL, it checks to determine: o If you are logged in to a privileged account. Digital recommends that you install software from the system manager's account with your default device and directory set to SYS$UPDATE. o 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 o 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-10 Preparing to Install PL/I 1.4.5 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital 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. Preparing to Install PL/I 1-11 2 _________________________________________________________________ Installing PL/I This chapter describes the installation procedures for PL/I. Please perform the tasks described in Chapter 1 and read the release notes before you begin the procedures in this chapter. Section 2.1 explains each step in the installation procedure for OpenVMS VAX. Section 2.2 explains the installation procedure for OpenVMS AXP. 2.1 Installation Procedure for VAX PL/I Defaults appear in brackets throughout the installation procedure. To abort the installation procedure at any time, press Ctrl/y. When you press Ctrl/y, the installation procedure deletes the files it has created up to that point and returns you to DCL level. If you want to retry the installation procedure after pressing Ctrl/y, you must proceed from step 2. Step 1: Log in to a privileged account and set your default device and directory to SYS$UPDATE. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE Installing PL/I 2-1 Step 2: Invoke VMSINSTAL. $ @VMSINSTAL PLI03n MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.4 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? If you are satisfied with the backup of your system disk, press Return. Otherwise, enter NO and press Return to discontinue the installation. Step 3: Insert the first installation kit volume. Please mount the first volume of the set on MUA0:. * Are you ready? YES The following products will be processed: PLI V3.n Beginning installation of PLI V3.n at hh:mm %VMSINSTAL-I-RESTORE, Restoring product saveset A... Step 4: Select a release notes option. This step applies only if you specified OPTIONS N in step 2. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes on line immediately. You can terminate the display at any time by pressing Ctrl/c. After you view them, VMSINSTAL copies the release notes to SYS$HELP. 2-2 Installing PL/I If you select option 2, VMSINSTAL prompts you for a queue name. Enter a queue name, or press Return to send the file to the default output print device. After you print them, VMSINSTAL copies the release notes to SYS$HELP. * Queue name [SYS$PRINT]: If you select option 3, VMSINSTAL displays the release notes on line immediately. (You can terminate the display at any time by pressing Ctrl/c). VMSINSTAL then prompts you for a queue name. Enter a queue name, or press Return to send the file to the default output print device. The VAX PL/I release notes are then copied to SYS$HELP. If you select option 4, VMSINSTAL does not display, print, or copy the release notes; typically this option is selected when the user wants to terminate the installation. ________________________ Note ________________________ This version of the release notes file installed by VMSINSTAL is labeled with the current product name and version number (for example, PLI$035.RELEASE_NOTES). Take care not to delete release notes for previous versions of VAX PL/I. ______________________________________________________ Next, VMSINSTAL displays the following prompt: * Do you want to continue the installation [N]?: Y %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. VAX PL/I Installation is commencing ... If you want to continue the installation, enter Y and press Return. If you enter N or press Return, VMSINSTAL discontinues the installation. In either case, VMSINSTAL moves the release notes to SYS$HELP. Step 5: Insert the subsequent installation kit volumes. %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for reading Enter "YES" when ready: YES Installing PL/I 2-3 VMSINSTAL prompts you to insert the next volume and waits for you to enter YES after inserting it. If you enter NO, VMSINSTAL displays the prompt again. This prompt is displayed only if your installation kit contains more than one volume. Step 6: Respond to license registration queries. PL/I supports the OpenVMS License Management Facility (LMF). The installation procedure displays license information about your product and then asks if you have registered and loaded your product authorization key (PAK) for VAX PL/I. The following is an example of such information: Product: PLI Producer: DEC Version: 3.n Release Date: dd-mmm-yyyy * Does this product have an authorization key registered and loaded? If you have not registered and loaded your PAK, answer NO to this question. To install VAX PL/I successfully, stop the installation now, register and load your PAK, and restart the installation. Step 7: Select installation options. * Do you want to purge files replaced by this installation [YES] ? The directories SYS$HELP, SYS$MESSAGE, SYS$LIBRARY and SYS$SYSTEM may contain previous versions of PL/I files. These files are replaced during the installation with new files, but the old files are not automatically purged. Purging is recommended. In response to the purging prompt, press Return to purge the files or enter NO to keep them. Do you want to run the IVP after the installation [YES]? The Installation Verification Procedure (IVP) checks if the installation procedure was successful. Press Return to run the IVP after the installation. If you do not want to run the IVP, enter NO in response to the prompt. The dialogue continues: Do you want to decompress PLI$STARLET? [YES]? 2-4 Installing PL/I You can install the VAX PL/I system library in either a compressed or decompressed form. If you install a compressed system library, the library uses about 2100 blocks less disk space than in its uncompressed form. However, during compilations that include modules from the library, the system uses more CPU time. If you install an uncompressed system library, the installation requires more time because the library is uncompressed during the installation. Also, the decompressed form requires that about 4500 additional blocks be available during the installation procedure. Step 8: Read informational messages. The VAX PL/I installation procedure produces a number of informational messages that report on the progress of the installation. The messages include a list of all new and modified files written during the VAX PL/I installation. See Appendix B for a list of these files. Your OpenVMS system will now be modified to include the following new and modified files: . . . The file SYS$MANAGER:PLI$STARTUP.COM contains commands to be executed at system startup to allow for the best compilation performance. You may want to invoke this command file from your system's site specific start up file. This command file does not have to be invoked for correct operation of VAX PL/I. If you requested that files be purged at step 7, previous versions of the VAX PL/I files are now purged. The following message indicates a successful installation: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... If the installation procedure is successful, the new or modified files are moved to their target directories. Installing PL/I 2-5 The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE files are updated to include the new versions of the PL/I HELP text and the command line definition, respectively. Step 9: Observe the Installation Verification Procedure. If you chose to run the IVP in step 7, VMSINSTAL now calls the IVP to verify that PL/I was installed successfully. IVP test ASSIGN... IVP test CONV... IVP test BIF... IVP test IO... IVP test SYSERV... IVP test LANG... VAX PL/I V3.n-nnn Installation Verification Procedure completed successfully. *** VAX PL/I Installation Verification Procedure *** ***** Ending at dd-mmm-yyyy hh:mm:ss.ss ***** Installation of PLI V3.n completed at hh:mm Step 10: End the installation procedure. Installation of PL/I V3.n completed at hh:mm VMSINSTAL procedure completed at hh:mm $ LOGOUT SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss When the product installation procedure is complete, you can choose to install more products or to log out (as shown here). If you removed any media from the console drive before beginning the installation, you should replace it now. VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you continue to use the system manager's account and you want to restore these symbols, you should log out and log in again. 2-6 Installing PL/I 2.1.1 Error Conditions If the installation procedure fails for any reason, a message such as the following is displayed: %VMSINSTAL-E-INSFAIL, The installation of VAX PL/I V3.n has failed. An error during the installation can occur if one or more of the following conditions exist: o Incorrect operating system version o Incorrect prerequisite software version o Insufficient quotas necessary for successful installation (see Section 1.4.3) o Process quotas required by VMSINSTAL are incorrect (see Section 1.4.3) o OpenVMS HELP library currently in use o PAK for VAX PL/I registered incorrectly, not registered, or unloaded. For descriptions of the error messages generated by these conditions, see the OpenVMS System Messages and Recovery Procedures Reference Manual or your processor-specific installation/operations guide. If you are notified that any of these conditions exist, take the appropriate action as described in the message. You may need to change a system parameter or increase an authorized quota value. If the installation fails, restart the installation procedure from step 2. If the installation fails due to an IVP failure, contact a Digital service representative. 2.1.2 Installing VAX PL/I as a Shared Image If VAX PL/I will be used extensively on your system, you can reduce the system overhead and memory requirements by installing it as a shared image. To perform the installation on a system that is currently running, use the OpenVMS Install Utility while you are logged in to a privileged account. If errors occur, see the OpenVMS Messages Utility Reference Manual manual. Installing PL/I 2-7 First, determine the number of available global pages and global sections on your system. See Section 1.4 for information on how to do so. If you have enough available global pages and global sections, install VAX PL/I as a shared image using the supplied VAX PL/I startup procedure. SYS$MANAGER:PLI$STARTUP.COM This procedure installs the compiler and run-time library as shared images. Update the system startup file to install VAX PL/I. To ensure that VAX PL/I is installed as a shared image each time the system is bootstrapped, include the following line in SYS$MANAGER:SYSTARTUP_V5.COM (the site-specific startup file): $ @SYS$MANAGER:PLI$STARTUP 2.2 Installation Procedure for DEC PL/I This section explains each step in the installation procedure and contains excerpts from it. Defaults appear in brackets throughout the installation procedure. To abort the installation procedure at any time, press Ctrl/y. When you press Ctrl/y, the installation procedure deletes the files it has thus far created and returns you to DCL level. To retry the installation procedure after pressing Ctrl/y, you must proceed from step 2. Step 1: Log in to a privileged account and set your default device and directory to SYS$UPDATE. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE 2-8 Installing PL/I Step 2: Invoke VMSINSTAL. $ @VMSINSTAL DPLI04n MUA0: OPTIONS N OpenVMS AXP Software Product Installation Procedure V1.5 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? If you are satisfied with the backup of your system disk, press Return. Otherwise, enter NO and press Return to stop the installation. Step 3: Insert the first installation kit volume. Please mount the first volume of the set on MUA0:. * Are you ready? YES The following products will be processed: DPLI V4.n Beginning installation of DPLI V4.n at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A... Step 4: Select a release notes option. This step applies only if you specified OPTIONS N in step 2. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes on line immediately. You can terminate the display at any time by pressing Ctrl/c. After you view them, VMSINSTAL copies the release notes to SYS$HELP. If you select option 2, VMSINSTAL prompts you for a queue name. Press Return to send the file to the default output print device. Enter a queue name to send them to another printer. After you print them, VMSINSTAL copies the release notes to SYS$HELP. Installing PL/I 2-9 * Queue name [SYS$PRINT]: If you select option 3, VMSINSTAL displays the release notes on line immediately. You can terminate the display at any time by pressing Ctrl/c. VMSINSTAL then prompts you for a queue name. Enter a queue name, or press Return to send the file to the default output print device. The DEC PL/I release notes are then copied to SYS$HELP. If you select option 4, VMSINSTAL does not display, print, or copy the release notes. Typically this option is selected when the user wants to terminate the installation. ________________________ Note ________________________ This version of the release notes file installed by VMSINSTAL is labeled with the current product name and version number (for example, DPLI041.RELEASE_NOTES). Take care not to delete release notes for previous versions of PL/I. ______________________________________________________ Next, VMSINSTAL displays the following prompt: %VMSINSTAL-I-RELMOVED, The product's release notes have been moved to SYS$HELP. DEC PL/I for OpenVMS AXP(tm) Systems V4.1 . . . *--------------------------------------------* * Installation Command Procedure for * * DEC PL/I for OpenVMS AXP Systems V4.1 * *--------------------------------------------* The DEC PL/I for OpenVMS AXP Systems V4.1 kit contains the compiler, message files and help files. These files require 11,000 blocks during and after installation. Step 5: Insert the subsequent installation kit volumes. %BACKUP-I-READYREAD, mount volume 2 on _ddcu: for reading Enter "YES" when ready: YES 2-10 Installing PL/I VMSINSTAL prompts you to insert the next volume and waits for you to enter YES after inserting it. If you enter NO, VMSINSTAL displays the prompt again. This prompt is displayed only if your installation kit contains more than one volume. Step 5a: Respond to compiler installation query. * Do you want to install the DEC PL/I compiler [YES]? The DEC PL/I for OpenVMS AXP Systems Version 4.1 kit contains the compiler, message files, and help files. These files require 11,000 blocks during installation and will occupy 11,000 blocks after the installation. Step 5b: Respond to query on compressed or uncompressed system library. * Do you want to decompress PLI$STARLET [NO]? PLI$STARLET, the PL/I system library, is supplied in a compressed format, which requires less disk space but also causes the system to use more CPU time during compilations that include modules from the library. To accept the compressed format, enter NO. Decompressing PLI$STARLET requires approximately 4520 additional blocks during and after the installation. Decompressing also means that the installation will require more CPU time. To decompress the system library, enter YES. Step 5c: Respond to example programs query. * Do you want to install the DEC PL/I examples [YES]? The DEC PL/I Version 4.1 kit contains a set of example programs using many features of DEC PL/I and OpenVMS AXP. The example files require 250 blocks during and after installation. Step 5d: Respond to special debugger query. * Do you want to install the special debugger [YES]? The system debugger in OpenVMS AXP Version 1.5 does not support the PL/I language. A special version of the OpenVMS AXP Debugger in this (DEC PL/I Version 4.1) kit contains support for the DEC PL/I compiler. Installing PL/I 2-11 ________________________ Note ________________________ The special debugger, which is installed in SYS$COMMON:[DECPLI], does not replace the existing system debugger. If you do not install the special debugger now, you may do so later using this kit. Future releases of the OpenVMS AXP operating system may contain a debugger that supersedes this special debugger for DEC PL/I. ______________________________________________________ Release notes explaining how to choose between the DEC PL/I special debugger and the system debugger are in: SYS$COMMON:[DECPLI]PLI_DEBUGGER.RELEASE_NOTES Please inform your user community of the existence of the special debugger and the release notes describing it. The debugger requires 13,500 blocks of disk space both during and after installation. Step 6 : Respond to license registration queries. Product: PLI Producer: DEC Version: 4.n Release Date: dd-mmm-yyyy * Does this product have an authorization key registered and loaded? DEC PL/I supports the OpenVMS License Management Facility (LMF). The installation procedure displays license information about DEC PL/I and asks if you have registered and loaded your authorization key for DEC PL/I. If you have not registered and loaded your Product Authorization Key (PAK), answer NO to this question. To complete the installation successfully, stop the installation, register and load your Product Authorization Key, and restart the installation. 2-12 Installing PL/I Step 7: Select installation options. * Do you want to purge files replaced by this installation [YES] ? The directories SYS$HELP, SYS$MESSAGE, SYS$LIBRARY, and SYS$SYSTEM may contain previous versions of PL/I files. These files are replaced during the installation with new files, but the old files are not automatically purged. Purging is recommended. Press Return to purge the old files. Enter NO to keep the old files. The dialogue continues: * Do you want to run the IVP after the installation [YES]? The Installation Verification Procedure (IVP) determines whether or not the installation procedure has succeeded. Press Return to run the IVP. To avoid running the IVP, enter NO. This kit contains a file summarizing the new features, changes, restrictions, and compatibility issues in DEC PL/I. Named DPLI$041.RELEASE_NOTES, the file is in SYS$HELP:. The release notes contain information that is important to DEC PL/I programmers. Please inform your user community of this file's existence. Installing OpenVMS AXP DEBUG Version T2.0-PLI.000 in SYS$COMMON:[DECPLI]... %VMSINSTAL-I-RESTORE, Restoring product save set E ... Step 8: Read informational messages. The DEC PL/I installation procedure produces several informational messages that report on the progress of the installation. The informational messages include a list of all new and modified files created during the DEC PL/I installation. See Appendix B for a list of these files. This kit will install the following definition file: SYS$LIBRARY:PLI$STARLET.TLB This kit provides several example files in SYS$COMMON:[SYSHLP.EXAMPLES.DECPLI]. The names of the files are abbreviations keyed to the functions of the examples. The IVP (Installation Verification Procedure) will be left in SYS$TEST:DPLI$IVP.COM. After the installation is complete, you can invoke the command file at any time to reverify that DEC PL/I is installed and working correctly. Installing PL/I 2-13 An optional startup file has been placed in SYS$STARTUP:DPLI$STARTUP.COM. The file installs the DEC PL/I compiler, run-time library, and message files as shared images to improve the performance of using the DEC PL/I compiler or applications written in PL/I. To improve the performance of using the DEC PL/I compiler or applications written in PL/I, the startup file installs the DEC PL/I compiler, run-time library, and message files as shared images. If you wish to use this file, add the following DCL command to SYS$MANAGER:SYSTARTUP_VMS.COM $ @SYS$STARTUP:DPLI$STARTUP.COM All questions regarding the installation have now been asked. The installation of DEC PL/I V4.1 will now continue for 5 to 30 minutes depending on your configuration and the options requested. Installing DEC PL/I compiler... %VMSINSTAL-I-RESTORE, Restoring product save set B ... Installing DEC PL/I definition files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Installing DEC PL/I example programs... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECPLI]. Installing OpenVMS AXP DEBUG Version T2.0-PLI.000 in SYS$COMMON:[DECPLI]... %VMSINSTAL-I-RESTORE, Restoring product save set E ... Your OpenVMS system will now be updated to include the following new and modified files: The file SYS$MANAGER:DPLI$STARTUP.COM contains commands to be executed at system startup to allow for the best compilation performance. You may want to invoke this command file from your system's site-specific startup file. This command file does not have to be invoked for correct operation of DEC PL/I. If you requested that files be purged at step 7, previous versions of the DEC PL/I files are now purged. 2-14 Installing PL/I The following message indicates that the installation has been successful: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... If the installation procedure is successful, the new or modified files are moved to their target directories. The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE files are updated to include the new versions of the PL/I HELP text and the command line definition, respectively. Step 9: Observe the Installation Verification Procedure. If you chose to run the IVP in step 7, VMSINSTAL now calls the IVP to verify that PL/I was installed successfully. *--------------------------------------------* * Installation Verification Procedure * * DEC PL/I for OpenVMS AXP(tm) Systems V4.1 * *--------------------------------------------* © UniPrise Systems, Inc. 1996. All rights reserved. IVP test ASSIGN... IVP test CONV... IVP test BIF... IVP test IO... IVP test SYSERV... **** DEC PL/I V4.1-002 Installation Verification Successful **** Step 10: End the installation procedure. *--------------------------------------------* * Completed Installation Verification for * * DEC PL/I for OpenVMS AXP(tm) Systems V4.1 * *--------------------------------------------* Installation of DPLI V4.1 completed at hh:mm Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DPLI041.VMI_ DATA VMSINSTAL procedure completed at hh:mm Installing PL/I 2-15 $ LOGOUT SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss When the product installation procedure is complete, you can choose to install additional products or to log out (as shown here). If you removed any media from the console drive before beginning the installation, replace it now. VMSINSTAL deletes or changes entries in the process symbol tables during the installation. To continue to use the system manager's account and to restore these symbols, log out of the account and log in. 2.2.1 Error Conditions If the installation procedure fails, a message similar to the following is displayed: %VMSINSTAL-E-INSFAIL, The installation of DEC PL/I V4.n has failed. An error during the installation can occur if one or more of the following conditions exist: o Incorrect operating system version o Incorrect prerequisite software version o Insufficient quotas necessary for successful installation (see Section 1.4.3) o Process quotas required by VMSINSTAL are incorrect (see Section 1.4.3) o OpenVMS HELP library currently in use o PAK for DEC PL/I registered incorrectly, not registered, or unloaded For descriptions of the error messages generated by these conditions, see the OpenVMS system messages documentation or your processor-specific installation/operations guide. If you are notified that any of these conditions exist, follow the instructions in the message. You may need to change a system parameter or increase an authorized quota value. If the installation fails, you must restart the installation procedure from step 2. If the installation fails due to an IVP failure, contact a Digital service representative. 2-16 Installing PL/I 2.2.2 Installing DEC PL/I as a Shared Image If you plan to use DEC PL/I extensively, you can reduce system overhead and memory requirements by installing DEC PL/I as a shared image. To perform the installation on a system that is currently running, log into a privileged account and use the OpenVMS Install Utility. First, determine the number of available global pages and global sections on your system. See Section 1.4 for information on how to do this. If you have enough available global pages and global sections, install DEC PL/I as a shared image using the supplied startup procedure: SYS$MANAGER:DPLI$STARTUP.COM This procedure installs the compiler and run-time library as shared images. Update the system startup file to install DEC PL/I. To ensure that DEC PL/I is installed as a shared image each time the system is bootstrapped, include the following line in SYS$MANAGER:SYSTARTUP_V5.COM (the site-specific startup file): $ @SYS$MANAGER:DPLI$STARTUP Installing PL/I 2-17 3 _________________________________________________________________ After the Installation PL/I is now installed and can be invoked by all users with the DCL command, PLI. The installation procedure modifies the DCL command table so that the PLI command is recognized and processed. However, the previous command table is still in effect for those users who are currently logged in. All logged- in users who want to use the PLI command for the newly installed product must log out of the system and log in again. If PL/I is used extensively on your system, you can reduce system overhead requirements by installing it as a shareable image using the OpenVMS Install Utility. For more information, read Section 2.1.2 or Section 2.2.2. 3.1 Running the Installation Verification Procedure Separately The Installation Verification Procedure (IVP) is usually run at installation. You can also run it separately at any time to ensure the integrity of installed files if you have problems with your system. The following command procedures execute the IVP: VAX PL/I $ @SYS$SYSROOT:[SYSTEST]PLI$IVP.COM DEC PL/I $ @SYS$SYSROOT:[SYSTEST]DPLI$IVP.COM If the IVP fails, one of the following messages is displayed, depending upon which OpenVMS system you are using: After the Installation 3-1 VAX PL/I *** VAX PL/I Installation Verification Procedure *** **** Beginning at dd-mmm-yyyy hh:mm:ss.ss **** IVP test ASSIGN... ******** VAX PL/I Installation Verification FAILED ******** *** VAX PL/I Installation Verification Procedure *** ***** Ending at dd-mmm-yyyy hh:mm:ss.ss **** 3-2 After the Installation DEC PL/I *--------------------------------------------* * Installation Verification Procedure * * DEC PL/I for OpenVMS AXP(tm) Systems V4.1 * *--------------------------------------------* © UniPrise Systems, Inc. 1996. All rights reserved. **** Beginning at dd-mmm-yyyy hh:mm:ss.ss **** IVP test ASSIGN... ******** DEC PL/I Installation Verification FAILED ******** *** DEC PL/I Installation Verification Procedure *** ***** Ending at dd-mmm-yyyy hh:mm:ss.ss **** 3.2 Installing PL/I on a VMScluster If you want to run PL/I on multiple nodes of a VMScluster, first check to see that you have the appropriate software license. Then, follow these steps after installing PL/I: 1. Execute the LICENSE LOAD command to activate the license on each node in the VMScluster on which PL/I is to be executed. 2. To use the product on other nodes in the VMScluster, you must replace the version of the DCL tables installed on the other VMScluster nodes. To do this, perform the following steps: a. Log in to a node on the cluster. b. Run INSTALL and enter the following command at the INSTALL> prompt: INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE c. Repeat steps a and b for each node of the cluster. As a faster alternative, you can use the SYSMAN utility to replace the DCL tables on all cluster nodes. To do this, perform the following steps. 1. Log in to a node on the cluster. After the Installation 3-3 2. Run SYSMAN and enter the following commands at the SYSMAN> prompt: SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO INSTALL REPLACE SYS$LIBRARY::DCLTABLES.EXE You need do this on only one node of the cluster, and all nodes will be updated. 3.3 Maintenance Updates Digital may periodically issue maintenance updates of PL/I. Each update consists of an installation kit. You should install this kit as described herein or in any documentation that may accompany the maintenance update. Each time a maintenance update is released, the version number changes. For example, if the current version is 3.0, the version number of the first maintenance update will be 3.1. In addition, the maintenance update includes new release notes. The release notes describe the changes that have been made to PL/I since the previous release. The update release notes are online. To locate the release notes after installing PL/I, type or print one of the following files: VAX/PL/I SYS$HELP:PLI$035.RELEASE_NOTES DEC PL/I SYS$HELP:DPLI040A.RELEASE_NOTES or, enter the following command: $ HELP PLI RELEASE_NOTES 3.4 Determining and Reporting Problems If an error occurs while using PL/I and you believe that the error is caused by a problem with PL/I, take one of the following actions: o If you purchased PL/I within the past 90 days and you think the problem is caused by a software error, you can submit a Software Performance Report (SPR). 3-4 After the Installation o If you have a Basic or DECsupport Software Agreement, call your Customer Support Center. With these services, you receive telephone support that provides high-level advisory and remedial assistance. For more information, contact your local Digital service representative. o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). If you find an error in the PL/I documentation, complete and submit a Reader's Comments form from the back of the manual containing the error. Include the section and page number on which the error occurred. After the Installation 3-5 A _________________________________________________________________ Sample Installation This appendix contains sample installations of VAX PL/I on OpenVMS VAX and DEC PL/I on OpenVMS AXP. Note that these are only sample installations. The installation procedure may be modified in maintenance updates of this product. Because this installation guide is not always revised for maintenance updates, be sure to read the Read Before Installing or Using PL/I letter before you install this product. The letter notes any significant changes in the installation that vary from this sample. A.1 Installing VAX PL/I on OpenVMS VAX Systems Welcome to VAX/VMS V5.4 Username: SYSTEM Password: Welcome to VAX/VMS version V5.4 on node GULCH Last interactive login on Tuesday, 10-DEC-1991 10:11 Last non-interactive login on Friday, 12-DEC-1991 14:07 $ @SYS$UPDATE:VMSINSTAL PLI035 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.4 It is 13-DEC-1991 at 13:31. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: PLI V3.5 Beginning installation of PLI V3.5 at 13:32 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... Release Notes Options: Sample Installation A-1 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: * Queue name [SYS$PRINT]: Job PLI$035.RELEASE_NOTES (queue SYS_ PRINT, entry 312) started on GULCH_LPA0 * Do you want to continue the installation? Y %VMSINSTAL-I- RELMOVED , The product's release notes have been successfully moved to SYS$HELP. Product: PLI Producer: DEC Version: 3.5 Release Date: 13-DEC-1991 * Does this product have an authorization key registered and loaded? Y * Do you want to purge files replaced by this installation [YES]? This kit contains an Installation Verification Procedure (IVP) to verify the correct installation of VAX PL/I. The IVP will be left in: SYS$COMMON:[SYSTEST]PLI$IVP.COM After the installation is complete, you can invoke the command file at any time to verify that VAX PL/I is installed and working correctly. * Do you want to run the IVP after the installation [YES]? This kit contains a file summarizing the new features, changes, restrictions, and compatibility issues in this release of VAX PL/I. This file is named PLI$035.RELEASE_NOTES and has been placed in SYS$HELP:. This file contains information valuable to VAX PL/I programmers. Please inform your user community of this file's existence. A-2 Sample Installation The VAX PL/I system interface library PLI$STARLET.TLB can be installed either in compressed form or in decompressed form. The compressed form of the library requires approximately 1500 blocks less disk space, but requires more CPU time during compilations of programs that include modules from the library. Installing the decompressed form of the library will require more time for this installation to complete, because the library decompression is performed by the installation; also, the decompressed form will require approximately 3000 additional blocks to be available during the installation procedure. * Do you want to decompress PLI$STARLET [YES]? You have answered all of the questions for this installation. The installation will now execute in 5 to 30 minutes without further intervention, depending on your configuration, installation media, and so forth. %VMSINSTAL-I-RESTORE, Restoring product saveset B ... Decompressing PLI$STARLET... %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.PLI]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.PLI]. Your VMS system will now be modified to include the following new and modified files: [SYSEXE]PLI$COMPILER.EXE [new] [SYSHLP]HELPLIB.HLB [modified] [SYSHLP]PLI$035.RELEASE_NOTES [new] [SYSHLP.EXAMPLES.PLI]*.* [new] [SYSLIB]DCLTABLES.EXE [modified] [SYSLIB]PLI$STARLET.TLB [new] [SYSMGR]PLI$STARTUP.COM [new] [SYSMSG]PLI$COMPILER_MSG.EXE [new] [SYSTEST]PLI$IVP.COM [new] [SYSTEST.PLI]*.* [new] The file SYS$MANAGER:PLI$STARTUP.COM contains commands to be executed at system startup to allow for the best compilation performance. You may want to invoke this command file from your system's site specific start up file. This command file does not have to be invoked for correct operation of VAX PL/I. %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... Sample Installation A-3 *** VAX PL/I Installation Verification Procedure *** **** Beginning at 13-DEC-1991 13:51:50.06 **** IVP test ASSIGN... IVP test CONV... IVP test BIF... IVP test IO... IVP test SYSERV... IVP test LANG... ****** VAX PL/I V3.5 Installation Verification Successful ****** *** VAX PL/I Installation Verification Procedure *** ***** Ending at 13-DEC-1991 13:55:41.14 ***** Installation of PLI V3.5 completed at 13:55 A.2 Installing DEC PL/I on OpenVMS AXP Systems $ @sys$update:vmsinstal dpli041 ddcu: options n OpenVMS ALPHA Software Product Installation Procedure V1.5 It is 26-MAY-1996 at 14:05. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: DPLI V4.1 Beginning installation of DPLI V4.1 at 14:05 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 2 * Queue name [SYS$PRINT]: %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. A-4 Sample Installation DEC PL/I for OpenVMS AXP(tm) Systems V4.1 (C) UniPrise Systems, Inc. 1996. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227- 14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. *--------------------------------------------* * Installation Command Procedure for * * DEC PL/I for OpenVMS AXP Systems V4.1 * *--------------------------------------------* The DEC PL/I for OpenVMS AXP Systems V4.1 kit contains the compiler, message files and help files. These files require 11000 blocks during installation and will occupy 11000 blocks after the installation. * Do you want to install the DEC PL/I compiler [YES]? PLI$STARLET is supplied in compressed (reduced data) format. This format saves disk space, but requires more CPU time during compilation. Decompressing PLI$STARLET will require an additional 4520 blocks of disk space. * Do you want to decompress PLI$STARLET [NO]? The DEC PL/I V4.1 kit contains a set of example programs using many features of DEC PL/I and OpenVMS. The example files require 250 blocks during installation and will occupy 250 blocks after installation. * Do you want to install the DEC PL/I examples [YES]? The debugger which is currently installed on this system does not contain any special support for the PL/I language. The DEC PL/I V4.1 kit contains a special version of the OpenVMS AXP Debugger. This debugger supports debugging programs compiled with the DEC PL/I compiler. The debugger will require 13500 blocks during installation and 13500 after installation. Sample Installation A-5 Note If you chose to install this debugger, it will not replace the existing system debugger, but will instead be installed in SYS$COMMON:[DECPLI]. Please see the release notes on how to select between the DEC PL/I special debugger and the system debugger. If you chose not to install the debugger at this time, you may install it later from this same kit. Future releases of the OpenVMS AXP operating system may supersede this special version of the debugger. The release notes for the debugger may be found in: SYS$COMMON:[DECPLI]PLI_DEBUGGER.RELEASE_NOTES Please inform your user community of the existence of this debugger. * Do you want to install the special debugger [YES]? * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? Product: PLI Producer: DEC Version: 4.1 Release Date: MAY-1996 * Does this product have an authorization key registered and loaded? YES This kit contains a file summarizing the new features, changes, restrictions, and compatibility issues in this release of DEC PL/I. This file is named DPLI041.RELEASE_NOTES and has been placed in SYS$HELP:. This file contains information valuable to DEC PL/I programmers. Please inform your user community of this file's existence. This kit will install the following definition file: SYS$LIBRARY:PLI$STARLET.TLB This kit provides several examples in SYS$COMMON:[SYSHLP.EXAMPLES.DECPLI]. The names of the files reflect the topic being demonstrated by the programs. The IVP (Installation Verification Procedure) will be left in SYS$TEST:DPLI$IVP.COM. After the installation is complete, you can invoke the command file at any time to reverify that DEC PL/I is installed and working correctly. A-6 Sample Installation An optional startup file has been placed in SYS$STARTUP:DPLI$STARTUP.COM. The file installs the DEC PL/I compiler, run- time library, and message files as shared images to improve the performance of using the DEC PL/I compiler or applications written in PL/I. If you wish to use this file, add the following DCL command to SYS$MANAGER:SYSTARTUP_VMS.COM $ @SYS$STARTUP:DPLI$STARTUP.COM All questions regarding the installation have now been asked. The installation of DEC PL/I V4.1 will now continue for 5 to 30 minutes depending on your configuration and the options requested. Installing DEC PL/I compiler... %VMSINSTAL-I-RESTORE, Restoring product save set B ... Installing DEC PL/I definition files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Installing DEC PL/I example programs... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECPLI]. %CREATE-I- EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.DECPLI] already exists Installing OpenVMS AXP DEBUG Version T2.0- PLI.000 in SYS$COMMON:[DECPLI]... %VMSINSTAL-I-RESTORE, Restoring product save set E ... Your OpenVMS system will now be updated to include the following new and modified files: Sample Installation A-7 [SYSHLP]DPLI041.RELEASE_NOTES [new] [SYSEXE]DPLI$COMPILER.EXE [new] [SYSMSG]DPLI$COMPILER_MSG.EXE [new] [SYSHLP]HELPLIB.HLB [modified] [SYSLIB]DCLTABLES.EXE [modified] [SYSTEST.DECPLI]DPLI$IVPASSIGN.PLI [new] [SYSTEST.DECPLI]DPLI$IVPCONV.PLI [new] [SYSTEST.DECPLI]DPLI$IVPCONV.CMP [new] [SYSTEST.DECPLI]DPLI$IVPBIF.PLI [new] [SYSTEST.DECPLI]DPLI$IVPIO.PLI [new] [SYSTEST.DECPLI]DPLI$IVPIO4.IDX [new] [SYSTEST.DECPLI]DPLI$IVPLANG.PLI [new] [SYSTEST.DECPLI]DPLI$IVPPRINT.PLI [new] [SYSTEST.DECPLI]DPLI$IVPSYSERV.PLI [new] [SYSTEST]DPLI$IVP.COM [new] [SYS$STARTUP]DPLI$STARTUP.COM [new] [SYSLIB]PLI$STARLET.TLB [new] [DECPLI]DBG$HELP.HLB [new] [DECPLI]DBG$HELP.PS [new] [DECPLI]DBG$HELP.TXT [new] [DECPLI]DBG$UIHELP.HLB [new] [DECPLI]DBGTBKMSG.EXE [new] [DECPLI]DEBUG.EXE [new] [DECPLI]DEBUGSHR.EXE [new] [DECPLI]DEBUGUISHR.EXE [new] [DECPLI]PLI_DEBUGGER.RELEASE_NOTES [new] [DECPLI]SETUP_PLI_DEBUGGER.COM [new] [DECPLI]VMSDEBUGCUSTUIL.UID [new] [DECPLI]VMSDEBUGUIL.UID [new] [SYSHLP.EXAMPLES.DECPLI]AREA-EXAMPLE.PLI [new] [SYSHLP.EXAMPLES.DECPLI]BUILD_PHONE.COM [new] [SYSHLP.EXAMPLES.DECPLI]CONSTANTS.PLI [new] [SYSHLP.EXAMPLES.DECPLI]DATABASE.PLI [new] [SYSHLP.EXAMPLES.DECPLI]DECOVF.PLI [new] [SYSHLP.EXAMPLES.DECPLI]ENTRY.PLI [new] [SYSHLP.EXAMPLES.DECPLI]EXAMPLES.TXT [new] [SYSHLP.EXAMPLES.DECPLI]GET_COMMAND_LINE.PLI [new] [SYSHLP.EXAMPLES.DECPLI]GLOBAL.PLI [new] [SYSHLP.EXAMPLES.DECPLI]INTOVF.PLI [new] [SYSHLP.EXAMPLES.DECPLI]KEYS.PLI [new] [SYSHLP.EXAMPLES.DECPLI]LINES.PLI [new] [SYSHLP.EXAMPLES.DECPLI]MTH$DEXP.PLI [new] [SYSHLP.EXAMPLES.DECPLI]MTH$HEXP.PLI [new] A-8 Sample Installation [SYSHLP.EXAMPLES.DECPLI]OLDFILE.DAT [new] [SYSHLP.EXAMPLES.DECPLI]OPERATIONS.PLI [new] [SYSHLP.EXAMPLES.DECPLI]OTS$CVT_TO_L.PLI [new] [SYSHLP.EXAMPLES.DECPLI]OTS$CVT_TZ_L.PLI [new] [SYSHLP.EXAMPLES.DECPLI]PARTLIST.TLB [new] [SYSHLP.EXAMPLES.DECPLI]PHONE.FDL [new] [SYSHLP.EXAMPLES.DECPLI]PHONE.PLI [new] [SYSHLP.EXAMPLES.DECPLI]RANDOM.PLI [new] [SYSHLP.EXAMPLES.DECPLI]SCREEN.PLI [new] [SYSHLP.EXAMPLES.DECPLI]SIGN_EXTEND.PLI [new] [SYSHLP.EXAMPLES.DECPLI]STATE.TXT [new] [SYSHLP.EXAMPLES.DECPLI]UM-02-01.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-06-01.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-07-01.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-02.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-03.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-04.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-05.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-06.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-07.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-08.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-09.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-10.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-11-SORTED.DAT [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-11-UNSORTED.DAT [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-11.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-12-SORTED.DAT [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-12-TEMP.DAT [new] [SYSHLP.EXAMPLES.DECPLI]UM-11-12.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-13-01.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-13-02.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-14-01.PLI [new] [SYSHLP.EXAMPLES.DECPLI]UM-14-02.PLI [new] [SYSHLP.EXAMPLES.DECPLI]USER_OPEN.PLI [new] [SYSHLP.EXAMPLES.DECPLI]WILDCARD.PLI [new] %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... *--------------------------------------------* * Installation Verification Procedure * * DEC PL/I for OpenVMS AXP(tm) Systems V4.1 * *--------------------------------------------* Sample Installation A-9 IVP test ASSIGN... IVP test CONV... IVP test BIF... IVP test IO... IVP test SYSERV... ****** DEC PL/I V4.1- 002 Installation Verification Successful ****** *--------------------------------------------* * Completed Installation Verification for * * DEC PL/I for OpenVMS AXP(tm) Systems V4.1 * *--------------------------------------------* Installation of DPLI V4.1 completed at 14:08 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DPLI041.VMI_ DATA VMSINSTAL procedure done at 14:09 $ logout SYSTEM logged out at 26-MAY-1996 14:12:08.23 A-10 Sample Installation B _________________________________________________________________ Files Created During Installation This appendix lists the files created during installation. Table B-1 lists the VAX PL/I files, and Table B-2 lists the DEC PL/I files. VAX PL/I Table_B-1_Files_Created_During_Installation________________ Directory__________________File_Name__________________Status [SYSEXE] PLI$COMPILER.EXE new [SYSHLP] HELPLIB.HLB modified [SYSHLP] PLI$03n.RELEASE_NOTES new [SYSHLP.EXAMPLES.PLI] AREA-EXAMPLE.PLI new [SYSHLP.EXAMPLES.PLI] BUILD_PHONE.COM new [SYSHLP.EXAMPLES.PLI] CONSTANTS.PLI new [SYSHLP.EXAMPLES.PLI] DATABASE.PLI new [SYSHLP.EXAMPLES.PLI] DECOVF.PLI new [SYSHLP.EXAMPLES.PLI] ENTRY.PLI new [SYSHLP.EXAMPLES.PLI] EXAMPLES.TXT new [SYSHLP.EXAMPLES.PLI] GET_COMMAND_LINE.PLI new [SYSHLP.EXAMPLES.PLI] GLOBAL.PLI new [SYSHLP.EXAMPLES.PLI] INTOVF.PLI new [SYSHLP.EXAMPLES.PLI] KEYS.PLI new [SYSHLP.EXAMPLES.PLI] LINES.PLI new [SYSHLP.EXAMPLES.PLI] MTH$DEXP.PLI new [SYSHLP.EXAMPLES.PLI] MTH$HEXP.PLI new (continued on next page) Files Created During Installation B-1 Table_B-1_(Cont.)_Files_Created_During_Installation________ Directory__________________File_Name__________________Status [SYSHLP.EXAMPLES.PLI] OLDFILE.DAT new [SYSHLP.EXAMPLES.PLI] OPERATIONS.PLI new [SYSHLP.EXAMPLES.PLI] OTS$CVT_TO_L.PLI new [SYSHLP.EXAMPLES.PLI] OTS$CVT_TZ_L.PLI new [SYSHLP.EXAMPLES.PLI] PARTLIST.TLB new [SYSHLP.EXAMPLES.PLI] PHONE.FDL new [SYSHLP.EXAMPLES.PLI] PHONE.PLI new [SYSHLP.EXAMPLES.PLI] RANDOM.PLI new [SYSHLP.EXAMPLES.PLI] SCREEN.PLI new [SYSHLP.EXAMPLES.PLI] SIGN_EXTEND.PLI new [SYSHLP.EXAMPLES.PLI] STATE.TXT new [SYSHLP.EXAMPLES.PLI] UM-02-01.PLI new [SYSHLP.EXAMPLES.PLI] UM-06-01.PLI new [SYSHLP.EXAMPLES.PLI] UM-07-01.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-02.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-03.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-04.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-05.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-06.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-07.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-08.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-09.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-10.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-11-SORTED.DAT new [SYSHLP.EXAMPLES.PLI] UM-11-11-UNSORTED.DAT new [SYSHLP.EXAMPLES.PLI] UM-11-11.PLI new [SYSHLP.EXAMPLES.PLI] UM-11-12-SORTED.DAT new [SYSHLP.EXAMPLES.PLI] UM-11-12-TEMP.DAT new [SYSHLP.EXAMPLES.PLI] UM-11-12.PLI new (continued on next page) B-2 Files Created During Installation Table_B-1_(Cont.)_Files_Created_During_Installation________ Directory__________________File_Name__________________Status [SYSHLP.EXAMPLES.PLI] UM-13-01.PLI new [SYSHLP.EXAMPLES.PLI] UM-13-02.PLI new [SYSHLP.EXAMPLES.PLI] UM-14-01.PLI new [SYSHLP.EXAMPLES.PLI] UM-14-02.PLI new [SYSHLP.EXAMPLES.PLI] USER_OPEN.PLI new [SYSHLP.EXAMPLES.PLI] WILDCARD.PLI new [SYSLIB] DCLTABLES.EXE modified [SYSLIB] PLI$STARLET.TLB new [SYSMGR] PLI$STARTUP.COM new [SYSMSG] PLI$COMPILER_MSG.EXE new [SYSTEST] PLI$IVP.COM new [SYSTEST.PLI] all files new [SYSTEST.PLI] PLI$IVPASSIGN.PLI new [SYSTEST.PLI] PLI$IVPBIF.PLI new [SYSTEST.PLI] PLI$IVPCONV.CMP new [SYSTEST.PLI] PLI$IVPCONV.PLI new [SYSTEST.PLI] PLI$IVPIO.PLI new [SYSTEST.PLI] PLI$IVPIO4.IDX new [SYSTEST.PLI] PLI$IVPLANG.PLI new [SYSTEST.PLI] PLI$IVPPRINT.PLI new [SYSTEST.PLI] PLI$IVPSYSERV.PLI new [SYSTEST]__________________PLI$IVP.COM________________new__ DEC PL/I Table_B-2_Files_Created_During_Installation________________ Directory__________________File_Name__________________Status [SYSHLP] DPLI040A.RELEASE_NOTES new [SYSEXE] DPLI$COMPILER.EXE new (continued on next page) Files Created During Installation B-3 Table_B-2_(Cont.)_Files_Created_During_Installation________ Directory__________________File_Name__________________Status [SYSMSG] DPLI$COMPILER_MSG.EXE new [SYSHLP] HELPLIB.HLB modified [SYSLIB] DCLTABLES.EXE modified [SYS$STARTUP] DPLI$STARTUP.COM new [SYSLIB] PLI$STARLET.TLB new [DECPLI] DBG$HELP.HLB new DECPLI] DBG$HELP.PS new [DECPLI] DBG$HELP.TXT new [DECPLI] DBG$UIHELP.HLB new [DECPLI] DBGTBKMSG.EXE new [DECPLI] DEBUG.EXE new [DECPLI] DEBUGSHR.EXE new [DECPLI] DEBUGUISHR.EXE new [DECPLI] PLI_DEBUGGER.RELEASE_ new NOTES [DECPLI] SETUP_PLI_DEBUGGER.COM new [DECPLI] VMSDEBUGCUSTUIL.UID new [DECPLI] VMSDEBUGUIL.UID new [SYSHLP.EXAMPLES.DECPLI] AREA-EXAMPLE.PLI new [SYSHLP.EXAMPLES.DECPLI] BUILD_PHONE.COM new [SYSHLP.EXAMPLES.DECPLI] CONSTANTS.PLI new [SYSHLP.EXAMPLES.DECPLI] DATABASE.PLI new [SYSHLP.EXAMPLES.DECPLI] DECOVF.PLI new [SYSHLP.EXAMPLES.DECPLI] ENTRY.PLI new [SYSHLP.EXAMPLES.DECPLI] EXAMPLES.TXT new [SYSHLP.EXAMPLES.DECPLI] GET_COMMAND_LINE.PLI new [SYSHLP.EXAMPLES.DECPLI] GLOBAL.PLI new [SYSHLP.EXAMPLES.DECPLI] INTOVF.PLI new [SYSHLP.EXAMPLES.DECPLI] KEYS.PLI new (continued on next page) B-4 Files Created During Installation Table_B-2_(Cont.)_Files_Created_During_Installation________ Directory__________________File_Name__________________Status [SYSHLP.EXAMPLES.DECPLI] LINES.PLI new [SYSHLP.EXAMPLES.DECPLI] MTH$DEXP.PLI new [SYSHLP.EXAMPLES.DECPLI] MTH$HEXP.PLI new [SYSHLP.EXAMPLES.DECPLI] OLDFILE.DAT new [SYSHLP.EXAMPLES.DECPLI] OPERATIONS.PLI new [SYSHLP.EXAMPLES.DECPLI] OTS$CVT_TO_L.PLI new [SYSHLP.EXAMPLES.DECPLI] OTS$CVT_TZ_L.PLI new [SYSHLP.EXAMPLES.DECPLI] PARTLIST.TLB new [SYSHLP.EXAMPLES.DECPLI] PHONE.FDL new [SYSHLP.EXAMPLES.DECPLI] PHONE.PLI new [SYSHLP.EXAMPLES.DECPLI] RANDOM.PLI new [SYSHLP.EXAMPLES.DECPLI] SCREEN.PLI new [SYSHLP.EXAMPLES.DECPLI] SIGN_EXTEND.PLI new [SYSHLP.EXAMPLES.DECPLI] STATE.TXT new [SYSHLP.EXAMPLES.DECPLI] UM-02-01.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-06-01.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-07-01.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-02.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-03.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-04.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-05.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-06.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-07.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-08.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-09.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-10.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-11-11-SORTED.DAT new [SYSHLP.EXAMPLES.DECPLI] UM-11-11-UNSORTED.DAT new [SYSHLP.EXAMPLES.DECPLI] UM-11-11.PLI new (continued on next page) Files Created During Installation B-5 Table_B-2_(Cont.)_Files_Created_During_Installation________ Directory__________________File_Name__________________Status [SYSHLP.EXAMPLES.DECPLI] UM-11-12-SORTED.DAT new [SYSHLP.EXAMPLES.DECPLI] UM-11-12-TEMP.DAT new [SYSHLP.EXAMPLES.DECPLI] UM-11-12.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-13-01.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-13-02.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-14-01.PLI new [SYSHLP.EXAMPLES.DECPLI] UM-14-02.PLI new [SYSHLP.EXAMPLES.DECPLI] USER_OPEN.PLI new [SYSHLP.EXAMPLES.DECPLI]___WILDCARD.PLI_______________new__ B-6 Files Created During Installation