VAX BLISS-32 Installation Guide Order Number: AA-H510J-TE October 1989 This document contains instructions for installing VAX BLISS- 32 on the VMS operating system. It also explains how to read the online release notes before or after installing the product. This document applies to VAX BLISS-32 Version 4.6 and all maintenance updates beyond that version. Revision/Update Information: This revised document su- persedes the VAX BLISS-32 Installation Guide (Order No. AA-H510I-TE). Operating System and Version: VMS Version 5.0 or higher Software Version: VAX BLISS-32 Version 4.6 digital equipment corporation maynard, massachusetts ___________________________________________________ First Printing, January 1979 Revised, February 1980 Revised, March 1981 Revised, January 1982 Revised, July 1983 Revised, October 1984 Revised, May 1987 Revised, October 1988 Revised, October 1989 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1979, 1980, 1981, 1982, 1983, 1984, 1987, 1988, 1989. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this docu- ment request your critical evaluation to assist in preparing future documentation. ZK5345 Contents ________________________________________________________________ Preface .......................................................v. 1 Preparing to Install VAX BLISS-32............... 1 1.1 Prerequisite Software..................... 1 1.2 Accessing the Online Release Notes...... 1 1.3 Installation Procedure Requirements..... 2 1.4 User Account Quotas and Privileges...... 4 1.5 Special Requirements ...................... 5 1.6 VMS License Management Facility ......... 5 1.7 Using VMSINSTAL............................ 6 2 Installing VAX BLISS-32........................... 9 2.1 Installing VAX BLISS-32 on a VAXcluster.................................. 17 3 After the Installation............................ 18 4 Running the Installation Verification Procedure Separately.............................. 19 5 Error Conditions...................................20 6 Installing VAX BLISS-32 as a Shared Image...... 21 7 Maintenance Updates............................... 22 iii 8 Determining and Reporting Problems.............. 22 9 Sample Installation............................... 23 iv Preface ________________________________________________________________ This document describes how to install VAX BLISS-32 on the VMS operating system. It is intended for system managers. This document applies to VAX BLISS-32 Version 4.6 and all maintenance updates in that version. A major version number is represented by the digits to the left of the decimal point; the maintenance update version number is indicated by the digits to the right of the decimal point. Therefore, this document applies to VAX BLISS-32 Version 4.6 and all maintenance updates up to but not including Version 5.0. Keep this document with your distribution kit. You will need it to install maintenance updates or need to reinstall VAX BLISS-32 for any other reason. At the back of this document are two Reader's Comments forms. If you have any comments about this manual, please fill out one form and mail it; your comments will be considered for the next version of the installation guide. Refer to the VAX BLISS-32 Implementation Language Software Support Addendum (SSA) for a list of supported processors, configurations, and ordering information for this and other VMS software products. Also, refer to the VAX/VMS Optional Software Cross-Reference Tables (SPD 25.99.xx and SPD 28.99.xx) for information on optional products and versions. v For more information on installing VAX BLISS-32 on VMS systems, refer to your processor-specific installa- tion/operations guide. The installation procedure is described step-by-step, and is, for the most part, self-explanatory. The system prompts you to answer questions and change volumes, and waits for you to tell it to continue. Defaults appear in brackets ([]) throughout the installation procedure. Text you type is indicated in red. vi ____________________________________________________________ 1 Preparing to Install VAX BLISS-32 Your bill of materials (BOM) and indented bills report (BIL) specifies the number and contents of your media. Be sure to check the contents of your kit against this material. If your kit is damaged, or if you find that parts of it are missing, please call your Digital 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. ____________________________________________________________ 1.1 Prerequisite Software VAX BLISS-32 requires Version 5.0 or higher of the VMS oper- ating system. If you use DECwindows, Version 5.2 or higher of the VMS operating system is required. The VMS operating system comes with a variety of support options, or classes. Classes include such features as net- working and RMS journaling. To use VAX BLISS-32, your system should be running a version of VMS that includes the classes listed in the Software Support Addendum (SSA), which comes with the Software Product Description (SPD). ____________________________________________________________ 1.2 Accessing the Online Release Notes VAX BLISS-32 provides online release notes. The prompt to display or print the release notes during installation ap- pears in step 5 of the installation procedure when you invoke VMSINSTAL with the OPTIONS N parameter. To obtain the release notes after the installation, type or print the file SYS$HELP:BLS32046.RELEASE_NOTES. Online help also directs you to the release notes. After the installa- tion, type the following command: $ HELP BLISS RELEASE_NOTES ____________________________________________________________ 1.3 Installation Procedure Requirements The installation takes approximately 10 to 45 minutes, de- pending on the type of media and your system configuration. Before installing VAX BLISS-32, you must have the following privileges and resources: o SETPRV privileges, or CMKRNL, WORLD, and SYSPRV privileges o A minimum of 5000 blocks of free disk space during instal- lation; 3600 blocks are used after installation o A minimum of 600 free global pages plus the size (in num- ber of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE at installation o A minimum of 2 free global sections at installation; 1 global section is used after installation. NOTE You must ensure that your system has the necessary global page and global section SYSGEN quotas for the installation. Failure to do so could cause the DCL tables to be corrupted in some situations. In addition, if BLISS-32 is already installed as a known image, VMSINSTAL attempts to reinstall it. It is possible for this to result in global page over- flow, which causes VMSINSTAL to abort. To avoid this problem, increase the number of pages by 600. To determine the number of available global pages on your system, invoke the VMS Install Utility by typing the follow- ing command: $ INSTALL Then type the following command: INSTALL> LIST/GLOBAL/SUMMARY Summary of Local Memory Global Sections ?? Global Sections Used, ???/???? Global Pages Used/Unused INSTALL> EXIT When you issue these commands, the system displays a summary of the number of global sections used, the number of global pages used, and the number of global pages unused. To exit from the VMS Install Utility, type the EXIT command. VAX BLISS-32 requires approximately 600 global pages. If there are fewer than 600 pages available, you can delete an existing known image with the VMS Install Utility, or you can increase the GBLPAGES system parameter with the VMS System Generation Utility (SYSGEN) by editing the file SYS$SYSTEM:MODPARAMS.DAT and then invoking the AUTOGEN com- mand procedure, SYS$UPDATE:AUTOGEN.COM. For more information on the AUTOGEN command procedure, see your processor-specific installation/operations guide. You can determine the number of available global sections by invoking SYSGEN as follows: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW GBLSECTIONS SYSGEN> EXIT The last number displayed is the maximum number of global sections. Compare this number to the number of global sec- tions in use displayed by the VMS Install Utility. VAX BLISS-32 requires 2 global sections. Therefore, if the number of global sections used plus 2 exceeds the maxi- mum number of global sections, you must increase the num- ber of available global sections before you can install VAX BLISS-32. To increase the number, you must increase the GBLSECTIONS system parameter with SYSGEN by editing the file SYS$SYSTEM:MODPARAMS.DAT and then invoking the SYS$UPDATE:AUTOGEN.COM procedure. For more information on the AUTOGEN.COM procedure, see your processor-specific in- stallation/operations guide. If the number of global sections used plus 2 is less than the maximum number of global sections, you can exit from SYSGEN and continue. Refer to the VMS System Manager's Manual for more information on modifying GBLPAGE and GBLSECTION values. ____________________________________________________________ 1.4 User Account Quotas and Privileges To use VAX BLISS-32, each account must have TMPMBX and NETMBX privileges and the following requirements: o AST limit (ASTLM) 24 (minimum) o Buffered I/O quota (BIOLM) 18 (minimum) o Buffered I/O byte count quota (BYTLM) 4100 (minimum) o Direct I/O quota (DIOLM) 18 (minimum) o Enqueue quota (ENQLM) 30 (minimum) o Open file limit (FILLM) 20 (minimum) o Paging file quota (PGFLQUOTA) 17000 (minimum) o Subprocess creation quota (PRCLM) 2 (minimum) o Working set size (WSDEF) 300 pages (minimum) Use the VMS Authorize Utility (AUTHORIZE) to compare the current values of these quotas with the requirements for VAX BLISS-32. For example, the account used in the following example is in the SYSTEM account: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM To change the values of these quotas, use the VMS Authorize Utility's MODIFY command. For more information, see the VMS Authorize Utility Manual. ____________________________________________________________ 1.5 Special Requirements VAX BLISS-32 Version 4.6 requires VMS Version 5.0 or higher. If you use DECwindows, Version 5.2 or higher of the VMS operating system is required. Before you install VAX BLISS-32, you must register the prod- uct using the Product Authorization Key (PAK) provided in the VAX BLISS-32 kit. See the VMS License Management Utility Manual for registration instructions. ____________________________________________________________ 1.6 VMS License Management Facility The VMS License Management facility (LMF) is available with Version 5.0 of the VMS operating system. If you are in- stalling VAX BLISS-32 on a VMS Version 5.0 system, you must register your VAX BLISS-32 software license. The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with VAX BLISS-32. The PAK is a paper certificate that contains information about the license you have to run a particular piece of software. During the installation, you are asked if you have registered the VAX BLISS-32 license and loaded the appropriate autho- rization key. You must register and load your license for VAX BLISS-32 before you start the installation in order to compile system libraries, run the Installation Verification Procedure (IVP), and use the software. To register a license under VMS Version 5.0, first log in to the system manager's account, SYSTEM. You then 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 Issue the LICENSE REGISTER DCL command with the appro- priate qualifiers that correspond to information on the PAK. Depending on the way in which you registered the VAX BLISS- 32 license, you also have a choice of two ways to load the license. o Type YES in response to the appropriate question when you are running SYS$UPDATE:VMSLICENSE.COM. o Enter the DCL LICENSE LOAD command. Note that you need the CMKRNL, SYSNAM, and SYSPRV priveleges to load a license. For complete information on using LMF, see the VMS License Management Utility Manual in the VMS documentation set. ____________________________________________________________ 1.7 Using VMSINSTAL After you log in to a privileged account to install VAX BLISS-32, invoke VMSINSTAL, the command procedure that in- stalls this product. An example of this procedure is shown in steps 1 and 2 of the Installing VAX BLISS-32 section. The VMSINSTAL command procedure has the following syntax: $ @SYS$UPDATE:VMSINSTAL BLS32n ddcu: [OPTIONS N] n Represents the maintenance update of VAX BLISS-32. Refer to the label on the VAX BLISS-32 distribution kit or the VAX BLISS-32 Bill of Materials for the maintenance update number of your kit. You can also type an asterisk (*) in place of BLS32n. If you are installing from magnetic tape, you can use the asterisk to save installation time; the asterisk causes VAX BLISS-32 to be installed with a minimum of tape passes. ddcu: Represents a device name where the distribution volumes will be mounted for the VAX BLISS-32 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 VAX BLISS-32. If you do use the console drive, you should replace any media you removed from the drive. CSA1: is the device name used in examples in this document. 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 prompt you to display or print the release notes. VMSINSTAL permits the use of several other options. For more infor- mation on the other options, see your processor-specific installation/operations guide. If you do not supply the first two parameters, VMSINSTAL prompts you for the product and device names. If you wish to be prompted for the product and device names and to display or print the release notes, type the following: $ @SYS$UPDATE:VMSINSTAL When you invoke VMSINSTAL, it checks the following: o Whether you 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 Whether you have adequate quotas for installation. VMSINSTAL checks for the following quota values: _ ASTLM = 24 _ BIOLM = 18 _ BYTLM = 18000 _ DIOLM = 18 _ ENQLM = 30 _ FILLM = 20 VMSINSTAL then checks whether the following conditions ex- ist. If so, discontinue the conditions before resuming the installation procedure. o Whether DECnet is up and running o Whether any users are logged in to the system If VMSINSTAL detects either of these conditions, you will be asked whether you want to continue the installation. If you want to continue, type YES. If you want to stop the installation, press RETURN. Register the information contained in the Product Authorization Key (PAK) that is shipped with VAX BLISS-32 by using ei- ther the VMS license command procedure (VMSLICENSE) or the LICENSE REGISTER and LICENSE LOAD commands, as described in VMS License Management Utility Manual. ____________________________________________________________ 2 Installing VAX BLISS-32 This section contains excerpts from the installation pro- cedure and explains each step. 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 all files it has created up to that point and then returns you to DCL level. If you want to retry the installa- tion procedure after pressing CTRL/Y, you must proceed from step 2. In future releases of the VMS operating system, enhancements to VMSINSTAL may create additional prompts during the instal- lation. Although such prompts may not appear in this guide, the installation should proceed normally. Refer to the Read Before Installing or Using VAX BLISS-32 letter for any notes about installing this product. 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 Step 2: Invoke VMSINSTAL. $ @SYS$UPDATE:VMSINSTAL BLS32n CSA1: OPTIONS N VAX/VMS Software Product Installation Procedure VX.X 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, type 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 CSA1:. * Are you ready? YES The following products will be processed: BLS32 Vn.n Beginning installation of BLS32 Vn.n at hh:mm %VMSINSTAL-I-RESTORE, Restoring product saveset A... To indicate that you want to continue the installation, mount volume 1, type YES, and press RETURN. Step 4: Respond to licensing prompt. Product: BLISS32 Producer: DEC Version: 4.6 Release Date: 1-JUN-1989 * Does this product have an authorization key registered and loaded? Y VAX BLISS-32 supports the VMS License Management Facility (LMF). This prompt refers to the Product Authorization Key (PAK) provided in the VAX BLISS-32 kit. You must verify that VAX BLISS-32 has been registered correctly. If you have registered VAX BLISS-32 using the PAK, type YES and press RETURN. If you have not registered VAX BLISS-32, type NO and press RETURN. If you type NO, the installation of VAX BLISS-32 will continue, but you will not be able to run VAX BLISS-32 when the installation is complete. After the installation, register the product using the PAK. Then, to run VAX BLISS-32, you must compile the system require files and run the Installation Verification Procedure (IVP) by entering the following commands: $ SET DEFAULT SYS$LIBRARY $ BLISS/LIBRARY STARLET $ BLISS/LIBRARY=LIB STARLET+LIB $ BLISS/LIBRARY TPAMAC Then, run the Installation Verification Procedure (IVP) by entering the following command: $ @SYS$TEST:BLISS32$IVP See the VMS License Management Utility Manual for registration instructions. Step 5: Select a release notes option. This step applies only if you specified OPTIONS N in step 2. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [3]: 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. If you select option 2, VMSINSTAL prompts you for a queue name. Either type a queue name or press RETURN to send the file to the default output print device. * 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. Either type a queue name or press RETURN to send the file to the default output print device. The VAX BLISS-32 release notes are then copied to SYS$HELP:BLS32046.RELEASE_NOTES. If you select option 4, VMSINSTAL copies the release notes to SYS$HELP immediately. If you select option 5, VMSINSTAL does not display, print or copy the release notes; typically this option is selected when you want 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. Take care not to delete release notes for previous versions of VAX BLISS-32. Next, VMSINSTAL displays the following prompt: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product release notes have been successfully moved to SYS$HELP. If you want to continue the installation, type YES and press RETURN. If you type NO or press RETURN, VMSINSTAL discontinues the installation. In either case, VMSINSTAL moves the release notes to SYS$HELP. Step 6: Select installation options. * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after installation [YES]? This kit contains a file summarizing the new features, changes, restrictions, and compatibility issues in this release of VAX BLISS-32. This file is named BLS32046.RELEASE_NOTES and will be placed in SYS$HELP:. The release notes contain information valuable to VAX BLISS-32 programmers. Please inform your VAX BLISS-32 users of this file's existence. The directories SYS$LIBRARY and SYS$SYSTEM contain previous versions of VAX BLISS-32 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 type NO to keep them. The Installation Verification Procedure (IVP) runs tests to check whether the installation procedure was successful. Press RETURN to run the IVP after the installation. If you do not want to run the IVP, type NO in response to the prompt. The BLISS help file contains extensive documentation on the BLISS language. Since this material requires about 525 blocks of disk space, its inclusion is optional. Do you want the long help file [YES]? If you choose to install the long form of VAX BLISS-32 help, the additional help file is appended to the shorter version and the shorter version is deleted. If you choose not to install the longer help file, only standard information about the DCL BLISS command is included in the help library. However, the file SYS$HELP:BLS32046.RELEASE_NOTES remains. Do you want to install the DECwindows Compiler Interface [YES]? The DECwindows compiler interface (DWCI) for VAX BLISS-32 allows you to use a window interface to select compiler options when you compile a VAX BLISS-32 program. See the Release Notes for more information on DWCI. The DWCI option requires that FileView directories [VUE$LIBRARY.SYSTEM] and [VUE$LIBRARY.USER] be present on the target disc. For more information on FileView, see the VMS DECwindows User's Guide. Step 7: Read informational messages. The VAX BLISS-32 installation procedure produces a number of informational messages that report on the progress of the installation. %BLS32-I-LIBBUILD, Building the precompiled libraries This phase of the installation process compiles the STARLET, LIB, and TPAMAC L32 files. The corresponding REQ files are expected to be in SYS$LIBRARY. If one is missing, you will receive a warning message and that library file will not be created. This will not interfere with the rest of the installation. The installation continues with the following system messages: All questions regarding the installation have now been asked. The system directories will now be updated. The installation of VAX BLISS-32 V4.6 will be complete in approximately 5 to 40 minutes. The success of the installation is indicated by the following message: %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 following files are created or modified by the installation procedure: _____________________________________________________________ Component________Destination______Function___________________ BLISS32.EXE [SYSEXE] BLISS-32 compiler BLISS.HLP [SYSHLP] System HELP library BLISS$DWCI.HLB [SYSHLP] DWCI HELP library BLISS$DWCI.EXE [VUE$LIBRARY.USERDECwindows interface BLISS$DWCI.UID [VUE$LIBRARY.USERDWCI user interface definition BLISS32$IVP.BLI [SYSTEST.BLS32] Source for test file BLISS32$IVP.COM [SYSTEST] IVP test file BLS32046.RELEASE_[SYSHLP] System HELP library CONDIT.R32 [SYSLIB] Condition handling macros EZIO32.B32 [SYSLIB] Simplified input/output module EZIO.DOC [SYSLIB] Documentation for above _____________________________________________________________ Component________Destination______Function___________________ MODULE.BLI [SYSLIB] Module-routine template TUTIO.R32 [SYSLIB] BLISS primer input/output macros TUTIO.DOC [SYSLIB] Documentation for above TUTIO.RNO [SYSLIB] RUNOFF source for documentation VUE$COMPILE.COM [VUE$LIBRARY.USERDECwindows command __________________________________procedure__________________ The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE files are updated to include the new versions of the VAX BLISS-32 help text and the BLISS command line definition, respectively. The VAX BLISS-32 release notes are copied to SYS$HELP:BLS32046.RELEASE_NOTES. If you typed YES in response to the prompt that requests a file purge at step 6, previous versions of the VAX BLISS-32 files are now purged. Step 8: Observe the Installation Verification Procedure (IVP). If you chose to run the IVP in step 6, the installation procedure now calls the IVP to verify that VAX BLISS-32 was successfully installed. %BLS32-I-IVP, Performing Installation Verification Procedure *************************** Successful Installation of VAX BLISS-32 V4.n *************************** Step 9: End the installation procedure. Installation of BLS32 V4.n completed at hh:mm Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at hh:mm $ LOGOUT SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss When the VAX BLISS-32 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 are going to continue using the system manager's account and want to restore those symbols, you should log out and log in again. ____________________________________________________________ 2.1 Installing VAX BLISS-32 on a VAXcluster If you want to run VAX BLISS-32 on multiple nodes of a VAXcluster, first check to see that you have the appropriate software license. Refer to the Licensing Management Utility Manual for directions on how to load the license on nodes licensed to use VAX BLISS-32. Then, follow these steps after installing VAX BLISS-32: 1.Determine whether BLISS32.EXE was installed using the INSTALL utility (as described in the Installing VAX BLISS-32 as Shared Image section). If INSTALL was used, perform all of the following steps. If INSTALL was not used, omit step 6. 2.Log in to the SYSTEM account. 3.Invoke the SYSMAN utility with the following command: $ MCR SYSMAN 4.Instruct SYSMAN to perform the commands you enter on every node in the VAXcluster, as follows: SYSMAN> SET ENVIRONMENT /CLUSTER 5.Enter the following command to update the DCL tables: SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE 6.Then, if VAX BLISS-32 was installed using the INSTALL utility, enter the following command to replace the INSTALL entry for BLISS32.EXE: SYSMAN> DO INSTALL REPLACE SYS$SYSTEM:BLISS32.EXE ____________________________________________________________ 3 After the Installation VAX BLISS-32 is now installed and can be invoked with the BLISS command. The installation procedure modifies the DCL command table so that the BLISS command is recognized and processed. However, the previous command table is still in effect for users who are currently logged in. All logged-in users who want to use the BLISS command must log out of the system and log in again. If VAX BLISS-32 will be used extensively on your system, you can reduce system overhead and memory requirements by installing it as a shared image using the VMS Install Utility. For more information, see the section Installing VAX BLISS-32 as a Shared Image. ____________________________________________________________ 4 Running the Installation Verification Procedure Separately The Installation Verification Procedure (IVP) is usually run at installation. If you want to run the IVP separately to ensure the integrity of installed files if system problems occur, execute the following command procedure: $ @SYS$TEST:BLISS32$IVP If the IVP fails for any reason, the following messages are displayed: The VAX BLISS-32 V4.6 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for VAX BLISS-32 V4.6 has failed. If you did not register VAX BLISS-32 before installing VAX BLISS-32, after the installation register the product using the Product Authorization Key (PAK). Then, to run VAX BLISS-32 you must compile the system require files and run the IVP by entering the following commands: $ SET DEFAULT SYS$LIBRARY $ BLISS/LIBRARY STARLET $ BLISS/LIBRARY=LIB STARLET+LIB $ BLISS/LIBRARY TPAMAC Then, run the Installation Verification Procedure (IVP) by entering the following command: $ @SYS$TEST:BLISS32$IVP Refer to step 4 in the Installing VAX BLISS-32 section for more information. ____________________________________________________________ 5 Error Conditions If the installation procedure fails for any reason, a message like the one following is displayed: VAX BLISS-32 V4.6 Installation failed. Please consult the VAX BLISS-32 Installation Guide for further information. An error during the installation can occur if one or more of the following conditions exist: o Operating system version is incorrect. o Quotas necessary for successful installation are insufficient (see the Installation Procedure Requirements section). o Process quotas required by VMSINSTAL are incorrect (see the Using VMSINSTAL section). o The VMS HELP library is currently in use. o The product was registered incorrectly or not registered. o The DECwindows FileView application files are not present. For descriptions of the error messages generated by these conditions, see the VMS System Messages and Recovery Procedures Reference Volume, your processor-specific installation/operations guide, or the VMS License Management Utility Manual. If you are notified that any of these conditions exist, you should 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, you must restart the installation procedure from step 2. If the installation fails due to an IVP failure, contact a Digital field service representative. ____________________________________________________________ 6 Installing VAX BLISS-32 as a Shared Image If VAX BLISS-32 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 VMS Install Utility while you are logged in to a privileged account. It is recommended that you perform the following steps on a system that has just been bootstrapped because the available space in the global page table is less likely to be fragmented. If errors occur, see VMS System Messages and Recovery Procedures Reference Volume. First, determine the number of available global pages and global sections on your system. See the Installation Procedures Requirements section for information on how to do this. Then, invoke the VMS Install Utility and install VAX BLISS-32 as a shared image by typing the following commands: $ RUN SYS$SYSTEM:INSTALL INSTALL> ADD SYS$SYSTEM:BLISS32.EXE/OPEN/SHARED INSTALL> EXIT Then, update the system startup file to install VAX BLISS-32. To ensure that VAX BLISS-32 is installed as a shared image each time the system is bootstrapped, include the following lines in SYS$MANAGER:SYSTARTUP_V5.COM (the site-specific startup file): $ INSTALL ADD SYS$SYSTEM:BLISS32.EXE/OPEN/SHARED EXIT ____________________________________________________________ 7 Maintenance Updates Digital may periodically issue maintenance updates of VAX BLISS-32. Each update consists of an installation kit. You should install this kit as described in this document 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 1.0, the version number of the first maintenance update will be 1.1. In addition, the maintenance update includes new release notes. The release notes describe the changes that have been made to VAX BLISS-32 since the previous release. The update release notes are provided on line. You should read the release notes when you first install VAX BLISS-32; they are also accessible at any time after the product is installed. For information on reading the release notes at the time that you install VAX BLISS-32, follow the installation procedure through step 6. To locate the release notes after VAX BLISS-32 is installed, display or print the file SYS$HELP:BLS32046.RELEASE_NOTES, or type the following command: $ HELP BLISS RELEASE_NOTES ____________________________________________________________ 8 Determining and Reporting Problems If an error occurs while you are using VAX BLISS-32, and you believe that the error is caused by a problem with VAX BLISS-32, take one of the following actions: o If you purchased VAX BLISS-32 within the last 90 days and you think the problem is caused by a software error, submit a Software Performance Report (SPR). 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 representative.) o If you have a Self-Maintenance Software Agreement, submit a Software Performance Report (SPR). If you find an error in the VAX BLISS-32 documentation, fill out and submit a Reader's Comments form from the back of the document in which the error was found. Specify the section and page number where the error was found. ____________________________________________________________ 9 Sample Installation This section contains a sample installation of VAX BLISS-32. Note that this is only a sample. Sometimes the installation procedure is modified slightly in maintenance updates of this product. Because this installation guide is not usually revised for maintenance updates, be sure to read the Read Before Installing or Using VAX BLISS-32 letter before you install this product. The letter notes any significant changes in the installation that vary from this sample. Username: SYSTEM Password: $ @SYS$UPDATE:VMSINSTAL BLS32046 CSA1: OPTIONS N VAX/VMS Software Product Installation Procedure V5.n It is 29-MAY-1989 13:02:29.21 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: BLS32 V4.6 Beginning installation of BLS32 V4.6 at 13:04 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. Copyright - Digital Equipment Corporation. 1976, 1989. All rights reserved. Product: BLISS32 Producer: DEC Version: 4.6 Release Date: 1-JUN-1989 * Does this product have an authorization key registered and loaded? YES Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [3]: 2 * Queue name [SYS$PRINT]: Job BLS32046 (queue SYS$PRINT, entry 262) started on SYS$PRINT Do you want to continue the installation [NO]?: YES %VMSINSTAL-I-RESTORE, Restoring product saveset B ... * Do you want to purge files replaced by this installation [YES]? * 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 BLISS-32. This file is named BLS32046.RELEASE_NOTES and will be placed in SYS$HELP:. The release notes contain information valuable to VAX BLISS-32 programmers. Please inform your VAX BLISS-32 users of this file's existence. The BLISS help file contains extensive documentation on the BLISS language. Since this material requires about 525 blocks of disk space, its inclusion is optional. * Do you want the long help file [YES]? Do you want to install the DECwindows Compiler Interface [YES]? All questions regarding the installation have now been asked. The systen directories will now be updated. The installation of VAX BLISS-32 V4.6 will be complete in approximately 5 to 40 minutes %BLS32-I-LIBBUILD, Building the precompiled libraries This phase of the installation process compiles the STARLET, LIB, and TPAMAC L32 files. The corresponding REQ files are expected to be in SYS$LIBRARY. If one is missing, you will receive a warning message and that library file will not be created. This will not interfere with the rest of the installation. All questions regarding the installation have now been asked. The system directories will now be updated. The installation of VAX BLISS-32 V4.6 will be complete in approximately 5 to 15 minutes. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.BLISS32]. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %BLS32-I-IVP, Performing Installation Verification Procedure *************************** Successful Installation of VAX BLISS-32 V4.6 *************************** Installation of BLS32 V4.6 completed at 13:23 Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 13:23 $ LOGOUT SYSTEM logged out at 29-MAY-1989 13:23:29.21