! Frontmatter BASEstar for VMS Installation Guide Order Number: AA-PD1QB-TE April 1991 This manual describes installation prerequisites, installation procedures, and post-installation tasks for BASEstar for VMS. Revision/Update Information: This manual supersedes the BASEstar Integration Platform Installation Guide, Version 2.0. Operating System and Version: VMS Version 5.3 Software Version: BASEstar for VMS, Version 3.0 DIGITAL ________________________ April 1991 __________ The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. __________ Copyright ©1991 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. __________ The READER'S COMMENTS form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DIGITAL BASEstar MicroVAX VAXcluster DEC PATHWORKS VAX DOCUMENT DECnet Q-bus VAXstation DECserver Rdb/VMS VMS DIGITAL ReGIS VT FMS ULTRIX LAT VAX This document was prepared using VAX DOCUMENT, Version 1.2 _____________________________________________________________________ Contents Preface....................................................... v New and Changed Features ...................................... ix Chapter 1 Introduction....................................... 1-1 1.1 Overview............................................ 1-1 1.1.1 Main Installation Options..................... 1-2 1.1.2 Optional Installation Procedures.............. 1-3 1.1.2.1 Device Connection Management........... 1-3 1.1.2.2 Library Management..................... 1-4 1.1.2.3 Utilities.............................. 1-4 1.1.2.4 Rdb/VMS Database Server................ 1-5 1.1.3 Installation Checklist........................ 1-5 1.2 Installation Preparation............................ 1-6 1.2.1 Distribution Kit.............................. 1-7 1.2.2 Hardware Requirements......................... 1-9 1.2.3 Software Requirements......................... 1-9 1.2.4 Disk Space Requirements....................... 1-10 1.3 Preliminary Installation Steps...................... 1-10 1.4 VAXcluster Installation............................. 1-17 Chapter 2 Installation....................................... 2-1 2.1 Installing BASEstar Software........................ 2-3 2.1.1 BASEstar Single Node Installation............. 2-3 2.1.2 BASEstar VAXcluster Installation.............. 2-12 iii Contents 2.2 BASEstar Device Connection Management Installation Procedure........................................... 2-20 2.3 BASEstar Library Installation Procedure............. 2-25 2.4 BASEstar Utilities Installation Procedure........... 2-29 2.5 Installation Messages............................... 2-31 2.5.1 Message Format................................ 2-31 2.5.2 Message Listing............................... 2-32 Chapter 3 Post Installation.................................. 3-1 Appendix A Sample BASEstar Installations ..................... A-1 A.1 Single Node......................................... A-1 A.2 VAXcluster System................................... A-7 A.3 Upgrade............................................. A-12 A.4 Device Connection Management........................ A-15 A.5 Library............................................. A-19 A.6 Utility............................................. A-21 Appendix B Files Created During Installation ................. B-1 B.1 Files Created by the BASEstar Installation Procedure B-1 B.2 Files Created by the BASEstar Device Connection Management Installation Procedure................... B-7 B.3 Files Created by the BASEstar Library Installation Procedure........................................... B-13 Index iv Contents _____________________________________________________________________ Tables 1-1 Library Preinstallation Minimum SYSGEN Parameters............................................ 1-13 3-1 BASEstar Minimum SYSGEN Parameters................... 3-2 3-2 Library Minimum SYSGEN Parameters.................... 3-2 3-3 VMS Privileges Required to Start BASEstar Software.............................................. 3-5 B-1 BASEstar Installation Files.......................... B-1 B-2 BASEstar Device Connection Management Installation Files................................................. B-7 B-3 BASEstar Library Installation Files.................. B-13 v _____________________________________________________________________ Preface This manual provides instructions for installing BASEstar software. ___________________________________________________________________ Intended Audience This manual is intended for system managers who install and maintain BASEstar software. Readers of this manual must have a thorough understanding of VMS operations to install a BASEstar system. To obtain a complete understanding of BASEstar configuration management before installation, refer to the BASEstar for VMS Configuration and Tuning Guide. ___________________________________________________________________ Document Structure This document provides information needed to install BASEstar software: o Chapter 1, Introduction provides a description of the BASEstar installation, software distribution kits, required hardware and software, preliminary installation steps, and VAXcluster installation overview. o Chapter 2, Installation describes step-by-step installation of BASEstar software on a single node or on a VAXcluster system. This section also includes instructions for the optional installation of BASEstar library, utility, and device connection management software. o Chapter 3, Post Installation describes post-installation tasks. v Preface o Appendix A, Sample BASEstar Installations presents sample installations of BASEstar software. o Appendix B, File Created During Installation lists all BASEstar files created during installation with their directory locations. ___________________________________________________________________ Conventions The following conventions are used in this manual. __________________________________________________________________ Convention_______Meaning__________________________________________ A symbol with a one- to six-character label or abbreviation indicates you press a key on the terminal (for example, ). The symbol indicates that you hold down the key marked , at the same time pressing the key marked . $ CREATE POINT User entries are shown in two ways: uppercase [point_name] letters indicate exact input, lowercase letters indicate user-supplied input. [logical_name] Brackets indicate that the enclosed item is optional. (Brackets are not, however, optional in the syntax of a directory name in a file specification.) New term Italic lettering designates a new term, or a term or phrase used in a manner specific to the subject being discussed. All new terms are defined in the BASEstar master glossary, which is _________________included_in_the_BASEstar_for_VMS_Introduction.___ vi Preface ___________________________________________________________________ Associated Documents For further information on installing and configuring BASEstar software, refer to the following documents: o BASEstar for VMS Release Notes o BASEstar for VMS Configuration and Tuning Guide o BASEstar for VMS Command Line Interface User's Guide o Introduction to VMS System Management o VMS Backup Utility Manual o VMS License Management Utility Manual o Guide to Setting Up a VMS System vii _____________________________________________________________________ New and Changed Features The BASEstar for VMS Introduction describes several new BASEstar features including: o VAXcluster installation The main BASEstar installation procedure enables installation of BASEstar application integration software on all targeted systems from one node in a VAXcluster system for those nodes sharing a system disk. Optionally installed software such as BASEstar device connection management, library management, and utilities must be installed on each target system. o BASEstar external data support installation During the main BASEstar installation procedure, you have the option to install BASEstar external data support. This option enables users to export BASEstar data to a destination such as a database, data file, application, or other computer system. BASEstar users create external maps used to format data which is then transferred to the target system using a BASEstar database server. BASEstar software includes a database server to export data to an Rdb/VMS database. Instructions for installing the Rdb/VMS database server are in the BASEstar for VMS Rdb/VMS Database Server Guide. o File size selection during installation During the main BASEstar installation procedure and the device connection management installation procedure the user is prompted to select disk space allocation for several BASEstar data files. These choices affect the total peak and net disk space utilization required for BASEstar installation. o BASEstar library installation ix New and Changed Features BASEstar library software is installed on one node in a BASEstar system to provide centralized management of many different types of manufacturing files. BASEstar library features are only accessible through the menu interface; therefore, you must install the BASEstar menu system during the main installation procedure. BASEstar library functions involving device communication (such as uploading and downloading library files) require installation of BASEstar device connection management software and appropriate device access software. o Single distribution tape BASEstar software is distributed on a single magnetic tape or TK50 cartridge. BASEstar application integration capabilities including data management, menu system, and external data support are installed as part of the main installation procedure. Optional software including device connection management, library management, utilities, and Rdb/VMS database server software are installed from separate savesets included on the distribution media. x ! Pre-installation tasks 1 _____________________________________________________________________ Chapter 1 Introduction This chapter is an overview of BASEstar software installation procedures and installation options. It also describes installation preparation, preliminary steps, and provides an overview of VAXcluster installation. ___________________________________________________________________ 1.1 Overview The BASEstar installation procedures allow you to customize each BASEstar system by installing only those system components intended for the target system. You can install BASEstar software on a single node or on a VAXcluster system, which is a group of VAX systems sharing the same system disk. The main BASEstar installation procedure is mandatory for all BASEstar systems and installs basic application integration features, such as: messaging, application synchronization and control, and distributed name processing. The main installation procedure has options, including the ability to install BASEstar data management capabilities, the BASEstar menu interface, and BASEstar external data support used to export real-time manufacturing data collected by BASEstar software to a database, an application, or another computer system. In addition to the main installation options, there are optional installation savesets available with BASEstar software that provide device connection management, library management, and BASEstar utilities. Continue with the instructions in the following sections to understand installation options in the main installation procedures and to learn about optional BASEstar savesets that you can install. Introduction 1-1 Whether you install BASEstar software on a new system or upgrade an existing BASEstar system to the latest software revision, the VMSINSTAL utility performs the software installation procedures. VMSINSTAL prompts you to choose installation options, set directory specifications, and choose the VAXcluster configuration option. This chapter contains a checklist you can follow to ensure the correct BASEstar software is installed on each system. 1.1.1 Main Installation Options Since the processing requirements for each node within your manufacturing system are distinct, the first step in installing BASEstar software is to determine which BASEstar components should be installed on each system. Basic application integration software is installed on all systems. However, during the main BASEstar installation procedure you are prompted to indicate which of the following additional BASEstar software components you wish to install: o Data management o External data support o Menu interface These components are optional in order to save disk space on systems not requiring these features. Consult the manufacturing system designer or user group to understand which, if any, of this optional software must be installed. 1-2 Introduction 1.1.2 Optional Installation Procedures In addition to the main installation, you can also install any of four optional BASEstar components. This software is installed from separate savesets to reduce the amount of system space required for the BASEstar installation if these capabilities are not needed. Optional installation procedures are included for the following BASEstar software components: o Device connection management o Library management o Utilities o Rdb/VMS database server 1.1.2.1 Device Connection Management BASEstar device connection management software is installed after the main BASEstar installation procedure is complete. In order to communicate with plant equipment, BASEstar device access software (DAS) must also be installed for the industrial control devices used at each BASEstar site. Consult the manufacturing system designer or user group to understand which, if any, of this additional software must be installed. NOTE: Before installing BASEstar device connection management software, delete all BASEstar for VMS, V2.0 device access software from the system. The BASEstar device connection management installation procedure offers the option to install menu screens. These screens cannot be installed unless the BASEstar menu system was installed during the main installation procedure. The device connection management installation procedure also includes installation of BASEstar device access software for RS-232 devices and for DECnet and TCP/IP networks. Refer to the BASEstar Device Access Software Introduction 1-3 Guide for RS-232 Devices and BASEstar Device Access Software Guide for DECnet and TCP/IP Networks for information on how to configure and use these DAS modules. 1.1.2.2 Library Management BASEstar library software manages many different types of manufacturing files, including: ladder logic programs, executive files, graphics, and text files. Install BASEstar library software on each network node that you want to use to communicate with BASEstar devices. BASEstar library management functions are only accessible through the BASEstar menu interface; therefore, you must install the BASEstar menu system during the main BASEstar installation procedure. 1.1.2.3 Utilities The BASEstar utility saveset offers three BASEstar functions. 1. The BCC$BASEGEN.COM utility for tuning BASEstar systems. Run this procedure on a loaded BASEstar system to analyze its current VMS resource utilization and obtain suggested values for BASEstar parameters, SYSGEN parameters, and VMS process quota settings. 2. BASEstar text services for translating the BASEstar message files. These services are designed to support international use of BASEstar software by providing the text message files needed when conversion of the user interface to a non-English language is required. 3. Software for reconciling VMS version mismatches. 1-4 Introduction The utility saveset contains software for reconciling VMS versions if a version mismatch error occurs during BASEstar installation. If a mismatch occurs, it is reconciled automatically by installing BASEstar utility software. 1.1.2.4 Rdb/VMS Database Server BASEstar software includes an Rdb/VMS database server to export BASEstar data to an Rdb/VMS database. Instructions for installing and using the BASEstar Rdb/VMS database server are in the BASEstar for VMS Rdb/VMS Database Server Guide. 1.1.3 Installation Checklist This section provides a checklist for interviewing BASEstar system users to understand which BASEstar software components need to be installed on each BASEstar system. Answer all of these questions for every node in your network of BASEstar systems. __________________________________________________________________ Do users need Optio#______to...____________Then_install...______________________ 1. _____ Share data on Data Management during the main this system? installation procedure. 2. _____ Export data External Data Support during the main from this installation procedure. system? 3. _____ Access the Menu System during the main BASEstar menu installation procedure. interface? Introduction 1-5 __________________________________________________________________ Do users need Optio#______to...____________Then_install...______________________ 4. _____ Control or Device Connection Management from the monitor plant DCM030 saveset. equipment or collect plant data using this system? 5. _____ Store and Library Management from the BCCLIB030 manage a saveset on one node in a VAXcluster library of system. files on this system? 6. _____ Access to Utilities from the BCCUTL030 saveset. BASEstar utilities? 7. _____ Export data Rdb/VMS Database Server from the to an Rdb/VMS BRI030 saveset. ____________database?_____________________________________________ Once you have planned the software to install on each BASEstar system, continue with the instructions in the following section to check hardware, software, and disk space prerequisites before installing BASEstar software. ___________________________________________________________________ 1.2 Installation Preparation This section provides information needed to prepare for a BASEstar installation. 1-6 Introduction 1.2.1 Distribution Kit BASEstar software is available in two forms: a 1600-bpi 9-track tape or a TK50 tape cartridge for use with development or runtime licenses. Each medium contains the following installable savesets: o BCC030-BASEstar application integration software o DCM030-BASEstar device connection management software o BCCLIB030-BASEstar library management software o BCCUTL030-BASEstar utilities software o BRI030-BASEstar Rdb/VMS database server software BASEstar technical documentation is available as three separate kits containing the following manuals: Introduction 1-7 System Management Kit: o BASEstar for VMS Release Notes o BASEstar for VMS Installation Guide o BASEstar for VMS Configuration and Tuning Guide General User Kit: o BASEstar for VMS Introduction o BASEstar for VMS Menu Interface User's Guide o BASEstar for VMS Command Line Interface User's Guide Programming Kit: o BASEstar for VMS Introduction to Callable Services o BASEstar for VMS Guide to Writing a Database Server o BASEstar for VMS Rdb/VMS Database Server Guide o BASEstar for VMS Guide to Writing BASEstar Device Access Software o BASEstar Device Access Software Guide for RS-232 Devices o BASEstar Device Access Software Guide for DECnet and TCP/IP Networks o BASEstar for VMS Application Programming Interface Reference Guide NOTE: Check the bill of materials enclosed with the kit to ensure the kit is complete. 1-8 Introduction 1.2.2 Hardware Requirements The minimum hardware configuration required for BASEstar software to run efficiently follows: o VAX Processor- A single VAX or MicroVAX processor supports BASEstar software. The single VAX processor can be networked with other VAX or MicroVAX systems or a VAXcluster system using DECnet software. Any or all systems in the distributed network can run BASEstar software. NOTE: Installation of BASEstar library software increases the minimum processor requirements for BASEstar system configuration to MicroVAX II system with 13 Mb of memory. o ANSI-compatible video display terminal such as the VT100, VT200, or VT300 series. o Nine-track magnetic tape drive or TK50 as appropriate for distribution media. o Minimum of 8 Mb of memory. o RD54 or equivalent disk drive (Additional RD53 required for storing library files if the BASEstar library is used). 1.2.3 Software Requirements The following software must be installed on your system before installing BASEstar software. o VMS V5.3 or higher. o DECnet software, as provided with the VMS operating system. Introduction 1-9 o VAX FMS V2.3 or higher is required for the BASEstar menu system only. If you do not install the menu system, you do not need VAX FMS. 1.2.4 Disk Space Requirements The actual amount of disk space required depends on your BASEstar system configuration. The disk space requirements for the BASEstar software components follow: __________________________________________________________________ Peak Utilization in Blocks (During BASEstar_Component____InstallationNet_Utilization_in_Blocks_______ BASEstar software 31,500 24,300 with all main options Device connection 13,000 12,700 management Library 16,190 15,920 Utility 2,800 200 Rdb/VMS Database 1,150 800 Server____________________________________________________________ ___________________________________________________________________ 1.3 Preliminary Installation Steps Before installing BASEstar software, review the following checklist. If you need more information on how to perform some 1-10 Introduction of the functions on the checklist, refer to the Introduction to VMS System Management. __________________________________________________________________ Step_#______Before_installing_BASEstar_software...________________ 1. _____ Ensure VMS V5.3 or higher is installed on the system. 2. _____ Ensure DECnet software is configured on your system. 3. _____ Verify FMS V2.3 or higher is installed on your system if you intend to install the menu interface. 4. _____ Install the BASEstar product license. 5. _____ Decide which BASEstar software components to install on each system. 6. _____ Develop your global name server configuration (if you have two or more BASEstar systems in a network that share information). 7. _____ Verify SYSGEN parameters before installing BASEstar library software. 8. _____ Stop interactive processes and disable user logins. 9. _____ Stop batch queues. 10. _____ Stop the BASEstar system (if performing an upgrade). 11. _____ Close the library database (upgrades only). 12. _____ Back up the system disk. ____________Verify_logical_names_for_an_upgrade.__________________ Perform these tasks before installing BASEstar software: Introduction 1-11 1. Ensure VMS V5.3 or higher is installed on the system. Verify V5.3 or higher of VMS is installed on each system planned for installation of BASEstar software. 2. Ensure DECnet software is configured on your system. DECnet software must be configured in order to install BASEstar software. Refer to the BASEstar for VMS Configuration and Tuning Guide for instructions on the minimum DECnet configuration required. 3. Verify FMS V2.3 or higher is installed on your system if you intend to install the menu interface. If you plan to use the BASEstar menu interface, ensure V2.3 or higher of FMS is installed on each system planned for installation of BASEstar menu software. 4. Install the BASEstar product license. Before you can install BASEstar software, you must register the information from your product authorization key (PAK) in the VMS license database. You can do so using the VMSLICENSE.COM procedure found in the SYS$UPDATE directory. This command procedure prompts you to enter your product license information. When you register a license with the VMSLICENSE.COM procedure, you can confirm an option to activate the license database information automatically. If you register a license with the LICENSE REGISTER command, you must also activate it with a LICENSE LOAD command. For complete instructions on how to register and load license information, refer to the VMS License Management Utility Manual. 5. Decide which BASEstar software components to install on each system. Review the installation checklist with software developers and process engineers to create a list indicating which BASEstar software components must be installed on each VAX system in your hardware configuration. 1-12 Introduction 6. Define your global name server configuration. In order to make BASEstar objects accessible within a distributed system, at least one BASEstar system must be defined as a global name server. Other nodes are designated as name dispatchers. Before installing BASEstar software, determine your global name server configuration so you can enter definitions properly during installation. For information on defining global name servers, refer to the BASEstar for VMS Configuration and Tuning Guide. 7. Verify minimum SYSGEN parameters for BASEstar library installation. Before installing BASEstar library software, ensure that your system meets the minimum required SYSGEN parameter settings referenced in Table 1-1. Table_1-1:__Library_Preinstallation_Minimum_SYSGEN_Parameters_____ MODPARAMS.DAT_Entries______Minimum_Value__________________________ CTLPAGES 60 GBLPAGFIL______________________4096_______________________________ For example, follow these steps to steps to adjust the SYSGEN parameter GBLPAGFIL. a. Begin by running the VMS System Generation utility to view the current setting for the GBLPAGFIL parameter on your system as follows: Introduction 1-13 $ SET DEF SYS$SYSTEM $ RUN SYSTEM SYSGEN>USE ACTIVE SYSGEN>SHOW GBLPAGFIL GBLPAGES 1024 SYSGEN>EXIT $ b. Edit the MODPARAMS.DAT file to increase the size of the global page file. If the GBLPAGFIL parameter is already set, change the current value to the desired value. If the parameter is not specified, you can add a line to the MODPARAMS.DAT file to specify your desired minimum amount as follows: MIN_GBLPAGFIL=4096 In this way, a larger global page file can be allocated if needed, however, your system will maintain a minimum global page file size equal to your desired value. c. Run the AUTOGEN command procedure to update the new value. If you want a feedback report, enter the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK If you do not require feedback, enter the following command: $ @SYS$UPDATE:AUTOGEN GETDATA SETPARAMS NOFEEDBACK d. Once you have run the AUTOGEN procedure, you must shut down the system and reboot in order for the new parameter value to take effect. 8. Disable log ins. 1-14 Introduction Ensure that all BASEstar users have logged off and no other users can log on to the system during the installation. To disable users from logging in, enter: $ SET LOGINS/INTERACTIVE=0 Re-enable logins after the installation is complete. Refer to the Introduction to VMS System Management for more information on logins. 9. Stop batch processes. Do not run any processes during the BASEstar installation. Users must log off of the system during the installation. To stop the batch queues, enter: $ STOP/QUEUE/NEXT queue_name 10.Stop the BASEstar system. If performing an upgrade of existing BASEstar software, ensure the current version of the system is not running. Stopping the BASEstar system also stops device connection management and all user-written BASEstar applications. To stop the BASEstar system, enter: $ BSTAR STOP SYSTEM 11.Close the library database (upgrades only). Before backing up the system disk or reinstalling BASEstar library software, you must close the library database using the following command: $ @SYS$MANAGER:BCCLIB$CLOSE This command procedure ensures that all information in the library global sections has been copied to the disk-based library database files. It then closes the database files and removes the library global sections from memory. Introduction 1-15 12.Back up the system disk. Back up the system disk before installing the BASEstar software. This backup is a protection in the event of disk corruption or accidental changes or deletions during installation. The procedure for backing up the system is described in the VMS Backup Utility Manual. 13.Verify logical names (upgrades only). Logical names reflect where previous versions of BASEstar software were installed. Define these logical names so the installation procedure can locate the files that need to be upgraded. If upgrading your BASEstar system, ensure the logical names BCC$SYSTEM and BCC$SYSDATA are defined by entering the following commands: $ SHOW LOGICAL BCC$SYSTEM $ SHOW LOGICAL BCC$SYSDATA If the logical names are not already defined, define them by executing the SYS$STARTUP:BCC$STARTUP.COM command procedure. If upgrading BASEstar device connection management, ensure the logical name ILAN$SYSTEM is defined in the system startup file by entering the following command: $ SHOW LOGICAL ILAN$SYSTEM If the logical name is not already defined, define it by executing the SYS$STARTUP:ILAN$STARTUP.COM command procedure. 1-16 Introduction ___________________________________________________________________ 1.4 VAXcluster Installation The BASEstar installation procedure for VAXcluster systems allows installation of BASEstar software on all systems from one node in a VAXcluster for those nodes sharing a system disk. The installation procedure prompts you to indicate if this is a single node or a VAXcluster installation. If you choose cluster installation, the installation procedure prompts you to provide information about each node in the cluster and installs appropriate BASEstar software as specified for the configuration. Step-by-step instructions for VAXcluster installation are provided in Chapter 2. ! Installation procedures Introduction 1-17 _____________________________________________________________________ Chapter 2 Installation This chapter describes the step-by-step installation of BASEstar software. It also contains a list of error messages that may appear during installation and provides a description of recovery procedures for each error. BASEstar software components are installed using a combination of four installation procedures: 1. Single node installation or VAXcluster installation procedure 2. Device connection management installation procedure 3. Library installation procedure 4. Utility installation procedure Begin by reading the instructions for installing BASEstar software on either a single node or on a VAXcluster system, whichever applies to your installation. Proceed by following the instructions for the installation of BASEstar device connection management, library management, and utility software, all of which are optional installations. Refer to Appendix A for sample installation procedures. All installation procedures are designed for new and upgrade installations. NOTE: It is strongly recommended that system managers read the BASEstar for VMS Release Notes before performing an upgrade installation.) Installation 2-1 Be prepared to provide the following information during the installation. __________________________________________________________________ Step_#______Information_to_prepare_before_installation..._________ 1. _____ BCC$SPECIFIC directory location 2. _____ Global name server or name dispatcher selection 3. _____ Local name file, point file, and group file estimated sizes for your BASEstar system 4. _____ BCC$COMMON directory location (VAXcluster installation only) 5. _____ Names of the global name server nodes and size of ____________global_name_file______________________________________ During the installation procedure, you are asked to give responses to questions. Type Y for yes or N for no to respond to a question and press or just press to select the default response. You can type a question mark and press after any prompt to receive on-line help. 2-2 Installation NOTE: DECnet software must be running during the installation. Do not shut down the network for installation. Even if you do not have a DECnet license and your system is not networked, DECnet must be configured and running to install BASEstar software. ___________________________________________________________________ 2.1 Installing BASEstar Software This section describes how to install BASEstar software. If you are installing BASEstar software on a single node, follow the installation procedure in Section 2.1.1. To install BASEstar software on a VAXcluster system, follow the installation procedure in Section 2.1.2. 2.1.1 BASEstar Single Node Installation BASEstar software installation consists of the following steps: 1. Log in to the system manager's account. 2. Set the default directory to SYS$UPDATE: $ SET DEFAULT SYS$UPDATE 3. Invoke VMSINSTAL. $ @VMSINSTAL BCC030 ddcu: where BCC030 is the BASEstar product name and version and ddcu: is the name of the disk or tape drive containing the software kit. Installation 2-3 4. When you invoke VMSINSTAL, the system displays the following: VAX/VMS Software Product Installation Procedure V5.3-1 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. 5. VMSINSTAL asks if you are satisfied with the backup of your system disk: * Are you satisfied with the backup of your system disk [YES]? Enter Y or N and press . The procedure displays the following: The following products will be processed: BCC V3.0 Beginning installation of BCC V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A .... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. 6. The procedure prompts to ensure you have the corrct BASEstar license installed on the system. Press if the license is already installed. If not, halt the installation and install the BASEstar license. BASEstar Kernel Version 3.0 Installation Procedure -------------------------------------------------- BASEstar requires one of the following licenses to be registered and loaded on all nodes on which BASEstar will run: 2-4 Installation Product Producer Release Date --------------- -------- ------------ [1] BASESTAR DEC 6-Mar-1991 [2] BASESTAR-RT DEC 6-Mar-1991 [3] BASESTAR-LTD DEC 6-Mar-1991 [4] BASESTAR-RT-LTD DEC 6-Mar-1991 * Which of the above licenses will be used? [1]: Product: BASESTAR Producer: DEC Release Date: 6-MAR-1991 * Does this product have an authorization key registered and loaded? y 7. The procedure prompts you to indicate if this is a single node or VAXcluster installation. This section provides the description of the single node installation only. This installation allows for either a cluster installation or a single node installation. The cluster installation option can only be chosen for nodes that share a cluster common system disk. * Do you want to install BASEstar on just one node [YES]? Press for a single node installation. %BCC-I-SYSCONFIG, Processing node nodename . . . 8. The procedure installs BASEstar software and asks if you want to install additional capabilities. You can optionally install data management software, external data support, and the menu interface now, or in an update installation. For example, if this is a new installation, the following text displays: Installation 2-5 This is a new BASEstar installation. The BASEstar CORE must be installed, but the Data Management and Menu System subsystems are optional. * Do you want to install BASEstar Data Management [YES]? Enter Y or N and press . VMSINSTAL asks if you want to install External Data Support: * Do you want to install BASEstar External Data Support [YES]? Enter Y or N and press . VMSINSTAL asks if you want to install the Menu System: * Do you want to install BASEstar Menu System [YES]? Enter Y or N and press . 9. VMSINSTAL asks for a directory location for the BASEstar command and data files: A location must be chosen for the BCC$SPECIFIC directory. By default, BASEstar data and command files are installed in SYS$SPECIFIC:[BCC$SPECIFIC]. This specification may be overridden if desired. * Enter the BASEstar specific directory specification [SYS$SPECIFIC:[BCC$SPECIFIC]]: If you do not specify a directory name, the BASEstar files are installed into the [BCC$SPECIFIC] directory under the system specific root directory. If you enter a different directory, be sure it resides on a permanently mounted disk. (Since these files are data and command files, the system disk may not be an appropriate location.) If installing on a VAXcluster node and you do not use the system disk, specify a unique directory name within the VAXcluster system. Verify the directory name specified: * Is directory [directory_name_you_typed] correct [YES]? 2-6 Installation 10.Specify whether the system is to be configured as a global name server or message dispatcher. To perform global name operations, at least one BASEstar system in the network must be a global name server. VMSINSTAL asks: * Do you want this system to be configured as a Global Name Server [YES]? If you enter Y, the system is a global name server. If you enter N, the system is a name dispatcher. 11.Select a target size for the following data files: BCC$POINT_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 POINTS 500 POINTS 840 [2] 2,000 POINTS 1,000 POINTS 2,223 [3] 10,000 POINTS 5,000 POINTS 10,675 [4] 30,000 POINTS 10,000 POINTS 27,219 * Enter BCC$POINT_FILE size [1]: Installation 2-7 BCC$GROUP_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 GROUPS 500 GROUPS 819 [2] 2,000 GROUPS 1,000 GROUPS 2,223 * Enter BCC$GROUP_FILE size [1]: BCC$LOCAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$LOCAL_NAME_FILE size [1]: 12.Choose a location for the BCC$COMMON directory. By default, the BASEstar executable files are installed in SYS$COMMON: [BCC$COMMON]. This specification may be overridden if desired. A location must be chosen for the BCC$COMMON directory. By default, BASEstar executable files are installed in SYS$COMMON:[BCC$COMMON]. This specification may be overridden if desired. * Enter the BASEstar common directory specification [SYS$COMMON:[BCC$COMMON]]: * Is directory SYS$COMMON:[BCC$COMMON] correct [YES]? The node names of all BASEstar Global Name Server systems with which this node will work must now be entered. These names are required for both global name server systems and for name dispatcher systems. 2-8 Installation 13.Enter the node names of all the BASEstar global name server systems with which this node will work. These names are required for both global name server systems and name dispatcher systems. * Enter a Global Name Server node name, to end list: nodename * Enter a Global Name Server node name, to end list: The value of the BASEstar parameter BCC$QUORUM is established from the list of global name servers entered; the following is displayed: %BCC-I-QUORUMSET, Global server quorum will be set to n. If the above quorum value is not consistent with other Global Name Server systems in the same BASEstar cluster, the value of BCC$QUORUM should be changed after the installation is finished and before BASEstar is started on this node for the first time. 14.Choose a target size for the global name file on the global name server systems: BCC$GLOBAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$GLOBAL_NAME_FILE size [1]: Installation 2-9 15.After all prompts have displayed, the following appears: The installation procedure has no further questions to ask and can continue from this point without user assistance. The installation time will vary depending on the number of nodes selected for installation and the type of processor on which the installation is being done. This installation creates an identifier name BCC$USER, which is used to control access to the BCC$SYSDATA directory and the data files contained in that directory. After the installation is finished, the VMS Authorize Utility must be used to grant this identifier to all accounts that will use BASEstar. The installation procedure restores the savesets, creates system directories, and displays the following: $VMSINSTAL-I-RESTORE, Restoring product save set B . . . $VMSINSTAL-I-RESTORE, Restoring product save set C . . . $VMSINSTAL-I-RESTORE, Restoring product save set D . . . $VMSINSTAL-I-RESTORE, Restoring product save set E . . . %BCC-I-INSTALLNODE, Installing BASEstar on node nodename . . . %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[BCC$COMMON]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[SYS0.BCC$SPECIFIC]. %BCC-I-STARTCORE, BASEstar CORE installation beginning on nodename. This installation places a file name BCC$STARTUP.COM in the directory SYS$SPECIFIC:[SYS$STARTUP] in each system root on which this installation is being performed. The SYSTARTUP_V5.COM file should be edited to invoke this startup file when the system boots. %BCC-I-STARTDMGT, BASEstar Data Management installation beginning on nodename 2-10 Installation %BCC-I-STARTDMGT, BASEstar External Data Support installation beginning on nodename %BCC-I-STARTMENU, BASEstar Menu System installation beginning on nodename. The following UAF parameters should be checked on all accounts that will use BASEstar: ASTLM BIOLM BYTLM DIOLM ENQLM FILLM PGFLQUO PRCLM TQELM WSDEF WSEXTENT WSQUO Refer to the installation guide for recommended minimum values for these parameters. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... The BASEstar system disk directories are established, the startup command procedure is created, and the installation verification procedure (IVP) is run. BASEstar Kernel V3.0 Installation Verification Procedure %BCCIVP-I-CORESTART, CORE verification starting on node nodename. %BCCIVP-I-PASS, CORE data files check passed %BCCIVP-I-PASS, CORE command files check passed %BCCIVP-I-PASS, CORE executable files check passed %BCCIVP-I-PASS, CORE support files check passed %BCCIVP-I-PASS, CORE system files check passed %BCCIVP-I-PASS, CORE parameter check passed %BCCIVP-I-DMGTSTART, DMGT verification starting on node nodename %BCCIVP-I-PASS, DMGT file check passed %BCCIVP-I-EXTMAPSTART, External Data Server verification starting on node nodename %BCCIVP-I-PASS, External Data Server file check passed Installation 2-11 %BCCIVP-I-MENUSTART, MENU verification starting on node nodename %BCCIVP-I-PASS, Menu System file check passed %BCCIVP-I-PASS, Menu System command check passed %BCCIVP-I-PASS, Menu System menu check passed BASEstar V3.0 IVP completed successfully 16.When the IVP completes, the following message is displayed: Installation of BCC V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm The BASEstar single node installation is complete. Continue with instructions in this section to install additional BASEstar software. 2.1.2 BASEstar VAXcluster Installation This section describes how to perform an installation for multiple nodes. The BASEstar VAXcluster installation consists of the following steps: 1. Log in to the system manager's account. 2. Set the default directory to SYS$UPDATE: $ SET DEFAULT SYS$UPDATE 3. Invoke VMSINSTAL: $ @VMSINSTAL BCC030 ddcu: where BCC030 is the BASEstar product name and ddcu: indicates the disk or tape drive containing the software kit. 2-12 Installation 4. When you invoke VMSINSTAL, the system displays the following: VAX/VMS Software Product Installation Procedure V5.3-1 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. 5. VMSINSTAL asks if you are satisfied with the backup of your system disk: * Are you satisfied with the backup of your system disk [YES]? Enter Y or N and press . The procedure displays the following: The following products will be processed: BCC V3.0 Beginning installation of BCC V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A .... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. 6. The procedure first prompts to ensure you have the correct BASEstar license installed on the system. Press if the license is already installed. If not, halt the installation and install the BASEstar license. BASEstar Kernel Version 3.0 Installation Procedure -------------------------------------------------- BASEstar requires one of the following licenses to be registered and loaded on all nodes on which BASEstar will run: Installation 2-13 Product Producer Release Date --------------- -------- ------------ [1] BASESTAR DEC 6-Mar-1991 [2] BASESTAR-RT DEC 6-Mar-1991 [3] BASESTAR-LTD DEC 6-Mar-1991 [4] BASESTAR-RT-LTD DEC 6-Mar-1991 * Which of the above licenses will be used? [1]: Product: BASESTAR Producer: DEC Release Date: 6-MAR-1991 * Does this product have an authorization key registered and loaded? y 7. The procedure asks if you want to install on a single node. This installation allows for either a cluster installation or a single node installation. The cluster installation option can only be chosen for nodes that share a cluster common system disk. * Do you want to install BASEstar on just one node [YES]? N Enter N and press to perform a VAXcluster installation. 8. You are prompted to enter each VAXcluster node name. Press after each node name. * Enter a node name, to end list: nodename1 %BCC-I-SYSINFO, Verifying node information... * Enter a node name, to end list: nodename2 %BCC-I-SYSINFO, Verifying node information... * Enter a node name, to end list: 2-14 Installation %BCC-I-SYSCONFIG, Processing node nodename1... NOTE: The following installation questions are asked for each node specified as part of the VAXcluster. After all questions are answered, the installation verification procedure displays messages indicating software installed and checks passed for each node as well. 9. The procedure installs BASEstar software and asks if you want to install additional capabilities. You can optionally install data management software, external data support, and the menu interface now or in an update installation. For example, if this is a new installation, the following text displays: This is a new BASEstar installation. The BASEstar CORE must be installed, but the Data Management and Menu System subsystems are optional. * Do you want to install BASEstar Data Management [YES]? Enter Y or N and press . VMSINSTAL asks if you want to install External Data Support: * Do you want to install BASEstar External Data Support [YES]? Enter Y or N and press . VMSINSTAL asks if you want to install the Menu System: * Do you want to install BASEstar Menu System [YES]? Enter Y or N and press . 10.VMSINSTAL asks for a directory location for the BASEstar command and data files: A location must be chosen for the BCC$SPECIFIC directory. By default, BASEstar data and command files are installed in SYS$SPECIFIC:[BCC$SPECIFIC]. This specification may be overridden if desired. Installation 2-15 * Enter the BASEstar specific directory specification [SYS$SPECIFIC:[BCC$SPECIFIC]]: If you do not specify a directory name, the BASEstar files are installed into the [BCC$SPECIFIC] directory under the system specific root directory. If you enter a different directory, be sure it resides on a permanently mounted disk. (Since these files are data and command files, the system disk may not be an appropriate location.) If installing on a VAXcluster node and you do not use the system disk, specify a unique directory name within the VAXcluster system. Verify the directory name specified: * Is directory [directory_name_you_typed] correct [YES]? 11.Specify whether the system is to be configured as a global name server or a message dispatcher. To perform global name operations, at least one BASEstar system in the network must be a global name server. VMSINSTAL asks: * Do you want this system to be configured as a Global Name Server [YES]? If you enter Y, the system is a global name server. If you enter N, the system is a name dispatcher. 12.Select a target size for the following data files: BCC$POINT_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE 2-16 Installation [1] 500 POINTS 500 POINTS 840 [2] 2,000 POINTS 1,000 POINTS 2,223 [3] 10,000 POINTS 5,000 POINTS 10,675 [4] 30,000 POINTS 10,000 POINTS 27,219 * Enter BCC$POINT_FILE size [1]: BCC$GROUP_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 GROUPS 500 GROUPS 819 [2] 2,000 GROUPS 1,000 GROUPS 2,223 * Enter BCC$GROUP_FILE size [1]: BCC$LOCAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$LOCAL_NAME_FILE size [1]: 13.Choose a location for the BCC$COMMON directory. By default, the BASEstar executable files are installed in SYS$COMMON: [BCC$COMMON]. This specification may be overridden if desired. A location must be chosen for the BCC$COMMON directory. By default, BASEstar executable files are installed in SYS$COMMON:[BCC$COMMON]. This specification may be overridden if desired. * Enter the BASEstar common directory specification [SYS$COMMON: [BCC$COMMON]]: * Is directory SYS$COMMON:[BCC$COMMON] correct [YES]? Installation 2-17 The node names of all BASEstar Global Name Server systems with which this node will work must now be entered. These names are required for both global name server systems and for name dispatcher systems. 14.Enter the node names of all the BASEstar global name server systems with which this node will work. These names are required for both global name server systems and name dispatcher systems. * Enter a Global Name Server node name, to end list: The value of the BASEstar parameter BCC$QUORUM is established from the list of global name servers entered; the following is displayed: %BCC-I-QUORUMSET, Global server quorum will be set to n. If the above quorum value is not consistent with other Global Name Server systems in the same BASEstar cluster, the value of BCC$QUORUM should be changed after the installation is finished and before BASEstar is started on this node for the first time. 15.Choose a target size for the global name file on the global name server systems: BCC$GLOBAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$GLOBAL_NAME_FILE size [1]: 2-18 Installation 16.After all prompts have displayed, the following displays: The installation procedure has no further questions to ask and can continue from this point without user assistance. The installation time will vary depending on the number of nodes selected for installation and the type of processor on which the installation is being done. This installation creates an identifier name BCC$USER, which is used to control access to the BCC$SYSDATA directory and the data files contained in that directory. After the installation is finished, the VMS Authorize Utility must be used to grant this identifier to all accounts that will use BASEstar. The installation procedure restores the savesets, creates system directories, and displays the following information for each node on which you are installing BASEstar software: $VMSINSTAL-I-RESTORE, Restoring product save set B . . . $VMSINSTAL-I-RESTORE, Restoring product save set C . . . $VMSINSTAL-I-RESTORE, Restoring product save set D . . . $VMSINSTAL-I-RESTORE, Restoring product save set E . . . %BCC-I-INSTALLNODE, Installing BASEstar on node nodename . . . %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[BCC$COMMON]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[SYS0.BCC$SPECIFIC]. %BCC-I-STARTCORE, BASEstar CORE installation beginning on nodename. This installation places a file name BCC$STARTUP.COM in the directory SYS$SPECIFIC:[SYS$STARTUP] in each system root on which this installation is being performed. The SYSTARTUP_V5.COM file should be edited to invoke this startup file when the system boots. %BCC-I-STARTDMGT, BASEstar Data Management installation beginning on nodename Installation 2-19 %BCC-I-STARTDMGT, BASEstar External Data Support installation beginning on nodename %BCC-I-STARTMENU, BASEstar Menu System installation beginning on nodename. The following UAF parameters should be checked on all accounts that will use BASEstar: ASTLM BIOLM BYTLM DIOLM ENQLM FILLM PGFLQUO PRCLM TQELM WSDEF WSEXTENT WSQUO Refer to the installation guide for recommended minimum values for these parameters. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... The BASEstar system disk directories are established, the startup command procedure is created, and the installation verification procedure (IVP) is run. When the IVP completes, the following displays: Installation of BCC V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm The BASEstar VAXcluster installation is complete. Continue with instructions in this section to install additional BASEstar software. ___________________________________________________________________ 2.2 BASEstar Device Connection Management Installation Procedure This section describes how to install BASEstar device connection management software. If your main BASEstar installation did not include installing the menu interface, the device connection management installation cannot install or update the device connection management menus. 2-20 Installation NOTE: Delete all BASEstar for VMS, V2.0 device access software from your system before installing BASEstar device connection management software. The BASEstar device connection management installation consists of the following steps: 1. Log in to the system manager's account. 2. Set the default directory to SYS$UPDATE: $ SET DEFAULT SYS$UPDATE 3. Invoke VMSINSTAL: $ @VMSINSTAL DCM030 ddcu: where DCM030 is the device connection management product name and version and ddcu: is the disk or tape drive containing the software kit. When you invoke VMSINSTAL, the system displays the following: VAX/VMS Software Product Installation Procedure V5.3 It is dd-mm-19yy at hh:mm. Enter a question mark (?) at any time for help. 4. VMSINSTAL verifies you are logged into the system manager's account, you have adequate account quotas for installing layered products, DECnet software is not running on the system, and all other users are logged off the system. If these conditions are not met, VMSINSTAL tells you which conditions were not met and prompts as follows: Installation 2-21 %VMSINSTAL-W-DECNET, Your DECnet network is up and running. *Do you want to continue anyway [NO]? DECnet must be running to install the device connection management software. To continue, enter Y and press . 5. The installation procedure prompts you to verify that you are satisfied with your system disk backup: *Are you satisfied with the backup of your system disk [YES]? If you have not backed up your system, enter N and refer to Section 1.3. If satisfied with your back up, press to continue. The installation continues with the following: The following products will be processed: DCM V3.0 Beginning installation of DCM V3.0 at hh:mm %VMSINSTAL-I-RESTORE, restoring product saveset A... 6. You are prompted to indicate if you want to run the installation verification procedure after installation. *Do you want to run the IVP after the installation [YES]? If you want to run the installation verification procedure (IVP), enter Y. If you have not yet installed BASEstar software on all the systems, enter N and press . 7. The installation procedure prompts: *Do you want to purge files replaced by this installation? [YES]? 2-22 Installation If the installation is an upgrade, delete the previous versions of the files created by the installation by entering Y. Site- specific files or VMS installed images are not purged. The files not purged include: o SYS$STARTUP:ILAN$STARTUP.COM o BCC$SYSDATA:ILAN$SYSTEM.STARTUP.COM o SYS$COMMON:[SYSMSG]:ILAN$MSG.EXE o SYS$COMMON:[SYSLIB]:ILAN$SHR.EXE o SYS$COMMON:[SYSLIB]:ILAN$SERVER_SHR.EXE o SYS$COMMON:[SYSLIB]:ILAN$CLI_SHR.EXE 8. VMSINSTAL then installs sample device access software and displays the following: As part of this installation, Device Access Software for simple terminal devices, bar code readers (RS-232 devices) and Network devices are provided along with BASEstar Device Connect Management. The configuration template file, ILAN_CFG_TT_SUPPORT.COM, is used to define the paths, types, and devices for terminal devices and the pseudo device. Edit this file, as necessary, to reflect your specific site configuration. During installation it will be placed in the directory BCC$SYSDATA:. The configuration template file for Network support, DCM_NET_CONFIG.TEMPLATE, is used to define Network DAS compatible paths, types, and devices. Edit this file, as necessary, to reflect your specific site configuration. During installation it will be placed in the directory BCC$SYSDATA:. Installation 2-23 9. Select a file size for the physical point data file. Enter the correct choice from the menu and press . During a new installatin, you must choose a target size for the PHYSICAL POINT data file: ILAN$PHYPOINT_FILE ================== Initial Allocation Extend Allocation File Size [1] 500 Phypoints 500 Phypoints 1,251 Blocks [2] 2,000 Phypoints 1,000 Phypoints 3,333 Blocks [3] 10,000 Phypoints 5,000 Phypoints 15,744 Blocks [4] 20,000 Phypoints 10,000 Phypoints 32,604 Blocks * Enter ILAN$PHYPOINT_FILE size [1]: 10.Once all prompts have displayed, the following displays: The installation procedure has no further questions to ask and can continue from this point without user assistance. The rest of the installation will take approximately 25 minutes depending on system load and configuration. Now checking the BASEstar Parameter file for DCM parameters. The BASEstar DCM Parameters have been successfully installed The installation procedure is continuing... The BASEstar DCM Menus have been successfully installed The installation procedure is continuing... %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[BCC$COMMON.EXAMPLES.ILAN$EXAMPLES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[BCC$COMMON.RS232_EXAMPLE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[BCC$COMMON.NCT_EXAMPLE] 2-24 Installation ILAN$STARTUP.COM, the startup command procedure, is used to set up the environment for device connection management. During installation it will be placed in the [SYS$STARTUP] directory of the system root on which this installation is being performed. SYS$MANAGER: SYSTARTUP_V5.COM, your system startup procedure, should be modified to invoke this procedure when the system boots. However, it will not be necessary to reboot the system after the installation, since this procedure is invoked as part of the installation. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 11.When the IVP runs, the following displays: BASEstar DCM V3.0 Installation Verification Procedure (IVP) starting %ILANIVP-I-PASS, file check passed %ILANIVP-I-PASS, installed image check passed %ILANIVP-I-PASS, parameter check passed BASEstar DCM V3.0 IVP completed successfully. Installation of DCM V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm The BASEstar device connection management installation is complete. Continue with instructions in this chapter for installing additional BASEstar software. ___________________________________________________________________ 2.3 BASEstar Library Installation Procedure This section describes how to install BASEstar library software. The BASEstar library management system is designed to provide centralized management of a variety of library files. Therefore, it should be installed on only one node within your network of BASEstar systems. Installation 2-25 NOTE: Since the library is a menu-based system, it cannot be installed if your BASEstar installation did not include the menu system. The BASEstar library installation consists of the following steps: 1. Log in to the system manager's account. 2. Set the default directory to SYS$UPDATE. $ SET DEFAULT SYS$UPDATE 3. Invoke VMSINSTAL with the following command and kit name: $ @vmsinstal bcclib030 ddcu: where BCCLIB030 is the BASEstar library kit name and version number and ddcu: is the disk or tape drive containing the software kit. VAX/VMS Software Product Installation Procedure V5.3 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. The following products will be processed: BCCLIB V3.0 Beginning installation of BCCLIB V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully move. The procedure prompts you to choose whether you want to run the installation verification procedure after installation. If this is an upgrade installation you are prompted to choose whether to purge files replaced by installation. 2-26 Installation BASEstar Library System V3.0 Installation Procedure --------------------------------------------------- * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? 4. The procedure prompts you to choose a directory to install library software. Enter the library directory specification and press or press to specify the [SYS$SPECIFIC:[BCC$SPECIFIC.LIBRARY]]: directory. This is a new Library installation. A location must be chosen for the directory which will contain the directory structure and the actual files referenced by the BASEstar Library's file repository system on this node. The default directory is SYS$SPECIFIC:[BCCLIB$SPECIFIC] and may be overridden if desired. The device on which this directory resides must always be mounted and available. * Enter the library file repository directory specification [SYS$SPECIFIC:[BCCLIB$SPECIFIC]]: 5. Verify the directory name was correctly entered by pressing . If you enter N and press the installation procedure prompts again for the library directory specification. * Is directory correct [YES]? %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SPECIFIC:[BCCLIB$SPECIFIC]. 6. Enter the directory specification for the library database file and press or press to specify the [SYS$SPECIFIC:[BCCLIB$SPECIFIC]] directory. Installation 2-27 A location must be chosen for the library database file. This is the file which maintains all of the relationships and attributes for the libraries, groups, directories, and files. The default directory for this file is SYS$SPECIFIC:[BCCLIB$SPECIFIC] and may be overridden if desired. The device on which this directory resides must always be mounted and available. * Enter the library database file location directory specification [SYS$SPECIFIC:[BCCLIB$SPECIFIC]]: 7. Verify the directory name was correctly entered by pressing . If you enter N and press , the installation procedure prompts again for the library directory specification. * Is directory correct [YES]? At this point, the installation procedure continues without further input as follows: The installation procedure has no further questions to ask and can continue from this point without user assistance. The installation time will vary depending on the type of processor on which the installation is being done. This installation places a file named BCCLIB$STARTUP.COM in the directory SYS$SPECIFIC:[SYS$STARTUP]. The command file SYS$STARTUP_V5.COM file should be edited to invoke this startup file when the system boots. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Expansion Bytes <250000> BASEstar Library V3.0 Installation Verification Procedure BASEstar Library V3.0 IVP completed successfully Installation of BCCLIB V3.0 completed at HH:MM VMSINSTAL procedure done at hh:mm 2-28 Installation The BASEstar library installation is complete. Continue with instructions in this chapter for installing additional BASEstar software. ___________________________________________________________________ 2.4 BASEstar Utilities Installation Procedure This section describes how to install BASEstar utilities, including: o The BCC$BASEGEN command procedure which provides suggested settings for BASEstar and SYSGEN parameters, as well as VMS process quotas. Refer to the BASEstar for VMS Configuration and Tuning Guide for information on how to use this utility. o Text message files if conversion to a non-English language is necessary. These services can also be used to copy the appropriate files into new BASEstar directories. o VMS version number mismatch software resolves problems with an incorrect version of VMS software installed on a system. The BASEstar utilities installation consists of the following steps: 1. Log in to the system manager's account. 2. Set the default directory to SYS$UPDATE: $ SET DEFAULT SYS$UPDATE 3. Invoke VMSINSTAL: $ @VMSINSTAL BCCUTL ddcu: Installation 2-29 where BCCUTL is the utilities product name and ddcu: is the name of the tape or disk drive containing the software kit. 4. When you invoke VMSINSTAL, the system displays the following: VAX/VMS Software Product Installation Procedure V5.3-1 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. 5. VMSINSTAL asks if you are satisfied with the backup of your system disk: * Are you satisfied with the backup of your system disk [YES]? Enter Y or N and press . The procedure displays the following: The following products will be processed: BCCUTL V3.0 Beginning installation of BCCUTL V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A .... Installing BASEstar CORE Utilities Kit This kit provides the following optional BASEstar files: BCC$SYSTEM directory: BCC$GET_TEXT_FILE.EXE BCC$PUT_TEXT_FILE.EXE BCC$BASEGEN.COM SYS$TEST directory: BCC$UTL_IVP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 2-30 Installation BASEstar Utility V3.0 Installation Verification Procedure %BCCUTL-I-PASS, Utility file check passed Installation of BCCUTL V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm The BASEstar utilities installation is complete. Log out and proceed to Chapter 3 to begin post-installation tasks. ___________________________________________________________________ 2.5 Installation Messages This section describes the installation message formats and the messages you may receive during the BASEstar installation. 2.5.1 Message Format BASEstar installation messages display in the following format: %FACILITY-L-IDENT, TEXT where: FACILITY The facility or component name. The facility references are %IVP and %VMSINSTALL. Installation 2-31 L The severity indicator codes including: o S for success. The procedure generating the condition value completed successfully. o I for informational. The procedure generating the condition value successfully completed, but has some further explanatory information. o W for warning. A procedure returns data or completes an operation but the results might be incomplete or not what the user expected. o E for error. An error has occurred. The operation was attempted but could not be completed. Any returned information should be regarded as invalid. o F for severe error. A severe error occurred and the attempted operation was not complete. Any information returned is invalid and further processing will be incorrect. IDENT An abbreviation of the message text. The message descriptions are alphabetized according to this abbreviation. TEXT The explanation of the message. 2.5.2 Message Listing The installation messages are in alphabetical order by the IDENT abbreviation. 2-32 Installation BADBCC, The installed version of BASEstar is obsolete. Explanation: Error. An old version of BASEstar software is installed. User Action: Install BASEstar for VMS, V3.0. BADBCCVER, This kit only updates version V3.0 of BASEstar. Explanation: Error. The distribution kit being installed can only be used to update V3.0 of BASEstar for VMS from V2.0 systems. User Action: If you do not already BASEstar for VMS, V2.0 on your system, contact your Digital sales representative. BADDCM, The installed version of BASEstar DCM is obsolete. Explanation: Error. The installed version of BASEstar device connection management software is earlier than V2.0. User Action: You can only upgrade V2.0 BASEstar systems to V3.0. Contact your Digital sales representative for assistance if you do not own BASEstar for VMS, V2.0. BADID, Invalid DECnet ID, please try again. Explanation: Error. You entered an incorrect DECnet ID. User Action: Enter the correct DECnet ID. BADVMS, You must be running at least V5.3 of VMS Explanation: Error. The user is not running VMS V5.3 or later. User Action: Install VMS V5.3 or later. Installation 2-33 BCCRUNNING, BASEstar cannot be running during an installation. Explanation: Error. BASEstar software cannot be running during an installation. User Action: Stop BASEstar software on the node. COMMON, Cluster installations require different roots. Explanation: Error. An attempt was made to specify the same root directory for both BCC$COMMON and BCC$SPECIFIC on a VAXcluster installation. User Action: Install BASEstar software using directory locations not in the same system root. FAIL, Not all processes were started correctly. Explanation: Error. IVP failed because it could not start the system. User Action: Verify that BASEstar software is installed correctly. Check the log file, make any corrections, and restart the installation. FAIL, Not all processes were stopped correctly. Explanation: Error. IVP failed because it could not stop the device connection management system correctly. User Action: Start BASEstar software and verify that processes are running correctly (not in local event flag (LEF) state). Also, check that SYSGEN parameters are set correctly. 2-34 Installation ILANFAIL, The installation of BASEstar device connection management V3.0 has failed. Explanation: Error. This message informs you that VMSINSTAL has failed for BASEstar device connection management V3.0. This message displays with other error messages. User Action: Take the appropriate action for the error condition indicated. INSFBLOCKS, Insufficient system disk free blocks for installation. Explanation: Error. There are not enough free blocks on the system disk for this installation. User Action: Free some blocks and restart the installation. MISSING, A required device connection management data file is missing. Explanation: Informational. The installation procedure cannot find a required data file. User Action: Try to locate the missing data file. NEEDBCC, BASEstar is not installed on this system. Explanation: Informational. BASEstar for VMS, V3.0 software is not installed. User Action: Install BASEstar for VMS V3.0. NEEDBCC030, Please install BASEstar V3.0 or a later version. Explanation: Informational. BASEstar for VMS, V3.0 is not installed. User Action: Install BASEstar for VMS, V3.0 or later. Installation 2-35 NEEDDCM030, Please install Product BASEstar DCM V3.0 or later. Explanation: Informational. BASEstar device connection management software V3.0 is not installed. User Action: Install V3.0 of BASEstar device connection management software. NEEDDIR, Unable to locate directory for new ILAN files. Explanation: Error. The BASEstar directories could not be found. User Action: Ensure that BASEstar software is installed. NEEDLICENSE, A BASEstar license is required for installation. Explanation: Error. The BASEstar license was not installed. User Action: Install the correct BASEstar license before attempting to install BASEstar software. NETBLOCKS, BASEstar requires "nn" blocks after installation. Explanation: Error. Not enough free space exists on the disk. The number of disk blocks required by this installation is represented by "nn". User Action: Purge disk files or install the system on another disk that has adequate disk space. NETBLOCKS, Device Connect Management requires 9000 blocks after installation. Explanation: Error. Not enough free space exists on the disk. User Action: Purge disk files or install the system on another disk that has adequate disk space. 2-36 Installation NOALTROOT, BASEstar cannot be installed in an alternate system root. Explanation: Error. The installation command line indicated an alternate system root using the OPTIONS command. User Action: Restart the installation without this option. NODECNET, DECnet nodename cannot be translated. Explanation: Error. The nodename specified cannot be found in the DECnet database. User Action: Define the nodename and restart the installation. NODIR, The logical name BCC$SYSTEM or BCC$SYSDATA is not defined on the installed system. Explanation: Error. The logical name for the BASEstar directories is not defined. User Action: Check for the location of the directories to see if they exist. If they do, define the logical and restart the installation. If not, de-install BASEstar software and restart the installation. NOSHR, Shareable image file BCC$SHR.EXE was not found in SYS$LIBRARY. Explanation: Error. The shareable image file BCC$SHR.EXE could not be found in the appropriate directory. User Action: Locate the shareable image file, correct the situation, and restart the installation procedure. If the file cannot be found, contact your Digital sales representative. Installation 2-37 NOVAXFMS, VAX FMS V2.3 or higher is not installed on this system. Explanation: Warning. The BASEstar menu system is selected for installation, but FMS V2.3 or higher is not present on the system. User Action: The BASEstar menu system is not usable until FMS V2.3 or higher is installed. Install VAX FMS V2.3 or higher. OLDFMS, The installed version of VAX FMS is obsolete. Explanation: Warning. An old version of VAX FMS is present on the system. The BASEstar menu system requires a minimum of VAX FMS version V2.3 or higher. User Action: Install VAX FMS V2.3 or higher. REINIT, All DCM data files will be replaced. Explanation: Warning. One or more of the data files is missing; device connection management will create (or recreate) all data files. User Action: None. WHERESBASESTAR, The logical name BCC$SYSTEM is not defined. Explanation: Error. The BASEstar startup procedure did not create the BCC$SYSTEM logical. User Action: Invoke the BASEstar startup command file, located in SYS$MANAGER. Exit the BASEstar system and restart the device connection management installation. ! Post installation tasks 2-38 Installation _____________________________________________________________________ Chapter 3 Post Installation This chapter describes BASEstar post-installation tasks. When you have completed the installation procedures, log in to the system manager's account and perform the following: 1. Back up the system disk. Back up the system disk after installing BASEstar software. The procedure for backing up the system disk is described in the VMS Backup Utility Manual. 2. Verify minimum run-time SYSGEN parameters. Table 3-1 describes the SYSGEN parameters recommended for the minimum run-time BASEstar configuration. Post Installation 3-1 Table_3-1:__BASEstar_Minimum_SYSGEN_Parameters____________________ MODPARAMS.DAT_Entries______Minimum_Value__________________________ GBLSECTIONS 250 GBLPAGFIL 4096 GBLPAGES 18000 CTLPAGES 60 LOCKIDTBL 2048 RESHASHTBL 512 MAXPROCESSCNT 35 BALSETCNT 33 VIRTUALPAGECNT________________25000_______________________________ Table 3-2 describes the minimum run-time SYSGEN parameters recommended when the BASEstar library system is installed. Table_3-2:__Library_Minimum_SYSGEN_Parameters_____________________ MODPARAMS.DAT_Entries______Minimum_Value__________________________ GBLPAGES 45000 GBLSECTIONS 400 PROCSECTCNT 100 GBLPAGFIL 4096 3-2 Post Installation Table_3-2_(Cont.):__Library_Minimum_SYSGEN_Parameters_____________ MODPARAMS.DAT_Entries______Minimum_Value__________________________ CTLPAGES 60 LOCKIDTBL 2048 RESHASHTBL 512 MAXPROCESSCNT 35 BALSETCNT 33 VIRTUALPAGECNT 25000 WSMAX_________________________15000_______________________________ Since these values represent minimum BASEstar runtime SYSGEN parameter settings, you may need to adjust their values as required for systems larger than the minimum BASEstar hardware configuration or for systems running software in addition to BASEstar applications. For example, if you are using BASEstar library software and need to use large libraries, use the following steps to adjust the SYSGEN parameter GBLPAGES. a. Begin by running the VMS System Generation utility to view the current setting for the GBLPAGES parameter on your system as follows: $ SET DEF SYS$SYSTEM $ RUN SYSTEM SYSGEN>USE ACTIVE SYSGEN>SHOW GBLPAGES GBLPAGES 18000 SYSGEN>EXIT $ Post Installation 3-3 b. Edit the MODPARAMS.DAT file to increase the global pages available. If the GBLPAGES parameter is already set, change the current value to the desired value. If the parameter is not specified, you can add a line to the MODPARAMS.DAT file to specify your desired minimum amount as follows: MIN_GBLPAGES=45000 In this way, more global pages can be dynamically allocated if needed, however, your system will maintain a minimum number of global pages equal to your desired value. c. Run the AUTOGEN command procedure to update the new value. If you want a feedback report, enter the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK If you do not require feedback, enter the following command: $ @SYS$UPDATE:AUTOGEN GETDATA SETPARAMS NOFEEDBACK d. Once you have run the AUTOGEN procedure, you must shut down the system and reboot in order for the new parameter value to take effect. 3. Edit the system startup procedure. If you want BASEstar software to automatically start when the system boots, add the following line to the SYS$MANAGER:SYSTARTUP_V5.COM file: $ @SYS$STARTUP:BCC$STARTUP.COM To automatically start BASEstar device connection management when the system boots, add the following line to the SYS$MANAGER:SYSTARTUP_V5.COM file: $ @SYS$STARTUP:ILAN$STARTUP.COM 3-4 Post Installation To automatically start BASEstar library software when the system boots, add the following line to the SYS$MANAGER:SYSTARTUP_V5.COM file: $ @SYS$STARTUP:BCCLIB$STARTUP.COM For a new installation, this procedure creates the library database files and associated global sections. During an upgrade installation, this command procedure locates the existing database files and creates the library database global sections. 4. Select BASEstar users. Decide which VMS users require access to BASEstar software and grant them the BCC$USER identifier using the VMS AUTHORIZE utility. UAF> GRANT/IDENTIFIER BCC$USER username where username is the name of the user account. 5. Start BASEstar software. BASEstar software can be started from the SYSTEM account once it has been granted the BCC$USER identifier. It can also be started from any account having the privileges listed in Table 3-3. These privileges must be in the account's authorized privilege list and are added using the VMS Authorize utility: Table_3-3:__VMS_Privileges_Required_to_Start_BASEstar_Software____ ALTPRI DETACH LOG_IO NETMBX PHY_IO PSWAPM SHARE SYSGBL SYSLCK Post Installation 3-5 Table 3-3 (Cont.): VMS Privileges Required to Start BASEstar ____________________Software______________________________________ ____________SYSNAM______TMPMBX____________________________________ Though accounts used to start BASEstar require these privileges in their authorized privilege list, they do not require them in their default privilege list for security reasons. This list represents the minimum privileges needed by all BASEstar processes and applications. Some BASEstar processes may not need all privileges and can be started with only a subset. Whenever new applications need additional privileges not in this list, the additional privileges can be added to the account's authorized list. The new privileges are available after restarting BASEstar software. NOTE: The SYSTEM account must be granted the BCC$USER identifier regardless of whether it will be used to start BASEstar. Failure to grant the BCC$USER identifier to the SYSTEM account causes the BASEstar startup process to fail. To start BASEstar software, enter the following command at the DCL prompt: $ BSTAR START SYSTEM ! Sample Installation logs 3-6 Post Installation _____________________________________________________________________ Appendix A Sample BASEstar Installations This appendix contains sample installation procedures for BASEstar software. The dialogs are examples of the following types of BASEstar installations: o Single node o VAXcluster system o Upgrade o Device connection management o Library o Utility ___________________________________________________________________ A.1 Single Node This section displays a sample BASEstar single node installation. $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL BCC030 ddcu: VAX/VMS Software Product Installation Procedure V5.3-1 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Sample BASEstar Installations A-1 The following products will be processed: BCC V3.0 Beginning installation of BCC V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A .... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. BASEstar Kernel Version 3.0 Installation Procedure -------------------------------------------------- BASEstar requires one of the following licenses to be registered and loaded on all nodes on which BASEstar will run: Product Producer Release Date --------------- -------- ------------ [1] BASESTAR DEC 6-Mar-1991 [2] BASESTAR-RT DEC 6-Mar-1991 [3] BASESTAR-LTD DEC 6-Mar-1991 [4] BASESTAR-RT-LTD DEC 6-Mar-1991 * Which of the above licenses will be used? [1]: Product: BASESTAR Producer: DEC Release Date: 6-MAR-1991 * Does this product have an authorization key registered and loaded? y This installation allows for either a cluster installation or a single node installation. The cluster installation option can only be chosen for nodes that share a cluster common system disk. * Do you want to install BASEstar on just one node [YES]? %BCC-I-SYSCONFIG, Processing node nodename . . . This is a new BASEstar installation. The BASEstar CORE must be installed, but the Data Management and Menu System subsystems are optional. * Do you want to install BASEstar Data Management [YES]? A-2 Sample BASEstar Installations * Do you want to install BASEstar External Data Support [YES]? * Do you want to install BASEstar Menu System [YES]? A location must be chosen for the BCC$SPECIFIC directory. By default, BASEstar data and command files are installed in SYS$SPECIFIC:[BCC$SPECIFIC]. This specification may be overridden if desired. * Enter the BASEstar specific directory specification [SYS$SPECIFIC:[BCC$SPECIFIC]]: * Is directory [directory_name_you_typed] correct [YES]? * Do you want this system to be configured as a Global Name Server [YES]? BCC$POINT_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 POINTS 500 POINTS 840 [2] 2,000 POINTS 1,000 POINTS 2,223 [3] 10,000 POINTS 5,000 POINTS 10,675 [4] 30,000 POINTS 10,000 POINTS 27,219 * Enter BCC$POINT_FILE size [1]: BCC$GROUP_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 GROUPS 500 GROUPS 819 [2] 2,000 GROUPS 1,000 GROUPS 2,223 * Enter BCC$GROUP_FILE size [1]: BCC$LOCAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE Sample BASEstar Installations A-3 [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$LOCAL_NAME_FILE size [1]: A location must be chosen for the BCC$COMMON directory. By default, BASEstar executable files are installed in SYS$COMMON:[BCC$COMMON]. This specification may be overridden if desired. * Enter the BASEstar common directory specification [SYS$COMMON:[BCC$COMMON]]: * Is directory SYS$COMMON:[BCC$COMMON] correct [YES]? The node names of all BASEstar Global Name Server systems with which this node will work must now be entered. These names are required for both global name server systems and for name dispatcher systems. * Enter a Global Name Server node name, to end list: nodename * Enter a Global Name Server node name, to end list: %BCC-I-QUORUMSET, Global server quorum will be set to n. If the above quorum value is not consistent with other Global Name Server systems in the same BASEstar cluster, the value of BCC$QUORUM should be changed after the installation is finished and before BASEstar is started on this node for the first time. BCC$GLOBAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$GLOBAL_NAME_FILE size [1]: A-4 Sample BASEstar Installations The installation procedure has no further questions to ask and can continue from this point without user assistance. The installation time will vary depending on the number of nodes selected for installation and the type of processor on which the installation is being done. This installation creates an identifier name BCC$USER, which is used to control access to the BCC$SYSDATA directory and the data files contained in that directory. After the installation is finished, the VMS Authorize Utility must be used to grant this identifier to all accounts that will use BASEstar. $VMSINSTAL-I-RESTORE, Restoring product save set B . . . $VMSINSTAL-I-RESTORE, Restoring product save set C . . . $VMSINSTAL-I-RESTORE, Restoring product save set D . . . $VMSINSTAL-I-RESTORE, Restoring product save set E . . . %BCC-I-INSTALLNODE, Installing BASEstar on node nodename . . . %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[BCC$COMMON]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[SYS0.BCC$SPECIFIC]. %BCC-I-STARTCORE, BASEstar CORE installation beginning on nodename. This installation places a file name BCC$STARTUP.COM in the directory SYS$SPECIFIC:[SYS$STARTUP] in each system root on which this installation is being performed. The SYSTARTUP_V5.COM file should be edited to invoke this startup file when the system boots. %BCC-I-STARTDMGT, BASEstar Data Management installation beginning on nodename %BCC-I-STARTDMGT, BASEstar External Data Support installation beginning on nodename %BCC-I-STARTMENU, BASEstar Menu System installation beginning on nodename. The following UAF parameters should be checked on all accounts that will use BASEstar: Sample BASEstar Installations A-5 ASTLM BIOLM BYTLM DIOLM ENQLM FILLM PGFLQUO PRCLM TQELM WSDEF WSEXTENT WSQUO Refer to the installation guide for recommended minimum values for these parameters. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... BASEstar Kernel V3.0 Installation Verification Procedure %BCCIVP-I-CORESTART, CORE verification starting on node nodename. %BCCIVP-I-PASS, CORE data files check passed %BCCIVP-I-PASS, CORE command files check passed %BCCIVP-I-PASS, CORE executable files check passed %BCCIVP-I-PASS, CORE support files check passed %BCCIVP-I-PASS, CORE system files check passed %BCCIVP-I-PASS, CORE parameter check passed %BCCIVP-I-DMGTSTART, DMGT verification starting on node nodename %BCCIVP-I-PASS, DMGT file check passed %BCCIVP-I-EXTMAPSTART, External Data Server verification starting on node nodename %BCCIVP-I-PASS, External Data Server file check passed %BCCIVP-I-MENUSTART, MENU verification starting on node nodename %BCCIVP-I-PASS, Menu System file check passed %BCCIVP-I-PASS, Menu System command check passed %BCCIVP-I-PASS, Menu System menu check passed BASEstar V3.0 IVP completed successfully Installation of BCC V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm A-6 Sample BASEstar Installations ___________________________________________________________________ A.2 VAXcluster System This section displays a sample BASEstar VAXcluster installation. $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL BCC030 ddcu: VAX/VMS Software Product Installation Procedure V5.3-1 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: BCC V3.0 Beginning installation of BCC V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A .... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. BASEstar Kernel Version 3.0 Installation Procedure -------------------------------------------------- BASEstar requires one of the following licenses to be registered and loaded on all nodes on which BASEstar will run: Product Producer Release Date --------------- -------- ------------ [1] BASESTAR DEC 6-Mar-1991 [2] BASESTAR-RT DEC 6-Mar-1991 [3] BASESTAR-LTD DEC 6-Mar-1991 [4] BASESTAR-RT-LTD DEC 6-Mar-1991 * Which of the above licenses will be used? [1]: Product: BASESTAR Producer: DEC Release Date: 6-MAR-1991 Sample BASEstar Installations A-7 * Does this product have an authorization key registered and loaded? y This installation allows for either a cluster installation or a single node installation. The cluster installation option can only be chosen for nodes that share a cluster common system disk. * Do you want to install BASEstar on just one node [YES]? No * Enter a node name, to end list: nodename1 %BCC-I-SYSINFO, Verifying node information... * Enter a node name, to end list: nodename2 %BCC-I-SYSINFO, Verifying node information... * Enter a node name, to end list: %BCC-I-SYSCONFIG, Processing node nodename1... This is a new BASEstar installation. The BASEstar CORE must be installed, but the Data Management and Menu System subsystems are optional. * Do you want to install BASEstar Data Management [YES]? * Do you want to install BASEstar External Data Support [YES]? * Do you want to install BASEstar Menu System [YES]? A location must be chosen for the BCC$SPECIFIC directory. By default, BASEstar data and command files are installed in SYS$SPECIFIC:[BCC$SPECIFIC]. This specification may be overridden if desired. * Enter the BASEstar specific directory specification [SYS$SPECIFIC:[BCC$SPECIFIC]]: * Is directory [directory_name_you_typed] correct [YES]? * Do you want this system to be configured as a Global Name Server [YES]? BCC$POINT_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE A-8 Sample BASEstar Installations [1] 500 POINTS 500 POINTS 840 [2] 2,000 POINTS 1,000 POINTS 2,223 [3] 10,000 POINTS 5,000 POINTS 10,675 [4] 30,000 POINTS 10,000 POINTS 27,219 * Enter BCC$POINT_FILE size [1]: BCC$GROUP_FILE ============== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 GROUPS 500 GROUPS 819 [2] 2,000 GROUPS 1,000 GROUPS 2,223 * Enter BCC$GROUP_FILE size [1]: BCC$LOCAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$LOCAL_NAME_FILE size [1]: A location must be chosen for the BCC$COMMON directory. By default, BASEstar executable files are installed in SYS$COMMON:[BCC$COMMON]. This specification may be overridden if desired. * Enter the BASEstar common directory specification [SYS$COMMON: [BCC$COMMON]]: * Is directory SYS$COMMON:[BCC$COMMON] correct [YES]? The node names of all BASEstar Global Name Server systems with which this node will work must now be entered. These names are required for both global name server systems and for name dispatcher systems. * Enter a Global Name Server node name, to end list: Sample BASEstar Installations A-9 %BCC-I-QUORUMSET, Global server quorum will be set to n. If the above quorum value is not consistent with other Global Name Server systems in the same BASEstar cluster, the value of BCC$QUORUM should be changed after the installation is finished and before BASEstar is started on this node for the first time. BCC$GLOBAL_NAME_FILE =================== INITIAL ALLOCATION EXTEND ALLOCATION FILE SIZE [1] 500 NAMES 500 NAMES 342 [2] 2,000 NAMES 1,000 NAMES 867 [3] 10,000 NAMES 5,000 NAMES 4,023 [4] 30,000 NAMES 10,000 NAMES 10,179 * Enter BCC$GLOBAL_NAME_FILE size [1]: The installation procedure has no further questions to ask and can continue from this point without user assistance. The installation time will vary depending on the number of nodes selected for installation and the type of processor on which the installation is being done. This installation creates an identifier name BCC$USER, which is used to control access to the BCC$SYSDATA directory and the data files contained in that directory. After the installation is finished, the VMS Authorize Utility must be used to grant this identifier to all accounts that will use BASEstar. $VMSINSTAL-I-RESTORE, Restoring product save set B . . . $VMSINSTAL-I-RESTORE, Restoring product save set C . . . $VMSINSTAL-I-RESTORE, Restoring product save set D . . . $VMSINSTAL-I-RESTORE, Restoring product save set E . . . %BCC-I-INSTALLNODE, Installing BASEstar on node nodename . . . %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[BCC$COMMON]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[SYS0.BCC$SPECIFIC]. A-10 Sample BASEstar Installations %BCC-I-STARTCORE, BASEstar CORE installation beginning on nodename. This installation places a file name BCC$STARTUP.COM in the directory SYS$SPECIFIC:[SYS$STARTUP] in each system root on which this installation is being performed. The SYSTARTUP_V5.COM file should be edited to invoke this startup file when the system boots. %BCC-I-STARTDMGT, BASEstar Data Management installation beginning on nodename %BCC-I-STARTDMGT, BASEstar External Data Support installation beginning on nodename %BCC-I-STARTMENU, BASEstar Menu System installation beginning on nodename. The following UAF parameters should be checked on all accounts that will use BASEstar: ASTLM BIOLM BYTLM DIOLM ENQLM FILLM PGFLQUO PRCLM TQELM WSDEF WSEXTENT WSQUO Refer to the installation guide for recommended minimum values for these parameters. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of BCC V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm Sample BASEstar Installations A-11 ___________________________________________________________________ A.3 Upgrade This section displays a sample BASEstar upgrade installation. Username: SYSTEM Password: Welcome to VAX/VMS V5.3 Last interactive login on Wednesday, dd-MMM-yyyy hh:mm node1>set def sys$update node1>@vmsinstal bcc030 dua0: VAX/VMS Software Product Installation Procedure V5.3 It is dd-MMM-yyyy at hh:mm Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: BCC V3.0 Beginning installation of BCC V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. BASEstar Kernel V3.0 Installation Procedure ------------------------------------------- BASEstar requires one of the following licenses to be registered and loaded on all nodes on which BASEstar will run: Product Producer Release Date --------------- -------- ------------ [1] BASESTAR DEC 6-Mar-1991 [2] BASESTAR-RT DEC 6-Mar-1991 [3] BASESTAR-LTD DEC 6-Mar-1991 [4] BASESTAR-RT-LTD DEC 6-Mar-1991 * Which of the above licenses will be used? [1]: A-12 Sample BASEstar Installations Product: BASESTAR Producer: DEC Release Date: 6-MAR-1991 * Does this product have an authorization key registered and loaded? y This installation allows for either a cluster installation or a single node installation. The cluster installation option can only be chosen for nodes that share a cluster common system disk. * Do you want to install BASEstar on just one node [YES]? %BCC-I-SYSCONFIG, Processing node nodename... * Do you want to update the BASEstar CORE [YES]? y %BCC-I-DMGTUPDATE, BASEstar Data Management will be updated. %BCC-I-DMGTUPDATE, BASEstar External Data Support will be updated. %BCC-I-MENUUPDATE, BASEstar Menu System will be updated. * Do you want to purge files replaced by this installation [YES]? y The installation procedure has no further questions to ask and can continue from this point without user assistance. The installation time will vary depending on the number of nodes selected for installation and the type of processor on which the installation is being done. This installation creates an identifier named BCC$USER, which is used to control access to the BCC$SYSDATA directory and the data files contained in that directory. After the installation is finished, the VMS Authorize Utility must be used to grant this identifier to all accounts that will use BASEstar. Sample BASEstar Installations A-13 %BCC-I-IDENTEXISTS, The BCC$USER identifier already exists %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %BCC-I-INSTALLNODE, Installing BASEstar on node nodename... %BCC-I-STARTCORE, BASEstar CORE update beginning on NODENAME. This installation places a file named BCC$STARTUP.COM in the directory SYS$SPECIFIC:[SYS$STARTUP] in each system root on which this installation is being performed. The SYSTARTUP_V5.COM file should be edited to invoke this startup file when the system boots. %BCC-I-STARTDMGT, BASEstar Data Management update beginning on NODENAME. %BCC-I-STARTDMGT, BASEstar External Data Support update beginning on NODENAME. %BCC-I-STARTMENU, BASEstar Menu System update beginning on NODENAME. The following UAF parameters should be checked on all accounts that will use BASEstar: ASTLM BIOLM BYTLM DIOLM ENQLM FILLM PGFLQUO PRCLM TQELM WSDEF WSEXTENT WSQUO Refer to the installation guide for recommended minimum values for these parameters. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... BASEstar Kernel V3.0 Installation Verification Procedure %BCCIVP-I-CORESTART, CORE verification starting on node NODENAME. A-14 Sample BASEstar Installations %BCCIVP-I-PASS, CORE data files check passed %BCCIVP-I-PASS, CORE command files check passed %BCCIVP-I-PASS, CORE executable files check passed %BCCIVP-I-PASS, CORE support files check passed %BCCIVP-I-PASS, CORE system files check passed %BCCIVP-I-PASS, CORE installed image check passed %BCCIVP-I-PASS, CORE parameter check passed %BCCIVP-I-DMGTSTART, DMGT verification starting on node NODENAME %BCCIVP-I-PASS, DMGT file check passed %BCCIVP-I-EXTMAPSTART, External Data Server verification starting on node NODENAME %BCCIVP-I-PASS, External Data Server file check passed %BCCIVP-I-MENUSTART, MENU verification starting on node NODENAME %BCCIVP-I-PASS, Menu System file check passed %BCCIVP-I-PASS, Menu System command check passed %BCCIVP-I-PASS, Menu System menu check passed BASEstar V3.0 IVP completed successfully Installation of BCC V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm NODE1>lo SYSTEM logged out at dd-MMM-yyyy hh:mm ___________________________________________________________________ A.4 Device Connection Management This section displays a sample BASEstar device connection management installation. Sample BASEstar Installations A-15 $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL DCM030 ddcu: VAX/VMS Software Product Installation Procedure V5.3 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. *Do you want to continue anyway [NO]? *Are you satisfied with the backup of your system disk [YES]? The following products will be processed: DCM V3.0 Beginning installation of DCM V3.0 at hh:mm %VMSINSTAL-I-RESTORE, restoring product saveset A... *Do you want to run the IVP after the installation [YES]? *Do you want to purge files replaced by this installation? [YES]? As part of this installation, Device Access Software for simple terminal devices, bar code readers (RS-232 devices) and Network devices are provided along with BASEstar Device Connect Management. The configuration template file, ILAN_CFG_TT_SUPPORT.COM, is used to define the paths, types, and devices for terminal devices and the pseudo device. Edit this file, as necessary, to reflect your specific site configuration. During installation it will be placed in the directory BCC$SYSDATA: . The configuration template file for Network support, DCM_NET_CONFIG.TEMPLATE, is used to define Network DAS compatible paths, types, and devices. Edit this file, as necessary, to reflect your specific site configuration. During installation it will be placed in the directory BCC$SYSDATA: . A-16 Sample BASEstar Installations The installation procedure has no further questions to ask and can continue from this point without user assistance. The rest of the installation will take approximately 25 minutes depending on system load and configuration. You must choose a target size for the PHYSICAL POINT data file: Sample BASEstar Installations A-17 ILAN$PHYPOINT_FILE ================== Initial Allocation Extend Allocation File Size [1] 500 Phypoints 500 Phypoints 1,251 Blocks [2] 2,000 Phypoints 1,000 Phypoints 3,333 Blocks [3] 10,000 Phypoints 5,000 Phypoints 15,744 Blocks [4] 20,000 Phypoints 10,000 Phypoints 32,604 Blocks * Enter ILAN$PHYPOINT_FILE size [1]: The installation procedure has no further questions to ask and can continue from this point without user assistance. The rest of the installation will take approximately 25 minutes depending on system load and configuration. Now checking the BASEstar Parameter file for DCM parameters. The BASEstar DCM Parameters have been successfully installed The installation procedure is continuing... The BASEstar DCM Menus have been successfully installed The installation procedure is continuing... %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.ILAN$EXAMPLES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[BCC$COMMON.RS232.EXAMPLE] %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[BCC$COMMON.NCT_EXAMPLE] ILAN$STARTUP.COM, the startup command procedure, is used to set up the environment for device connection management. During installation it will be placed in the [SYS$STARTUP] directory of the system root on which this installation is being performed. SYS$MANAGER: SYSTARTUP_V5.COM, your system startup procedure, should be modified to invoke this procedure when the system boots. However, it will not be necessary to reboot the system after the installation, since this procedure is invoked as part of the installation. A-18 Sample BASEstar Installations %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... BASEstar DCM V3.0 Installation Verification Procedure (IVP) starting %ILANIVP-I-PASS, file check passed %ILANIVP-I-PASS, installed image check passed %ILANIVP-I-PASS, parameter check passed BASEstar DCM v3.0 IVP completed successfully Installation of DCM V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm ___________________________________________________________________ A.5 Library This section displays a sample library installation. NODE1>@sys$update:vmsinstal bcclib030 dua0: VAX/VMS Software Product Installation Procedure V5.3 It is dd-MMM-yyyy hh:mm * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: BCCLIB V3.0 Beginning installation of BCCLIB V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... BASEstar Library System V3.0 Installation Procedure --------------------------------------------------- * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? Sample BASEstar Installations A-19 This is a new Library installation. A location must be chosen for the directory which will contain the directory structure and the actual files referenced by the BASEstar Library's file repository system on this node. The default directory is SYS$SPECIFIC:[BCCLIB$SPECIFIC] and may be overridden if desired. The device on which this directory resides must always be mounted and available. * Enter the library file repository directory specification [SYS$SPECIFIC:[BCCLIB$SPECIFIC]]: * Is directory SYS$SPECIFIC:[BCCLIB$SPECIFIC] correct [YES]? %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SPECIFIC:[BCCLIB$SPECIFIC]. A location must be chosen for the library database file. This is the file which maintains all of the relationships and attributes for the libraries, groups, directories and files. The default directory for this file is SYS$SPECIFIC:[BCCLIB$SPECIFIC] and may be overridden if desired. The device on which the directory resides must always be mounted and available. * Enter the library database file location directory specification [SYS$SPECIFIC:[BCCLIB$SPECIFIC]]: * Is directory SYS$SPECIFIC:[BCCLIB$SPECIFIC] correct [YES]? The installation procedure has no more questions to ask and can continue from this point without user assistance. The installation time will vary depending on the type of processor on which the installation is being done. BASEstar 3.0 for VMS Copyright (c)1990, Digital Equipment Corporation. All Rights Reserved. A-20 Sample BASEstar Installations This installation places a file named BCCLIB$STARTUP.COM in the directory SYS$SPECIFIC:[SYS$STARTUP]. The command file SYSTARTUP_V5.COM should be edited to invoke this startup command file when the system boots. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Expansion Bytes <250000> BASEstar Library V3.0 Installation Verification Procedure BASEstar Library V3.0 IVP completed successfully Installation of BCCLIB V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm NODE1>lo ___________________________________________________________________ A.6 Utility This section displays a sample BASEstar utility installation. $ set def sys$update $ @vmsinstal bccutl030 duao: VAX/VMS Software Product Installation Procedure V5.3-1 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: BCCUTL V3.0 Beginning installation of BCCUTL V3.0 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... Installing BASEstar CORE Utilities Kit Sample BASEstar Installations A-21 * Do you want to purge files replaced by this installation [YES]? This kit provides the following optional BASEstar files: BCC$SYSTEM directory: BCC$GET_TEXT_FILE.EXE BCC$PUT_TEXT_FILE.EXE BCC$BASEGEN.COM SYS$TEST directory: BCC$UTL_IVP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... BASEstar Utility V3.0 Installation Verification Procedure %BCCUTL-I-PASS, Utility file check passed Installation of BCCUTL V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm ! Files created during installation A-22 Sample BASEstar Installations _____________________________________________________________________ Appendix B Files Created During Installation This appendix lists BASEstar files created during the installation of the BASEstar software including its device connection management and library software. Note that the directory locations in which the files are placed reflects the default placement of files by each installation procedure. ___________________________________________________________________ B.1 Files Created by the BASEstar Installation Procedure Table B-1 displays the files created during the BASEstar installation. These files are present only when BASEstar data management, menu interface, and external data support software is installed. Do not delete any of these files. Table_B-1:__BASEstar_Installation_Files______________________________ Directory________________Module______Filename________________________ BCC$SYSDATA: Core BCC$BCC_MSG.DAT BCC$GLOBAL_NAME_FILE.DAT BCC$GROUP_FILE.DAT BCC$HISTORY_FILE.DAT BCC$ITEM_FILE.DAT Files Created During Installation B-1 Table_B-1_(Cont.):__BASEstar_Installation_Files______________________ Directory________________Module______Filename________________________ BCC$LOCAL_NAME_FILE.DAT BCC$MEMBER_FILE.DAT BCC$MSG_SECTION.DAT BCC$NAME_SECTION.DAT BCC$NODE_FILE.DAT BCC$PARAMETER_FILE.DAT BCC$RPC_STORE_FILE.DAT BCC$SERVER_PORT_FILE.DAT BCC$SESSION_FILE.DAT BCC$SYSTEM_STARTUP.COM BCC$USER_FILE.DAT SITE_STARTUP.TEMPLATE Data BCC$DMGT_DATA_SECTION.DAT Management BCC$DMGT_EXTDAT_SECTION.DAT BCC$DMGT_MSG.DAT B-2 Files Created During Installation Table_B-1_(Cont.):__BASEstar_Installation_Files______________________ Directory________________Module______Filename________________________ BCC$DMGT_SECTION.DAT BCC$ELEMENT_FILE.DAT BCC$EXTMAP_FILE.DAT BCC$FIELD_FILE.DAT BCC$POINT_FILE.DAT BCC$RELATION_FILE.DAT BCC$STRUCTURE_FILE.DAT Menu BCC$MENU_FILE.DAT BCC$SYSTEM: Core BCC$CLI.EXE BCC$DISPATCHER.EXE BCC$GBLSERVER.EXE BCC$LOGGER.EXE BCC$MONITOR.EXE BCC$RPCR.EXE Files Created During Installation B-3 Table_B-1_(Cont.):__BASEstar_Installation_Files______________________ Directory________________Module______Filename________________________ BCC$SERVER.EXE Data BCC$DMGTSUP.EXE Management BCC$EVALUATOR.EXE BCC$EXTDATSRV.EXE Menu BCC$CFG_COLORS.EXE BCC$CFG_EXTERNAL_MAP.EXE BCC$CFG_KEYS.EXE BCC$CFG_POINT.EXE BCC$CFG_STRUCTURE.EXE BCC$CFG_USER.EXE BCC$SHOW_EXTERNAL_MAP.EXE BCC$SHOW_POINT.EXE BCC$SHOW_STRUCTURE.EXE BCC$SHOW_SYSTEM.EXE B-4 Files Created During Installation Table_B-1_(Cont.):__BASEstar_Installation_Files______________________ Directory________________Module______Filename________________________ BCC$SHOW_USER.EXE BCC$UI.EXE SYS$COMMON:[SYSHLP] Core BCC$CLI_HELP.HLB BCC030.RELEASE_NOTES Menu BCC$USER_HELP.HLB SYS$COMMON:[SYSLIB] Core BCC$$SHR.EXE BCC$SHR.EXE BCCDEFS.BAS BCCDEFS.FOR BCCDEFS.H BCCDEFS_UPCASE.H BCCDEFS.MAR BCCDEFS.PAS Files Created During Installation B-5 Table_B-1_(Cont.):__BASEstar_Installation_Files______________________ Directory________________Module______Filename________________________ BCCDEFS.PLI BCCDEFS.R32 BCC_.ADA SYS$COMMON:[SYSMSG] Core BCC$MSG.EXE BCC$MSG.MSG SYS$SPECIFIC:[SYS$STARTUPCore________BCC$STARTUP.COM_________________ B-6 Files Created During Installation ___________________________________________________________________ B.2 Files Created by the BASEstar Device Connection Management Installation Procedure Table B-2 displays the files created during the device connection management installation. Device connection management requires these files always be present on your system. Table_B-2:__BASEstar_Device_Connection_Management_Installation_Files_ Directory________________Module______Filename________________________ BCC$SYSDATA: ILAN$CONFIG_FILE.DAT ILAN$DEVICE_FILE.DAT ILAN$PHYPOINT_FILE.DAT ILAN$POLLING_FILE.DAT ILAN$SPT_SECTION.DAT ILAN$SYSTEM_STARTUP.COM ILAN$_SECTION.DAT ILAN_CFG_TT_SUPPORT.COM BCC$SYSTEM: ILAN$CLI.EXE ILAN$DEVSRV.EXE DCM Menu ILAN$CFG_CONNECT.EXE Files Created During Installation B-7 Table B-2 (Cont.): BASEstar Device Connection Management ____________________Installation_Files_______________________________ Directory________________Module______Filename________________________ ILAN$CFG_DEVICE.EXE ILAN$CFG_PHYPOINT.EXE ILAN$CFG_POLLSET.EXE ILAN$DELETE.EXE ILAN$DEV_CONTROL.EXE ILAN$DEV_DIRECTORY.EXE ILAN$DEV_READ_DATA.EXE ILAN$DEV_READ_IPOINT.EXE ILAN$DEV_STATUS.EXE ILAN$DEV_WRITE_DATA.EXE ILAN$DEV_WRITE_IPOINT.EXE ILAN$DOWNLOAD_FILE.EXE ILAN$SHOW_CONNECT.EXE ILAN$SHOW_DEVICE.EXE ILAN$SHOW_PHYPOINT.EXE B-8 Files Created During Installation Table B-2 (Cont.): BASEstar Device Connection Management ____________________Installation_Files_______________________________ Directory________________Module______Filename________________________ ILAN$SHOW_POLLSET.EXE ILAN$UPLOAD_FILE.EXE BCC$SYSTEM:[.RS232_ (RS-232 DAS example files) EXAMPLE] SYS$COMMON:[SYSHLP] ILAN$DEVICE_HELP.HLB ILAN$DEVICE_SPECIFIC.HLB ILAN$HELP.HLB SYS$COMMON:[SYSHLP.EXAMPLES.ILAN$EXAMPLES] ILAN_READ_EXAMPLE.PLI ILAN_WRITE_EXAMPLE.PLI SYS$COMMON:[SYSLIB] BCC$DCM_EAI.EXE BCC$DCM_EUI.EXE Files Created During Installation B-9 Table B-2 (Cont.): BASEstar Device Connection Management ____________________Installation_Files_______________________________ Directory________________Module______Filename________________________ ILAN$CLI_SHR.EXE ILAN$SERVER_SHR.EXE ILAN$SHR.EXE ILANDEFS.ADA ILANDEFS.BAS ILANDEFS.FOR ILANDEFS.H ILANDEFS_UPCASE.H ILANDEFS.MAR ILANDEFS.PAS ILANDEFS.PLI ILANDEFS.R32 ILANSUPPORT.ADA ILANSUPPORT.BAS ILANSUPPORT.FOR B-10 Files Created During Installation Table B-2 (Cont.): BASEstar Device Connection Management ____________________Installation_Files_______________________________ Directory________________Module______Filename________________________ ILANSUPPORT.H ILANSUPPORT_UPCASE.H ILANSUPPORT.MAR ILANSUPPORT.PAS ILANSUPPORT.PLI ILANSUPPORT.R32 ILAN_DEC.EXE ILAN_MIRROR.EXE ILAN_NULL.EXE ILAN_RS232.EXE SYS$COMMON:[SYSMSG] ILAN$MSG.EXE ILAN$MSG.MSG SYS$COMMON:[SYSTEST] ILAN$IVP.COM Files Created During Installation B-11 Table B-2 (Cont.): BASEstar Device Connection Management ____________________Installation_Files_______________________________ Directory________________Module______Filename________________________ SYS$SPECIFIC:[SYS$STARTUP]___________ILAN$STARTUP.COM________________ B-12 Files Created During Installation ___________________________________________________________________ B.3 Files Created by the BASEstar Library Installation Procedure Table B-3 displays the files created during the library management software installation. Library management requires these files always be present on your system. Table_B-3:__BASEstar_Library_Installation_Files______________________ Directory________________Module______Filename________________________ BCC$LIBRARY_LOCATION BCC$LIBRARY.DAT SIT$KNL_SID.DAT BCC$SYSTEM: Library BCC$CFG_DIRECTORY.EXE Menu BCC$CFG_FILE.EXE BCC$CFG_GENERATION.EXE BCC$CFG_GROUP.EXE BCC$CFG_LIBRARY.EXE BCC$COMPARE_DEVICE.EXE BCC$COMPARE_FILE.EXE BCC$COPY.EXE BCC$DELETE.EXE BCC$DIRECTORY.EXE Files Created During Installation B-13 Table_B-3_(Cont.):__BASEstar_Library_Installation_Files______________ Directory________________Module______Filename________________________ BCC$DOWNLOAD.EXE BCC$EDIT.EXE BCC$EXPORT.EXE BCC$GROUP_DOWNLOAD.EXE BCC$GROUP_INSERT.EXE BCC$GROUP_REMOVE.EXE BCC$GROUP_UPLOAD.EXE BCC$IMPORT.EXE BCC$PURGE.EXE BCC$RENAME.EXE BCC$SET_DEF.EXE BCC$SHOW_HISTORY.EXE BCC$UPLOAD.EXE BCC$SYSTEM: Library MSITLIB_CLI_SI.EXE Startup B-14 Files Created During Installation Table_B-3_(Cont.):__BASEstar_Library_Installation_Files______________ Directory________________Module______Filename________________________ MSITLIB_CLI_SIOSP.EXE SYS$COMMON:[SYSLIB] SIT$ATTRIBUTED_SHR.EXE SIT$AUTHORIZATION_SHR.EXE SIT$DEVICEFILES_SHR.EXE SIT$DEVICE_SHR.EXE SIT$FILEIO_SHR.EXE SIT$INDEX_SHR.EXE SIT$INTERESTING_SHR.EXE SIT$LIFECYCLE_SHR.EXE SIT$LOGGING_SHR.EXE SIT$LOGICALFILE_SHR.EXE SIT$MSITLIBRARY_SHR.EXE SIT$OPTCOLS_SHR.EXE SIT$STDFILETYPES_SHR.EXE SIT$STREAMS_SHR.EXE Files Created During Installation B-15 Table_B-3_(Cont.):__BASEstar_Library_Installation_Files______________ Directory________________Module______Filename________________________ SIT$TIME_SHR.EXE SIT$USERPROFILE_SHR.EXE SIT$VERSIONING_SHR.EXE SIT$KNLSS_SI.EXE SIT$KNL_SI.EXE SYS$COMMON:[SYSMSG] SIT$KNL_MSG.EXE SYS$COMMON:[SYSTEST]: BCCLIB$IVP.COM SYS$COMMON:[SYSMGR]: BCCLIB$REFMNT.COM SYS$SPECIFIC:[SYS$STARTUP]:__________BCCLIB$STARTUP.COM______________ B-16 Files Created During Installation Index __________________________________________________________ ___________________________ B Documentation ___________________________ general users kit, 1-8 Backing up the system, 1-16 listing of, 1-7 BASEstar programming kit, 1-8 installation steps, 2-1 systems managers kit, 1-8 license requirement, 1-12 ___________________________ logical names, 1-16 E post-installation tasks, ___________________________ 3-1 External data support pre-installation tasks, installation, 1-2 1-10 ___________________________ Batch process F stopping, 1-15 ___________________________ BCC$BASEGEN installation, FMS 1-4 version requirement, 1-12 ___________________________ ___________________________ C G ___________________________ ___________________________ Closing the library Global name server database, 1-15 defining, 1-13 ___________________________ ___________________________ D H ___________________________ ___________________________ Data management installa- Hardware tion, 1-2 requirements, 1-9 DECnet ___________________________ configuring, 1-12 I Device connection ___________________________ management Installation installation overview, checklist, 1-5 device connection 1-3 management sample, installation steps, 2-20 A-15 Disk space distribution kit, 1-7 requirements, 1-10 files created, B-1 Distribution kit information to prepare, documentation, 1-7 2-2 media, 1-7 Index-1 Installation (Cont.) Installation library prerequisites, prerequisites (Cont.) 1-9 hardware requirements, library sample, A-19 1-9 list of messages, 2-32 product license, 1-12 message format, 2-31 software, 1-9 messages, 2-31 stopping batch queues, optional software 1-15 installations, 1-3 stopping the system, options during main 1-15 installation, 1-2 verifying logical overview, 1-1 names, 1-16 overview of main, 1-1 VMS version, 1-12 overview of optional samples, A-1 software, 1-1 single node sample, A-1 post-installation steps automating startup, device connection 3-4 management, 2-20 backing up the system, library management, 3-1 2-25 granting the user new system, 2-3 identifier, 3-5 single node, 2-3 starting BASEstar, 3-5 utilities, 2-29 post-installation tasks, VAXcluster systems, 3-1 2-12 preliminary steps, 1-10 upgrade preparation, 1-6 verifying logical prerequisites names, 1-16 backing up the system, upgrade sample, A-12 1-16 utility sample, A-21 closing the library VAXcluster sample, A-7 database, 1-15 VAXcluster systems, 1-17 DECnet configuration, Installation procedures 1-12 overview, 1-1 determining software VAXcluster systems, 1-17 to install, 1-12 disabling logins, 1-14 disk space, 1-10 FMS version, 1-12 global name definition , 1-13 2-Index ___________________________ Preinstallation (Cont.) L verifying SYSGEN ___________________________ parameters for library Library closing the database, , 1-13 1-15 ___________________________ Library management S installation overview, ___________________________ 1-4 Sample installations, A-1 installation prerequi- Software sites, 1-9 distribution kit, 1-7 installation steps, 2-25 requirements, 1-9 Logical names Starting BASEstar, 3-5 verifying, 1-16 Stopping BASEstar, 1-15 Log ins SYSGEN parameters disabling, 1-14 preinstallation library ___________________________ minimum values, 1-13 M recommended minimum ___________________________ values, 3-1, 3-2 Menu interface installation System disk , 1-2 backing up, 1-16 Messages ___________________________ format, 2-31 U installation, 2-31 ___________________________ ___________________________ Utilities O installation overview, ___________________________ 1-4 Options installation steps, 2-29 overview, 1-1 ___________________________ ___________________________ V P ___________________________ ___________________________ VAXcluster installation, Post-installation 1-17 automating startup, 3-4 VMS backing up the system, version requirement, 1-12 3-1 VMSINSTAL granting the user using, 1-1 identifier, 3-5 starting BASEstar, 3-5 verifying SYSGEN run-time parameters, 3-1 Preinstallation Index-3 ! Reader's comment card 2 Files Created During Installation Reader's Comments BASEstar for VMS Installation Guide AA-PD1QB-TE Please use this postage-paid form to comment on this manual. Thank you for your assistance. I rate this manual's: Excellent Good Fair Poor Accuracy (software works as ma_ual says)_ _ _ Completeness (enough informat||n) || || || Clarity (easy to understand) || || || || Organization (structure of su||ect mat||r) || || Figures (useful) || || || || Examples (useful) || || || || Tables (useful) || || || || Index (ability to find topic)|| || || || Page layout (easy to find inf||mation)|| || || What I like best about this manual is ________________________ _______________________________________________________________ What I like least about this manual is _______________________ _______________________________________________________________ I would like to see more _____________________________________ _______________________________________________________________ I would like to see less _____________________________________ _______________________________________________________________ I found the following errors in this manual: Page Description ____ _________________________________________________________ ____ _________________________________________________________ ____ _________________________________________________________ Additional comments or suggestions to improve this manual: _______________________________________________________________ _______________________________________________________________ _______________________________________________________________ I am using Release ____ of the software this manual describes. Name/Title _____________________________ Dept. ______________ Company ______________________________________ Date _________ Mailing Address ______________________________________________ _________________________________________ Phone ______________ | | __________Do Not Tear - Fold Here and Tape _________________________|___ | __________ No Postage | DIGITAL Necessary if mailed in the |||||| United States | |||||| __________ |||||| | | | |||||| |__________| | |||||| | | | |__________| | | | _____________________________ |__________| | | | BUSINESS REPLY MAIL __________ | _____________________________ARD MASS._____ | | | | __________ |OSTAGE WILL BE PAID BY ADDRE|SEE __________ | | | | Digital Equipment Corporation __________ | Enterprise Integration Services __________ | 206 West Newberry Road __________ | | Bloomfield, CT 06002 | __________Do Not Tear - Fold Here and Tape _________________________|___