____________________________________________________ DEC Commserver for OpenVMS Installation Manual Order Number: AA-PE92C-TE April 1995 This manual describes the DEC Commserver for OpenVMS installation procedure. Revision/Update Information: This is a new manual. Operating System and Version OpenVMS Version 5.5 or 6.x Software Version: Version 3.x digital equipment corporation merrimack, massachusetts __________________________________________________________ April 1995 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 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 Digital Equipment Corporation 1995. All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, MicroVAX, OpenVMS, VAX, VAX C, VAXcluster, VAX DOCUMENT, VAXstation, and the DIGITAL logo. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents 1 Preparing to Install DEC Commserver for OpenVMS 1.1 Required Operating System Components.......... 1-1 1.2 License Registration.......................... 1-2 1.3 Installation Procedure Requirements........... 1-3 1.3.1 Privileges and Disk Space................. 1-3 1.3.2 System Parameters......................... 1-4 1.3.2.1 Checking System Parameter Values........ 1-6 1.3.2.2 Setting the MAXBUF Dynamic System Parameter............................... 1-6 1.3.2.3 Calculating the Values for GBLPAGES and GBLSECTIONS............................. 1-7 1.3.2.4 Changing System Parameter Values with AUTOGEN................................. 1-8 1.3.3 Process Account Quotas.................... 1-9 1.3.4 VMSINSTAL Requirements.................... 1-10 1.3.5 Backing Up Your System Disk............... 1-10 1.3.6 DEC Commserver for OpenVMS Requirements... 1-11 1.3.6.1 Determining the Ethernet Controller..... 1-11 1.3.6.2 Running DECnet With DEC Commserver for OpenVMS................................. 1-12 1.3.6.3 VAXcluster Considerations............... 1-12 1.4 Installation Kit Overview..................... 1-12 2 Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure.................... 2-1 2.2 Error Recovery................................ 2-9 iii 3 After Installing DEC Commserver for OpenVMS 3.1 Configuring a Host for Downline Loading....... 3-1 3.1.1 Recognizing Boot Requests................. 3-2 3.1.2 Adding the Server to the Host's Network Node Database............................. 3-3 3.2 Running the Installation Verification Procedure Separately.......................... 3-5 3.3 Editing the System Files...................... 3-5 3.4 User Account Requirements..................... 3-6 3.4.1 Privileges................................ 3-6 3.4.2 User Account Quotas....................... 3-6 3.5 Installing DEC Commserver for OpenVMS on a VAXcluster.................................... 3-7 3.6 Enhancing Performance......................... 3-8 3.6.1 OpenVMS Version 5.5....................... 3-8 3.6.2 OpenVMS VAX Version 6.x................... 3-9 3.7 Determining and Reporting Problems............ 3-9 A Sample Installation B Files and Logical Names Installed on Your System B.1 File Names.................................... B-1 B.2 Logical Names................................. B-2 C Startup Command File D IVP Command File Tables 1-1 Needed Class Support...................... 1-1 1-2 Disk Space Requirements................... 1-4 1-3 Required Minimum System Parameter Values.................................... 1-4 1-4 Process Account Quotas for the Installing Account................................... 1-9 3-1 Line and Circuit Mnemonics................ 3-2 iv 1 _________________________________________________________________ Preparing to Install DEC Commserver for OpenVMS This chapter discusses the preparations and requirements necessary for installing DEC Commserver for OpenVMS. This manual applies to Version 2.x of DEC Commserver for OpenVMS and all subsequent maintenance releases up to the next major product release. Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. DEC Commserver for OpenVMS provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 2.1. 1.1 Required Operating System Components To use DEC Commserver for OpenVMS, your system should be running OpenVMS Version 5.5 or 6.x that includes the following classes: Table_1-1_Needed_Class_Support_____________________________ Class_____________________Required_Files___________________ Network Support Remote Task Loading Programming Support ALL System Programming SYS.STB Support (continued on next page) Preparing to Install DEC Commserver for OpenVMS 1-1 Preparing to Install DEC Commserver for OpenVMS 1.1 Required Operating System Components Table_1-1_(Cont.)_Needed_Class_Support_____________________ Class_____________________Required_Files___________________ Utilities_________________OpenVMS_HELP_LIBRARY_____________ For a complete list of the required classes, see the Software Support Addendum (SSA), which comes with the Software Product Description (SPD). 1.2 License Registration You must register and load your license for DEC Commserver for OpenVMS before you start the installation in order to run the Installation Verification Procedure (IVP) and use the software. The information you need is in the Product Authorization Key (PAK) shipped with Commserver hardware. The PAK is a paper certificate that contains data about your license. Additional PAKs may be ordered for use on other host systems. Refer to the Ordering Information section of SPD 33.21.xx to order additional software PAKs. If your host system will load communications software into the device(s) installed on a server you must register and load your PAKs for these software packages. Refer to the Ordering Information section of SPD 33.21.xx on how to order these PAKs. To register the license, first log in to a privileged account such as the system manager's account, SYSTEM. Then choose one of the following procedures to perform the registration. The second method is faster for experienced users. - Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When prompted for information, respond with data from your Product Authorization Key (PAK). OR - Issue the DCL commands LICENSE REGISTER and LICENSE LOAD with the appropriate qualifiers that correspond to information on the PAK. 1-2 Preparing to Install DEC Commserver for OpenVMS Preparing to Install DEC Commserver for OpenVMS 1.2 License Registration To verify what licenses are installed on the system, use one of the following commands: $ SHOW LICENSE * or $ LICENSE LIST * For complete information on using LMF, see the VMS License Management Utility Manual. 1.3 Installation Procedure Requirements This section and those that follow discuss various requirements for installing DEC Commserver for OpenVMS. The installation takes approximately 5 to 75 minutes, depending on your type of media, your system configuration, and the software options selected. 1.3.1 Privileges and Disk Space To install DEC Commserver for OpenVMS, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o WORLD o SYSPRV Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. DEC Commserver for OpenVMS's requirements for free disk storage space are different during installation and after installation. Table 1-2 summarizes the storage requirements. Preparing to Install DEC Commserver for OpenVMS 1-3 Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements Table_1-2_Disk_Space_Requirements__________________________ Blocks During Blocks After Kit_______________Installation__________Installation_______ DEC Commserver 18,000 17,000 for OpenVMS software [1] [1]_These_counts_refer_to_the_disk_space_required_on_the___ system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options selected. ___________________________________________________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1.3.2 System Parameters Installing DEC Commserver for OpenVMS requires certain system parameter settings. Table 1-3 lists the minimum required system parameter values for the installation. Table_1-3_Required_Minimum_System_Parameter_Values_________ System_Parameter___________Minimum_Value___________________ GBLPAGES [1] 546 GBLSECTIONS [1] 5 MAXBUF [2] 6000 [1]_The_values_listed_for_these_system_parameters_represent the number of free global pages, global sections, Paged Pool and Non-Paged Pool required for the installation, not the total number you need to run your system and other software. [2] These dynamic system parameters must be set permanently to a value equal to or greater than the value listed. Do not lower this value after the installation. (continued on next page) 1-4 Preparing to Install DEC Commserver for OpenVMS Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements Table_1-3_(Cont.)_Required_Minimum_System_Parameter_Values_ System_Parameter___________Minimum_Value___________________ NPAGEDYN [1] 58000 + (37876 * S) [3] + (6850 * D) [4] PAGEDYN [1] 1100 + (176 * S) [3] + (48 * D) [4] [1]_The_values_listed_for_these_system_parameters_represent the number of free global pages, global sections, Paged Pool and Non-Paged Pool required for the installation, not the total number you need to run your system and other software. [3] S is the number of Servers that will be configured on the host system. [4] D is the number of Devices that will be configured on the host system. ___________________________________________________________ ________________________ NOTE ________________________ See Section 3.6 for other NPAGEDYN considerations. ______________________________________________________ Preparing to Install DEC Commserver for OpenVMS 1-5 Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements The following sections show you how to: o Check system parameter values. o Calculate values for the GBLPAGES and GBLSECTIONS system parameters. o Change parameter values with the OpenVMS AUTOGEN command procedure. o Set dynamic parameters (such as MAXBUF) with the OpenVMS System Generation Utility (SYSGEN). 1.3.2.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility (SYSGEN): $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values in the current column should equal or exceed the value of each system parameter listed in Table 1-3. The following example displays the value for the MAXBUF system parameter: SYSGEN> SHOW MAXBUF After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 1.3.2.2 Setting the MAXBUF Dynamic System Parameter The value of the OpenVMS SYSGEN parameter MAXBUF must be at least 16 bytes greater than the size of the largest transfer to be made to or from a device on a Commserver with a 2048 byte minimum. This allows the driver to allocate the necessary buffer from non-paged pool. The MAXBUF parameter determines the maximum size of a buffered I/O transfer. Change the setting with the following series of commands: 1-6 Preparing to Install DEC Commserver for OpenVMS Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SET MAXBUF 6000 SYSGEN> WRITE ACTIVE SYSGEN> WRITE CURRENT SYSGEN> EXIT ________________________ Note ________________________ When using BSCTRAN, MAXBUF must be set to no lower than 5004 to avoid an "Exceed Quota" error. ______________________________________________________ You can use these commands to set any dynamic parameter. Dynamic parameters changed with the System Generation Utility's WRITE ACTIVE command become active immediately, without any need to reboot your system. With the WRITE CURRENT command the MAXBUF setting is saved permanently for when you reboot the system. 1.3.2.3 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run DEC Commserver for OpenVMS, you must have sufficient free global pages and global sections. You must first find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the GBLPAGES and GBLSECTIONS system parameters. You can use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the values in Table 1-3, you do not need to increase the values for these parameters. If the value of free global pages or global sections is less than the value in Table 1-3, you must increase the system parameter setting. Preparing to Install DEC Commserver for OpenVMS 1-7 Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements Section 1.3.2.4 describes the procedures for increasing these values using AUTOGEN. 1.3.2.4 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example: MAXBUF = 6000 You can also modify incremental parameters in the MODPARAMS.DAT file. For example, after calculating the total (minimum) number of GBLPAGES required (FREE_GBLPAGES must be greater than 546), edit the MODPARAMS.DAT file and insert the following line: MIN_GBLPAGES = 15000 where "15000" represents the calculated minimum number of GBLPAGES required. After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. 1-8 Preparing to Install DEC Commserver for OpenVMS Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the OpenVMS System Management Subkit. 1.3.3 Process Account Quotas The account you use to install DEC Commserver for OpenVMS must have sufficient quotas to enable you to perform the installation. Table 1-4 summarizes the process quotas required for the installation account. Table_1-4_Process_Account_Quotas_for_the_Installing_Account Account_Quota____Value_____________________________________ ASTLM 24 BIOLM 18 BYTLM 32768 DIOLM 18 ENQLM 200 FILLM____________100_______________________________________ User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH Preparing to Install DEC Commserver for OpenVMS 1-9 Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=100 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the OpenVMS System Management Subkit. 1.3.4 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you have set your default device and directory to SYS$UPDATE o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o Whether any users are logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press RETURN. Then correct the problem and restart the installation. 1.3.5 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Management Subkit. 1-10 Preparing to Install DEC Commserver for OpenVMS Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements 1.3.6 DEC Commserver for OpenVMS Requirements 1.3.6.1 Determining the Ethernet Controller Before installing the DEC Commserver for OpenVMS software you must determine the Ethernet controller on your host that will be used by the DEC Commserver for OpenVMS software to communicate with servers in the Local Area Network (LAN). If you are not sure as to which device on the system is an Ethernet controller you can perform the following to determine the device class and type: $ SHOW DEVICE 1 $ WRITE SYS$OUTPUT F$GETDVI("dev","DEVCLASS") 2 $ WRITE SYS$OUTPUT F$GETDVI("dev","DEVTYPE") 3 1 Display a list of devices configured on the system. 2 Determine the Device Class of the device named dev. The device class must be equal to DC$_SCOM. See the F$GETDVI lexical function section of the OpenVMS DCL Dictionary: Part 1 reference manual. 3 Determine the Device Type of the device named dev. The device type must be equal to an Ethernet controller. See the F$GETDVI lexical function section of the OpenVMS DCL Dictionary: Part 1 reference manual for the equivalent device type for the value returned. Once the device type is known you can determine if the device is an Ethernet controller by referring to the Supported Hardware for OpenVMS section of the OpenVMS Operating System SPD 25.01.xx for your system. The following is an example of a device named ETA0 on a VAX 8550. $ WRITE SYS$OUTPUT F$GETDVI("ETA0","DEVCLASS") 32 $ WRITE SYS$OUTPUT F$GETDVI("ETA0","DEVTYPE") 29 Preparing to Install DEC Commserver for OpenVMS 1-11 Preparing to Install DEC Commserver for OpenVMS 1.3 Installation Procedure Requirements The DCL Dictionary states that the device class for the ETA0 device is DC$_SCOM, and the device type is ET_DEBNA. The OpenVMS SPD for a VAX 85xx type system states that a DEBNA is a supported Ethernet controller for this type of system. 1.3.6.2 Running DECnet With DEC Commserver for OpenVMS If DECnet is to be run on the same Ethernet controller as the DEC Commserver for OpenVMS software, then DECnet must be started before the DEC Commserver for OpenVMS software is started. Otherwise DECnet is not able to start correctly. To determine if DECnet is running perform the following: $ SHOW NETWORK 1.3.6.3 VAXcluster Considerations You can install the DEC Commserver for OpenVMS software on a VAXcluster. In a VAXcluster with a common system disk, you can execute the installation procedure on a single member of the cluster. After the installation is completed, each VAX processor can share the DEC Commserver for OpenVMS software. You must check the number of global sections and global pages, as well as the MAXBUF, NPAGEDYN, and PAGEDYN parameters on each node in the VAXcluster where you plan to install DEC Commserver for OpenVMS software. See Chapter 3 for details about VAXcluster postinstallation instructions. 1.4 Installation Kit Overview The installation kit for DEC Commserver for OpenVMS is designed to support installation of the product of any of the following environments: OpenVMS VAX Version 5.5 OpenVMS VAX Version 6.x OpenVMS AXP Version 6.x 1-12 Preparing to Install DEC Commserver for OpenVMS Preparing to Install DEC Commserver for OpenVMS 1.4 Installation Kit Overview The installation procedure automatically determines the system type during kit installation and installs the appropriate files for that environment. The user interface to the procedure is identical for all environments. The kit consists of 5 saveset files labeled A to E. - Saveset A contains the installation scripts - Saveset B contains files specific to OpenVMS VAX Version 5.5 - Saveset C contains files specific to OpenVMS VAX Version 6.x - Saveset D contains files specific to OpenVMS AXP Version 6.x - Saveset E contains 3222 protocol specific files ________________________ Note ________________________ See the DEC Commserver for OpenVMS Software Product Description and the System Support Addendum to determine which OpenVMS hosts are supported with your version of software. ______________________________________________________ Preparing to Install DEC Commserver for OpenVMS 1-13 2 _________________________________________________________________ Installing DEC Commserver for OpenVMS This chapter explains how to install DEC Commserver for OpenVMS. Section 2.1 contains a step-by-step description of the installation procedure. The last section covers postinstallation considerations. 2.1 The Installation Procedure The DEC Commserver for OpenVMS installation procedure consists of a series of questions and informational messages. See Appendix A for a sample installation. 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 exits. You can then start the installation again. 1. Invoke VMSINSTAL. @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The following list defines the elements of the VMSINSTAL command procedure: saveset-name The installation name for the component. For DEC Commserver for OpenVMS, use the following installation name: COMMSERVER0nn Installing DEC Commserver for OpenVMS 2-1 Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure device-name The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. Note that there are several other options you can select when you invoke VMSINSTAL. o Auto_answer option (A): Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). o Get save set option (G): Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L): Logs all activity to the terminal during installation. o Alternate root option (R): Lets you install the product to a system root other than that of the running system. See the OpenVMS documentation on software installation in the OpenVMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A,N). 2-2 Installing DEC Commserver for OpenVMS Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure The following example invokes VMSINSTAL to install DEC Commserver for OpenVMS from tape drive MTA0: and shows the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL COMMSERVER0nn MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.5 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. If you do not supply the product name, device name, or options, VMSINSTAL prompts you for this information later in the installation procedure. 2. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? YES VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 3. Mount the media. You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, COMSRV MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: COMMSERVER V0nn Beginning installation of COMMSERVER V0nn at hh:mm %VMSINSTAL-I-RESTORE, Restoring product saveset A... If you respond YES to indicate that you are ready, Installing DEC Commserver for OpenVMS 2-3 Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure VMSINSTAL displays a message that the media containing DEC Commserver for OpenVMS has been mounted on the specified device and that the installation has begun. If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press CTRL/Y. 4. Select a release notes option. If you specified OPTIONS N when you started the installation, VMSINSTAL asks a question on release notes. Release Notes Options: (1) Display release notes (2) Print release notes (3) Both 1 and 2 (4) None of the above * Select Option [2]: 1 If you select option 1, VMSINSTAL displays the release notes immediately on your screen. If you select option 2 or 3, VMSINSTAL prompts you for a queue name. * Queue name [SYS$PRINT]: You can type a queue name, or press the RETURN key to indicate the default output print device, SYS$PRINT. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press RETURN. In either case, the release notes are copied to a file in the SYS$HELP directory: SYS$HELP:COMMSERVER0nn.RELEASE_NOTES 2-4 Installing DEC Commserver for OpenVMS Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure After the installation, you can enter the following command to review the release notes through the Help facility: $ HELP COMSERVER RELEASE_NOTES ________________________ Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete release notes for previous versions of DEC Commserver for OpenVMS. ______________________________________________________ 5. Purge files. * Do you want to purge files replaced by this installation [YES]?YES You have the option to purge files from previous versions of DEC Commserver for OpenVMS that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. Installing DEC Commserver for OpenVMS 2-5 Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure 6. Layered Product The installation procedure asks the following: * Do you want to install the Layered Product [YES]? YES The Commserver software, the client software, and the server image are installed on the host if you select YES. If you select NO, the client software and server images are not installed. The procedure will continue and ask if you want to install any of the protocols. This question along with the questions about the protocols allows you to select only the components you need to install now. Optionally, any missing components can be installed later by running VMSINSTAL and selecting the desired components. For example, if the Commserver client software and 1622 Protocols are already installed on your system and later you want to add the 3222 Protocols, you can re-run VMSINSTAL and do a partial installation of just the 3222 Protocols. 7. Protocol The installation procedure asks the following: * Do you want to install the 3222 Protocols [YES]? YES If YES, then the protocol files and example program for that protocol are installed on the host. The protocol product requires a license to be installed on your system. If you have not installed the license for the protocol you may do so at this time. The installation procedure displays the following: The protocol products require a license(s) to be installed on this system. If you have not installed the license(s) for the protocol(s) you may do so at this time. * Do you wish to stop and install the license(s) [YES]? NO Enter NO if you have already installed the license(s) for the protocol package(s). Enter YES if you wish to exit the procedure to install the license(s). 8. Respond to license registration queries. 2-6 Installing DEC Commserver for OpenVMS Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure For OpenVMS VAX Version 5.5, the following is displayed: Product: COMMSERVER-V Producer: DEC Version: Vn.n Release Date: dd-mmm-yyyy * Does this product have an authorization key registered and loaded? The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAK to successfully complete the installation. If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. 9. Choose the Installation Verification Procedure (IVP) option. * Do you want to run the IVP after the installation [YES]? YES The installation procedure now asks if you want to run the IVP. The IVP for DEC Commserver for OpenVMS checks to be sure that the installation is successful. It is recommended that you run the IVP. After DEC Commserver for OpenVMS is installed, you can run the IVP independently to verify that the software is available on your system. You might need to run the IVP after a system failure to make sure that users can access DEC Commserver for OpenVMS. 10.Ethernet controller Since there may be more than one Ethernet controller in the system it is necessary to specify the particular device controller that the DEC Commserver for OpenVMS software product should use to establish communication with the servers. The installation procedure displays the following: * Enter the Ethernet controller you wish your host to communicate on: Installing DEC Commserver for OpenVMS 2-7 Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure Enter the Ethernet controller you wish to use for communications. The following are Ethernet controllers and some systems they are supported on: ________________________________________________________ Controller Name___________Supported_System_________________________ EF VAXFT 3000 ES MicroVAX 2000, 3100, 3300, 3400, VAXstation 2000, 3100, 3300, 3400, DEC 3000 ET VAX 6000, 8200, 8300, 85xx, 8700, 8800 EX VAX 7000, 9000, 10000, DEC 7000, 10000 EZ VAX 4000, DEC 4000 XE VAX-11 730, 750, 780, 785, VAX 8600, 8650 XQ MicroVAX II, VAXstation 3200, MicroVAX 3500, 3600, 3800, 3900 ER DEC 2000 EC_____________DEC_3000-300/with_PMAD_option____________ Please refer to Section 3.3 if you need to change the Ethernet controller in the startup file for DEC Commserver for OpenVMS software. 11.Read informational messages. At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. A message is displayed for each protocol that is installed. An example is shown below. All 1622 X25 files will be copied to COMMSERVER$DIRECTORY: [ICP_X25]. Read file READ_ME.FIRST in COMMSERVER$DIRECTORY:[ICP_X25] to run the IVP for this product. 12.Observe the installation Verification Procedure (IVP). 2-8 Installing DEC Commserver for OpenVMS Installing DEC Commserver for OpenVMS 2.1 The Installation Procedure If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: Installation Verification Procedure for DEC COMMSERVER for OpenVMS Vn.nn Completed Successfully 13.End the installation procedure. Installation of COMMSERVER Vn.n completed at hh:mm VMSINSTAL procedure done at hh:mm The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at dd-mmm-yyyy hh:mm:ss Note that 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 you want to restore these symbols, you should log out and log in again. 2.2 Error Recovery If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of COMMSERVER Vn.n has failed. If the IVP fails, you see this message: Installation Verification Procedure for DEC COMMSERVER for OpenVMS Vn.nn failed Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. Installing DEC Commserver for OpenVMS 2-9 Installing DEC Commserver for OpenVMS 2.2 Error Recovery o System parameter values for successful installation are insufficient. o The OpenVMS help library is currently in use. o The product license has not been registered and loaded. o The installer entered the wrong Ethernet controller name for this system. If this occurs then the IVP will fail with the following error: %COMSERVER-F-NOPROCESS, The process COMMSERVER$PROC is not running You can correct this problem by editing the COMMSERVER$STARTUP.COM file in SYS$STARTUP: and change the references to the Ethernet controller to the correct controller for this system. Once completed, the start up file may be executed and the IVP run again. $ @SYS$STARTUP:COMMSERVER$STARTUP $ @SYS$TEST:COMMSERVER$IVP For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 1. 2-10 Installing DEC Commserver for OpenVMS 3 _________________________________________________________________ After Installing DEC Commserver for OpenVMS The following tasks take place after installing DEC Commserver for OpenVMS: o Configuring the host to load the server software. o Running the Installation Verification Procedure separately. o Editing the system startup file. o Setting user account quotas. o Installing on a VAXcluster. o Enhancing performance. o Reporting problems. 3.1 Configuring a Host for Downline Loading At least one host in the LAN must be configured to down-line load the server image. If this host will not be configued to load the server image you may skip to Section 3.2. Once the DEC Commserver for OpenVMS software has been installed, the following steps must be taken in order for a OpenVMS host to load a server with the server image. The host must be running DECnet. Once DECnet is running you must configure your OpenVMS host for down-line loading. After Installing DEC Commserver for OpenVMS 3-1 After Installing DEC Commserver for OpenVMS 3.1 Configuring a Host for Downline Loading 3.1.1 Recognizing Boot Requests The following is a list of DECnet line and circuit names: Table_3-1_Line_and_Circuit_Mnemonics_______________________ Mnemonic______Host_Processor_______________________________ BN Processor that uses a DEBNA or DEBNI controller IS Processor that uses a SGEC controller MN Processor that uses a DEMNA controller QN Processor that uses a DEQNA or DELQA controller SV, KFE Processor that uses an integral controller UN Processor that uses a DEUNA or DELUA ______________controller___________________________________ To determine the Line, and Circuit name for your processor you can perform the following: $ RUN SYS$SYSTEM:NCP NCP> SHOW KNOWN CIRCUIT CHARACTERISTICS The above commands will display all DECnet controllers configured on the host. This will also display the type of controller. The controller must be an Ethernet controller. Issue the following commands, which enable the host to recognize boot-request messages from a target server: $ RUN SYS$SYSTEM:NCP NCP> DEFINE CIRCUIT xxx-0 SERVICE ENABLED NCP> SET CIRCUIT xxx-0 STATE OFF NCP> SET CIRCUIT xxx-0 ALL NCP> SET CIRCUIT xxx-0 STATE ON Replace xxx with the mnemonics of the Ethernet device displayed in the NCP SHOW KNOWN CIRCUIT command. 3-2 After Installing DEC Commserver for OpenVMS After Installing DEC Commserver for OpenVMS 3.1 Configuring a Host for Downline Loading 3.1.2 Adding the Server to the Host's Network Node Database You must describe the server in the network node database of the host system. Use the NCP utility to store the server node address, node name, Ethernet hardware address, host load device name, and load file name. You will need the following information before adding the server(s) to the DECnet database: o A unique DECnet node name for the server. o A unique DECnet address for the server with a DECnet area address which can be accessed by the host. In order to identify your host's DECnet address type the following: $ SHOW NETWORK o The host server Ethernet circuit name. See Section 3.1.1. o The server's Ethernet hardware address is required for down-line loading using the Ethernet and is the Ethernet address contained in ROM on the Ethernet hardware controller of the server. The server's Ethernet address is on a tag attached to the rear of the server. o The server software image to down line (SYS$SYSTEM:COMMSERVER$IMAGE.SYS) Invoke the utility as follows: $ RUN SYS$SYSTEM:NCP NCP> Use the DEFINE command to add target data to the permanent database: NCP> DEFINE NODE node-name ADDRESS address SERVICE CIRCUIT xxx-0 NCP> DEFINE NODE node-name HARDWARE ADDRESS address NCP> DEFINE NODE node-name LOAD FILE SYS$SYSTEM:COMMSERVER$IMAGE.SYS After Installing DEC Commserver for OpenVMS 3-3 After Installing DEC Commserver for OpenVMS 3.1 Configuring a Host for Downline Loading For example: $ SHOW NETWORK VAX/VMS Network status for local node 3.558 HOST1 on 28-FEB-1991 13:26:46.32 This is a nonrouting node, and does not have any network information. The designated router for HOST1 is node 3.1019 ROUTER. $ RUN SYS$SYSTEM:NCP NCP> DEFINE NODE COM1 ADDRESS 3.3 SERVICE CIRCUIT SVA-0 NCP> DEFINE NODE COM1 HARDWARE ADDRESS 08-00-2B-16-00-FF NCP> DEFINE NODE COM1 LOAD FILE SYS$SYSTEM:COMMSERVER$IMAGE.SYS ________________________ NOTE ________________________ To use the DEFINE COMMAND, you must set the system privilege option (SYSPRV). ______________________________________________________ Once the server has been added to the permanent database of the host system, use the SET command to copy information to the current database: NCP> SET NODE node-name ALL For example, using the server named COM1. NCP> SET NODE COM1 ALL ________________________ NOTE ________________________ To use the SET command, you must first set the operator privilege option (OPER). ______________________________________________________ If the DEFINE command has been executed, the information remains in both databases even after the host system is rebooted. Repeat the steps in this section for each server this host will be down-line loading. For more information on NCP commands please read the Guide to DECnet-VAX Networking. 3-4 After Installing DEC Commserver for OpenVMS After Installing DEC Commserver for OpenVMS 3.2 Running the Installation Verification Procedure Separately 3.2 Running the Installation Verification Procedure Separately You usually run the Installation Verification Procedure (IVP) during installation. If you want to run the IVP separately to ensure the integrity of installed files should system problems occur, execute the following command procedure: $ @SYS$TEST:COMMSERVER$IVP.COM 3.3 Editing the System Files You must edit the system startup files to provide for automatic startup of DEC Commserver for OpenVMS when your system is rebooted. o For OpenVMS Version 5.5, add the command line that starts DEC Commserver for OpenVMS to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM. o For OpenVMS VAX Version 6.x, add the command line that starts DEC Commserver for OpenVMS to the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM. If DECnet is to be run on the same Ethernet Controller, then the DEC Commserver for OpenVMS software cannot start until after the network has started. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the DEC Commserver for OpenVMS startup command line: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:COMMSERVER$STARTUP.COM ________________________ Note ________________________ Digital recommends that the DECnet startup file be run interactively during system startup, rather than in batch mode, in order to ensure the network software is running before starting up the Commserver client software. ______________________________________________________ After Installing DEC Commserver for OpenVMS 3-5 After Installing DEC Commserver for OpenVMS 3.3 Editing the System Files The Ethernet controller defined in the COMMSERVER$STARTUP.COM may be changed if another Ethernet controller is to be utilized on the host system. Edit the COMMSERVER$STARTUP.COM for the system and change the references to the Ethernet controller to the new controller that is to be utilized. The system must be rebooted if the DEC Commserver for OpenVMS software is currently running in order for the new Ethernet device to be used. To change the Ethernet controller, edit the Commserver startup file and modify the following line: $ DEFINE/SYSTEM/NOLOG/EXECUTIVE_MODE COMMSSERVER$NI_DEVICE ESA0: and change "ESA0:" to the desired type of controller. 3.4 User Account Requirements To work with DEC Commserver for OpenVMS, user accounts on your system must have certain privileges and quotas. The next two sections contain information on these requirements. The third section discusses how to set up user accounts. 3.4.1 Privileges To use DEC Commserver for OpenVMS, each account must have at least the TMPMBX and NETMBX privileges. To configure the COMMSERVER environment you need SYSPRV. Use the OpenVMS Authorize Utility to determine whether users have the privileges they require. 3.4.2 User Account Quotas You must make sure that the appropriate user accounts have sufficient quotas to be able to use DEC Commserver for OpenVMS. Table 1-4 summarizes the required user account quotas. ________________________ Note ________________________ For each device configured by a user, 310 bytes are subtracted from the account's BYTLM quota. ______________________________________________________ 3-6 After Installing DEC Commserver for OpenVMS After Installing DEC Commserver for OpenVMS 3.4 User Account Requirements Account quotas are highly dependent on the application being used, this includes the number of buffers outstanding, the size of the buffers, and number of ASTs used, if any. See Section 1.3.3 for a description of how to verify and change account quotas. 3.5 Installing DEC Commserver for OpenVMS on a VAXcluster To install DEC Commserver for OpenVMS on a cluster with a common system disk, make sure you load the DEC Commserver for OpenVMS license and any communications software license on each node in the cluster. To load the licenses, enter the following commands: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER/USER=SYSTEM Remote Password: SYSMAN> DO LICENSE LOAD license name Where license name is the license to load. SYSMAN> DO LICENSE LOAD COMMSERVER-V Before starting the Commserver software on any other node in the cluster which has a different Ethernet controller then the system where the software was originally installed the following must be performed: Copy the COMMSERVER$STARTUP.COM file in SYS$STARTUP: common directory to each systems' SYS$STARTUP: root directory. Once copied, edit the COMMSERVER$STARTUP.COM file in each SYS$STARTUP: root directory and change the references to the Ethernet controller to the correct controller for that system. The following can then be performed: SYSMAN> DO @SYS$STARTUP:COMMSERVER$STARTUP SYSMAN> EXIT After Installing DEC Commserver for OpenVMS 3-7 After Installing DEC Commserver for OpenVMS 3.6 Enhancing Performance 3.6 Enhancing Performance The DEC Commserver for OpenVMS software uses nonpaged memory for allocation of I/O buffers. A buffer is allocated whenever a read or write request is queued to the driver and is released back to the pool when the request is completed. The size of each buffer is equal to the size in bytes of the user's buffer plus twelve bytes for the buffer header. Each $QIO request causes the allocation of an IRP. The IRP is returned to the system when the request is completed. The number of IRPs required by this software is highly application dependent. As a beginning estimate, assume that each OpenVMS process accessing a device on a Commserver will need one IRP, or two or more if it will make extensive use of $QIOW requests. 3.6.1 OpenVMS Version 5.5 In order to alleviate allocation from the fragmentable pool the SRPCOUNT, IRPCOUNT, and LRPCOUNT SYSGEN parameters can be increased depending on the server configuration. If the driver requests a buffer of appropriate size, it is allocated from one of the look aside lists (small, intermediate, or large request packets-SRPs, IRPs or LRPs, respectively) rather than from the fragmentable pool. Use the SHOW MEMORY command to determine the available nonpaged memory on your system during a typically busy period. If necessary, increase NPAGEDYN so that you will have adequate free space in the pool even after the software is loaded and in use. If I/O activity causes depletion of the SRP, IRP, or LRP look aside lists, increase the value of the SRPCOUNT, IRPCOUNT, or LRPCOUNT parameters, respectively. As a guide the following shows the number of SRPs, IRPs, and LRPs used by the DEC Commserver for OpenVMS software alone. o For each server configured on the host, 3 SRPs, 2 IRPs, and 20 LRPs are consumed. o For each device configured on the host, 21 SRPs, 2 IRPs, and 1 LRPs are consumed. 3-8 After Installing DEC Commserver for OpenVMS After Installing DEC Commserver for OpenVMS 3.6 Enhancing Performance 3.6.2 OpenVMS VAX Version 6.x Use the SHOW MEMORY command to determine the available nonpaged memory on your system during a typically busy period. If necessary, increase NPAGEDYN so that you will have adequate free space in the pool even after the software is loaded and in use. 3.7 Determining and Reporting Problems If you encounter a problem while using DEC Commserver for OpenVMS, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Reader's Comments form if the problem has to do with the DEC Commserver for OpenVMS documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. After Installing DEC Commserver for OpenVMS 3-9 A _________________________________________________________________ Sample Installation This appendix contains a sample installation of DEC Commserver for OpenVMS. This sample was run on a system that had no previous version of DEC Commserver for OpenVMS installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. The sample installation assumes that DECnet has been shut down, and that no users are logged on to your system. The Installation Verification Procedure (IVP) runs at the end of the installation. Welcome to OpenVMS VAX T6.1-5Z0 Username: SYSTEM Password: Welcome to OpenVMS VAX version T6.1-5Z0 on node LIME Last interactive login on Thursday, 10-MAR-1994 15:18 Last non-interactive login on Monday, 21-MAR-1994 16:04 $ @sys$update:vmsinstal OpenVMS VAX Software Product Installation Procedure T6.1-5Z0 It is 21-MAR-1994 at16:10. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: DECW$SERVER_0 DECW$MWM VUE$MISTERX_3 DECW$TE_005A MISTERX * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: SYS$SYSDEVICE:[MISTERX.KIT] Sample Installation A-1 Sample Installation Enter the products to be processed from the first distribution volume set. * Products: commserver020 * Enter installation options you wish to use (none): The following products will be processed: COMMSERVER V3.0 Beginning installation of COMMSERVER V3.0 at 16:10 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. The Commserver Product requires the following System Resources for proper installation: VAX/VMS V5.5 or later 546 Global Pages 5 Global Sections 6000 Maximum Buffer Size 18000 free disk blocks. 3000 blocks for Layered Product. 15000 blocks for Protocols. Performing system resource verification * Do you want to purge files replaced by this installation [YES]? * Do you want to install the Layered Product [YES]? * Do you want to install the 3222 Protocols [YES]? The Protocol products require license(s) to be installed on this system. If you have not installed the license(s) for the protocol(s) you may do so at this time. * Do you wish to stop and install the license(s) [YES]? n Product: COMMSERVER-V Producer: DEC Version: 2.0 Release Date: 18-MAR-1994 * Does this product have an authorization key registered and loaded? y * Do you want to run the IVP after the installation [YES]? Since there may be more than one DEUNA/DEQNA/VAXBI controllers, it is necessary to specify the particular device controller that the DEC Commserver software product should use to establish communication with the DEC Commserver unit. Some samples of possible Ethernet controllers are as follows: Ethernet Controller Names A-2 Sample Installation Sample Installation ESA0: ETA0: EXA0: XEA0: XQA0: * Enter the Ethernet controller you wish your host to communicate on: esa0 Make sure you read the post installation section of the installation manual if this host will be used to downline load the server image into a target server. To automatically configure the Commserver software at system startup, include the line: @SYS$STARTUP:COMMSERVER$STARTUP.COM in the site specific startup file: SYS$MANAGER:SYSTARTUP_VMS.COM There will be no further questions asked during the remainder of the installation procedure. You will receive some informational/status messages. * Press RETURN to continue: %VMSINSTAL-I-RESTORE, Restoring product save set C ... Begin linking images Ignore the linker error message %LINK-W-USRTFR Linking REDRIVER.EXE %LINK-W-USRTFR, image LIME$DKA0:[SYS0.SYSUPD.COMMSERVER020] REDRIVER.EXE;1 has no user transfer address Linking RFDRIVER.EXE %LINK-W-USRTFR, image LIME$DKA0:[SYS0.SYSUPD.COMMSERVER020] RFDRIVER.EXE;1 has no user transfer address Linking RJDRIVER.EXE Linking COMMSERVER$SHR.EXE Linking COMSERVER.EXE Linking COMMSERVER$PROC.EXE Linking COMMSERVER$FIP.EXE %VMSINSTAL-I-RESTORE, Restoring product save set E ... Sample Installation A-3 Sample Installation %VMSINSTAL-I-SYSDIR, This product creates system directory [COMMSERVER$FILES.ICP_2780_3222]. All 3222 2780 files will be copied to COMMSERVER$DIRECTORY: [ICP_2780_3222]. Read file READ_ME.FIRST in COMMSERVER$DIRECTORY:[ICP_2780_3222] to run the IVP for this product. %VMSINSTAL-I-SYSDIR, This product creates system directory [COMMSERVER$FILES.ICP_3270_3222]. All 3222 3270 files will be copied to COMMSERVER$DIRECTORY: [ICP_3270_3222]. Read file READ_ME.FIRST in COMMSERVER$DIRECTORY:[ICP_3270_3222] to run the IVP for this product. %VMSINSTAL-I-SYSDIR, This product creates system directory [COMMSERVER$FILES.ICP_HDLC_3222]. All 3222 HDLC files will be copied to COMMSERVER$DIRECTORY: [ICP_HDLC_3222]. Read file READ_ME.FIRST in COMMSERVER$DIRECTORY:[ICP_HDLC_3222] to run the IVP for this product. %COMMSERVER-I-LOADED, Total of 3 3222 protocols loaded %RUN-S-PROC_ID, identification of created process is 00000061 Beginning Installation Verification Procedure for DEC Commserver for OpenVMS V3.0 $ COMSERVER ADD SERVER COMMSERVER_IVP 01-23-45-67-89-AB $ COMSERVER SHOW SERVER COMMSERVER_IVP DEC Commserver V3.0 Commserver System Status: Communications link stopped Name: COMMSERVER_IVP Address: 01-23-45-67-89-AB $ COMSERVER ADD DEVICE ZOA0: RE COMMSERVER_IVP "ZOA0" = "_REA1:" (COMMSERVER$COMMSERVER_IVP) $ COMSERVER SHOW LOGGING COMMSERVER_IVP DEC Commserver V3.0 Commserver System -- COMMSERVER_IVP logging enabled Device ZOA0: logging enabled A-4 Sample Installation Sample Installation $ COMSERVER REMOVE DEVICE ZOA0: COMMSERVER_IVP $ COMSERVER ADD DEVICE ZQA0: RE COMMSERVER_IVP "ZQA0" = "_REA2:" (COMMSERVER$COMMSERVER_IVP) $ COMSERVER SHOW LOGGING COMMSERVER_IVP DEC Commserver V3.0 Commserver System -- COMMSERVER_IVP logging enabled Device ZQA0: logging enabled $ COMSERVER REMOVE DEVICE ZQA0: COMMSERVER_IVP $ COMSERVER REMOVE SERVER COMMSERVER_IVP Installation Verification Procedure for DEC Commserver for OpenVMS V3.0 Completed Successfully Installation of COMMSERVER V3.0 completed at 16:30 Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 16:31 $ log SYSTEM logged out at 21-MAR-1994 16:31:31.96 Sample Installation A-5 B _________________________________________________________________ Files and Logical Names Installed on Your System The DEC Commserver for OpenVMS installation procedure installs a number of files on your system and defines some logical names. Section B.1 lists the files installed. Section B.1 tells where you can find the list of installed files. Section B.2 lists the logical names that are added to the system logical name table. B.1 File Names The following list contains the names of all files created on your system when DEC Commserver for OpenVMS is installed. SYS$TEST:COMMSERVER$IVP.COM ! IVP for the Commserver SYS$EXAMPLE:COMMSERVER$TEST.MAR ! Macro example program SYS$EXAMPLE:COMMSERVER$SHR_EXAMPLE.C ! C example calling shareable image SYS$EXAMPLE:COMMSERVER$ESP_EXAMPLE.C ! C example calling COMMSERVER$PROC SYS$LIBRARY:COMMSERVER_USER_DEF.MLB ! MACRO-32 Commserver Definitions SYS$LIBRARY:COMMSERVER_USER_DEF.H ! C Commserver Definitions SYS$LIBRARY:COMMSERVER_USER_DEF.PAS ! PASCAL Commserver Definitions SYS$LIBRARY:COMMSERVER_USER_DEF.FOR ! FORTRAN Commserver Definitions SYS$LOADABLE_IMAGES:REDRIVER.EXE ! SIMPACT Virtual Device driver SYS$LOADABLE_IMAGES:RFDRIVER.EXE ! Commserver Manager driver SYS$LOADABLE_IMAGES:RJDRIVER.EXE ! Commserver Transport Driver SYS$LIBRARY:COMMSERVER$SHR.EXE ! Commserver shareable image SYS$SYSTEM:COMSERVER.EXE ! Commserver DCL interface SYS$SYSTEM:COMMSERVER$PROC.EXE ! Event Status Process SYS$SYSTEM:COMMSERVER$IMAGE.SYS ! Loadable Server Image SYS$SYSTEM:COMMSERVER$FIP.EXE ! Fault Isolation Procedure SYS$STARTUP:COMMSERVER$STARTUP.COM ! Start up file Where: COMMSERVER$PROC is the name of the Event Status Process created by COMMSERVER$STARTUP.COM Files and Logical Names Installed on Your System B-1 Files and Logical Names Installed on Your System B.2 Logical Names B.2 Logical Names The following logical names are entered into the system logical name table when DEC Commserver for OpenVMS is installed. These names are stored in the product's startup file. They are automatically entered into the system logical name table whenever the system reboots or whenever the software is invoked. o COMMSERVER$NI_DEVICE - system wide logical defining the name of the Ethernet controller that the Commserver is to use. o COMMSERVER$DIRECTORY - If any protocol files have been installed this logical will be equivalent to the location SYS$COMMON:[COMMSERVER$FILES]. B-2 Files and Logical Names Installed on Your System C _________________________________________________________________ Startup Command File $ ! $ ! COPYRIGHT (C) 1991 BY $ ! DIGITAL EQUIPMENT CORPORATION, MAYNARD $ ! MASSACHUSETTS. ALL RIGHTS RESERVED. $ ! $ ! THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED $ ! ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THEINCLUSION $ ! OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER COPIES $ ! THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER $ ! PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED. $ ! $ ! THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE AND $ ! SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT CORPORATION. $ ! $ ! DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS $ ! SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY DIGITAL. $ ! $ ! Commserver Startup Procedure created on 1-MAR-1994 15:27:01.66 $ ! $ ON ERROR THEN GOTO EXIT $ ON CONTROL_Y THEN GOTO EXIT $ ! $ ! Check for right privileges $ ! $ Required_privileges = "CMKRNL,PRMMBX,OPER,EXQUOTA,BUGCHK,SYSLCK" $ Prev_privs = f$setprv(required_privileges) $ IF .not. f$privilege(required_privileges) THEN GOTO no_privileges $ ! $ ! Define the Ethernet device to be used $ ! $ DEFINE/SYSTEM/NOLOG/EXECUTIVE_MODE COMMSERVER$NI_DEVICE ESA0: $ ! Startup Command File C-1 Startup Command File $ IF F$GETDVI("COMMSERVER$NI_DEVICE", "EXISTS") THEN GOTO ETHERNET_LOADED $ RUN SYS$SYSTEM:SYSGEN AUTOCONFIGURE ALL /SELECT=(ESA) EXIT $ ! $ETHERNET_LOADED: $ ! $ ! If Commserver directory is there define a logical for it $ ! $ IF F$SEARCH("SYS$COMMON:[000000]COMMSERVER$FILES.DIR") .NES. "" $ THEN $ COMMSERVER_COMMON = F$TRNLNM("SYS$COMMON","LNM$SYSTEM_TABLE",,,,"VALUE") $ COMMSERVER_COMMON = "''COMMSERVER_COMMON'" - "]" +"COMMSERVER$FILES.]" $ DEFINE/SYSTEM/NOLOG/EXECUTIVE_MODE COMMSERVER$DIRECTORY 'COMMSERVER_COMMON'/TRANSLATION_ATTRIBUTES=CONCEALED $ ENDIF $ ! $ ! Load and start the Commserver Drivers $ ! RJDRIVER must be loaded first $ ! $ RUN SYS$SYSTEM:SYSGEN LOAD SYS$LOADABLE_IMAGES:RJDRIVER CONNECT RJA0:/NOADAPTER EXIT $ WAIT 00:00:03 $ RUN SYS$SYSTEM:SYSGEN LOAD SYS$LOADABLE_IMAGES:REDRIVER CONNECT REA0:/NOADAPTER EXIT $ WAIT 00:00:03 $ RUN SYS$SYSTEM:SYSGEN LOAD SYS$LOADABLE_IMAGES:RFDRIVER CONNECT RFA0:/NOADAPTER EXIT $ WAIT 00:00:03 $ ! $ ! Install the sharable image $ ! $ IF F$FILE_ATTRIBUTES("SYS$SHARE:COMMSERVER$SHR.EXE","KNOWN") .EQS. "FALSE" $ THEN $ INSTALL ADD/PROTECT/SHARE/OPEN/HEADER_RESIDENT SYS$SHARE:COMMSERVER$SHR.EXE $ ELSE $ INSTALL REPLACE/PROTECT/SHARE/OPEN/HEADER_RESIDENT SYS$SHARE:COMMSERVER$SHR.EXE C-2 Startup Command File Startup Command File $ ENDIF $ ! $ ! Start the ACP $ ! $ If F$GETDVI ("_RFA0:", "EXISTS" ) .eqs. "FALSE" then goto no_drivers $ RUN SYS$SYSTEM:COMMSERVER$PROC.EXE - /INPUT=NL: - /OUTPUT=SYS$MANAGER:COMMSERVER.LOG - /ERROR=SYS$MANAGER:COMMSERVER.LOG - /NOACCOUNTING - /NOAUTHORIZE - /PRIVILEGES=(CMKRNL,PRMMBX,OPER,EXQUOTA,BUGCHK,SYSLCK) - /UIC=[1,3] - /PRIORITY=7 - /PAGE_FILE=10000 - /AST_LIMIT=5 - /BUFFER_LIMIT=10240 - /FILE_LIMIT=5 - /MAXIMUN_WORKING_SET=350 - /WORKING_SET=200 - /EXTEND=1500 - /IO_BUFFERED=20 - /PROCESS_NAME=COMMSERVER$PROC $ ! $ WAIT 00:00:05 $Exit: $ Prev_privs = f$setprv(prev_privs) $ Exit $ ! $No_privileges: $ Write sys$output "Insufficient privileges to start the ACP" $ Write sys$output "Requires ",REQUIRED_PRIVILEGES," privileges." $ Goto exit $ ! $No_image: $ Goto exit $ ! $No_drivers: $ Write sys$output "COMMSERVER$PROC not started, RFDRIVER is not loaded." $ Goto exit Startup Command File C-3 D _________________________________________________________________ IVP Command File $ ! C O M M S E R V E R $ I V P . C O M $ ! $ ! COPYRIGHT (C) 1991 BY $ ! DIGITAL EQUIPMENT CORPORATION, MAYNARD $ ! MASSACHUSETTS. ALL RIGHTS RESERVED. $ ! $ ! THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED $ ! ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE INCLUSION $ ! OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER COPIES $ ! THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER $ ! PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED. $ ! $ ! THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE AND $ ! SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT CORPORATION. $ ! $ ! DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS $ ! SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY DIGITAL. $ ! $ WRITE := "WRITE" $ ON := "ON" $ SET := "SET" $ COMSERVER := "COMSERVER" $ ! $ SET NOVERIFY $ SET ON $ ! $ ON CONTROL_Y THEN EXIT $ ON WARNING THEN GOTO ERROR $ ! $ version = "V3.0" $ ! $ WRITE SYS$OUTPUT " " $ WRITE SYS$OUTPUT " Beginning Installation Verification Procedure for" $ WRITE SYS$OUTPUT " DEC Commserver for OpenVMS ''version'" IVP Command File D-1 IVP Command File $ WRITE SYS$OUTPUT " " $ WRITE SYS$OUTPUT "$ COMSERVER ADD SERVER COMMSERVER_IVP 01-23-45-67-89-AB" $ COMSERVER ADD SERVER COMMSERVER_IVP 01-23-45-67-89-AB $ ! $ WRITE SYS$OUTPUT "$ COMSERVER SHOW SERVER COMMSERVER_IVP" $ COMSERVER SHOW SERVER COMMSERVER_IVP $ ! $ WRITE SYS$OUTPUT "$ COMSERVER ADD DEVICE ZOA0: RE COMMSERVER_IVP" $ COMSERVER ADD DEVICE ZOA0: RE COMMSERVER_IVP $ ! $ WRITE SYS$OUTPUT "$ COMSERVER SHOW LOGGING COMMSERVER_IVP" $ COMSERVER SHOW LOGGING COMMSERVER_IVP $ ! $ WRITE SYS$OUTPUT "$ COMSERVER REMOVE DEVICE ZOA0: COMMSERVER_IVP" $ COMSERVER REMOVE DEVICE ZOA0: COMMSERVER_IVP $ ! $ WRITE SYS$OUTPUT "$ COMSERVER SHOW LOGGING COMMSERVER_IVP" $ COMSERVER SHOW LOGGING COMMSERVER_IVP $ ! $ WRITE SYS$OUTPUT "$ COMSERVER REMOVE SERVER COMMSERVER_IVP" $ COMSERVER REMOVE SERVER COMMSERVER_IVP $! $! $ WRITE SYS$OUTPUT " " $ WRITE SYS$OUTPUT " Installation Verification Procedure for" $ WRITE SYS$OUTPUT " DEC Commserver for OpenVMS ''version'" $ WRITE SYS$OUTPUT " Completed Successfully" $ WRITE SYS$OUTPUT " " $ EXIT $ERROR: $ ESTATUS = $STATUS $ WRITE SYS$OUTPUT " " $ WRITE SYS$OUTPUT " Installation Verification Procedure for" $ WRITE SYS$OUTPUT " DEC Commserver for OpenVMS ''version'" $ WRITE SYS$OUTPUT " Failed" $ WRITE SYS$OUTPUT " " $ EXIT ESTATUS D-2 IVP Command File