BASEstar_Classic____________________________________ Installation Guide Order Number: AA-PD1QF-TE October 1996 This manual describes installation prerequisites, installation procedures, and postinstallation tasks for BASEstar Classic, Version 3.4. Revision/Update Information: This is a revised manual. Operating System and Version: OpenVMS VAX OpenVMS Alpha Refer to BASEstar Classic SPD for current Operating System Version information. Software Version: BASEstar Classic, Version 3.4 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ October 1996 Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1991, 1993, 1994, 1995, 1996. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: BASEstar, DEC, DECmessageQ, DECnet, DECnet-DOS, Digital, FMS, LN03, MicroVAX, NAS, OpenVMS, PATHWORKS, Rdb/VMS, ReGIS, ThinWire, TK, ULTRIX, VAX, VAXcluster, VAX COBOL, VAX FORTRAN, VAX Pascal, VAX RMS, VMS/ULTRIX Connection, VT, and the DIGITAL logo. DataViews is a registered trademark of VI Corporation. IBM and OS/2 are registered trademarks of International Business Machines Corporation. Macintosh is a registered trademark of Apple Computer, Inc. Microsoft and MS-DOS are registered trademarks of Microsoft Corporation. SL-GMS is a trademark of SL Corporation. UNIX is a registered trademark of UNIX System Laboratories, Inc. X Window System is a trademark of Massachusetts Institute of Technology. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Introduction 1.1 Overview......................................... 1-1 1.1.1 Main Installation Options ..................... 1-2 1.1.2 Optional Installation Procedures .............. 1-2 1.1.2.1 Device Connection Management................ 1-3 1.1.2.2 Utilities................................... 1-3 1.1.2.3 DEC Rdb Database Server..................... 1-4 1.1.2.4 BASEstar Classic CIMfast Application Enabler..................................... 1-4 1.1.3 Installation Checklist ........................ 1-5 1.2 Installation Preparation......................... 1-6 1.2.1 Distribution Kit .............................. 1-6 1.2.2 Prerequisite Hardware ......................... 1-8 1.2.3 Prerequisite and Optional Software ............ 1-8 1.3 VMScluster Installation.......................... 1-9 1.3.1 Disk Space Requirements ....................... 1-10 1.4 Preinstallation Steps............................ 1-11 1.5 Upgrade Overview to a BASEstar Classic 3.4 system........................................... 1-21 2 Installation 2.1 Installing BASEstar Software..................... 2-2 2.2 Installing BASEstar Device Connection Management Software......................................... 2-13 2.3 Installing BASEstar Utilities Software........... 2-19 2.4 Installing BASEstar Classic CIMfast Software..... 2-24 2.5 Installation Messages............................ 2-33 2.5.1 Message Format ................................ 2-33 2.5.2 BASEstar Classic Message Listing .............. 2-34 iii 2.5.3 BASEstar Classic CIMfast Message Listing ...... 2-40 2.6 BASEstar Classic CIMfast Error Recovery.......... 2-40 3 Postinstallation 3.1 BASEstar Classic Postinstallation Procedures..... 3-1 3.2 BASEstar Classic CIMfast Postinstallation Procedures....................................... 3-6 A Sample BASEstar Classic Installations for OpenVMS Systems A.1 Main BASEstar Installation....................... A-1 A.2 Device Connection Management installation........ A-10 A.3 Utilities Installation........................... A-14 A.4 CIMfast Installation............................. A-16 B Sample BASEstar Classic Installation Upgrade for OpenVMS Systems B.1 Main Upgrade Installation........................ B-1 B.2 CIMfast Upgrade.................................. B-13 C Files Created During Installation C.1 Files Created by BASEstar Installation Procedure ................................................. C-1 C.2 Files Created by BASEstar Device Connection Management Installation Procedure................ C-5 C.3 Files Created by BASEstar Utility Installation Procedure........................................ C-8 C.4 Files Created by CIMfast Installation Procedure.. C-10 Index iv Tables 1-1 BASEstar Licenses ............................. 1-14 1-2 BASEstar Minimum System Parameter Values for OpenVMS VAX.................................... 1-16 1-3 BASEstar Minimum System Parameter Values for OpenVMS Alpha ................................. 1-17 3-1 Process Resource Limits for OpenVMS VAX Systems........................................ 3-3 3-2 Process Resource Limits for OpenVMS AXP Systems........................................ 3-4 3-3 Logical Names Created by BASEstar Classic Installation Procedures........................ 3-6 3-4 User Account Quotas for BASEstar Classic CIMfast........................................ 3-9 3-5 Logical Names Created by BASEstar Classic CIMfast Installations ......................... 3-11 C-1 BASEstar Main Installation Files .............. C-1 C-2 BASEstar Device Connection Management Installation Files............................. C-5 C-3 BASEstar Utility Installation Files ........... C-8 C-4 CIMfast Installation Files .................... C-10 C-5 CIMfast DCM Support Files ..................... C-11 C-6 CIMfast DQM Support Files ..................... C-12 C-7 CIMfast Development Option Files .............. C-12 C-8 CIMfast LSE File .............................. C-15 C-9 CIMfast SQL Support Files ..................... C-15 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 OpenVMS operations to install a BASEstar system. To obtain a complete understanding of BASEstar configuration management before installation, refer to the BASEstar Classic Configuration and Tuning Guide. Document Structure This document has the following structure: o Chapter 1 provides a description of the BASEstar installation, software distribution kits, required hardware and software, preliminary installation steps, and VMScluster installation overview. o Chapter 2 describes step-by-step installation of BASEstar software on a single node or on a VMScluster system. This section also includes instructions for the optional installation of utility, device connection management, and BASEstar Classic CIMfast software. The installation information is applicable for OpenVMS VAX and OpenVMS AXP systems. o Chapter 3 describes postinstallation tasks. o Appendix A presents sample installations of BASEstar software on OpenVMS systems. v o Appendix B presents sample Upgade installation of BASEstar software on OpenVMS systems. o Appendix C lists all BASEstar files created during installation with their directory locations. vi Conventions The following conventions are used in this manual. ___________________________________________________________ Convention______Meaning____________________________________ In examples, a key name enclosed in a box indicates that you press that key. Ctrl/x Ctrl/x indicates that you hold down the Ctrl key while you press another key. x A lowercase x indicates the generic use of a letter. For example, xxx indicates any combination of three alphabetic characters. n A lowercase n indicates the generic use of a number. For example, 19nn indicates a 4-digit number in which the last 2 digits are unknown. [ ] In format descriptions, brackets indicate optional elements. You can choose none, one, or all of the options. Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification. { } Braces indicate select one of enclosed items. ( ) In format descriptions, parentheses delimit the argument list. "point_a + Literal string. Using quotation marks is point_b" optional unless there is a space, slash (/), or parenthesis in the string. ... The horizontal ellipsis indicates omitted text within a string. . The vertical ellipsis indicates omitted . text within output. The information is . omitted because it is not important to the topic being discussed. italic type Italic type emphasizes important information, indicates variables, and indicates complete titles of manuals. vii ___________________________________________________________ Convention______Meaning____________________________________ boldface type Boldface type in examples indicates user input. Boldface type in text indicates the first instance of terms defined either in the text or in the BASEstar master glossary, which is included in the BASEstar Classic Introduction. BASEstar names Valid characters for the names of BASEstar objects are the alphanumeric characters (A-Z) and (0-9), the underscore (_), the dollar sign ($), and the following multinational characters: ________________ÅÀÁÂÃÄÇÈÉÊËÌÍÎÏÒÓÔÕÖÙÚÛÜÝÆÑ×Øß.____________ Associated Documents For further information on installing and configuring BASEstar software, refer to the following documents: o BASEstar Classic DEC Rdb Database Server Guide o BASEstar Classic Configuration and Tuning Guide o BASEstar Classic Command Line Interface User's Guide o BASEstar Classic CIMfast Guide to DCM Support o BASEstar CIMfast Guide to DECmessageQ Support o BASEstar CIMfast Programmer's Guide o BASEstar CIMfast User's Guide o OpenVMS System Manager's Manual o OpenVMS System Management Utilities Reference Manual o OpenVMS License Management Utility Manual o OpenVMS System Manager's Manual viii 1 _________________________________________________________________ Introduction This chapter is an overview of BASEstar software installation procedures and installation options. It also describes installation preparation and preliminary steps, and provides an overview of VMScluster installation. 1.1 Overview The BASEstar installation procedures allow you to customize each BASEstar system by installing only those system components that you want for the target system. You can install BASEstar software on a single node or on a VMScluster system, provided the cluster member nodes share the same system disk. The main BASEstar installation procedure is mandatory for all BASEstar systems and installs basic application integration features such as application synchronization and control and distributed name services. The main installation procedure has options, including the ability to install the BASEstar menu interface (OpenVMS VAX only), BASEstar data management capabilities, and BASEstar external data support. In addition to the main installation options, there are optional installation save sets available with BASEstar software that provide device connection management, BASEstar utilities, and DEC Rdb integration. See the following sections to learn about installation options in the main installation procedures and optional BASEstar kits that you can install. In addition to installing BASEstar software, you can install BASEstar Classic CIMfast software. Introduction 1-1 Introduction 1.1 Overview 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 VMScluster 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 Because the processing requirements for each node within your manufacturing system are unique, 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 want to install: o Data management o External data support o Menu interface (OpenVMS VAX only) 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.1.2 Optional Installation Procedures In addition to the main installation, you can install any of five optional BASEstar components. This software is installed from separate kits 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 Utilities o DEC Rdb database server 1-2 Introduction Introduction 1.1 Overview o BASEstar Classic CIMfast application enabler 1.1.2.1 Device Connection Management BASEstar device connection management software is installed after the main BASEstar installation procedure is complete. 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. The BASEstar device connection management installation procedure will conditionally install its menu interface component if the BASEstar menu system (OpenVMS VAX only) 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, DECnet and TCP/IP networks, and the DECdevice device communication module. Refer to the BASEstar Classic Device Access Software Guide for information on how to configure and use these DAS modules. 1.1.2.2 Utilities The BASEstar utility kit offers seven BASEstar functions: o The BCC$BASEGEN.COM utility for tuning BASEstar systems Run this procedure on a loaded BASEstar system to analyze its current OpenVMS resource utilization and obtain suggested values for BASEstar parameters, system parameters, and OpenVMS process quota settings. o 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 converting message text to a non-English language. o Software for reconciling OpenVMS version mismatches The utility kit contains software for reconciling OpenVMS versions if a version mismatch error occurs during BASEstar installation. o Logical point value change notification Introduction 1-3 Introduction 1.1 Overview Provided with the BASEstar development kit is a tool called the Value Notification Utility (Notify). You supply the utility with a list of logical points. Every time the value of one of the logical points changes, you are notified. This utility requires a BASEstar development license. o BASEstar process data display Use the Monitor BASEstar Utility to analyze the processes running on a BASEstar system. Monitor BASEstar continuously displays a default set of processes or allows the display of a customized set of processes. o Port activity display The Monitor Port Utility provides a continuously updated display of port data for all ports defined on the system. Use the Monitor Port Utility to observe port activity when tuning and troubleshooting. o BASEstar LSE Environment Language-Sensitive Editor (LSE) is a multiple-language text editor that speeds writing and compiling source code. BASEstar software provides an extension to the LSE in the form of expandable tokens for BASEstar callable services, DAS support routines, and BASEstar application programming interface (API) constants. Before the BASEstar LSE environment can be accessed, the LSE and BASEstar Classic Development Kit must be installed with the BASEstar LSE Environment selected. This utility requires a BASEstar development license. 1.1.2.3 DEC Rdb Database Server BASEstar software includes a DEC Rdb database server to export BASEstar data to a DEC Rdb database. Instructions for installing and using the BASEstar DEC Rdb database server are in the BASEstar Classic DEC Rdb Database Server Guide. 1.1.2.4 BASEstar Classic CIMfast Application Enabler The BASEstar Classic CIMfast application enabler is installed after the main BASEstar and device connection management installation procedures are complete. 1-4 Introduction Introduction 1.1 Overview 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 each node in your network of BASEstar systems. ___________________________________________________________ Optio______Do_users_need_to...___Then_install...__________ 1. _____ Use DECmessageQ with DECmessageQ before BASEstar software? starting BASEstar software. 2. _____ Share data on this Data Management during system? the main installation procedure. 3. _____ Export data from External Data Support this system? during the main installation procedure. 4. _____ Access the BASEstar Menu System during menu interface? the main installation procedure (OpenVMS VAX only). 5. _____ Control or monitor Device Connection plant equipment or Management from the collect plant data DCMVV034/BRIVV034 or using this system? DCMVA034/BRIVA034 kit. 6. _____ Access BASEstar Utilities from the utilities? BCCUTLVV034/BCCUTLVA034 kit. 7. _____ Export data to a DEC DEC Rdb Database Server Rdb database? from the BRIVV034 /BRIVA034 kit. 8. _____ Develop applications BASEstar Classic CIMfast using the BASEstar from the BCFVAX022 Classic CIMfast /BCFAXP022 kit. Event Language alone or with a high-level ____________language?______________________________________ Once you plan the software to install on each BASEstar system, continue with the instructions in the following Introduction 1-5 Introduction 1.1 Overview 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 Classic, Version 3.4 installation. 1.2.1 Distribution Kit BASEstar software is available in three forms: a 1600 bits/in 9-track tape, a TK50 tape cartridge, or through Digital Consolidated Distribution on CD-ROM for use with development or run-time licenses. Each medium contains the following software kits: For OpenVMS VAX o BCCVV034 - BASEstar application integration software o BCCUTLVV034 - BASEstar utilities software o BRIVV034 - BASEstar DEC Rdb database server software o DCMVV034 - BASEstar device connection management software o BCFVAX022 - BASEstar Classic CIMfast application enabler software For OpenVMS Alpha o BCCVA034 - BASEstar application integration software o BCCUTLVA034 - BASEstar utilities software o BRIVA034 - BASEstar DEC Rdb database server software o DCMVA034 - BASEstar device connection management software o BCFAXP022 - BASEstar Classic CIMfast application enabler software BASEstar technical documentation is available in either a development media kit or a run-time media kit. The run-time kit contains Volumes 1 and 2 of the documentation, and the development kit contains Volumes 1 to 4 and the BASEstar Classic CIMfast documentation. 1-6 Introduction Introduction 1.2 Installation Preparation System Management Documentation (Volume 1) o BASEstar Classic Installation Guide o BASEstar Classic Configuration and Tuning Guide General User Documentation (Volume 2) o BASEstar Classic Introduction o BASEstar Classic Menu Interface User's Guide o BASEstar Classic Command Line Interface User's Guide Programming Documentation (Volume 3) o BASEstar Classic Introduction to Callable Services o BASEstar Classic Guide to Writing a Database Server o BASEstar Classic DEC Rdb Database Server Guide o BASEstar Classic Guide to Writing Device Access Software o BASEstar Classic Device Access Software Guide Programming Documentation (Volume 4) o BASEstar Classic Application Programming Interface Reference Guide BASEstar Classic CIMfast Documentation o BASEstar Classic CIMfast Guide to DCM Support o BASEstar CIMfast Guide to DECmessageQ Support o BASEstar CIMfast Programmer's Guide o BASEstar CIMfast User's Guide o BASEstar CIMfast Guide to SQL support Your bill of materials (BOM) and Indented Bills Report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. BASEstar Classic provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. Introduction 1-7 Introduction 1.2 Installation Preparation 1.2.2 Prerequisite Hardware The minimum hardware configuration required for BASEstar software to run efficiently follows. Refer to the BASEstar Classic Software Product Description and System Support Addendum for more details. o VAX processor - For OpenVMS VAX systems, a single VAX or MicroVAX processor with a minimum of 8 Mb of memory supports BASEstar software. The single processor can be networked with other systems or a VMScluster system using DECnet software. Any or all systems in the distributed network can run BASEstar software. o Alpha processor - For OpenVMS Alpha systems, a single Alpha processor with a minimum of 64 Mb of memory. The single processor can be networked with other systems or a VMScluster system using DECnet software. Any or all systems in the distributed network can run BASEstar software. o For OpenVMS VAX systems, an RD54 or equivalent disk drive. o For OpenVMS Alpha systems, an RZ26 or equivalent disk drive. 1.2.3 Prerequisite and Optional Software The following software must be installed on your system before installing BASEstar software: For OpenVMS VAX systems: o OpenVMS VAX Version 5.5-2 or higher. (Refer to BASEstar Classic SPD for official supported VMS Versions) o DECnet software, as provided with the OpenVMS operating system. o FMS, Version 2.3 or higher for the BASEstar menu interface only. If you do not install the menu system, you do not need FMS. o Optionally, DECmessageQ Version 2.0 or higher for interprocess messaging. o Optionally, Digital RDB for use with BASEstar Classic RDB/VMS Database Server. 1-8 Introduction Introduction 1.2 Installation Preparation o Optionally, LSE (Language Sensitive Editor) for using the BASEstar LSE environment. For OpenVMS Alpha systems: o OpenVMS Alpha Version 6.1 or higher. (Refer to BASEstar Classic SPD for official supported VMS Versions) o DECnet software, as provided with the OpenVMS operating system. o Optionally, DECmessageQ Version 2.0 or higher for interprocess messaging. o Optionally, Digital RDB for use with BASEstar Classic RDB/VMS Database Server. o Optionally, LSE (Language Sensitive Editor) for using the BASEstar LSE environment. The following software must be installed on your system before installing BASEstar Classic CIMfast software: o OpenVMS VAX Version 6.1 or higher or OpenVMS Alpha Version 6.1. (Refer to BASEstar Classic SPD for official supported VMS Versions) o BASEstar for VMS (Kernel and Data Management), Version 3.4 or higher. o Optionally, DECmessageQ Version 2.0 or higher. o Optionally, Digital RDB version 6.0 or Oracle version 7.0 for use with CIMfast SQL support. o Optionally, DEC C for OpenVMS. 1.3 VMScluster Installation Each BASEstar installation procedure for VMScluster systems allows installation of BASEstar software from one node in a VMScluster for all nodes sharing a system disk. BASEstar software and device connection management software support VMScluster installation. The installation procedure automatically determines if the node that is executing the VMSINSTAL utility is part of a multinode VMScluster. If not, a single-node installation procedure will be performed. If the executing node is a member of a multinode VMScluster, the installation Introduction 1-9 Introduction 1.3 VMScluster Installation procedure will prompt you to specify the nodes to be processed and the BASEstar software configuration for each node. The executing node will automatically be the first node in the list of nodes to be processed. 1.3.1 Disk Space Requirements The amount of disk space required depends on your BASEstar system configuration. The disk space requirements for the BASEstar software components follow: ________________________ Note ________________________ Refer to Section 1.5 for additional disk space requirements for a UPGRADE from BASEstar Classic 3.3 database to a 3.4 database. ______________________________________________________ For OpenVMS VAX systems: ___________________________________________________________ Peak Utilization in Blocks (During Blocks After BASEstar_Component________Installation)___Installation_____ BASEstar software with 31,500 24,600 all main options Device connection 18,000 16,000 management Utility 3,300 400 DEC Rdb Database Server 1,150 800 BASEstar_Classic_CIMfast____6,000___________4,500__________ For OpenVMS Alpha systems: 1-10 Introduction Introduction 1.3 VMScluster Installation ___________________________________________________________ Peak Utilization in Blocks (During Blocks After BASEstar_Component________Installation)___Installation_____ BASEstar software with 52,000 29,000 all main options Device connection 19,000 13,000 management Utility 12,000 400 DEC Rdb Database Server 3,000 2,000 BASEstar_Classic_CIMfast____21,000__________13,000_________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1.4 Preinstallation Steps Before installing BASEstar software, review the following checklist. If you need more information on how to perform some of the functions on the checklist, refer to the OpenVMS System Manager's Manual. ___________________________________________________________ Step_______Before_installing_BASEstar_software..._________ 1. _____ Ensure that OpenVMS Version is as required for your processor. If you plan to use DECmessageQ, ensure that DECmessageQ Version 2.0 or higher is installed. 2. _____ Ensure that DECnet software is configured on your system. 3. _____ Optionally, ensure that the following software is installed: FMS for the menu interface, DECmessageQ for messaging, and LSE for the LSE environment. 4. _____ Install the BASEstar product license. 5. _____ Decide which BASEstar software components to install on each system. Introduction 1-11 Introduction 1.4 Preinstallation Steps ___________________________________________________________ Step_______Before_installing_BASEstar_software..._________ 6. _____ Define your global name server configuration (if you have two or more BASEstar systems in a network that share information). 7. _____ Verify minimum run-time system parameters. Table 1-2 and Table 1-3 describe the system parameter values recommended for the minimum run-time BASEstar configuration. 8. _____ Stop interactive processes and disable user logins. 9. _____ Stop batch queues. 10. _____ Stop the BASEstar system (upgrades only). 11. _____ Check VMSINSTAL requirements. 12. _____ Back up the system disk. 13. _____ Verify logical names for an upgrade (upgrades only). 14. _____ Review release notes. 15. _____ Check required OpenVMS tailoring classes in the BASEstar Classic System Software Addendum ____________(SSA)._________________________________________ Perform these tasks before installing BASEstar software: 1. Ensure that OpenVMS VAX Version 5.5-2 or higher or OpenVMS AXP Version 6.1 or higher is installed on the system. OpenVMS VAX Version 5.5-2 or higher or OpenVMS AXP Version 6.1 must be installed on each system planned for installation of BASEstar software. (Refer to BASEstar Classic SPD for official supported VMS Versions) To install BASEstar Classic CIMfast, OpenVMS VAX Version 6.1 or higher or OpenVMS AXP Version 6.1 or higher must be installed on each system planned for installation of BASEstar Classic CIMfast software. (Refer to BASEstar Classic SPD for official supported VMS Versions) DEC C Runtime Components must be installed for OpenVMS for use of CIMfast software. 2. Ensure that DECnet software is configured on your system. 1-12 Introduction Introduction 1.4 Preinstallation Steps DECnet software must be configured in order to install BASEstar software. Refer to the BASEstar Classic Configuration and Tuning Guide for instructions on the minimum DECnet configuration required. 3. Optionally, ensure that the following software is installed: FMS for the menu interface, DECmessageQ for messaging, and LSE for the Language Sensitive Editor environment. If you plan to use the BASEstar menu interface, ensure that FMS Version 2.3 or higher is installed on each system. If you plan to use DECmessageQ with your BASEstar system, install DECmessageQ Version 1.0 or higher. Refer to the DECmessageQ Installation Guide for OpenVMS for more information about installing DECmessageQ software. If you plan to use DECmessageQ with BASEstar Classic CIMfast, install DECmessageQ Version 2.0 or higher. Refer to the DECmessageQ Installation Guide for OpenVMS for more information about installing DECmessageQ software. If you plan to use the LSE environment for BASEstar, install Language-Sensitive Editor software. If you plan to use the CIMfast SQL component, install Digital RDB Version 6.0 or Oracle 7.0. 4. Install the BASEstar product license. Before you install and run BASEstar Classic, Version 3.4 software on a newly licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). The License PAK may be shipped with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. Before installing BASEstar, you must update the LMF database using the License Management Utility. For more information about the License Management Utility, refer to the OpenVMS License Management Utility Manual. Introduction 1-13 Introduction 1.4 Preinstallation Steps To update the LMF database, log in to a privileged account and follow these steps: a. Find the product name listed on the PAK that you received. b. To determine if a previous license is already registered and loaded for BASEstar software, enter the following command: $ LICENSE LIST product_name/FULL where product_name is the product name. c. If a new PAK is required to be registered and loaded, choose one of the following actions: o Execute the command procedure VMSLICENSE to register and load the new PAK: $ @SYS$UPDATE:VMSLICENSE.COM The VMSLICENSE procedure prompts for the information contained in the PAK, and then registers and loads the new PAK on your system. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. Table 1-1 shows the statuses of the licenses listed during the main BASEstar installation. Table_1-1_BASEstar_Licenses________________________________ License___________Availability_____________________________ CIMFAST-V No Longer Available CIMFAST-RT-V No Longer Available BASESTAR Available BASESTAR-RT Available BASESTAR-CU Available BASESTAR-LTD No Longer Available (continued on next page) 1-14 Introduction Introduction 1.4 Preinstallation Steps Table_1-1_(Cont.)_BASEstar_Licenses________________________ License___________Availability_____________________________ BASESTAR-RT-LTD No Longer Available BASESTAR-G Not Yet Available BASESTAR-RT-G Not Yet Available BASESTAR-USER_____Not_Yet_Available________________________ When performing a BASEstar installation, you must preload the licenses you want to use in order to authorize the use of BASEstar on the target node. A new license called BASESTAR-CU was added for BASEstar Classic, Version 3.2. This allows you to license a BASEstar system based on the maximum number of logical points residing on the target system. At installation, the BASESTAR-CU license is checked for its presence and the installation procedure verifies that the number of logical points is less than the number licensed at startup. If the BASEstar parameter BCC$MAX_POINTS exceeds the number of units specified in the BASESTAR-CU license, the system cannot be started. At BASEstar Classic CIMfast installation, the BASESTAR license or the BASEstar Classic CIMfast license must be present; either license is acceptable. 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 system in your hardware configuration. 6. Define your global name server configuration. 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 Introduction 1-15 Introduction 1.4 Preinstallation Steps information on defining global name servers, refer to the BASEstar Classic Configuration and Tuning Guide. 7. Verify minimum run-time system parameters. Table 1-2 describes the system parameter values recommended for the minimum run-time BASEstar configuration. Table 1-2 BASEstar Minimum System Parameter Values for __________OpenVMS_VAX______________________________________ MODPARAMS.DAT Entries_______________Minimum_Value________________________ GBLSECTIONS 250 GBLPAGFIL 4,096 GBLPAGES 18,000 CTLPAGES 60 LOCKIDTBL 2,048 RESHASHTBL 512 MAXPROCESSCNT 35 BALSETCNT 33 VIRTUALPAGECNT 25,000 MAXBUF 4,096 SCSSYSTEMID Refer to BASEstar Classic Release ______________________Notes._______________________________ 1-16 Introduction Introduction 1.4 Preinstallation Steps Table 1-3 BASEstar Minimum System Parameter Values for __________OpenVMS_Alpha____________________________________ MODPARAMS.DAT Entries_______________Minimum_Value________________________ GBLSECTIONS 512 GBLPAGFIL 4,096 GBLPAGES 150,000 CTLPAGES 80 LOCKIDTBL 3,840 RESHASHTBL 4,096 MAXPROCESSCNT 40 BALSETCNT 80 VIRTUALPAGECNT 300,000 MAXBUF 8,192 SCSSYSTEMID Refer to BASEstar Classic Release ______________________Notes._______________________________ Because these values represent minimum BASEstar run- time system 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. Use the following steps to adjust the system parameter GBLPAGES: a. Run the OpenVMS System Generation Utility (SYSGEN) to view the current setting for the GBLPAGES parameter on your system as follows: $ MCR SYSGEN SYSGEN>USE ACTIVE SYSGEN>SHOW GBLPAGES GBLPAGES 18000 SYSGEN>EXIT 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 value you want. If the parameter is not specified, you can add a line to the MODPARAMS.DAT file to specify your minimum amount as follows: Introduction 1-17 Introduction 1.4 Preinstallation Steps 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 the value you want. c. Use the OpenVMS AUTOGEN command procedure to update the new value as follows: 1. $ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS 2. $ @SYS$UPDATE:AUTOGEN SETPARAMS REBOOT 8. Stop interactive processes and disable logins. Ensure that all BASEstar users have logged out and no other users can log in to the system during the installation. To disable users from logging in, enter the following: $ SET LOGINS/INTERACTIVE=0 Reenable logins after the installation is complete. Refer to the OpenVMS System Manager's Manual for more information on logins. 9. Stop batch queues. To stop the batch queues, enter the following: $ STOP/QUEUE/NEXT batch_queue_name 10.Stop the BASEstar system. If you are performing an upgrade of existing BASEstar software, ensure that 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 the following: $ BSTAR STOP SYSTEM 11.Check VMSINSTAL requirements. VMSINSTAL requires that the system account used to install BASEstar software have a minimum of the following quotas: For OpenVMS VAX systems: o ASTLM=24 1-18 Introduction Introduction 1.4 Preinstallation Steps o BIOLM=18 o BYTLM=18,000 o DIOLM=18 o ENQLM=30 o FILLM=20 For OpenVMS Alpha systems: o ASTLM=100 o BIOLM=50 o BYTLM=32,000 o DIOLM=50 o ENQLM=100 o FILLM=35 If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter Y to continue. To stop the installation process and correct the situation, enter N or press Return. Then, correct the problem and restart the installation. 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 disk is described in the OpenVMS System Management Utilities Reference Manual. 13.Verify logical names (upgrades only). If you are upgrading your BASEstar system, ensure that 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 procedure. Introduction 1-19 Introduction 1.4 Preinstallation Steps If you are upgrading BASEstar device connection management, ensure that 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. 14.Review release notes. To read or print out the release notes included in the BASEstar distribution kit, invoke VMSINSTAL in the following manner: @VMSINSTAL BCCXX034 mtcu: OPTIONS N Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: Where XX = VV for OpenVMS VAX and XX = VA for OpenVMS Alpha. Select an option when the installation procedure prompts for release note options. 15.Check required OpenVMS tailoring classes in the BASEstar Classic System Software Addendum (SSA). OpenVMS classes are mutually exclusive subsets of OpenVMS files that provide a mechanism by which customers can include only site-specific OpenVMS files on their systems. This frees up space on the system disk and results in performance and maintenance gains. It also tailors the general all-purpose nature of the OpenVMS operating system to specific customer needs. Refer to the BASEstar Classic, Version 3.4 System Support Addendum (SSA) for a list of the required OpenVMS classes. 1-20 Introduction Introduction 1.5 Upgrade Overview to a BASEstar Classic 3.4 system 1.5 Upgrade Overview to a BASEstar Classic 3.4 system On an upgrade from BASEstar Classic V3.3 to V3.4, all data base files located in BCC$SYSDATA will be converted to the new V3.4 format during the installation IVP. This will require that all BASEstar logical point values, including points set up to be persistant, be set to their initial value on the next startup of the BASEstar system. The data base conversion execution will log its progress to sys$output during the IVP. Requirements for a successful conversion include the BCC$SYSDATA disk having 1.5 times the block usage in BCC$SYSDATA as free space, which is verified by the installation procedure. In addition, the user can request that log files be kept during the conversion, which would log each characteristic of a data base object both before and after it is converted. If log files are requested, it is reccommended that their location be a scratch disk (ie, NOT the system disk, and NOT the BCC$SYSDATA disk) with at least 100000 free blocks. IF the conversion process seems to hang, it may be due to this disk filling up, at which time the user will have to provide additional free space on the disk for the conversions to continue. Note that the time required for the conversions to complete is dependant on the size of the BASEstar object data base. This could take an hour or more with larger systems. This amount of time could cause a user to be concerned that the conversion is hung. If so, monitor the process performing the installation, as it should be consuming CPU time on a regular basis. Also note that all DCM data base files are also converted during the BASEstar IVP. This is because V3.3 of DCM will not run with V3.4 of BASEstar, and so a DCM upgrade is also required before restarting the BASEstar system. If for any reason the data base conversions fail, you can not start/use the BASEstar system until the problem is resolved. IF the cause of the problem is known (ie exiting via CTRL/Y for some reason, like the log file location disk is not large enough), you may rectify the problem, and re- run the conversions. Once the problem is fixed, execute the procedure SYS$COMMON:[SYSTEM.BCC]BCC$RESTORE_V33_DB.COM Introduction 1-21 Introduction 1.5 Upgrade Overview to a BASEstar Classic 3.4 system This will replace all the BASEstar object data base files to their V3.3 state. You can then re-execute the conversions, by executing the IVP provided by the installation, and placed in SYS$TEST:BCC$IVP. If you are unable to determine the cause of the problem, you must collect the following information, and submit it via normal problem reporting channels: - a LOG of your installation, including the data base conversion failure. - a FULL directory of the system's BCC$SYSDATA ($ DIR/FULL BCC$SYSDATA:). - the LOG file of the object type being converted at the time of the failure. Log files created are as follows; (where BCC$LOG_DATA is the directory location the user provided for log file placement): BCC$LOGDATA:DB_DEVICE.LOG BCC$LOGDATA: DB_PHYPOINT.LOG BCC$LOGDATA: DB_POLLING.LOG BCC$LOGDATA: DB_CONFIG.LOG BCC$LOGDATA: DB_POINT.LOG BCC$LOGDATA: DB_STRUCTURE.LOG BCC$LOGDATA: DB_FIELD.LOG BCC$LOGDATA: DB_ELEMENT.LOG BCC$LOGDATA: DB_EXTMAP.LOG BCC$LOGDATA: DB_LOCAL_NAME.LOG BCC$LOGDATA: DB_GLOBAL_NAME.LOG BCC$LOGDATA: DB_MEMBER.LOG BCC$LOGDATA: DB_RELATION.LOG BCC$LOGDATA: DB_ITEM.LOG BCC$LOGDATA: DB_NODE.LOG BCC$LOGDATA: DB_GROUP.LOG 1-22 Introduction Introduction 1.5 Upgrade Overview to a BASEstar Classic 3.4 system BCC$LOGDATA: DB_SERVERPORT.LOG BCC$LOGDATA: DB_SESSION.LOG BCC$LOGDATA: DB_USER.LOG BCC$LOGDATA: DB_PARAMETER.LOG Introduction 1-23 2 _________________________________________________________________ Installation This chapter describes the step-by-step installation of BASEstar Classic 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 Classic software components are installed using a combination of four procedures: o Main BASEstar (single node or VMScluster) o Device connection management (single node or VMScluster) o Utility (single node) o BASEstar Classic CIMfast (single node or VMScluster) There is also an optional software kit that can be installed for DEC Rdb integration. For more information, refer to the BASEstar Classic DEC Rdb Database Server Guide. Read the instructions for installing BASEstar software. Follow the instructions for installing BASEstar device connection management, utility, and BASEstar Classic CIMfast software, all of which are optional installations. Refer to Appendix A and Appendix B for sample installation procedures. All installation procedures will perform both new and upgrade installations. ________________________ Note ________________________ Digital strongly recommends that you read the release notes before performing an installation. ______________________________________________________ Installation 2-1 Installation Be prepared to provide the following information during the installation: ___________________________________________________________ Step_______Information_to_prepare_before_installation...__ 1. _____ BCC$SPECIFIC directory location 2. _____ BCC$COMMON directory location 3. _____ Global name server or name dispatcher selection 4. _____ Names of the global name server nodes and size of global name file 5. _____ Size estimates of local name file, point file, ____________and_group_file_for_your_BASEstar_system________ During the installation procedure, you are prompted to respond to questions. Enter Y for yes or N for no, or just press Return to select the default response. You can enter a question mark and press Return after any prompt to receive online help. To abort the installation procedure at any time, press Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. ________________________ 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 ________________________ Note ________________________ Although this chapter uses the installation example for an OpenVMS VAX system, the procedure is also applicable to OpenVMS Alpha systems. ______________________________________________________ 2-2 Installation Installation 2.1 Installing BASEstar Software This section describes how to install BASEstar software. Perform the following steps: 1. Log in to the OpenVMS user account named SYSTEM. 2. Invoke VMSINSTAL. $ @sys$update:vmsinstal The system displays the following: OpenVMS VAX Software Product Installation Procedure V6.2 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. 3. If you have active processes, VMSINSTAL lists them and asks if you want to continue. %VMSINSTAL-W-ACTIVE, The following processes are still active: SYSTEM * Do you want to continue anyway [NO]? YES 4. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? YES If you have not backed up your system, enter N and refer to the OpenVMS System Management Utilities Reference Manual. If you are satisfied with your backup, press Return to continue. 5. Mount the media. You are prompted for the location of the distribution media, the products you want to install, and options as follows: * Where will the distribution volumes be mounted: SYS$SYSDEVICE:[KIT] Enter the products to be processed from the first distribution volume set. * Products: BCCVV034 * Enter installation options you wish to use (none): The installation continues with the following: The following products will be processed: BCCVV V3.4 Beginning installation of BCCVV V3.4 at 10:49 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installation 2-3 Installation 2.1 Installing BASEstar Software BASEstar Kernel V3.4 VAX Installation Procedure ----------------------------------------------- This system is using OpenVMS Version 6.2 Image CLINOSHARE.EXE must be registered %REGISTER-I-ADDED added CLINOSHARE to registry %REGISTER-I-SUMMARY images examined: 1, dependent images: 1 6. Respond to license registration queries. BASEstar requires one of these licenses to be registered and loaded on all nodes on which BASEstar will run: Product --------------- [1] BASESTAR [2] BASESTAR-G [3] BASESTAR-RT [4] BASESTAR-RT-G [5] BASESTAR-USER [6] BASESTAR-LTD [7] BASESTAR-RT-LTD [8] BASESTAR-CU [9] BASESTAR-CU-RT * Which of the above licenses will be used? [1]: Product: BASESTAR Producer: DEC Version: Release Date: * Does this product have an authorization key registered and loaded? YES The procedure prompts you to ensure that you have the correct BASEstar license installed on the system. Enter the appropriate number if the license is already installed. If not, abort the installation and install the BASEstar license. 7. DECnet node information is verified and displayed. Getting data from $ MCR NCP LIST EXECUTOR ... ... Done. SCSNODE and SCSSYSTEMID checks passed. The DECnet node ID found for this node is: 36063 (35.223) 8. Respond to node information. 2-4 Installation Installation 2.1 Installing BASEstar Software The procedure determines if the executing node is a member of a multinode VMScluster. If the executing node is a standalone node or clustered with only one active member, the following message is displayed: This node is not a member of a multi-node VMScluster. A single-node installation will be performed. __________________________________ Processing node NODENAME:: __________________________________ If the executing node is a member of a multinode cluster, you will be prompted to indicate if you want a single-node installation: This node is a member of a multi-node VMScluster. A single-node installation or a multi-node installation can be chosen. For a multi-node installation, the nodes must share a cluster common system disk, and so must all be of the same architecture type (AXP or VAX). * Do you want to install BASEstar on just one node [YES]? NO If you answer N, the following text is displayed: A VMScluster installation will be performed. The current node, ALIGTR, will be the first node in the installation. Verifying node ALIGTR:: information ... 9. Enter additional nodes. If you are performing a cluster installation, you will be prompted to enter the additional nodes on which you want to install BASEstar software: You will now be prompted to enter the additional VMScluster nodes on which BASEstar is to be installed. End the list with a carriage return . (Enter Control-Y to abort the installation, if necessary.) Current node name list is: ALIGTR * Enter node name #2 (CR to end list): SAXPHN Verifying node SAXPHN:: information ... Current node name list is: ALIGTR, SAXPHN * Enter node name #3 (CR to end list): Installation 2-5 Installation 2.1 Installing BASEstar Software 2 valid node names were entered: ALIGTR, SAXPHN * Is this list correct? Y __________________________________ Processing node 1, ALIGTR:: __________________________________ 10.Install additional components. 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 is displayed: 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 List Services Support [YES]? * Do you want to install BASEstar Menu System [YES]? ________________________ Note ________________________ BASEstar Menu, available on VAX systems only. ______________________________________________________ 11.Provide directory location. 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]]: 2-6 Installation Installation 2.1 Installing BASEstar Software 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. (Because these files are data and command files, the system disk may not be an appropriate location.) If you are installing on a VMScluster node and do not use the system disk, specify a different directory name for each node within the VMScluster system. Verify the directory name specified: The directory entered is: SYS$SPECIFIC:[BCC$SPECIFIC] * Is this correct? YES 12.Choose a global name server or name dispatcher. Specify whether the system is to be configured as a global name server or name dispatcher. To perform global name operations, at least one BASEstar system in the BASEstar domain must be a global name server. VMSINSTAL displays the following prompt: Each BASEstar system must be configured to run either a Global Name Server or a Name Dispatcher. * Do you want this system to be configured as a Global Name Server [YES]? If you enter Y, the system will be a global name server. If you enter N, the system will be a name dispatcher. 13.Select a target size for data files. You must choose a target size for the following data files. BCC$POINT_FILE ______________ Initial Allocation Extend Allocation Initial File Size [1] 500 Points 500 Points 840 Disk Blocks [2] 2,000 Points 1,000 Points 2,223 Disk Blocks [3] 10,000 Points 5,000 Points 10,675 Disk Blocks [4] 30,000 Points 10,000 Points 27,219 Disk Blocks * Enter BCC$POINT_FILE size [1]: 2 BCC$GROUP_FILE ______________ Initial Allocation Extend Allocation Initial File Size Installation 2-7 Installation 2.1 Installing BASEstar Software [1] 500 Groups 500 Groups 819 Disk Blocks [2] 2,000 Groups 1,000 Groups 2,223 Disk Blocks * Enter BCC$GROUP_FILE size [1]: 1 BCC$LOCAL_NAME_FILE ___________________ Initial Allocation Extend Allocation Initial File Size [1] 500 Names 500 Names 342 Disk Blocks [2] 2,000 Names 1,000 Names 867 Disk Blocks [3] 10,000 Names 5,000 Names 4,023 Disk Blocks [4] 30,000 Names 10,000 Names 10,179 Disk Blocks * Enter BCC$LOCAL_NAME_FILE size [1]: 2 If you are performing a cluster installation, the information in steps 10 through 13 is displayed for each additional node in the cluster. 14.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. 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]]: The directory entered is: SYS$SPECIFIC:[BCC$SPECIFIC] * Is this correct? Y You must now enter a list of the node names of all BASEstar Global Name Server systems with which the newly-installed BASEstar node (or nodes) will interact. This list is required for both new Global Name Server systems and for new Name Dispatcher systems. For your convenience, the list will start with the list of nodes in this installation that you designated earlier to be configured as Global Name Servers. 2-8 Installation Installation 2.1 Installing BASEstar Software 15.Enter node names. Current Global Name Server list is: ALIGTR * Enter a Global Name Server node name, CR to end list: The final list is: ALIGTR * Is this list correct? Yes The value of the BASEstar parameter BCC$QUORUM is established from the list of global name servers entered. The following is displayed: %BCCVV-I-QUORUMSET, Global Name Server quorum will be set to 1 If the above quorum value is not consistent with other Global Name Server systems in the same BASEstar domain, 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. 16.Choose a target size for the global name file on the global name server systems. You must choose a target size for the Global Name File on the Global Name Server Systems: BCC$GLOBAL_NAME_FILE ____________________ Initial Allocation Extend Allocation Initial File Size [1] 500 Names 500 Names 342 Disk Blocks [2] 2,000 Names 1,000 Names 867 Disk Blocks [3] 10,000 Names 5,000 Names 4,023 Disk Blocks [4] 30,000 Names 10,000 Names 10,179 Disk Blocks * Enter BCC$GLOBAL_NAME_FILE size [1]: 2 17.Read informational messages. The installation procedure has no further questions to ask during the installation process. Until the IVP executes, it can continue without user assistance. Installation 2-9 Installation 2.1 Installing BASEstar Software IF this is a V3.3 to V3.4 UPGRADE, a data base conversion will execute during the IVP. This conversion requires user input regarding log file locations. The IVP will announce the beginning of the data base conversions, before prompting for logging information. 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. If the data base conversions are required, time will vary depending on the size of your BASEstar Classic object data base. Note: Please review introduction section, "Upgrade Overview to a BASEstar Classic 3.4 System" for disk space requirements needed for a conversion upgrade. __________________________________ 10:15:59 This installation creates a VMS rights identifier named BCC$USER, which is used to control access to BASEstar. After the installation is finished, the VMS Authorize Utility must be used to grant this identifier to all accounts that will use BASEstar. --------------------------------------------------------------- A R E M I N D E R T O T H E I N S T A L L E R Each VMS user account that will issue BSTAR commands must be granted the BCC$USER rights identifier, as well as having certain Authorized privileges set. >> Remember to grant the BCC$USER identifier to the SYSTEM account >> (and/or any other accounts you will be using to start the BASEstar >> system) and to check the Authorized privileges of those accounts >> BEFORE YOU ATTEMPT TO START THE BASESTAR SYSTEM. --------------------------------------------------------------- %BCCVV-I-IDENTEXISTS, The BCC$USER identifier already exists Note: The file SYS$SYSTEM:RIGHTSLIST.DAT will be modified to permit access by processes that have been granted the BCC$USER identifier. If RIGHTSLIST.DAT does not reside in SYS$SYSTEM, the logical name RIGHTSLIST will be translated to access the file for modification. 2-10 Installation Installation 2.1 Installing BASEstar Software The installation procedure restores the save sets, creates system directories, and displays the following: 10:16:05 %VMSINSTAL-I-RESTORE, Restoring product save set B ... 10:16:58 %VMSINSTAL-I-RESTORE, Restoring product save set C ... 10:17:09 %VMSINSTAL-I-RESTORE, Restoring product save set D ... 10:17:24 %VMSINSTAL-I-RESTORE, Restoring product save set E ... 10:17:29 __________________________________ Installing BASEstar on node ALIGTR:: ... __________________________________ %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]. 10:17:43 %BCCVV-I-STARTCORE, BASEstar CORE installation beginning on ALIGTR:: . 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_VMS.COM file should be edited to invoke this startup file when the system boots. 10:24:11 BASEstar Data Management installation beginning on ALIGTR %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[BCC$COMMON.DMQ_EXAMPLE]. 10:24:58 BASEstar External Data Support installation beginning on ALIGTR 10:25:08 BASEstar List Services Support installation beginning on ALIGTR 10:25:13 %BCCVV-I-STARTMENU, BASEstar Menu System installation beginning on ALIGTR. Installation 2-11 Installation 2.1 Installing BASEstar Software If you are performing a cluster installation, the system disk directory and installation messages are displayed for each additional node in the cluster. %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 is run. BASEstar Kernel V3.4 Installation Verification Procedure (IVP) $ DEFINE/NOLOG/PROCESS BCC$SYSDATA SYS$SPECIFIC:[BCC$SPECIFIC] $ DEFINE/NOLOG/PROCESS BCC$SYSTEM VMI$ROOT:[BCC$COMMON] $ set noverify 3.4 conversions checked/done... %BCCIVP-I-CORESTART, CORE verification starting on node ALIGTR. %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 ALIGTR. %BCCIVP-I-PASS, DMGT file check passed. %BCCIVP-I-EXTMAPSTART, External Data Server verification starting on node ALIGTR. %BCCIVP-I-PASS, External Data Server file check passed. %BCCIVP-I-MENUSTART, MENU verification starting on node ALIGTR. %BCCIVP-I-PASS, Menu System file check passed. %BCCIVP-I-PASS, Menu System command check passed. %BCCIVP-I-PASS, Menu System menu check passed. If you are performing a cluster installation, the check messages are displayed for each node in the cluster. BASEstar V3.4 IVP completed successfully. 2-12 Installation Installation 2.1 Installing BASEstar Software 18.End the installation procedure. Installation of BCCVV V3.4 completed at 10:39 VMSINSTAL procedure done at 10:39 The BASEstar single-node installation is complete. You can now log out of the privileged account if you do not want to install additional BASEstar software. Continue with instructions later in this section to install additional BASEstar software or consult Chapter 3 for postinstallation tasks. 2.2 Installing BASEstar Device Connection Management Software 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. The BASEstar device connection management upgrade installation consists of the following steps: 1. Log in to the OpenVMS user account named SYSTEM. 2. Invoke VMSINSTAL. The system displays the following: VAX/VMS Software Product Installation Procedure V6.2 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. 3. If you have active processes, VMSINSTAL lists them and asks if you want to continue. %VMSINSTAL-W-ACTIVE, The following processes are still active: SYSTEM * Do you want to continue anyway [NO]? YES 4. Confirm system 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 the OpenVMS System Management Utilities Reference Manual. If you are satisfied with your backup, press Return to continue. 5. Mount the media. Installation 2-13 Installation 2.2 Installing BASEstar Device Connection Management Software You are prompted for the location of the distribution media, the products you want to install, and options as follows: * Where will the distribution volumes be mounted: SYS$SYSDEVICE:[KIT] Enter the products to be processed from the first distribution volume set. * Products: DCMVV034 * Enter installation options you wish to use (none): The installation continues with the following: The following products will be processed: DCMVV V3.4 Beginning installation of DCMVV V3.4 at 10:42 %VMSINSTAL-I-RESTORE, Restoring product save set A ... BASEstar Device Connect Management (DCM) V3.4 VAX Installation Procedure ----------------------------------------------------------------- 6. Existing BASEstar installation message is displayed. If BASEstar is already installed on your system, the following message is displayed: BASEstar is installed on this system. The file SYS$COMMON:[SYSLIB]BCC$SHR.EXE was found. Its image file identification is: BCC 3.4 7. Respond to node information. The procedure determines if the executing node is a member of a multinode VMScluster. If the executing node is a standalone node or clustered with only one active member, the following message is displayed: This node is not a member of a multi-node VMScluster. A single-node installation will be performed. __________________________________ Processing node NODENAME:: __________________________________ If the executing node is a member of a multinode cluster, you will be prompted to indicate if you want a single-node installation: 2-14 Installation Installation 2.2 Installing BASEstar Device Connection Management Software This node is a member of a multi-node VMScluster. A single-node installation or a multi-node installation can be chosen. For a multi-node installation, you will be prompted to enter the node names to be processed. The nodes must share a cluster-common system disk. Also, the current node (the node presently executing VMSINSTAL) will automatically be the first node processed. * Do you want to install DCM on just this node [YES]? NO If you answer N, the following text is displayed: ----------------------------------------- A cluster installation has been selected. ----------------------------------------- The current node, ALIGTR, will be processed first. Checking node ALIGTR:: ... BASEstar is installed on this node. The file SYS$SPECIFIC:[SYS$STARTUP]BCC$STARTUP.COM was found. The node passed all checks. 8. Enter additional nodes. If you are performing a cluster installation, you will be prompted to enter the additional nodes on which you want to install BASEstar software: You will now be prompted to enter the additional cluster nodes on which BASEstar DCM is to be installed. End the list with a carriage return CR. (Enter Control-Y to abort the installation, if necessary.) Current node name list is: ALIGTR * Enter another node name (or CR to end the list): SAXPHN Checking node SAXPHN:: ... BASEstar is installed on this node. The file SYS$SPECIFIC:[SYS$STARTUP]BCC$STARTUP.COM was found. Installation 2-15 Installation 2.2 Installing BASEstar Device Connection Management Software ----------------------------------------------- Wait -- using SYSMAN utility to check certain logical names on cluster member ... ... Done. ----------------------------------------------- The node passed all checks. Current node name list is: ALIGTR, SAXPHN * Enter another node name (or CR to end the list): 2 valid node names were entered: ALIGTR, SAXPHN * Is this list correct? Y The installation continues: __________________________________ Processing node 1, ALIGTR:: __________________________________ The BASEstar Menu System is present. The DCM Menu System will be installed on this node. __________________________________ 9. Choose the size of the file. You must choose a initial size for the PHYSICAL POINT data file: ILAN$PHYPOINT_FILE ___________________ Initial Allocation Extend Allocation File Size [1] 500 Phypoints 500 Phypoints 1,251 Disk Blocks [2] 2,000 Phypoints 1,000 Phypoints 3,333 Disk Blocks [3] 10,000 Phypoints 5,000 Phypoints 15,744 Disk Blocks [4] 20,000 Phypoints 10,000 Phypoints 32,604 Disk Blocks * Enter ILAN$PHYPOINT_FILE size [1]: 2 Select a file size for the physical point data file. Enter the correct choice from the menu. If you are performing a cluster installation, VMSINSTAL processes each node in the cluster and you select the size of the PHYSICAL POINT data file. 2-16 Installation Installation 2.2 Installing BASEstar Device Connection Management Software 10.Read the informational messages. Post-installation messages for the installer appear next. Press [Return] to continue: Post-installation messages for the installer ---------------------------------------------------------- ILAN$STARTUP.COM, a startup command procedure, is used to set up the environment for Device Connect Management. During the installation, this file will be placed in the SYS$SPECIFIC:[SYS$STARTUP] directory of the nodes on which this installation is being performed. If this is a first-time DCM installation on a this system, the system startup command procedure SYS$MANAGER:SYSTARTUP_VMS.COM or SYS$MANAGER:SYSTARTUP_V5.COM (for VAX VMS versions prior to V6.0) needs to be manually edited (after this installation has successfully finished). Locate the line $ @ SYS$STARTUP:BCC$STARTUP.COM and add this new line immediately after the BCC$STARTUP line: $ @ SYS$STARTUP:ILAN$STARTUP.COM ---------------------------------------------------------- ---------------------------------------------------------- The installation procedure has no further questions to ask and can continue from this point without user assistance. The time needed to finish the installation will vary depending on the number of nodes selected for installation and the type of processors and disks involved. ---------------------------------------------------------- __________________________________ Installing DCM on node ALIGTR:: ... __________________________________ 10:44:59 Creating DCM data files for this node ... Providing images to BCC$SYSTEM ... Installation 2-17 Installation 2.2 Installing BASEstar Device Connection Management Software Providing DCM example PL/I programs to sub-directory of BCC$SYSTEM ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory $2$DUA0:[SYS0.SYSCOMMON.BCC$COMMON.DCM_EXAMPLE]. Providing RS232 DAS source files to sub-directory of BCC$SYSTEM ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory $2$DUA0:[SYS0.SYSCOMMON.BCC$COMMON.RS232_EXAMPLE]. Providing Network DAS NCT source files to sub-directory of BCC$SYSTEM ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory $2$DUA0:[SYS0.SYSCOMMON.BCC$COMMON.NCT_EXAMPLE]. ... Done. 10:47:47 Checking the BASEstar Parameter file for "ILAN$*" (DCM) parameters ... ... Done. 10:48:43 Installing the DCM Menu System on this node ... ... Done. If you are performing a cluster installation, the informational messages for each node in the cluster are displayed and the installation continues: 10:50:56 %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... IVP phase beginning on node ALIGTR ... %SYSMAN-I-ENV, current command environment: Individual nodes: ALIGTR Username SYSTEM will be used on nonlocal nodes %SYSMAN-I-TIMEVAL, timeout value is 00:11:00.00 %SYSMAN-I-OUTPUT, command execution on node ALIGTR $ @SYS$STARTUP:ILAN$STARTUP.COM $ @SYS$TEST:ILAN$IVP.COM ----------------------------------------------------------------------- BASEstar DCM V3.4 Installation Verification Procedure (IVP) starting. ----------------------------------------------------------------------- 2-18 Installation Installation 2.2 Installing BASEstar Device Connection Management Software Checking logical name BCC$SYSDATA ... Checking logical name BCC$SYSTEM ... Checking ILAN files ... Checking files in SYS$COMMON:[BCC$COMMON.DCM_EXAMPLE] ... Checking files in SYS$COMMON:[BCC$COMMON.NCT_EXAMPLE] ... Checking files in SYS$COMMON:[BCC$COMMON.RS232_EXAMPLE] ... %ILAN$IVP-E-FAIL, File check passed. Checking ILAN installed images ... %ILAN$IVP-I-PASS, Installed image check passed. Checking "ILAN$*" BASEstar parameters ... %ILAN$IVP-I-PASS, Parameter check passed. ----------------------------------------------------------------------- BASEstar DCM V3.4 IVP completed successfully. ----------------------------------------------------------------------- If you are performing a cluster installation, the IVP messages for each node in the cluster are displayed. 11.End the installation procedure. Installation of DCMVV V3.4 completed at 10:53 VMSINSTAL procedure done at 10:53 The BASEstar device connection management installation is complete. You can now log out of the privileged account if you do not want to install additional BASEstar software. Continue with instructions in this chapter for installing additional BASEstar software or consult Chapter 3 for postinstallation tasks. 2.3 Installing BASEstar Utilities Software This section describes how to install BASEstar utilities, including: o The BCC$BASEGEN command procedure, which provides suggested settings for BASEstar and system parameters as well as OpenVMS process quotas. Refer to the BASEstar Classic Configuration and Tuning Guide for information on how to use this utility. Installation 2-19 Installation 2.3 Installing BASEstar Utilities Software 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 OpenVMS version number mismatch software, which resolves, or relinks the BASEstar shareable image when a new version of OpenVMS software is installed on a system. o Monitor Port Utility, which provides a continuously updated display of port data for all ports defined on the system. o Monitor BASEstar Utility, which analyzes the processes running on a BASEstar system. Monitor BASEstar continuously displays a default set of processes or allows the display of a customized set of processes. o BASEstar LSE environment, which allows you to use VAX LSE, a multiple-language text editor that speeds the writing and compiling of source code. To use the BASEstar LSE environment, you must first install VAX Language-Sensitive Editor software. o Value Notification Utility, which notifies you of changes in the value of logical points that have been supplied to the utility. The BASEstar utilities installation consists of the following steps: 1. Log in to the OpenVMS user account named SYSTEM. 2. Invoke VMSINSTAL. $ @sys$update:vmsinstal The system displays the following: VAX/VMS Software Product Installation Procedure V5.5-2 It is dd-mm-yyyy at hh:mm. Enter a question mark (?) at any time for help. 3. If you have active processes, VMSINSTAL lists them and asks if you want to continue. %VMSINSTAL-W-ACTIVE, The following processes are still active: SYSTEM * Do you want to continue anyway [NO]? YES 2-20 Installation Installation 2.3 Installing BASEstar Utilities Software 4. Confirm system 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 the OpenVMS System Management Utilities Reference Manual. If you are satisfied with your backup, press Return to continue. 5. Mount the media. You are prompted for the location of the distribution media, the products you want to install, and options as follows: * Where will the distribution volumes be mounted: SYS$SYSDEVICE:[KIT] Enter the products to be processed from the first distribution volume set. * Products: BCCVVUTL034 * Enter installation options you wish to use (none): The procedure displays the following: The following products will be processed: BCCVVUTL V3.4 Beginning installation of BCCVVUTL V3.4 at 10:56 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Installing BASEstar CORE Utilities Kit 6. Choose the IVP. * Do you want to run the IVP after the installation [YES]? If you want to run the IVP, enter Y. 7. Purge files. * Do you want to purge files replaced by this installation [YES]? If the installation is an upgrade, enter Y to delete the previous versions of the files created by the installation. Site-specific files or OpenVMS installed images are not purged. 8. Choose options. Installation 2-21 Installation 2.3 Installing BASEstar Utilities Software Enter the option to perform. Type 99 to end selections: [1] Install All Options [2] BASEstar Text Services [3] BCC$BASEGEN.COM Utility [4] Monitor Port Utility [5] Monitor BASEstar Utility [6] BASEstar LSE Environment File (VAX Only) [7] Value Notification Utility [8] Resolve VMS Ident Version Mismatches * Enter Selection: : 1 Enter the appropriate number. 9. VMSINSTAL begins the installation procedure. BASEstar Text Services have been installed. The BASEGEN Utility has been installed. The Monitor Port Utility has been installed. Monitor BASEstar utility installed. The logical name BCC$MONITOR_DATA has been defined. Add the following line to the BASEstar startup procedure SYS$STARTUP:BCC$STARTUP.COM to define this logical name during system startup: $ DEFINE/NOLOG/SYSTEM BCC$MONITOR_DATA BCC$SYSDATA:BCC$MON_BSTAR_APP.DAT Installing the Value Notification Utility Installing the BASEstar LSE Environment File 10.Verify the BASEstar development license. A development license is required to be registered and loaded for all nodes on which the Value Notification or BASEstar LSE Environment File will run: 2-22 Installation Installation 2.3 Installing BASEstar Utilities Software Product --------------- [1] BASESTAR [2] BASESTAR-LTD [3] BASESTAR-USER [4] BASESTAR-G [5] BASESTAR-CU * Which of the above licenses will be used? [1]: Product: BASESTAR Producer: DEC Version: Release Date: * Does this product have an authorization key registered and loaded? y If you choose either the Value Notification Utility or the BASEstar LSE Environment file, the procedure prompts you to ensure that you have the correct BASEstar development license installed on the system. Enter the appropriate number if the license is already installed. If not, abort the installation and install the license. 11.Read informational messages. The installation procedure continues without further input as follows: The Value Notification Utility has been installed. The LSE Environment File has been installed. Resolving VMS ident version mismatches No ident version mismatch detected %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 12.Observe the IVP. BASEstar Utility V3.4 Installation Verification Procedure %BCCUTL-I-PASS, Utility file check passed BASEstar Utility V3.4 IVP completed successfully 13.End the installation procedure. Installation of BCCVVUTL V3.4 completed at 10:59 VMSINSTAL procedure done at 10:59 Installation 2-23 Installation 2.3 Installing BASEstar Utilities Software The BASEstar utilities installation is complete. You can now log out of the privileged account if you do not want to install additional BASEstar software. Consult Chapter 3 for postinstallation tasks. 2.4 Installing BASEstar Classic CIMfast Software This section describes how to install BASEstar Classic CIMfast software. ________________________ Note ________________________ If you plan to use DECmessageQ support, you must start DECmessageQ before installing BASEstar Classic CIMfast software. If you plan to use CIMfast SQL support, you must install and start the appropriate database software. ______________________________________________________ To install BASEstar Classic CIMfast software, perform the following steps: 1. Log in to the OpenVMS user account named SYSTEM. 2. Invoke VMSINSTAL. IVAX20 » @sys$update:vmsinstal BCFxxx022 DISK1:[CIMFAST.KITS] where BCFxxx022 is the BASEstar Classic CIMfast product name and version, (where xxx=VAX or xxx=AXP for Alpha) DISK1:[CIMFAST.KITS] is the name of the directory containing the software kit. If you include the optional OPTIONS parameter, a question is displayed that asks you if you want to see the release notes. If you do not include the OPTIONS N parameter, the VMSINSTAL command procedure does not ask you if you want to see the release notes. Ensure that you read the release notes before proceeding with the installation; they may contain additional information about the installation. If you are restarting the installation and have already read the release notes, you do not need to specify OPTIONS N. When you invoke VMSINSTAL, there are several other options you can choose, as follows: o Auto_answer option (A) 2-24 Installation Installation 2.4 Installing BASEstar Classic CIMfast Software Creates a file that contains your answers to the VMSINSTAL command procedure questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation or a system upgrade. o Get save set option (G) Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L) Logs all activity to the terminal during the installation. o Alternate root option (R) Lets you install the product to a system root other than the root of the system that is running. See the OpenVMS documentation on software installation in the OpenVMS System Management Subkit for more information on these options. If you specify more than one option, separate the options with commas (for example, OPTIONS A,N). The system displays the following: OpenVMS VAX Software Product Installation Procedure V6.1 It is 28-JUN-1996 at 10:45. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command procedure command line to access the release notes during the installation. 3. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? y You must back up the system disk before performing an installation. If you are satisfied with the backup of the system disk, press Return. If you are not satisfied, enter N to stop the installation. After you back up the system disk, you can restart the installation. Installation 2-25 Installation 2.4 Installing BASEstar Classic CIMfast Software 4. Mount the media. You must now mount the first distribution volume on the device if you specified one when you invoked VMSINSTAL. An example follows: Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, BASEstar CIMfast for OpenVMS VAX MOUNTED ON _$$MTA0:(NODE 1) The following products will be processed: BCFVAX V2.2 Beginning installation of BCFVAX V2.2 at 15:44 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name is displayed in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. If you enter Y to indicate that you are ready, VMSINSTAL displays a message that the media containing BASEstar Classic CIMfast has been mounted on the specified device and that the installation has started. If you enter the wrong device name when you invoke VMSINSTAL and need to restart the installation, enter N in response to the following question: Are you ready? To abort the installation, press Ctrl/Y. 5. Mount additional media volumes. If your installation kit contains more than one volume, VMSINSTAL prompts you to mount the additional volumes and then asks you to indicate that you are ready to continue the installation of BASEstar Classic CIMfast: %BACKUP-I-READYREAD, mount volume 2 on _MTA0: for reading Enter "YES" when ready: 6. Choose a release notes option. If you specified OPTIONS N when you invoked VMSINSTAL, the following is displayed: 2-26 Installation Installation 2.4 Installing BASEstar Classic CIMfast Software Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: You must choose one of the four options to read the release notes: o Option 1 VMSINSTAL displays the release notes on the console terminal. You can stop the display at any time by pressing Ctrl/C. o Option 2 VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can press Return to send the file to the default output print device or you can enter another queue name. o Option 3 VMSINSTAL displays the release notes on the console terminal and then prompts you for a queue name for the printed version. o Option 4 Choose this option if you have already read the release notes and are restarting the installation. VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To continue the installation, enter Y If you do not want to continue, press Return. In either case, the release notes are copied to the following file, located in the SYS$HELP directory: Installation 2-27 Installation 2.4 Installing BASEstar Classic CIMfast Software SYS$HELP:BCF022.RELEASE_NOTES ________________________ Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete the release notes for previous versions of BASEstar Classic CIMfast. ______________________________________________________ 7. Select the target installation directory. Select the directory where you want to install BASEstar Classic CIMfast. * In what directory do you wish CIMfast to be installed [SYS$SYSDEVICE:[BCF]]: 8. Select installation options. You can install the following options: o Cimfast DCM support. If you have BASEstar Classic DCM (Device Connection Manager) installed on your system, you have the option of installing CIMfast DCM programming support option. o Cimfast SQL support. In order to install CIMfast SQL support for RDB, a minimum of RDB V6.0 must be installed on your system. If you answer YES RDB installation, this version check will be done. * Do You want to install CIMfast SQL Support for DEC RDB [YES]? The installation checks for the existence of DEC RDB and Oracle software, and the previous existance of CIMfast SQL support. If BOTH RDB and Oracle are found, the procedure will prompt you for which software you choose to use with CIMfast SQL support. 2-28 Installation Installation 2.4 Installing BASEstar Classic CIMfast Software The database software MUST be started properly prior to the installation of CIMfast, and the logical SQL$DATABASE must be defined in order to run the IVP test procedure properly for CIMfast SQL support in your selected database. If no logical SQL$DATABASE is found the IVP will display a database location for its use or allow a change before the procedure runs. The installation procedure checks for the existence of the DMQ$USER logical to determine whether DECmessageQ is installed. It is possible for DECmessageQ to have been installed and the DMQ$USER logical to remain undefined. If the DMQ$USER logical is not defined, the following message is displayed: Is DECmessageQ installed on this system and do You want to have the CIMfast DMQ support installed ? If You answer 'Yes', the CIMfast installation will be aborted and You have to to run the file DMQ$STARTUP in the [EXE] directory of Your DMQ installation. If You answer 'No', the CIMfast installation continues without installing the CIMfast DMQ support. * Do You want to install the CIMfast DMQ support [YES]? The previous message indicates that you have the following options: o Abort the installation, run the DMQ$STARTUP file, and restart the installation. o Continue the installation without installing BASEst