Previous | Contents | Index |
At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Kednos 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.
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 Alpha.
2.1 Installation Procedure for Kednos PL/I for OpenVMS VAX
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.
[Return] Username: SYSTEM [Return] Password: [Return] $ SET DEFAULT SYS$UPDATE [Return] |
$ @VMSINSTAL PLI03n SYS$SYSDEVICE:[KITS] OPTIONS N [Return] VAX/VMS Software Product Installation Procedure V5.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]?[Return] |
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: Allow the installation to continue.
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]: [Return] |
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. 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]: [Return] |
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 Kednos PL/I for OpenVMS VAX 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.
This version of the release notes file installed by VMSINSTAL is labeled with the current product name and version number (for example, PLI$038.RELEASE_NOTES). Take care not to delete release notes for previous versions of Kednos PL/I for OpenVMS VAX. |
Next, VMSINSTAL displays the following prompt:
* Do you want to continue the installation [N]?: Y [Return] %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. VAX PL/I Installation is commencing ... |
Step 5: 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 Kednos PL/I for OpenVMS VAX. The following is an example of such information:
Product: PLI Producer: KEDNOS 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 Kednos PL/I for OpenVMS VAX successfully, stop the installation now, register and load your PAK, and restart the installation.
Step 6: Select installation options.
* Do you want to purge files replaced by this installation [YES] ?[Return] |
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]? [Return] |
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]? [Return] |
You can install the Kednos PL/I for OpenVMS VAX system library in either a compressed or decompressed form.
If you install a compressed system library, the library uses about 1500 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 7: Read informational messages.
The Kednos PL/I for OpenVMS VAX 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 Kednos PL/I for OpenVMS VAX 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 Kednos PL/I for OpenVMS VAX 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.
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 8: 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... Kednos PL/I V3.n-nnn Installation Verification Procedure completed successfully. ***** Ending at dd-mmm-yyyy hh:mm:ss.ss ***** Installation of PLI V3.n completed at hh:mm |
Step 9: End the installation procedure.
VMSINSTAL procedure completed at hh:mm $ LOGOUT [Return] 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.1.1 Error Conditions
If the installation procedure fails for any reason, a message such as the following is displayed:
%VMSINSTAL-E-INSFAIL, The IVP for PL/I V3.n has failed. |
An error during the installation can occur if one or more of the following conditions exist:
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
Kednos Corporation.
2.1.2 Installing Kednos PL/I for OpenVMS VAX as a Shared Image
If Kednos PL/I for OpenVMS VAX 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.
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 Kednos PL/I for OpenVMS VAX as a shared image using the supplied Kednos PL/I for OpenVMS VAX 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 Kednos PL/I for OpenVMS VAX.
To ensure that Kednos PL/I for OpenVMS VAX 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 |
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.
[Return] Username: SYSTEM [Return] Password: [Return] |
$ @VMSINSTAL DPLI04n SYS$SYSDEVICE:[KITS] OPTIONS N [Return] |
OpenVMS AXP Software Product Installation Procedure V7.3-1 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]?[Return] |
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: Allow the installation to continue.
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]: [Return] |
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.
* Queue name [SYS$PRINT]: [Return] |
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 Kednos PL/I for OpenVMS Alpha 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.
This version of the release notes file installed by VMSINSTAL is labeled with the current product name and version number (for example, DPLI044.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. |
Kednos PL/I for OpenVMS AXP(tm) Systems V4.4 . . . *--------------------------------------------* * Installation Command Procedure for * * Kednos PL/I for OpenVMS AXP Systems V4.4 * *--------------------------------------------* The Kednos PL/I for OpenVMS AXP Systems V4.4 kit contains the compiler, message files and help files. These files require 11576 blocks during and after installation. |
Step 5: Respond to compiler installation query.
* Do you want to install the Kednos PL/I compiler [YES]? |
The Kednos PL/I for OpenVMS AXP Systems Version 4.4 kit contains the compiler, message files, and help files. These files require 11576 blocks during installation and will occupy 11576 blocks after the installation.
Step 6: 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 7: Respond to example programs query.
* Do you want to install the Kednos PL/I examples [YES]? |
The Kednos PL/I Version 4.4 kit contains a set of example programs using many features of Kednos PL/I and OpenVMS AXP. The example files require 250 blocks during and after installation.
Step 8 : Respond to license registration queries.
Product: PLI Producer: KEDNOS Version: 4.n Release Date: dd-mmm-yyyy * Does this product have an authorization key registered and loaded? |
Kednos PL/I for OpenVMS Alpha supports the OpenVMS License Management Facility (LMF). The installation procedure displays license information about Kednos PL/I and asks if you have registered and loaded your authorization key for Kednos PL/I for OpenVMS Alpha.
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.
Step 9: Select installation options.
* Do you want to purge files replaced by this installation [YES] ?[Return] |
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]? [Return] |
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 Kednos PL/I. Named DPLI$044.RELEASE_NOTES, the file is in SYS$HELP:. The release notes contain information that is important to Kednos PL/I programmers. Please inform your user community of this file's existence. |
Step 11: Read informational messages.
The Kednos PL/I for OpenVMS Alpha 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 Kednos PL/I for OpenVMS Alpha 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 Kednos PL/I is installed and working correctly. An optional startup file has been placed in SYS$STARTUP:DPLI$STARTUP.COM. The file installs the Kednos PL/I compiler, run-time library, and message files as shared images to improve the performance of using the Kednos PL/I compiler or applications written in PL/I. To improve the performance of using the Kednos PL/I compiler or applications written in PL/I, the startup file installs the Kednos 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 Kednos PL/I V4.4 will now continue for 5 to 30 minutes depending on your configuration and the options requested. Installing Kednos PL/I compiler... %VMSINSTAL-I-RESTORE, Restoring product save set B ... Installing Kednos PL/I definition files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Installing Kednos 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 Kednos PL/I.
If you requested that files be purged at step 7, previous versions of the Kednos PL/I for OpenVMS Alpha files are now purged.
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 12: 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 * * Kednos PL/I for OpenVMS AXP(tm) Systems V4.4 * *-==-------------------------------------------* Copyright Kednos Corporation 1999-2003. All rights reserved. IVP test ASSIGN... IVP test CONV... IVP test BIF... IVP test IO... IVP test SYSERV... **** Kednos PL/I V4.4-002 Installation Verification Successful **** |
Step 13: End the installation procedure.
*--------------------------------------------* * Completed Installation Verification for * * Kednos PL/I for OpenVMS AXP(tm) Systems V4.4 * *--------------------------------------------* Installation of DPLI V4.4 completed at hh:mm Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DPLI044.VMI_DATA VMSINSTAL procedure completed at hh:mm $ LOGOUT [Return] 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.
Previous | Next | Contents | Index |