DEComni/VMS Software Installation Guide May 1991 This document describes how to install DEComni/VMS software and documentation. Revision/Update Information: This is a revised document. Operating System: VMS Version 5.3 or Version 5.4 Software Version: DEComni/VMS Version 1.1 digital equipment corporation maynard, massachusetts Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Any 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 or 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 1990, 1991. All rights reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: Bookreader, CompacTape (TK50), DEC, DECnet, DEComni/VMS, DECwindows, MicroVAX, VAX, VAXcluster, VAX DEC/MAP, VAX Rdb /VMS, VAXstation, VMS, and the DIGITAL logo. This document is available in online and CDROM versions. This document was prepared with VAX DOCUMENT, Version 1.2. Contents ________________________________________________________________ Preface ......................................................... vii ________________________________________________________________ Chapter 1 Introduction to DEComni/VMS 1.1 Product Description ............................... 1-1 1.2 Checking the Contents of the Kit ................ 1-2 1.3 DEComni/VMS Documentation ........................ 1-3 1.4 Obtaining the Online Installation Guide........ 1-5 1.5 Using VMSINSTAL.................................... 1-7 ________________________________________________________________ Chapter 2 Preparing for Installation 2.1 Backing Up Your System Disk...................... 2-1 2.2 Hardware Requirements............................. 2-1 2.3 Prerequisite Software............................. 2-2 2.4 Preinstallation Requirement...................... 2-2 iii 2.5 Preliminary VMS Class Considerations............ 2-3 2.6 Checking the VMS Version.......................... 2-3 2.7 Obtaining Required Privileges ................... 2-3 2.8 Disk Space Requirements........................... 2-3 2.9 Setting Required System Parameters.............. 2-4 2.9.1 Displaying System Parameters............. 2-4 2.9.2 Changing System Parameter Values with AUTOGEN ..................................... 2-5 2.10 Setting Required Account Process Quotas........ 2-6 2.11 Running the License Registration ................ 2-8 2.12 Displaying and Printing Release Notes .......... 2-8 ________________________________________________________________ Chapter 3 Installing DEComni/VMS 3.1 DEComni/VMS Installation Procedure.............. 3-1 ________________________________________________________________ Chapter 4 Postinstallation Considerations 4.1 Starting DEComni/VMS .............................. 4-1 4.2 Running the Installation Verification Procedure........................................... 4-2 4.3 Resolving IVP Failures............................ 4-3 4.4 User Account Quotas and Privileges.............. 4-4 iv 4.5 Stopping DEComni/VMS .............................. 4-4 4.6 DEComni Example Programs.......................... 4-5 4.7 The DEComni Database and Rdb..................... 4-6 4.8 Determining and Reporting Problems.............. 4-6 ________________________________________________________________ Appendix A DEComni/VMS Files Added or Modified on the System A.1 Files Added......................................... A-1 A.2 Files Modified ..................................... A-3 ________________________________________________________________ Appendix B Installation Example B.1 Installation Session .............................. B-1 ________________________________________________________________ Appendix C Products on Your System ________________________________________________________________ Index ________________________________________________________________ Tables 1-1 Documentation Names and Filenames............... 1-3 1-2 Viewing Documentation............................. 1-4 2-1 Installation Options and Disk Space............. 2-4 2-2 System Parameters.................................. 2-4 2-3 Account Quotas ..................................... 2-6 v 4-1 Resolving IVP Failures............................ 4-3 4-2 Account Quotas ..................................... 4-4 C-1 Products and Processes............................ C-1 vi Preface ________________________________________________________________ The DEComni/VMS Software Installation Guide describes how to install DEComni. ____________________________________________________________ Intended Audience This document is for system and network managers. ____________________________________________________________ Document Structure The DEComni/VMS Software Installation Guide is structured as follows: o Chapter 1 contains introductory information about DEComni /VMS software and online documentation. o Chapter 2 describes the preparations and requirements necessary for installing DEComni/VMS. o Chapter 3 describes how to install DEComni/VMS. o Chapter 4 describes postinstallation considerations. o Appendix A contains a list of files added to or modified on your system after installing DEComni/VMS. vii o Appendix B provides a sample installation of DEComni/VMS. o Appendix C provides information about how to check if VAX Rdb/VMS, VAX DEC/MAP, and DEComni/VMS are running on your system. ____________________________________________________________ Associated Documents This document is part of the following online documentation set: o DEComni/VMS Application Programmer's Guide o DEComni/VMS Guide to Using OmniView o DEComni/VMS Software Installation Guide o DEComni/VMS Network Manager's Guide ____________________________________________________________ Conventions The following conventions are used in this document. _____________________________________________________________ Convention_________Meaning___________________________________ Press the Return key. UPPERCASE All uppercase letters in a command line indicate keywords that must be entered. You can enter them in either uppercase or lowercase. You can use the first three characters to abbreviate command key- words, or you can use the minimum unique abbreviation. viii _____________________________________________________________ Convention_________Meaning___________________________________ lowercase italics Lowercase italics in command syntax or examples indicate variables for which either you or the system supplies a value. [ ] In examples showing VMS directory specifi- cations, square brackets are a necessary part of the specification, [directory- name]. In a procedure, square brackets in an in- quiry enclose the default response for the inquiry. Press the specified key. While holding down the Ctrl key, press the key specified by x. . Vertical ellipses (dots) in examples . represent data that has been omitted. .____________________________________________________________ ix Chapter 1 Introduction to DEComni/VMS ________________________________________________________________ This chapter provides information about DEComni/VMS, the contents of the DEComni/VMS kit, and VMSINSTALL. ____________________________________________________________ 1.1 Product Description DEComni/VMS is Digital's OSI-based software product that im- plements the ISO 9506 specification. DEComni/VMS provides Manufacturing Messages Specification (MMS) services for a VMS application program. MMS supports applications involved in the control and monitoring of manufacturing devices in a distributed processing environment. DEComni/VMS provides com- munication support over an IEEE 802.3 or IEEE 802.4 physical layer. For a complete product description of DEComni/VMS, see the DEComni/VMS Software Product Description (SPD) included in this kit. Introduction to DEComni/VMS 1-1 ____________________________________________________________ 1.2 Checking the Contents of the Kit Check your distribution kit to ensure it contains everything listed on the Bill of Materials (BOM). DEComni/VMS software is available on CompacTape (TK50) and Magtape. This tape contains DEComni software and online documentation. The kit includes a Digital Product Authorization Key (PAK) for the DEComni/VMS software. You use the PAK to supply information to the VMSLICENSE procedure as described in Chapter 2. 1-2 Introduction to DEComni/VMS ____________________________________________________________ 1.3 DEComni/VMS Documentation DEComni/VMS now provides you with two sets of documentation; a hardcopy documentation set and an online documentation set. The online documentation set includes the following: o DEComni/VMS Software Installation Guide o DEComni/VMS Application Programmer's Guide o DEComni/VMS Guide to Using OmniView o DEComni/VMS Network Manager's Guide The hardcopy documentation set consists of two reference cards and a pocket guide and is packaged with the DEComni/VMS kit. The hardcopy documentation set includes the following: o DEComni/VMS Installation Card o DEComni/VMS OmniView Reference Card o DEComni/VMS Pocket Guide The online DEComni documentation set is physically contained in the software distribution medium and is labeled as fol- lows: Table 1-1: Documentation Names and Filenames _____________________________________________________________ Title______________________Filename__________________________ DEComni/VMS Software OMNI$INSTALLATION_GUIDE Installation Guide DEComni/VMS Application OMNI$APPL_PROG_GUIDE Programmer's Guide _____________________________________________________________ (continued on next page) Introduction to DEComni/VMS 1-3 Table 1-1 (Cont.): Documentation Names and Filenames _____________________________________________________________ Title______________________Filename__________________________ DEComni/VMS Guide to OMNI$GUIDE_TO_OMNIVIEW Using OmniView DEComni/VMS Network OMNI$NETWORK_MNGR_GUIDE Manager's_Guide______________________________________________ NOTE Both ASCII text and PostScript versions of each book are provided, the filename extensions are .TXT for ASCII text and .PS for PostScript. The DEComni/VMS installation procedure allows for easy trans- fer of the documentation files. Once transfered to disk the files can be viewed in any of the methods listed in Table 1-2: Table 1-2: Viewing Documentation _____________________________________________________________ Format___________Method______________________________________ ASCII text Use the editor of your choice Use the DCL command TYPE/PAGE Print the file(s) PostScript Display on a workstation with VIEW command Print the file(s) _____________________________________________________________ See Chapter 3 for details on how to transfer the files, and see Chapter 2 for details on disk space requirements for the software and online documents. 1-4 Introduction to DEComni/VMS ____________________________________________________________ 1.4 Obtaining the Online Installation Guide You can obtain the DEComni/VMS Software Installation Guide by following these steps: 1. Log in to the SYSTEM accout or similarly priviledged account. For example: Welcome to VAX/VMS V5.4-1 Username: SYSTEM Password: Welcome to VAX/VMS version V5.4-1 on node SAFRON Last interactive login on Tuesday, 5-MAR-1991 16:20 Last non-interactive login on Thursday, 14-FEB-1991 11:27 $ 2. Physically load the software distribution medium(magtape or TK50) on the appropriate device. 3. Invoke VMSINSTAL as follows: $ @SYS$UPDATE:VMSINSTAL OMNI011 ddcu: where ddcu: is the device name dd is the device code, c is the controller letter, and u is the unit number. For example: $ @SYS$UPDATE:VMSINSTAL OMNI011 mua0: VAX/VMS Software Product Installation Procedure V5.4-1 It is 5-MAR-1991 at 16:22. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Y The following products will be processed: OMNI V1.1 Beginning installation of OMNI V1.1 at 16:22 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Introduction to DEComni/VMS 1-5 © Digital Equipment Corporation. 1990,1991. All Rights Reserved. Installation procedure for DEComni/VMS V1.1 All of the DEComni/VMS documentation is now provided in an electronic online fashion. That is, all documents are provided in both ASCII text and Postscript file formats as part of this software kit. Once moved to disk you may read them using any of the following methods: ASCII text formatted files - Using the editor of your choice. -------------------------- - Using the DCL command TYPE/PAGE. - Print the file(s). POSTSCRIPT formatted files - Display on a workstation with VIEW command -------------------------- - Print the file(s). * Press RETURN to continue: 4. You will then be given the choice of displaying or print- ing the installation guide. Accessing the DEComni/VMS Installation Guide -------------------------------------------- You now have the following options for accessing this product's installation guide. The installation guide will always be copied to SYS$HELP as OMNI$INSTALLATION_GUIDE.TXT filename. 1. Displayed on your screen now. 2. Print the installation guide. 3. Both 1 and 2. 4. None of the above. * Select option [1]:4 Your are now being given an opportunity to exit this installation procedure. An ASCII text format of the installation guide will be copied to SYS$HELP even if you choose not to continue the instal- lation at this point. * Do you wish to continue this installation [N]? N The ASCII text format of the DEComni/VMS Installation Guide will be copied to the following: DIRECTORY: SYS$HELP FILENAME: OMNI$INSTALLATION_GUIDE.TXT %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 1-6 Introduction to DEComni/VMS Installation of OMNI V1.1 completed at 16:25 VMSINSTAL procedure done at 16:25 $ 5. An ASCII text format of the DEComni/VMS Installation Guide will be moved to directory: SYS$HELP as filename: OMNI$INSTALLATION_GUIDE.TXT whether you choose to continue the installation or not. 6. After exiting VMSINSTAL you can read the DEComni/VMS Installation Guide using any of the following methods. _ Read it in the editor of your choice. $ EDIT/READ sys$help:OMNI$INSTALLATION_GUIDE.TXT _ Print it on any printer that accepts ASCII text files. $ PRINT sys$help:OMNI$INSTALLATION_GUIDE.TXT _ Type the file. $ TYPE/PAGE sys$help:OMNI$INSTALLATION_GUIDE.TXT ____________________________________________________________ 1.5 Using VMSINSTAL Chapter 3 explains how to install DEComni/VMS using VMSINSTAL, a standard utility used to install most VAX/VMS software products that is provided with the VMS operating system. For further information about VMSINSTAL, see the sec- tion about "Installing Software" in the VMS System Manager's Manual which is part of the VMS Base Documentation Set. Introduction to DEComni/VMS 1-7 Chapter 2 Preparing for Installation ________________________________________________________________ This chapter explains the preparations you need to make before you begin installing DEComni/VMS. Also, this chapter explains how to access the DEComni/VMS release notes and provides information about backing up your system disk. The following sections provide details about the preparatory steps you take when installing DEComni/VMS. ____________________________________________________________ 2.1 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 do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details in performing a system disk backup, see the section about the Backup Utility in the VMS System Management Subkit. ____________________________________________________________ 2.2 Hardware Requirements The appropriate IEEE 802.3 or IEEE 802.4 communication con- troller must be installed on your VAX computer before in- stalling DEComni/VMS, and your VAX computer must meet the hardware requirements specified in the DEComni/VMS Software Product Description/System Support Addendum (SPD/SSA). Preparing for Installation 2-1 ____________________________________________________________ 2.3 Prerequisite Software Prerequisite software and software versions may change. For the most accurate prerequisite information, please con- sult the current DEComni/VMS System Support Addendum (SSA 32.32.xx) which is part of the DEComni/VMS Software Product Description (SPD 32.32.xx). Before you install DEComni/VMS, you must install the follow- ing software: o VMS V5.3 or V5.4 o VAX Rdb/VMS (Run-time option) V4.0 o VAX DEC/MAP V3.0 NOTE In addition to having all prerequisite software in- stalled before installing DEComni/VMS, you must also have VAX Rdb/VMS running before DEComni/VMS instal- lation; and if you plan to run the DEComni/VMS IVP as part of the DEComni/VMS installation (which is recom- mended), you must also have VAX DEC/MAP running before installing DEComni/VMS. ____________________________________________________________ 2.4 Preinstallation Requirement Before you install and use DEComni/VMS, you must configure and start DECnet. The DECnet services that VMS provides are sufficient to accomplish this task - a DECnet license is not a prerequisite for DEComni/VMS. You will need to run NETCONFIG.COM and STARTNET.COM. For further information, see the "Guide to DECnet-VAX Networking" section in the VMS System Management Subkit. 2-2 Preparing for Installation ____________________________________________________________ 2.5 Preliminary VMS Class Considerations The following VMS classes are required for full functionality of this VMS layered product: o VMS Required saveset o Network o Programming support o System Programming support o Utilities ____________________________________________________________ 2.6 Checking the VMS Version To check the VMS version of your system, use the following command: $ write sys$output f$getsyi("version") ____________________________________________________________ 2.7 Obtaining Required Privileges Before you can install DEComni/VMS, you must have the fol- lowing: On the SYSTEM account, you should have SETPRV privi- leges, or CMKRNL, WORLD, and SYSPRV privileges. You can ver- ify that you have those privileges by issuing the following command: $ show process/privileges ____________________________________________________________ 2.8 Disk Space Requirements Table 2-1 indicates the amount of free disk space you need before you install DEComni/VMS and the amount of free disk space you need for permanent use by DEComni/VMS. Preparing for Installation 2-3 Table 2-1: Installation Options and Disk Space _____________________________________________________________ InstallationBlocks To Type________Install_____Blocks_for_Permanent_Use_____________ Software 32,000 31,000 only Software 43,000 41,600 and docu- mentation Documentatio11,000 10,600 only_________________________________________________________ To verify how much disk space you have, issue the following command: $ show device sys$sysdevice ____________________________________________________________ 2.9 Setting Required System Parameters System parameters must be set to the following values to accommodate the space requirements for DEComni/VMS data structures: Table 2-2: System Parameters _____________________________________________________________ Parameter________Minimum_Value_______________________________ FREE_GBLPAGES 200 FREE_GBLSECTS____10__________________________________________ ____________________________________________________________ 2.9.1 Displaying System Parameters To check the system parameters, use the commands described in the following sections. 2-4 Preparing for Installation Displaying Free Global Pages To determine the current number of free global pages: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") VMS displays the current value associated with the FREE_GBLPAGES parameter. Displaying Free Global Sections To determine the current number of free global sections: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") VMS displays the current value associated with the FREE_GBLSECTS parameter. For additional information about these parameters, or for help when checking values, see the "System Generation (SYSGEN) Utility" section in the VMS System Management Subkit. If you need to change one or more system parameters, proceed to Section 2.9.2. If you do not need to change system parameters, proceed to Section 2.10. ____________________________________________________________ 2.9.2 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parame- ters. AUTOGEN automatically adjusts values for parameters as- sociated with the values you reset manually. To change system parameters with AUTOGEN, edit the SYS$SYSTEM:MODPARAMS.DAT file. Use an editor to access the file. To change a parameter value already listed in this file, delete the current value associated with that parameter and enter the new value. To modify incremental parameters, such as GBLPAGES and GBLSECTIONS, use ADD_. The following example increases the global page setting by 380: ADD_GBLPAGES = 380 Preparing for Installation 2-5 After you have made all your changes, exit from the editor and run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system when it has finished. Any users logged on to the system are immediately discon- nected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources during the last reboot. To take advantage of this feature, do not use the NOFEEDBACK parameter (P3) in the AUTOGEN command line. For more information about how to use AUTOGEN, see the "Guide to Setting Up a VMS System" section in the VMS System Management Subkit. ____________________________________________________________ 2.10 Setting Required Account Process Quotas Before you install DEComni/VMS, you must ensure that the account from which you install (typically the SYSTEM account) and the VAX OSI Transport Service (VOTS) account have the account quotas shown in Table 2-3. Table 2-3: Account Quotas _____________________________________________________________ Attribute_____Minimum_Value__________________________________ ASTlm 24 BIOlm 18 BYTlm 20480 DIOlm 18 _____________________________________________________________ (continued on next page) 2-6 Preparing for Installation Table 2-3 (Cont.): Account Quotas _____________________________________________________________ Attribute_____Minimum_Value__________________________________ ENQlm 2000 FILlm 50 Pgflquota 20000 Prclm 1+ WSdefault 256 WSextent 3072 WSquota_______768____________________________________________ To display process quotas, use the AUTHORIZE utility: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM If no changes are necessary, enter the EXIT command to leave the AUTHORIZE utility. To modify system account quotas (for example, ENQLM): UAF> MODIFY SYSTEM/ENQLM=2000 You will get a message confirming the change. Then enter the EXIT command to leave the utility. You must log out and then log in again to reset the system account quotas. The AUTHORIZE utility is described in the VMS System Manager's Manual of the VMS Base Documentation Set. Preparing for Installation 2-7 ____________________________________________________________ 2.11 Running the License Registration You must register the DEComni/VMS license through the VMS License Management Facility (LMF) in accordance with the license agreement signed for your site. The license reg- istration information you need is contained in the Product Authorization Key (PAK) that is shipped with DEComni/VMS. The PAK is a paper certificate that contains information about your license to run a particular piece of software. During the installation, VMSINSTAL asks if you have regis- tered your DEComni license and loaded the appropriate au- thorization key. You must register and load your DEComni/VMS license before you start the installation in order to run the Installation Verification Procedure (IVP) and use the software. To register a license under VMS, first log into the system manager's account, SYSTEM. You can then register it in one of two ways: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your Product Authorization Key (PAK). o At the DCL prompt, issue the LICENSE REGISTER command with the needed qualifiers, which are listed in the PAK. If you use DEComni/VMS on more than one node of a VAXcluster system, you must perform a license load on the other nodes after you complete this installation. For complete information about how to use the license util- ity, see the VMS License Management Utility Manual in the VMS Base Documentation Set. ____________________________________________________________ 2.12 Displaying and Printing Release Notes DEComni/VMS provides online release notes, which can be displayed or printed. It is recommended that you read the release notes before installation. 2-8 Preparing for Installation To display or print release notes, you must invoke VMSINSTAL with option N. Option N allows you to exit the installa- tion procedure after reading the release notes. For more information, see Chapter 3. VMSINSTAL automatically places the release notes with the file name OMNI011.RELEASE_NOTES in SYS$HELP. Preparing for Installation 2-9 Chapter 3 Installing DEComni/VMS ________________________________________________________________ This chapter describes how to install DEComni/VMS on your VAX computer. The procedure described in this chapter indicates the in- stallation of the DEComni/VMS software and the entire online documentation set. If you use a VAXstation 3600 and the TK50 medium, you can in- stall DEComni/VMS in approximately 20 minutes - during which time the software is installed and the online documentation is transferred. Other hardware and medium configurations can effect the installation time. ____________________________________________________________ 3.1 DEComni/VMS Installation Procedure This section contains excerpts from the installation dialog, along with explanatory text. Digital may enhance future releases of VMSINSTAL and add additional prompts. While the additional prompts may not be documented in this guide, the installation should proceed normally. NOTE Once started, the installation procedure can be aborted at any time by pressing Ctrl/y. Also, you can enter a question mark (?) at anytime for additional information. Installing DEComni/VMS 3-1 1. If you are not logged in, log in to the system manager's account or equivalent: Welcome to VAX/VMS V5.4-2 Username: SYSTEM Password: Welcome to VAX/VMS version V5.4-2 on node SAFRON Last interactive login on Thursday, 28-MAR-1991 14:58 Last non-interactive login on Thursday, 28-MAR-1991 15:36 2. Invoke VMSINSTAL: $ @SYS$UPDATE:VMSINSTAL OMNI011 ddcu: OPTIONS N where: ddcu: is the device name, dd is the device code, c is the controller letter, and u is the unit number OPTIONS N allows you to display or print the release notes and to exit the installation procedure after reading the release notes. 3. The DEComni/VMS installation procedure begins. The follow- ing VMSINSTAL prompts are displayed: VAX/VMS Software Product Installation Procedure V5.4.2 It is 28-March-1991 at 15:38. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Y The following products will be processed: OMNI V1.1 Beginning installation of OMNI V1.1 at 15:38 %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 3-2 Installing DEComni/VMS * Select option [2]: 4 4. If you select option 4, as the example shows, the re- lease notes are moved to the directory SYS$HELP with the filename OMNI011.RELEASE_NOTES. 5. Next, VMSINSTAL displays the following message: * Do you want to continue the installation [NO]? Y 6. You can exit the installation at this point if you want to read the release notes outside of the context of VMSINSTAL. 7. If you decide to continue the installation, the following messages are displayed: %VMSINSTAL-I-RELMOVED , The product's release notes have been moved to SYS$HELP. © Digital Equipment Corporation. 1990, 1991. All Rights Reserved. Installation procedure for: DEComni/VMS V1.1 All of the DEComni/VMS documentation is now provided in an electronic online fashion. That is, all documents are provided in both ASCII text and Postscript file formats as part of this software kit. Once moved to disk you may read them using any of the following methods: ASCII text formatted files - Using the editor of your choice. -------------------------- - Using the DCL command TYPE/PAGE. - Print the file(s). POSTSCRIPT formatted files - Display on a workstation with VIEW command -------------------------- - Print the file(s). * Press RETURN to continue: Accessing the DEComni/VMS Installation Guide -------------------------------------------- You now have the following options for accessing this product's installation guide. Note: The installation guide will always be copied to SYS$HELP as OMNI$INSTALLATION_GUIDE.TXT filename. Installing DEComni/VMS 3-3 1. Displayed on your screen now. 2. Print the installation guide. 3. Both 1 and 2. 4. None of the above. * Select option [1]: 4 8. If you select option 4 (as indicated above), the in- stallation guide is copied to SYS$HELP with the name OMNI$INSTALLATION_GUIDE.TXT. Note that you can also select display or print options. You are now being given an opportunity to exit this installation procedure. An ASCII text format of the installation guide will be copied to SYS$HELP even if you choose not to continue the installation at this point. * Do you wish to continue this installation [N]? Y 9. Next, you can exit the installation procedure. You may want to exit to read the online copy of this guide. The DEComni/VMS online documentation set consists of the following books: Title: Filename: DEComni/VMS Software Installation Guide OMNI$INSTALLATION_GUIDE DEComni/VMS Application Programmer's Guide OMNI$APPL_PROG_GUIDE DEComni/VMS Guide to Using OmniView OMNI$GUIDE_TO_OMNIVIEW DEComni/VMS Network Manager's Guide OMNI$NETWORK_MNGR_GUIDE You will now be given the option of having all of these online books copied to the destination of your choice. The amout of free disk space needed to transfer these files is approximately 11,000 blocks. NOTE: Both ASCII text and POSTSCRIPT versions of each book are provided, the filename extensions are .TXT for ASCII text and .PS for POSTSCRIPT. * Would you like the online documentation copied to disk [Y]? Y 10.You can now move all of the online documents to disk. If you do not want to trasfer the online documentation now, answer NO. The installation then continues. 3-4 Installing DEComni/VMS 11.If you answered Yes, the installation prompts you for the name of the directory where you want the online doc- umentation stored. The default destination directory is SYS$HELP. If you provide an alternate destination, it should be in the form of device:[directory] or an equiva- lent logical name. * Enter the destination [SYS$HELP]: SYS$HELP 12.Next, the installation displays the following information: Now checking available disk space... * Do you wish to continue with this installation [N]? Y Product: DECOMNI Producer: DEC Version: 1.1 Release Date: 4-APR-1991 13.Next, the installation displays the following authoriza- tion key prompt: * Does this product have an authorization key registered and loaded? Y DEComni/VMS can be installed but will not run unless its Product Authorization Key (PAK) is registered. Therefore, to answer Yes to the authorization key prompt, you must have registered and loaded the DEComni/VMS PAK. If you have not registered the DEComni/VMS PAK, answer No to this question. The installation procedure contin- ues even if you answer No, but you will not be allowed to run the Installation Verification Procedure (IVP) as part of the installation. To run the IVP in this case, regis- ter and load the DEComni/VMS PAK after the installation completes and then follow the IVP instructions found in Chapter 4. 14.Next, VMSINSTAL displays the following prompt: * Will you use DEC/MAP for device communications[Y]? Y You should answer Yes to the device communications prompt, if you are using DEComni/VMS with VAX DEC/MAP. Installing DEComni/VMS 3-5 15.Next, VMSINSTAL displays messages that indicate the system environment is being checked for prerequisite software, correct system parameters, and available disk space. The messages displayed are as follows: Now performing software prerequisite check . . . Now checking system parameters . . . Now checking for available disk space for software installation . . . If VMSINSTAL finds an error within your system environ- ment, an appropriate error message will be displayed on the screen. 16.Next, VMSINSTAL checks for process quota values and dis- plays the following message: Now checking process quota values . . . 17.Next, VMSINSTAL displays the following message that asks if you want files that are replaced by this installation purged: * Do you want to purge files replaced by this installation [YES]? Y If this is a first-time installation of DEComni/VMS, there will be no files to purge and you can answer No to the following question. If you answer Yes to the prompt, VMSINSTAL purges any files replaced by this installation. 18.Next, VMSINSTAL asks if you want to run the IVP as part of the DEComni/VMS installation procedure: * Do you want to run the IVP after the installation [YES]? Y If you choose not to run the IVP as part of the installa- tion, you should invoke it independently after the instal- lation has been completed. See Chapter 4 for details about the IVP and how to run the IVP independently. 19.At this point in the installation procedure, you must decide whether to continue the installation or abort it. Respond to the following question appropriately: 3-6 Installing DEComni/VMS This is your last chance to exit this installation procedure. After this point, the installation will go into an unattended mode of operation. * Do you wish to continue with this installation [Y]? Y If you answer NO, the installation will be aborted; if you answer Yes, the following message is displayed: ***************************************************************** This installation will now continue in an unattended mode of operation, which will not require any user interaction. Estimated time to completion from this point is 20 minutes. This estimate is based on a configuration consisting of a VAXstation 3600 and installation from TK50 medium. The current time is: 15:40.17 ***************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... Now building the database... Now configuring DEComni for use with DEC/MAP as the network provider.... %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECO MNI]. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation. 1990,1991. All Rights Reserved. Startup procedure for: DEComni/VMS V1.1 Now checking process privileges... Now checking for DEComni license... Now checking that prerequisite software has been started... MDS Application Name OMNI$IVP_SENDER At 28-MAR-1991 15:51:28.66 Successfully registered in local directory Installing DEComni/VMS 3-7 MDS Application Name OMNI$IVP_REC At 28-MAR-1991 15:51:32.73 Successfully registered in local directory Address OMNI$IVP_R_P.OMNI$IVP_R_S.OMNI$IVP_R_T. At 28-MAR-1991 15:51:36.83 Successfully registered SYNTAX TRANSFORMATION MMS-PCI At 28-MAR-1991 15:51:40.06 Successfully registered Now installing the DEComni sharable images... Now creating the OMNI$CP process... %RUN-S-PROC_ID, identification of created process is 20200184 %OMNI-S-STARTUP, DEComni startup successfully completed +-----------------------------------------------+ | | | The DEComni IVP will now be invoked.... | | | +-----------------------------------------------+ © Digital Equipment Corporation. 1990,1991. All Rights Reserved. Installation Verification Procedure for: DEComni/VMS V1.1 Now checking process quota values... Now creating IVP VMD's... Now running the DEComni IVP sender application... The DEComni IVP sender application has run successfully. %OMNI-S-IVP, the DEComni IVP has successfully completed Installation of OMNI V1.1 completed at 15:52 VMSINSTAL procedure done at 15:52 $ $ LO SYSTEM logged out at 28-MAR-1991 15:53:55.66 3-8 Installing DEComni/VMS 20.The DEComni installation is now complete. NOTE For postinstallation information, please see Chapter 4. Specifically, if the DEComni IVP fails, see the section in Chapter 4 entitled "Resolving IVP Failures". Installing DEComni/VMS 3-9 Chapter 4 Postinstallation Considerations ________________________________________________________________ This chapter explains how to start, verify, and stop DEComni /VMS. Also, the chapter provides information on other postin- stallation considerations. ____________________________________________________________ 4.1 Starting DEComni/VMS You must have the following privileges enabled before you invoke the DEComni/VMS startup command procedure: DETACH PRMMBX SYSNAM CMKRNL SYSGBL PRMGBL WORLD GROUP You can start DEComni/VMS by typing the following command: $ @SYS$STARTUP:OMNI$STARTUP Also, you can enter the above startup command in your system startup so that DEComni/VMS will start automatically each time the system is booted. For details about system startup, see the "Guide to Setting Up a VMS System" section of the VMS System Management Subkit. Postinstallation Considerations 4-1 NOTE Remember that the VAX DEC/MAP startup command pro- cedure (SYS$STARTUP:MAP$STARTUP.COM) and the VAX Rdb/VMS (Run-time option) startup command procedure (SYS$STARTUP:RMONSTART.COM) must be running before you invoke the DEComni/VMS startup command procedure (SYS$STARTUP:OMNI$STARTUP.COM). ____________________________________________________________ 4.2 Running the Installation Verification Procedure If you did not run the IVP as part of the DEComni/VMS in- stallation, you should run it independently after you have installed the product and started it. You must have the following privileges enabled before you invoke the DEComni/VMS IVP: NETMBX PRMMBX SYSLCK WORLD GROUP To run the IVP, enter: $ @SYS$TEST:OMNI$IVP.COM NOTE Before you run the IVP, DEComni/VMS should be started. See Section 4.1. The DEComni/VMS IVP verifies that the DEComni/VMS software system is correctly installed. As the IVP progresses, infor- mation messages are displayed. If the IVP fails, a message is displayed indicating the reason for the failure. You should correct the problem and reexecute the IVP. When the DEComni /VMS IVP executes successfully, the DEComni/VMS software system is ready for use. 4-2 Postinstallation Considerations ____________________________________________________________ 4.3 Resolving IVP Failures The DEComni IVP can fail for various reasons. Table 4-1 indicates possible causes for IVP failure and ways to resolve the IVP problem. Table 4-1: Resolving IVP Failures _____________________________________________________________ Possible_Cause___Resolution__________________________________ VOTS account Run the AUTHORIZE utility and modify the set to DISUSER DISUSER flag. in AUTHORIZE VOTS account Run MAPCL and check the TRANSPORT password. PASSWORD does Compare the password in AUTHORIZE and make not match in corrections in AUTHORIZE. VAX DEC/MAP and AUTHORIZE VOTS account Run the AUTHORIZE utility and compare the quotas not values with those found in the Account sufficient Quota table in this guide. Make needed corrections. VAX Rdb was not Check for the existence of the "RDMS_ running. MONITOR" process. Start VAX Rdb, if the process is not found. VAX DEC/MAP was Check for the existence of the "LES$ACP" not running. and "OSIF$OSAKSERVER" processes. Start VAX _________________DEC/MAP,_if_the_processes_are_notfound._____ NOTE Additional inofrmation on why the IVP may have failed can be found in a log file in the VOTS account default directory named OMNI$START_RCVR.LOG. Postinstallation Considerations 4-3 ____________________________________________________________ 4.4 User Account Quotas and Privileges Each DEComni/VMS user account should have the following account quotas: Table 4-2: Account Quotas _____________________________________________________________ Attribute_____Minimum_Value__________________________________ ASTlm 24 BIOlm 18 BYTlm 20480 DIOlm 18 ENQlm 2000 FILlm 50 Pgflquo 20000 Prclm 1+ WSdef 256 WSextent 3072 WSquo_________768____________________________________________ ____________________________________________________________ 4.5 Stopping DEComni/VMS You must have the following privileges enabled before you invoke the DEComni/VMS stop procedure: DETACH PRMMBX SYSNAM CMKRNL SYSGBL 4-4 Postinstallation Considerations PRMGBL WORLD GROUP To manually shut down DEComni/VMS, enter: $ @SYS$MANAGER:OMNI$STOP.COM If you want DEComni/VMS to shut down automatically each time your system is brought down, include this in the SYS$MANAGER:SYSHUTDWN.COM file (the site-specific shutdown file): NOTE Be sure that OMNI$STOP.COM is executed before MAP$STOP.COM and before the RMONSTOP.COM in the system site shutdown file, SYS$MANAGER:SYSHUTDWN.COM. ____________________________________________________________ 4.6 DEComni Example Programs As part of the DEComni installation, a directory is created that contains DEComni example programs; and as part of the DEComni startup command procedure, a system-wide logical name, OMNI$EXAMPLES, is created. It is recommended that you review these program examples before you design and implement applications that will inter- face with DEComni. Postinstallation Considerations 4-5 ____________________________________________________________ 4.7 The DEComni Database and Rdb DEComni/VMS utilizes a VAX Rdb/VMS database. It is recom- mended that you periodically backup this database. The DEComni/VMS database files are: SYS$LIBRARY:OMNI$DATABASE.RDB SYS$LIBRARY:OMNI$DATABASE.SNP See the VAX Rdb/VMS RDO and RMU Reference Manual for details on how to backup the Rdb database. Also, if you upgrade your version of VAX Rdb/VMS, you must verify that your existing DEComni/VMS database is com- patible with the VAX Rdb/VMS upgrade. See the VAX Rdb/VMS Installation Guide for details. ____________________________________________________________ 4.8 Determining and Reporting Problems If an error occurs while you are using DEComni/VMS, you should submit a Software Performance Report (SPR). When you submit an SPR, follow these steps: o Describe as accurately as possible the state of the system and the circumstance in which the problem occurred. o Illustrate the problem with specific examples. o State the problem concisely. o Report only one problem per SPR. This ensures a quick response. o Notify your Software Services representative, who will submit your SPR. Experience shows that many SPRs do not contain sufficient information to enable duplication or identification of the problem. Complete and concise information will help Digital resolve your software problems. If you find an error in the DEComni/VMS documentation, you should fill out and submit the Reader's Comments form that is in the back of the manual in which the error was found. Specify the title of the manual and include the section and page number where a description of the error appears. 4-6 Postinstallation Considerations Appendix A DEComni/VMS Files Added or Modified on the System ________________________________________________________________ This appendix lists the DEComni/VMS files that are added or modified by the installation procedure. ____________________________________________________________ A.1 Files Added The following files have been added: SYS$COMMON:[SYS$STARTUP]OMNI$STARTUP.COM SYS$COMMON:[SYSEXE]OMNI$CL.EXE SYS$COMMON:[SYSEXE]OMNI$CP.EXE SYS$COMMON:[SYSEXE]OMNI$ODF.EXE SYS$COMMON:[SYSEXE]OMNI$VIEW.EXE SYS$COMMON:[SYSHLP]OMNI$APPL_PROG_GUIDE.PS SYS$COMMON:[SYSHLP]OMNI$APPL_PROG_GUIDE.TXT SYS$COMMON:[SYSHLP]OMNI$CL.HLB SYS$COMMON:[SYSHLP]OMNI$GUIDE_TO_OMNIVIEW.PS SYS$COMMON:[SYSHLP]OMNI$GUIDE_TO_OMNIVIEW.TXT SYS$COMMON:[SYSHLP]OMNI$INSTALLATION_GUIDE.PS SYS$COMMON:[SYSHLP]OMNI$INSTALLATION_GUIDE.TXT SYS$COMMON:[SYSHLP]OMNI$NETWORK_MNGR_GUIDE.PS SYS$COMMON:[SYSHLP]OMNI$NETWORK_MNGR_GUIDE.TXT SYS$COMMON:[SYSHLP]OMNI$ODF_HELP.HLB SYS$COMMON:[SYSHLP]OMNI$VIEW.HLB SYS$COMMON:[SYSHLP]OMNI011.RELEASE_NOTES SYS$COMMON:[SYSHLP.EXAMPLES]DECOMNI.DIR SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$FORTRAN_READ.FOR SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$FORTRAN_READ_ RSP.FOR SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$LOAD_DEF_VAR.C DEComni/VMS Files Added or Modified on the System A-1 SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$MMSI_GET_DOM_ ATTR_EXAMPLE.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$MMSI_GET_PI_ATTR_ EXAMPLE.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$MMSI_IDENTIFY_ EXAMPLE.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$MMSI_STATUS_ EXAMPLE.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$ODF-VAR.TXT SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$ODF_EXAMPLE.TXT SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$READ_DOM_ATTR_ EXAMPLE.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$READ_EXAMPLE.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$RUN_TIME_PI_DOM.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$RUN_TIME_VAR.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$RUN_TIME_VMD.C SYS$COMMON:[SYSHLP.EXAMPLES.DECOMNI]OMNI$WRITE_EXAMPLE.C SYS$COMMON:[SYSLIB]OMNI$CODES.ADA SYS$COMMON:[SYSLIB]OMNI$CODES.BAS SYS$COMMON:[SYSLIB]OMNI$CODES.FOR SYS$COMMON:[SYSLIB]OMNI$CODES.H SYS$COMMON:[SYSLIB]OMNI$CODES.MAR SYS$COMMON:[SYSLIB]OMNI$CODES.PAS SYS$COMMON:[SYSLIB]OMNI$CODES.PLI SYS$COMMON:[SYSLIB]OMNI$CODES.R32 SYS$COMMON:[SYSLIB]OMNI$DATABASE.RDB SYS$COMMON:[SYSLIB]OMNI$DATABASE.SNP SYS$COMMON:[SYSLIB]OMNI$DEFS.ADA SYS$COMMON:[SYSLIB]OMNI$DEFS.BAS SYS$COMMON:[SYSLIB]OMNI$DEFS.FOR SYS$COMMON:[SYSLIB]OMNI$DEFS.H SYS$COMMON:[SYSLIB]OMNI$DEFS.MAR SYS$COMMON:[SYSLIB]OMNI$DEFS.PAS SYS$COMMON:[SYSLIB]OMNI$DEFS.PLI SYS$COMMON:[SYSLIB]OMNI$DEFS.R32 SYS$COMMON:[SYSLIB]OMNI$MMSI_CODES.H SYS$COMMON:[SYSLIB]OMNI$MMSI_DEFS.H SYS$COMMON:[SYSLIB]OMNI$OBJECTS.OLB SYS$COMMON:[SYSLIB]OMNI$VAXCSHR.EXE SYS$COMMON:[SYSLIB]OMNI$VAXVMSSHR.EXE SYS$COMMON:[SYSLIB]OMNI_VIEW.UID SYS$COMMON:[SYSMGR]OMNI$STOP.COM SYS$COMMON:[SYSMSG]OMNI$CODES_MSG.EXE SYS$COMMON:[SYSTEST]OMNI$IVP.COM A-2 DEComni/VMS Files Added or Modified on the System SYS$COMMON:[SYSTEST]OMNI$IVP_RCVR.EXE SYS$COMMON:[SYSTEST]OMNI$IVP_SNDR.EXE SYS$COMMON:[SYSTEST]OMNI$START_RCVR.COM SYS$COMMON:[SYS$STARTUP]OMNI$STARTUP.COM ____________________________________________________________ A.2 Files Modified No files have been modified. DEComni/VMS Files Added or Modified on the System A-3 Appendix B Installation Example ________________________________________________________________ This appendix contains a sample installation session. ____________________________________________________________ B.1 Installation Session Welcome to VAX/VMS V5.4-2 Username: SYSTEM Password: Welcome to VAX/VMS version V5.4-2 on node SAFRON Last interactive login on Thursday, 28-MAR-1991 14:58 Last non-interactive login on Thursday, 28-MAR-1991 15:36 $ $ @SYS$UPDATE:VMSINSTAL OMNI011 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.4-2 It is 28-MAR-1991 at 15:38. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Y The following products will be processed: OMNI V1.1 Beginning installation of OMNI V1.1 at 15:38 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Installation Example B-1 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]: 4 * Do you want to continue the installation [NO]? Y %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. © Digital Equipment Corporation. 1990,1991. All Rights Reserved. Installation procedure for DEComni/VMS V1.1 All of the DEComni/VMS documentation is now provided in an electronic online fashion. That is, all documents are provided in both ASCII text and Postscript file formats as part of this software kit. Once moved to disk you may read them using any of the following methods: ASCII text formatted files - Using the editor of your choice. -------------------------- - Using the DCL command TYPE/PAGE. - Print the file(s). POSTSCRIPT formatted files - Display on a workstation with VIEW command -------------------------- - Print the file(s). * Press RETURN to continue: Accessing the DEComni/VMS Installation Guide -------------------------------------------- You now have the following options for accessing this product's installation guide. Note: The installation guide will always be copied to SYS$HELP as OMNI$INSTALLATION_GUIDE.TXT filename. 1. Displayed on your screen now. 2. Print the installation guide. 3. Both 1 and 2. 4. None of the above. * Select option [1]: 4 B-2 Installation Example Your are now being given an opportunity to exit this installation procedure. An ASCII text format of the installation guide will be copied to SYS$HELP even if you choose not to continue the instal- lation at this point. * Do you wish to continue this installation [N]? Y The ASCII text format of the DEComni/VMS Installation Guide will be copied to the following: DIRECTORY: SYS$HELP FILENAME: OMNI$INSTALLATION_GUIDE.TXT * Press RETURN to continue: The DEComni/VMS online documentation set consists of the following books: Title: Filename: DEComni/VMS Software Installation Guide OMNI$INSTALLATION_ GUIDE DEComni/VMS Application Programmer's Guide OMNI$APPL_PROG_ GUIDE DEComni/VMS Guide to Using OmniView OMNI$GUIDE_TO_ OMNIVIEW DEComni/VMS Network Manager's Guide OMNI$NETWORK_MNGR_ GUIDE You will now be given the option of having all of these online books copied to the destination of your choice. The amout of free disk space needed to transfer these files is approximately 11000 blocks. NOTE: Both ASCII text and POSTSCRIPT versions of each book are provided, the filename extensions are .TXT for ASCII text and .PS for POSTSCRIPT. * Would you like the online documentation copied to disk [Y]? Y * Enter the destination [SYS$HELP]: SYS$HELP Now checking available disk space... * Do you wish to continue with this installation [N]? Y Product: DECOMNI Producer: DEC Version: 1.1 Release Date: 4-APR-1991 Installation Example B-3 * Does this product have an authorization key registered and loaded? Y * Will you use DEC/MAP for device communications [Y]? Y Now performing software prerequisite check... Now checking system parameters... Now checking available disk space for software installation... Now checking process quota values... * Do you want to purge files replaced by this installation [YES]? Y * Do you want to run the IVP after the installation [YES]? Y This is your last chance to exit this installation procedure. After this point, the installation will go into an unattended mode of operation. * Do you wish to continue with this installation [Y]? Y ***************************************************************** This installation will now continue in an unattended mode of operation, which will not require any user interaction. Estimated time to completion from this point is 20 minutes. This estimate is based on a configuration consisting of a VAXstation 3600 and installation from TK50 medium. The current time is: 15:40.17 ***************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... Now building the database... Now configuring DEComni for use with DEC/MAP as the network provider.... %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECO MNI]. %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... © Digital Equipment Corporation. 1990,1991. All Rights Reserved. Startup procedure for: DEComni/VMS V1.1 Now checking process privileges... B-4 Installation Example Now checking for DEComni license... Now checking that prerequisite software has been started... MDS Application Name OMNI$IVP_SENDER At 28-MAR-1991 15:51:28.66 Successfully registered in local directory MDS Application Name OMNI$IVP_REC At 28-MAR-1991 15:51:32.73 Successfully registered in local directory Address OMNI$IVP_R_P.OMNI$IVP_R_S.OMNI$IVP_R_T. At 28-MAR-1991 15:51:36.83 Successfully registered SYNTAX TRANSFORMATION MMS-PCI At 28-MAR-1991 15:51:40.06 Successfully registered Now installing the DEComni sharable images... Now creating the OMNI$CP process... %RUN-S-PROC_ID, identification of created process is 20200184 %OMNI-S-STARTUP, DEComni startup successfully completed +-----------------------------------------------+ | | | The DEComni IVP will now be invoked.... | | | +-----------------------------------------------+ © Digital Equipment Corporation. 1990,1991. All Rights Reserved. Installation Verification Procedure for: DEComni/VMS V1.1 Now checking process quota values... Now creating IVP VMD's... Now running the DEComni IVP sender application... The DEComni IVP sender application has run successfully. Installation Example B-5 %OMNI-S-IVP, the DEComni IVP has successfully completed Installation of OMNI V1.1 completed at 15:52 VMSINSTAL procedure done at 15:52 $ $ LO SYSTEM logged out at 28-MAR-1991 15:53:55.66 B-6 Installation Example Appendix C Products on Your System ________________________________________________________________ This appendix explains how you determine what products are running on your system. To determine if VAX Rdb/VMS, VAX DEC/MAP, or DEComni/VMS are running on your system, you can check specific processes on your system. Table C-1 lists the processes you should see for each layered product. Table C-1: Products and Processes _____________________________________________________________ Product_________Process_Name(s)______________________________ VAX Rdb/VMS RDMS_MONITOR VAX DEC/MAP LES$ACP OSIF$OSAKSERVER DEComni/VMS_____OMNI$CP______________________________________ Products on Your System C-1 Index ________________________________________________________________ A___________________________ Installation (Cont.) AUTHORIZE, 2-7 required privileges and AUTOGEN disk space, 2-3 using, 2-5 required process quotas, C 2-6 ____________________________ steps to follow, 3-1 Communication device Installation Verification requirements, 2-1 Procedure (IVP), 4-2 D___________________________ K___________________________ DECnet, 2-2 Kit contents, 1-2 DEComni example programs, 4-5 L___________________________ DEComni/VMS License Management Facility kit contents, 1-2 (LMF), 2-8 product description, 1-1 reporting problems, 4-6 N Device name, 3-2 ____________________________ I NETCONFIG.COM, 2-2 ____________________________ P Installation ____________________________ files added at, A-1 Prerequisite software, 2-2 modifying quotas, 2-7 Product Authorization Key preparation for, 2-1 (PAK), 2-8 required parameters, 2-4 Products on system, C-1 Index-1 R___________________________ Release notes U___________________________ DEComni/VMS, 2-8 User account quotas and S privileges, 4-2 ____________________________ Sample installation session, V___________________________ B-1 VMS classes, 2-3 Starting DEComni, 4-1 VMSINSTAL STARTNET.COM, 2-2 purpose, 1-7 Stopping DEComni/VMS, 4-4 VMS version checking the, 2-3 Index-2