BASEstar_Open_Server_for_OpenVMS____________________ Inst. & Management Guide Order Number: AA-QS3SB-TE April 1999 This manual provides instructions for installing and managing BASEstar Open Server for OpenVMS on VAX and Alpha platforms. Revision/Update Information: This is a revised document for the current release. Operating System and Version: OpenVMS Version 6.1, 6.2, 7.1 and 7.2 Software Version: BASEstar Open Server Version 3.2 Compaq Computer Corporation Huston,Texas ) ii ________________________________________________________________ First printing, July 1996 Revised, April 1997 Revised, April 1999 © Digital Equipment Corporation 1999. All Rights Reserved. The software described in this guide is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of the agreement. Compaq Computer 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. COMPAQ,the Compaq logo and the Digital logo are registered in the U.S. Patent and Trademark Office. Tru64 is a trademark of Compaq Computer Corporation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, BASEstar, DEC, DECmessageQ, DECnet, DECnet-DOS, DECosap, DEComni, DIGITAL, DIGITAL UNIX, FMS, LN03, MicroVAX, NAS, OpenVMS, OpenVMS Alpha, PATHWORKS, PDAS, Rdb/VMS, ReGIS, ThinWire, TK, ULTRIX, VAX, VAXcluster, VAX COBOL, VAX FORTRAN, VAX Pascal, VAX RMS, VMS/ULTRIX Connection, and VT. Microsoft and Windows NT are registered trademarks of Microsoft Corporation. The following are third-party trademarks: Other product names mentioned herein may be the trademarks of their respective companies. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... xi Part I Installing BASEstar Open Server 1 Preparing to Install BASEstar Open Server 1.1 Pre-Installation Check List...................... 1-1 1.2 Checking the Contents of the Distribution Kit.... 1-1 1.3 Required Operating System Components............. 1-2 1.4 Pre-requisite Hardware........................... 1-2 1.5 Pre-requisite Software........................... 1-3 1.6 Pre-requisite Licenses........................... 1-4 1.7 Backing Up Your System Disk...................... 1-4 1.8 Preparing Your System............................ 1-5 1.8.1 Account Privileges ............................ 1-5 1.8.2 Disk Space Requirements ....................... 1-5 1.8.3 Account Quotas for Installation ............... 1-6 1.8.4 OpenVMS SYSGEN Parameters and Minimum Values .. 1-8 1.9 Error Recovery................................... 1-9 2 Installing BASEstar Open Server 2.1 The Installation Procedure....................... 2-1 2.1.1 VMSINSTAL Checks .............................. 2-1 2.1.2 Installation Steps ............................ 2-2 iii 3 After Installing BASEstar Open Server 3.1 Post-Installation Checklist...................... 3-1 3.2 Running the Installation Verification Procedure Separately....................................... 3-1 3.2.1 Running the BASEstar Open Server Installation Verification Procedure......................... 3-2 3.2.2 Running the DEComni API Installation Verification Procedure......................... 3-2 3.3 Setting Up and Starting the BASEstar Open Environment...................................... 3-2 3.4 User Account Requirements........................ 3-3 3.5 Starting DEComni API............................. 3-3 3.6 Stopping DEComni API............................. 3-4 3.7 Getting Help and Reporting Problems.............. 3-4 4 Installing BASEstar CIMfast Part II Installing the Device Connection Manager 5 Before Installing the BASEstar Classic Device Manager 5.1 Overview......................................... 5-1 5.2 Main Installation Options........................ 5-1 5.3 Installation of the Device Connection Management Software......................................... 5-2 5.4 Distribution Kit................................. 5-2 5.5 Pre-requisite Hardware........................... 5-2 5.6 Pre-requisite and Optional Software.............. 5-2 5.7 Pre-installation Steps........................... 5-3 6 Installing the BASEstar Classic Device Manager 6.1 The Installation Procedure....................... 6-1 6.2 Installing BASEstar Software..................... 6-2 6.3 Installing BASEstar Device Connection Management Software......................................... 6-7 iv 7 After Installing the BASEstar Classic Device Manager 7.1 The Device Connection Manager Post-installation Procedures....................................... 7-1 Part III Environment Management 8 Introduction to Environment Management 8.1 Environment Management Overview.................. 8-1 8.2 Environment and Application Components Relationship..................................... 8-2 8.3 BASEstar Open Environment Components............. 8-2 8.3.1 Nodes ......................................... 8-3 8.3.2 PODB Nodes .................................... 8-4 8.3.3 Realms ........................................ 8-5 8.3.4 Sample Environment Configuration .............. 8-7 9 Environment Management Procedures 9.1 Setup Procedures................................. 9-2 9.1.1 Setting Up a Node ............................. 9-2 9.1.2 Setting Up a Realm ............................ 9-2 9.1.2.1 Setting Up a Realm on a Node................ 9-2 9.1.2.2 Setting Up the Realm Database on the PODB Node........................................ 9-3 9.1.3 Setting Up the Sample Environment ............. 9-3 9.2 Startup Procedures............................... 9-5 9.2.1 Starting Up a Node ............................ 9-5 9.2.2 Starting Up a Realm ........................... 9-5 9.2.2.1 Starting Up a Realm on a Node............... 9-5 9.2.2.2 Starting Up the Database Server for a Realm on the PODB Node............................ 9-5 9.2.3 Starting Up the Sample Environment ............ 9-6 9.3 Shutdown Procedures.............................. 9-8 9.3.1 Shutting Down a Realm ......................... 9-8 9.3.1.1 Shutting Down the Database Server for a Realm on the PODB Node...................... 9-8 9.3.1.2 Shutting Down a Realm on a Node............. 9-8 9.3.2 Shutting Down a Node .......................... 9-9 9.3.3 Shutting Down the Sample Environment .......... 9-10 9.4 Unset Procedures................................. 9-12 v 9.4.1 Unsetting a Realm ............................. 9-12 9.4.1.1 Unsetting a Realm from a Node............... 9-12 9.4.1.2 Unsetting a Realm Database on the PODB Node........................................ 9-12 9.4.2 Unsetting a Node .............................. 9-12 9.4.3 Unsetting the Sample Environment .............. 9-13 9.5 Monitoring BASEstar Open......................... 9-14 10 Environment Management Command Reference 10.1 Executing Environment Commands................... 10-1 10.1.1 Requirements and Constraints .................. 10-1 10.1.1.1 Users and Commands.......................... 10-1 10.1.1.2 Executing a Command......................... 10-4 10.2 Privileges for Running Environment Management Procedures....................................... 10-4 cli_bstr......................................... 10-6 bstr_env_show.................................... 10-8 bstr_node_setup.................................. 10-14 bstr_node_shut................................... 10-21 bstr_node_start.................................. 10-23 bstr_node_unset.................................. 10-25 bstr_realm_check_env............................. 10-27 bstr_realm_setup_db.............................. 10-30 bstr_realm_setup_node............................ 10-32 bstr_realm_shut_db............................... 10-34 bstr_realm_shut_node............................. 10-35 bstr_realm_start_db.............................. 10-37 bstr_realm_start_node............................ 10-38 bstr_realm_unset_db.............................. 10-40 bstr_run......................................... 10-42 11 BASEstar Open Environment Monitor 11.1 Introduction..................................... 11-1 11.2 Running the BASEstar Open Environment Monitor.... 11-3 11.3 General Characteristics.......................... 11-3 11.4 Views............................................ 11-4 11.4.1 Active Realm View ............................. 11-4 11.4.2 Active Node View .............................. 11-7 vi 12 BASEstar Open-Supplied Servers 12.1 Servers, Activities and Owned Resources.......... 12-3 12.1.1 Snapshots ..................................... 12-3 12.1.2 Logged Information ............................ 12-4 12.2 Global Object Services........................... 12-5 12.3 Application Management Services.................. 12-7 12.3.1 Logical Names - Inheritance and Usage ......... 12-7 12.3.1.1 Application Management Services Server Privileges.................................. 12-8 12.4 Event Services................................... 12-10 12.4.1 Using Application Management Services to Manage an Event Services Server....................... 12-10 12.4.2 Starting Up and Shutting Down an Event Services Server from the Command Interpreter............ 12-10 12.5 Packet Services.................................. 12-13 12.5.1 Using Application Management Services to Manage a Packet Services Server....................... 12-13 12.5.2 Starting Up and Shutting Down a Packet Services Server from the Command Interpreter............ 12-13 12.6 Data Services.................................... 12-16 12.6.1 Environmental Variables ....................... 12-16 12.6.2 Using Application Management Services to Manage a Data Services Server......................... 12-17 12.6.3 Starting Up and Shutting Down a Data Services Server from the Command Interpreter............ 12-18 12.7 Device Services.................................. 12-20 12.7.1 Global Variables .............................. 12-20 12.7.1.1 Specifying the Calling VMD.................. 12-20 12.7.1.2 Specifying the Connection Retry Timeout to a VMD......................................... 12-21 12.7.2 Using Application Management Services to Manage a Device Services Server....................... 12-22 12.7.3 Starting Up and Shutting Down a Device Services Server from the Command Interpreter............ 12-23 12.8 Combined Data & Device Services.................. 12-25 12.8.1 Environmental Variables ....................... 12-25 12.8.2 Using the Data & Device Services to Support Passive Connections............................ 12-27 12.9 PC Communication Servers......................... 12-28 vii 13 Application Management Services Monitor 13.1 Introduction..................................... 13-1 13.2 Running Application Management Services Monitor.. 13-1 13.3 General Characteristics.......................... 13-2 13.4 Views............................................ 13-4 13.4.1 Actor View .................................... 13-5 13.4.2 Activity View ................................. 13-8 13.4.3 Program View .................................. 13-10 13.4.4 Process View .................................. 13-12 13.4.5 Node View ..................................... 13-14 14 Log Services Features 14.1 Saving Copies of Log Files....................... 14-1 14.1.1 Purging Log Files ............................. 14-2 14.2 Log File Record Format........................... 14-2 14.2.1 Displaying Log Files .......................... 14-6 14.2.1.1 Displaying a Save Copy...................... 14-7 14.2.1.2 Displaying a Working Copy................... 14-7 14.3 Log Services Server Activities................... 14-7 15 Log Services Command Reference DISPLAY LOG...................................... 15-2 OPEN LOG......................................... 15-4 Part IV Installation and System Management Appendices A Files and Logical Names Installed by BASEstar Open Server A.1 Directories Created by BASEstar Open Server...... A-1 A.2 Files Created by BASEstar Open Server............ A-2 A.3 Systemwide Logical Names Created by BASEstar Open Server........................................... A-7 A.4 Files Created by DEComni API..................... A-7 A.4.1 DEComni API Files for Application Development.................................... A-8 A.4.2 DEComni API Files in VMI$ROOT ................. A-8 A.4.3 DEComni API Image Files in VMI$ROOT ........... A-12 viii B BASEstar Open Installation Messages B.1 BASEstar Open Message Listing.................... B-1 C Sample Installation Log Files for BASEstar Open Server on OpenVMS C.1 Installation of BASEstar Open Server for OpenVMS Alpha............................................ C-1 C.2 Installation of BASEstar Open Server for OpenVMS VAX.............................................. C-6 D Additional Files Created During Installation D.1 Files Created During DCM-Modeled Device Connectivity Installation........................ D-1 D.2 Files Created During BASEstar Open Server Utility Installation..................................... D-9 D.3 Files Created During BASEstar CIMfast Installation..................................... D-9 D.4 Systemwide Logical Names Created by the Device Connection Manager............................... D-14 E Device Connection Manager Installation Messages E.1 Message Format................................... E-1 E.2 Device Connection Manager Message Listing........ E-2 F Sample Installation Log File of the Device Connection Manager G BASEstar Open Global Variables G.1 Global Variable List............................. G-1 G.2 Installation-specific Global Variables........... G-8 G.3 BSTR_REALM Global Variable....................... G-9 G.4 Global Variables for Server Activation........... G-9 G.5 Application Management Services Global Variables........................................ G-9 ix H Environment and Parameter Files H.1 General Record Format............................ H-1 H.2 Format of the File for the Node environment Attribute........................................ H-3 H.3 Format of the File for the Program parameters Attribute........................................ H-4 H.3.1 File Format ................................... H-4 I Environment Component Processes J Managing Snapshot Files in a Distributed Environment J.1 Using Configuration Management Commands in a Multi-Node Environment........................... J-1 J.2 Snapshot File Location........................... J-2 J.3 The BSTR_DBACCESS_KEY Global Variable............ J-2 J.4 Making Snapshot Files Accessible................. J-3 J.4.1 Installing Snapshot Directories on a Shared Disk........................................... J-3 J.4.2 Copying Snapshot Files Via DECnet ............. J-3 Index Examples 14-1 Node Log File Example ......................... 14-4 14-2 Realm Log File Example ........................ 14-5 H-1 Program Parameter File (flag not set) ......... H-9 H-2 Program Parameter File (flag set to NOUAF) .... H-9 Figures 8-1 Sample BASEstar Open Environment .............. 8-9 11-1 Active Realm View ............................. 11-4 11-2 Active Node View .............................. 11-7 13-1 Cursor Mode ................................... 13-4 13-2 Actor View with Actor Attributes .............. 13-5 13-3 Actor View with Activity Attributes ........... 13-7 13-4 Activity View ................................. 13-9 x 13-5 Program View .................................. 13-11 13-6 Process View .................................. 13-13 13-7 Node View ..................................... 13-14 Tables 1 Conventions Used in BASEstar Open ............. xiv 1-1 Pre-Installation Check List ................... 1-1 1-2 Hardware Requirements for Installing BASEstar Open Server.................................... 1-3 1-3 Disk Space Requirements for BASEstar Open Server Components.............................. 1-6 1-4 Minimum Quotas for Installing BASEstar Open Server on OpenVMS.............................. 1-7 1-5 Minimum Required System Parameter Values - OpenVMS Alpha.................................. 1-8 3-1 Post-Installation Check List .................. 3-1 5-1 BASEstar Licenses ............................. 5-3 5-2 BASEstar Minimum System Parameter Values ...... 5-4 7-1 Process Resource Limits ....................... 7-2 7-2 VMS Privileges Required to Start BASEstar Software....................................... 7-4 10-1 OpenVMS Relationship Between Environment Management Commands and Users.................. 10-3 10-2 Environment Management Privileges ............. 10-4 12-1 Logical Names - Validity and Usage ............ 12-8 12-2 Data Management-Environmental Variables ....... 12-16 12-3 Device Management-Environmental Variables ..... 12-21 12-4 Data and Device Management-Environmental Variables...................................... 12-25 14-1 Log Services CLI Commands ..................... 14-1 14-2 Log File Component Identifier ................. 14-3 A-1 BASEstar Open Server Directories .............. A-1 A-2 Files Installed by BASEstar Open Server ....... A-2 A-3 Files Installed by DEComni API ................ A-8 A-4 Files Installed by DEComni API ................ A-8 A-5 Image Files Installed by DEComni API .......... A-12 D-1 DCM-Modeled Device Connectivity Installation Files.......................................... D-1 xi D-2 BASEstar Open Server Utility Installation Files.......................................... D-9 D-3 BASEstar CIMfast Directories .................. D-10 D-4 BASEstar CIMfast Installation Files ........... D-11 D-5 BASEstar CIMfast LSE Files .................... D-14 D-6 Logical Names Created by the Device Connection Manager Installation Procedures................ D-14 G-1 BASEstar Open Global Variables ................ G-2 H-1 Valid Values of the File for the Node environment Attribute.......................... H-3 H-2 Valid Values of the File for the Program parameters Attribute........................... H-4 I-1 Processes ..................................... I-3 xii _________________________________________________________________ Preface Intended Audience This manual is addressed to system managers responsible for installing and setting up BASEstar Open software. You must be familiar with the OpenVMS installation procedure (VMSINSTAL). Structure of this Document This manual is organized as follows: o Chapter 1 describes the operating system and hardware requirements for installation and related procedures that you must complete before installing BASEstar Open Server. o Chapter 2 describes the BASEstar Open Server installation procedure. o Chapter 3 describes the Installation Verification Procedure (IVP) and any post-installation procedures that you must complete in order to use BASEstar Open Server. o Chapter 4 describes the BASEstar CIMfast installation procedure. o Chapter 5 describes the pre-requisites for installing the BASEstar Classic Device Connection Manager. o Chapter 6 describes the BASEstar Classic Device Connection Manager installation procedure. o Chapter 7 describes the post-installation tasks for the BASEstar Classic Device Connection Manager. xi o Chapter 8 provides an overview of environment management issues. o Chapter 9 describes the procedures that allow you to set up, start up and shut down the components of your BASEstar Open environment. o Chapter 10 contains reference information for the above procedures (e.g., pre-reqisites, privileges, etc.). o Chapter 11 describes the BASEstar Open Environment Monitor, an interactive tool that enables you to monitor the BASEstar Open environment at run-time. o Chapter 12 explains how to start up, shut down and manage BASEstar Open-supplied servers. o Chapter 13 describes the Application Management Services Monitor, an interactive tool that enables you to monitor Application Management Services objects. o Chapter 14 describes how Node-specific log services collect information from the environment components. o Chapter 15 contains reference information for the log services commands. o Appendix A describes the files and directories created on your system by the installation procedure. o Appendix B provides a comprehensive list of the BASEstar Open Server installation messages. o Appendix C contains sample listings for BASEstar Open Server installation on OpenVMS VAX and Alpha platforms. o Appendix D lists the additional files created during the installation of the BASEstar Open Server software (including files pertaining to device connection management, library management and utility software). o Appendix E explains the format used for the Device Connection Manager installation messages. It also provides a comprehensive list of the error messages associated with the installation procedure, together with the recommended recovery procedure for each error. o Appendix F contains a sample installation log for installation of the Device Connection Manager on OpenVMS VAX and Alpha platforms. xii o Appendix G lists and describes the BASEstar Open Server global variables. o Appendix H describes the format and contents of: - The environment file, as specified by the environment attribute of a Node object - The parameter file, as specified by the parameters attribute of a Program object. o Appendix I lists the platform-dependent processes that implement each BASEstar Open environment component. o Appendix J provides information about managing snapshot files in a multinode environment. BASEstar Open Documentation Set This manual describes a software component or aspects of the BASEstar Open family of products. The complete set of documents relating to the BASEstar Open family is as follows: o BASEstar Open: - BASEstar Open Introduction - BASEstar Open Reference Guide - BASEstar Open Command Language Interface - BASEstar Open Application Programming Interface - BASEstar Open Messages - Platform-specific installation and management guides - BASEstar Open Guide to DCM-Modeled Device Connectivity (for supported platforms) o BASEstar CIMfast (for supported platforms): - BASEstar CIMfast User's Guide - BASEstar CIMfast Programmer's Reference Guide - BASEstar CIMfast Guide to DECmessageQ Support (not available on Windows NT platforms) - BASEstar CIMfast Guide to SQL Support xiii o DEComni API: - DEComni API and MMS User Guide - DEComni API Guide to Using Omni Directory Services (for supported platforms) - DEComni API Guide to Using OmniView (for supported platforms) - DEComni API Omni Definition Facility User Guide (for supported platforms) o Device Access Software documentation - Specific manuals for each supported device Conventions Table 1 lists the conventions used in the BASEstar Open documentation set. Table_1_Conventions_Used_in_BASEstar_Open________________________ % The default user prompt is your system name followed by a right angle bracket (>). In the BASEstar Open docset, a percent sign (%) is used to represent this prompt. / Indicates that you must hold down the Ctrl key while you press another key. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) . A vertical ellipsis indicates the omission of . items from a code example or sample command; . the items are omitted because they are not important to the topic being discussed. (continued on next page) xiv Table_1_(Cont.)_Conventions_Used_in_BASEstar_Open________________ . . . A horizontal ellipsis in format descriptions or in examples indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. [] In format descriptions, brackets indicate optional elements; you can select none, one, several, or all of the choices. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification, or in the syntax of a substring specification in an assignment statement.) ( ) In format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. boldface text Boldface text represents one of the following cases: o user input o the introduction of a new term o the status values true or false italic type Indicates titles of manuals, variables, arguments, data structures, fields, callable functions, operands, and utilities. Italic text also represents information that can vary in system messages (for example, Internal error number), command lines (for example, /PRODUCER=name), and command operands in text. (continued on next page) xv Table_1_(Cont.)_Conventions_Used_in_BASEstar_Open________________ code type Indicates information that is part of the code for a program or application. numbers Unless otherwise noted, all numbers in the text are assumed to be decimal. Nondecimal radixes- binary, octal, or hexadecimal-are explicitly indicated. UPPERCASE TEXT Uppercase text indicates a command, the name of a file, the name of a file protection code, the abbreviation for a system privilege, the name of a field, or the value of an attribute where attributes are chosen from a list. "point_a + Literal string. Using quotation marks is point_b" optional unless there is a space, slash (/), or parenthesis in the string. BASEstar Open Valid characters for the names of BASEstar Open names objects are the alphanumeric characters (A-Z) and (0-9), the underscore (_), the dollar sign ($), and the following multinational __________________characters:_ÅÀÁÂÃÄÇÈÉÊËÌÍÎÏÒÓÔÕÖÙÚÛÜÆÑ@Øß._____ xvi Part I _________________________________________________________________ Installing BASEstar Open Server The section consists of three chapters that describe the following: o Pre-installation tasks - the tasks and checks you must perform before beginning installation of BASEstar Open Server o The installation procedure o Post-installation tasks - the tasks you must perform immediately after installing BASEstar Open Server. 1 _________________________________________________________________ Preparing to Install BASEstar Open Server 1.1 Pre-Installation Check List Table 1-1 summarizes the tasks you must perform before installing BASEstar Open Server. Make sure that you have performed all these tasks before proceeding with the installation. Table_1-1_Pre-Installation_Check_List______________________ Task____________________________For_More_Information_______ Check that you have the See Section 1.2 complete kit Check that you have the pre- See Section 1.4, requisite hardware, software, Section 1.5, and and license Section 1.6 Back up your system disk See Section 1.7 Check that you have the See Section 1.8.1 required privileges Check that you have enough See Section 1.8.2 disk space Check account quotas See Section 1.8.3 Check_system_parameters_________See_Section_1.8.4__________ 1.2 Checking the Contents of the Distribution Kit 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 1-1 Preparing to Install BASEstar Open Server 1.2 Checking the Contents of the Distribution Kit that parts of it are missing, contact your COMPAQ representative. COMPAQ provides a BASEstar Open Server cover letter with the kit, and online release notes in the following files: o SYS$HELP:BSTROSVA032.RELEASE_NOTES (OpenVMS Alpha) o SYS$HELP:BSTROSVV032.RELEASE_NOTES (OpenVMS VAX) COMPAQ strongly recommends that you read both the cover letter and the release notes before proceeding with the installation. 1.3 Required Operating System Components Both the OpenVMS Alpha and the OpenVMS VAX operating systems come with a variety of support options, or classes. Classes include such features as networking and RMS Journaling. For a complete list of the required classes, refer to the BASEstar Open Server Software Product Description (SPD). 1.4 Pre-requisite Hardware Table 1-2 describes the hardware items needed to install BASEstar Open Server. 1-2 Preparing to Install BASEstar Open Server 1.4 Pre-requisite Hardware Table 1-2 Hardware Requirements for Installing BASEstar __________Open_Server______________________________________ Item_________________________________Purpose_______________ RRD40 CD Reader[1] To install from media RRD40 CD Reader, nine-track magnetic tape drive, TK50 or TK70 as appropriate for distribution kit media[2] ANSI-compatible video display To communicate terminal such as the VT300 or VT400 with the Operating series System and respond to prompts. Any VAXstation[2] or terminal that For graphic screen supports the X Window System development. [1]For_OpenVMS_Alpha_only._________________________________ [2]For OpenVMS VAX only. ___________________________________________________________ 1.5 Pre-requisite Software You can install BASEstar Open Server Version 3.2 on: o OpenVMS Version 6.1, 6.2, 7.1 and 7.2 The pre-requisite software also includes the following layered products: o DEC TCP/IP Services for OpenVMS o DEC Rdb for OpenVMS (optional) o DECnet OSI (for certain DASes) o OSAK (for MMS DASes only) For further details of these products, including the currently supported version numbers, refer to the BASEstar Open Server Software Product Description (SPD 47.87.xx). The following command displays the OpenVMS operating system version that you are running: $ WRITE SYS$OUTPUT F$GETSYI("VERSION") 1-3 Preparing to Install BASEstar Open Server 1.6 Pre-requisite Licenses 1.6 Pre-requisite Licenses Before you install and run BASEstar Open Server Version 3.2 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 along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing BASEstar Open Server as an update on a node or cluster already licensed for this software, you have already completed the License PAK registration requirements. Refer to the OpenVMS License Management Utility Manual for further information about the License Management Utility. VMSINSTAL checks which license has been installed and installs the required components of the BASEstar Open Server for OpenVMS (VAX or Alpha) kit. If no license is installed, VMSINSTAL only installs the components for the runtime option of BASEstar Open Server, and asks if you wish to continue with the installation. If you respond affirmatively, the IVP is not executed and BASEstar Open Server will not run. However, if a valid license is installed later, you can still run BASEstar Open Server. If you are installing pre-requisite or optional software along with BASEstar Open Server, review the PAK status and install the PAKs for any pre-requisite or optional software before you install BASEstar Open Server. Refer to the BASEstar Open Server Software Product Description for further details of the licenses available for BASEstar Open Server. 1.7 Backing Up Your System Disk At the beginning of the installation, the procedure asks if you have backed up your system disk. COMPAQ recommends that you do a system disk backup before installing any software. If a system failure occurs at a critical point during the installation, some of the files could be corrupted. For further information about backing up your system disk, refer to the section on the Backup Utility in the OpenVMS System Manager's Manual. 1-4 Preparing to Install BASEstar Open Server 1.7 Backing Up Your System Disk Also ensure that the VMS Help library is not used during the period of the BASEstar Open Server installation. 1.8 Preparing Your System This section discusses the disk space and the privileges and parameter values that are required for installing BASEstar Open Server for OpenVMS (Alpha and VAX). VMSINSTAL asks if you wish to install DEComni; answer no if you do not wish to do so. Account privileges, quotas, and system parameters vary according to whether or not VMSINSTAL performs the DEComni installation. If you are running a multiversion of DEC Rdb, you must choose the version to be used before installing BASEstar Open Server, by running the following command line: $ @SYS$LIBRARY:RDBVMS_SETVER version_number VMSINSTAL checks for the required values and reports any errors before deciding if to fail. 1.8.1 Account Privileges To install BASEstar Open Server, you must be logged in to the system management account SYSTEM, and have ALL privileges set. If you are not logged into the SYSTEM account and VMSINSTAL will be installing or reinstalling DEComni, the BASEstar Open Server installation procedure warns you that DEComni IVP will not be able to be run. Note that the installation procedure, VMSINSTAL, turns off BYPASS privilege at the start of the installation. 1.8.2 Disk Space Requirements To install BASEstar Open Server, you require at least 110,000 blocks (Alpha systems) or 83,000 blocks (VAX systems) of free disk space (peak block count) on your system disk. Table 1-3 lists the requirements of each individual component. 1-5 Preparing to Install BASEstar Open Server 1.8 Preparing Your System Table 1-3 Disk Space Requirements for BASEstar Open Server __________Components_______________________________________ Blocks Required Blocks Required Component_____________(Alpha)_______________(VAX)__________ BASEstar Open Server 31,000 30,000 DEComni API 66,000 45,000 BASEstar CIMfast 13,000 8,000 Total:________________110,000_______________83,000_________ After BASEstar Open Server is installed, the BASEstar Open environment requires 29,000 blocks of free disk space. This value does not take into account disk space required by the Permanent Object Database. To determine the number of free disk blocks, enter the following command at the DCL prompt: # SHOW DEVICE device_name where device_name is the device on which you want to install BASEstar Open Server for OpenVMS. 1.8.3 Account Quotas for Installation The account from which BASEstar Open Server is installed must have certain minimum quotas. Before attempting to install BASEstar Open Server, verify that the account has the correct quotas. Table 1-4 summarizes the minimum quotas required (both with and without the DEComni installation stage) for the installation of BASEstar Open Server on OpenVMS Alpha and OpenVMS VAX. 1-6 Preparing to Install BASEstar Open Server 1.8 Preparing Your System Table 1-4 Minimum Quotas for Installing BASEstar Open __________Server_on_OpenVMS________________________________ Minimum Values User Account Without DEComni Parameter________API______________With_DEComni_API_________ ASTLM 20 24 BIOLM 40 40 BYTLM 80000 80000 DIOLM 20 20 ENQLM 20 2000 FILLM 20 50 JTQUOTA 1024 1024 PGFLQUOTA 10,000 30,000 PRCLM 4 4 TQELM 6 6 WSDEFAULT 512 512 WSQUOTA 1024 1024 WSEXTENT_________2048_____________3072_____________________ Use the Authorize utility to display the process quotas, as follows: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM If no changes are necessary, enter the EXIT command to leave the Authorize utility. To modify system account quotas (for example, BYTLM), use the following command line: UAF> MODIFY SYSTEM/BYTLM=32768 The utility responds with a message confirming the change. You can then enter the EXIT command to exit from the utility. You must log out and then log in again to reset the system account quotas. The Authorize utility is described in the OpenVMS System Manager's Manual. 1-7 Preparing to Install BASEstar Open Server 1.8 Preparing Your System 1.8.4 OpenVMS SYSGEN Parameters and Minimum Values For the BASEstar Open Server installation to complete successfully some System Generation Utility (SYSGEN) parameters must be set to certain values before the installation. Table 1-5 and lists the minimum required values for the system parameters. To install and run BASEstar Open Server, you must have sufficient free global pages and global sections. You must first determine how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the values of the GBLPAGES and GBLSECTIONS system parameters. Table 1-5 Minimum Required System Parameter Values - __________OpenVMS_Alpha____________________________________ Minimum Values[1] System_Parameter______Without_DEComni__With_DEComni________ Available GBLPAGES 7000 (Alpha) 7995 (Alpha) 3100 (VAX) 4095 (VAX) Available 50 65 GBLSECTIONS [1]The_values_listed_for_these_system_parameters_represent_ the minimum number of free global pages and global sections required to run BASEstar Open Server in addition to the requirements of your current system and other software. These values are not the total number you need to run your system and other software. ___________________________________________________________ Checking System Parameter Values To check the values of your system parameters, use either of the following methods: o For the number of remaining free pages and free sections Use the DCL lexical F$GETSYI with a system parameter item (for example, FREE_GBLPAGES and FREE_GBLSECTS) as follows: 1-8 Preparing to Install BASEstar Open Server 1.8 Preparing Your System $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 5680 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 128 If the values for the free global pages or global sections displayed by the system are greater than the values in Table 1-5, you do not need to increase them. If the values are less, you must increase the system parameter setting. o For the static number of free pages and free sections Invoke the System Generation Utility (SYSGEN): # RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 1-5. The following example displays the value for the GBLPAGES system parameter: SYSGEN> SHOW GBLPAGES After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 1.9 Error Recovery If errors occur during the installation, VMSINSTAL displays failure messages. If the installation itself fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of BSTROSVA032 V3.2 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A pre-requisite software version is incorrect 1-9 Preparing to Install BASEstar Open Server 1.9 Error Recovery o Quotas necessary for successful installation are insufficient[1] o System parameter values for successful installation are insufficient o The OpenVMS Help library is currently in use. For descriptions of the error messages generated by these conditions, refer to the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you receive notification that one of these conditions exist, take the appropriate action as described in the message. If an error occurs while using BASEstar Open Server and you believe the error is caused by a problem with the product, take the appropriate action as described in Section 3.7. ____________________ [1] If GBLPAGES and GBLSECTIONS are insufficient, the installation continues but displays warning messages that BASEstar Open Server may fail during the IVP or at run-time. 1-10 2 _________________________________________________________________ Installing BASEstar Open Server 2.1 The Installation Procedure Before you begin installing BASEstar Open Server, make sure that your system meets the requirements outlined in Chapter 1 and that you have completed all the tasks listed in Table 1-1. The BASEstar Open Server installation procedure consists of a series of questions and informational messages. To abort the installation procedure at any time, press /. When you press /, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. The approximate time required for the full installation of BASEstar Open Server is as follows: o 20 to 40 minutes, for OpenVMS Alpha o 35 to 50 minutes, for OpenVMS VAX However, the exact time depends largely on the type of media you are using and your system configuration. 2.1.1 VMSINSTAL Checks When you invoke VMSINSTAL, it checks whether: o You have set your default device and directory to SYS$UPDATE o You are logged in to the system management account SYSTEM o DECnet is running o Any users are logged in to the system 2-1 Installing BASEstar Open Server 2.1 The Installation Procedure If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press . Then correct the problem and restart the installation. 2.1.2 Installation Steps The following steps describe how to install BASEstar Open Server on an OpenVMS Alpha system: 1. Start the installation To start the installation, invoke the SYS$UPDATE:VMSINSTAL.COM procedure from a privileged account (for example, SYSTEM). Use the kit name BSTROSVA032 as the first parameter to the command VMSINSTAL. Use the device or directory on which the installation kit is located as the second parameter. For example, if the media containing the BASEstar Open Server software is on device mua0, then you must issue the following command to install BASEstar Open Server (on an OpenVMS Alpha system): # @SYS$UPDATE:VMSINSTAL BSTROSVA032 SYS$MANAGER OpenVMS AXP Software Product Installation Procedure V7.1 It is dd-mmm-yyyy at hh:mm. 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. 2. Confirm system backup * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press . Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 2-2 Installing BASEstar Open Server 2.1 The Installation Procedure 3. Specify the drive on which you will mount the distribution volumes * Where will the distribution volumes be mounted: Enter the appropriate device/directory name. 4. Enter the name(s) of the product(s) to be installed Enter the products to be processed from the first distribution volume set. * Products: bstrosva032 * Enter installation options you wish to use (none): Specify any installation options to be used. The following products will be processed: BSTROSVA V3.2 5. Begin the installation At this point, VMSINSTAL checks which license has been installed and continues with the installation as follows: Beginning installation of BSTROSVA V3.2 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. *************************************************************************** Copyright Digital Equipment Corporation. 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. - BASEstar Open V3.2-0 Installation Procedure - This procedure decides from the license which component is to be installed. If you do not have any license, the procedure allows you to install the run-time option, but does not execute the IVP. 2-3 Installing BASEstar Open Server 2.1 The Installation Procedure For more information on the license requirement for the installation of BASEstar Open Server, refer to Section 1.6. 6. Check whether DEComni is already installed VMSINSTAL checks whether DEComni API is already installed. It then informs you that DEComni API will be installed automatically if it is not already installed or if an incorrect version is installed. If the correct version of DEComni API has already been installed, VMSINSTAL asks if you wish to reinstall it, as follows: This procedure will also give you the option of installing the Device Connection component (DEComni). If you wish to use the device access capability of this version of BASEstar Open, you must install the Device Connection component included in this kit. ************************************************************************ BASEstar Open Development option will be installed * Do you want to install the Device Connection component (DEComni) [Y]?) 7. Specify the target disk VMSINSTAL asks you where you would like to have BASEstar Open Server installed. If your system is a VAXcluster and you would like to have BASEstar Open Server available on all or a set of nodes in the cluster you must install BASEstar Open Server on a disk that is visible to those nodes in the cluster. BASEstar Open can be installed on any disk of your system. There is no default disk: you must enter a disk name. The following disks are available on the system. $1$DKA0: (VONALB) Mounted 0 PCTS 126180 2 1 $1$DKB0: (VONALB) Mounted 0 BASESTAR 355743 7 1 $1$DKB400: (VONALB) Mounted 0 ALPHASYS 147556 417 1 * Target disk: $1$DKA0: * BSTROSVA V3.2 root directory [[BSTROSVA032]]: You are going to install BSTROSVA V3.2 on Target disk: $1$DKA0: Root directory: [BSTROSVA032] 2-4 Installing BASEstar Open Server 2.1 The Installation Procedure * Is this correct [Y]? ********************************************************** For more information on managing BASEstar Open Server, refer to Part III, Environment Management. 8. Specify the DEComni API/DAS product(s) that you wish to install Select which products you want to install: 1 DEComni API 2 DASTkRUN 3 DASTk 232 4 ALL of the above ********************************************************** * Enter number(s): [1]:4 ********************************************************** DEComni API V3.1 is installed on this system. It is recommended that the database files be renamed or deleted if you do not wish to use the existing database. If you choose not to rename or delete the database,the existing database will continue to be used. ********************************************************** 1. Rename existing database 2. Continue to use existing database * Enter a number [2]: A directory for Omni Directory Services will be created. You need to provide the disk name in which the directory will be located. If you do not specify a location, the directory will be placed in SYS$SYSDEVICE:[OMNI...]. Include the colon after the disk name. * Enter the disk now [ddcu:] : * Do you want to purge files replaced by this installation [YES]? 9. Run the BASEstar Open Server and DEComni API IVPs The installation procedure now asks if you wish to run the BASEstar Open Server Installation Verification Procedure (IVP) (which calls the DEComni IVP) after the installation is complete, as follows: 2-5 Installing BASEstar Open Server 2.1 The Installation Procedure * Do you want to run the IVP after the installation [YES]? For more information on the IVP, refer to Section 3.2. There are no further questions concerning the installation of BASEstar Open Server. 10.Read informational messages At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. For further information about how to run the BASEstar Open Server IVP separately, refer to Section 3.2.1. For full example logs of BASEstar Open Server installations on both OpenVMS Alpha and VAX systems, refer to Appendix C. 2-6 3 _________________________________________________________________ After Installing BASEstar Open Server 3.1 Post-Installation Checklist Table 3-1 summarizes the tasks you should perform after installing BASEstar Open Server. Make sure that you perform these tasks before using BASEstar Open Server. Table_3-1_Post-Installation_Check_List_____________________ Task____________________________Notes______________________ Run the Installation See Section 3.2 Verification Procedure (IVP) Set up and start the BASEstar See Section 3.3 Open_environment___________________________________________ 3.2 Running the Installation Verification Procedure Separately After BASEstar Open Server is installed, COMPAQ recommends that you run the Installation Verification Procedure (IVP) to verify that the software is available on your system. You might also want to run the IVP after a system failure to make sure that users can access BASEstar Open Server. The approximate duration of the IVP is as follows: o 15 minutes (OpenVMS Alpha) o 20 minutes (OpenVMS VAX) 3-1 After Installing BASEstar Open Server 3.2 Running the Installation Verification Procedure Separately 3.2.1 Running the BASEstar Open Server Installation Verification Procedure To run the BASEstar Open Server IVP, you must: o Choose the version of DEC Rdb to be used before installing BASEstar Open Server (only necessary if you are running a multiversion of DEC Rdb): $ SYS$LIBRARY:RDBVMS_SETVER version_number o Execute the following command from an account that has all privileges set: # @BSTR$KIT:[ETC]BSTR_IVP You are not asked any questions during the IVP. If the IVP has terminated successfully, a message similar to the following is displayed: BASEstar Open Version 3.2 IVP completed successfully Refer to Appendix C for a complete log of the IVP phase. 3.2.2 Running the DEComni API Installation Verification Procedure To run the DEComni API IVP, follow these steps: 1. Ensure that DEComni API is running 2. Enable the following privileges: NETMBX PRMMBX SYSLCK WORLD GROUP 3. Execute the following command: # @SYS$TEST:OMNI_IVP 3.3 Setting Up and Starting the BASEstar Open Environment After installing BASEstar Open Server, you must perform procedures which set up and start up Nodes and Realms. Refer to Chapter 9 for a description of these procedures. 3-2 After Installing BASEstar Open Server 3.4 User Account Requirements 3.4 User Account Requirements To work with BASEstar Open Server, user accounts on your system must have certain privileges and quotas. Refer to Section 1.8.3 for a description of how to verify and change account quotas. 3.5 Starting DEComni API To start DEComni API, follow these steps: 1. Enable the following privileges: DETACH PRMMBX SYSNAM CMKRNL SYSGBL PRMGBL WORLD GROUP SYSLCK 2. Enter the following command line: # @SYS$STARTUP:OMNI_STARTUP You can add this startup command to your system startup file so that DEComni API starts each time you load the system. ________________________ Note ________________________ You must not start DEComni API simultaneously started on nodes in a VAXcluster configuration because the startup procedures will fail while checking the ODS schema files. You must execute the DEComni API startup one node at a time. ______________________________________________________ 3-3 After Installing BASEstar Open Server 3.6 Stopping DEComni API 3.6 Stopping DEComni API To stop DEComni API, follow these steps: 1. Enable the following privileges: DETACH PRMMBX SYSNAM CMKRNL SYSGBL PRMGBL WORLD GROUP 2. Enter the following command line: # @SYS$MANAGER:OMNI_STOP If you want to stop DEComni API each time you shut down the system, include the previous command line in the site-specific shutdown file SYS$MANAGER:SYSHUTDOWN.COM. 3.7 Getting Help and Reporting Problems If an error occurs while you are using BASEstar Open Server, and you believe the error is the result of a problem associated with the product, take one of the following actions: o If you have a basic or COMPAQ support Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you purchased BASEstar Open Server within the last 90 days and you think the problem is caused by a software error, you can submit an SPR. If you submit an SPR, please take the following steps: 1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. Include the description and version number of BASEstar Open Server that you were using. Demonstrate the problem with specific examples. 3-4 After Installing BASEstar Open Server 3.7 Getting Help and Reporting Problems 2. Reduce the problem to as small a size as possible. 3. Remember to include listings of any command files, include files, relevant data files, and so forth. 4. Provide a listing of the program. 5. If the program is longer than 50 lines, submit a copy of it on machine-readable media (floppy diskette or magnetic tape). If necessary, also submit a copy of the program library used to build the application. 6. Report only one problem per SPR. This will facilitate a faster response. 7. Mail the SPR package to COMPAQ. Experience shows that many SPRs do not contain enough information to duplicate or identify the problem. Concise, complete information helps COMPAQ give accurate and timely service to software problems. If you find an error in the BASEstar Open Server documentation, send an electronic mail message to manufacturing@compaq.com. 3-5 4 _________________________________________________________________ Installing BASEstar CIMfast This section describes how to install BASEstar CIMfast, an application development environment for creating real-time event-driven applications, on an OpenVMS system. Before attempting to install BASEstar CIMfast, make sure that you have: o Installed BASEstar Open Server, as described in Section 2.1[1] o Set up your BASEstar Open Node, using the bstr_node_ setup function o Run RDBVMS_SETVER (only necessary if you are running a multiversion of DEC Rdb). Although the BASEstar CIMfast software is a separate kit, it resides on the same CDROM as the BASEstar Open Server software, in the directory assigned to the BASEstar Open Server kits. The BASEstar CIMfast kit is called BCFAXP022. It consists of a base module, together with a DEC Rdb-based SQL bridge module (minimum DEC Rdb version 6.0). The following steps describe how to install BASEstar CIMfast on an OpenVMS Alpha system: 1. Start the installation To start the installation, invoke the SYS$UPDATE:VMSINSTAL.COM procedure from a privileged account (for example, SYSTEM): ____________________ [1] It is also possible to use BASEstar CIMfast with BASEstar Classic. 4-1 Installing BASEstar CIMfast # @SYS$UPDATE:VMSINSTAL OpenVMS AXP Software Product Installation Procedure V7.1 It is dd-mmm-yyyy at hh:mm. 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. 2. Confirm system backup %VMSINSTAL-W-ACTIVE, The following processes are still active: BATCH_288 BATCH_289 * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? 3. Specify the drive on which you will mount the distribution volumes * Where will the distribution volumes be mounted: sys$manager 4. Enter the name of the BASEstar CIMfast kit that you wish to install Enter the products to be processed from the first distribution volume set. * Products: BCFAXP022 * Enter installation options you wish to use (none): Specify any installation options to be used. The following products will be processed: BCFAXP V2.2 5. Begin the installation At this point, VMSINSTAL checks which license has been installed and continues with the installation as follows: Beginning installation of BCFAXP V2.2 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. BASEstar CIMfast for OpenVMS installation procedure. Copyright (c) 1999 Digital Equipment Corporation. All Rights Reserved. Enter ? at any time for help. 4-2 Installing BASEstar CIMfast For more information about the license requirement for the installation of BASEstar CIMfast, refer to Section 1.6. 6. Specify the target disk/directory VMSINSTAL asks you where you wish to install BASEstar CIMfast (by default, it performs the installation in [SYS$SYSDEVICE:[BCF]) It also requests you to provide other information about how you want to perform the installation. * In what directory do you wish to install CIMfast [SYS$SYSDEVICE:[BCF]]: * Do you want to install CIMfast SQL Support for DEC RDB [YES]? * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? All questions regarding the installation of CIMfast have been asked. Depending upon system load and configuration the installation will take between 5 and 15 minutes. This installation provides a system startup file SYS$STARTUP:BCF$STARTUP.COM. You must edit your system startup procedure(s) to invoke this file on each node where CIMfast will be run. The CIMfast per-user setup command procedure is in BCF$HOME:BCF$SETUP.COM. It should be executed at login time by each CIMfast user, by including a line such as the following in each user's LOGIN.COM procedure: $ @BCF$HOME:BCF$SETUP Alternatively, the above line may added to the system-wide login command procedure (usually SYS$MANAGER:SYLOGIN.COM). 4-3 Installing BASEstar CIMfast %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.EXE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.LIB]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.BLD]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.BLD.BCF]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.BLD.BSTR]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.BLD.RDB]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.DEMO.POINTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.DEMO.CBCF_POINTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.DEMO.CALLABLE_BCF]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.DEMO.EXPRESSIONS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.DEMO.MACROS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DKB400:[BCF.DEMO.SQL]. If this product is being installed in a OpenVMS cluster, several actions must be taken to enable other nodes in the cluster to be able to use this product. These actions include: 1 Define CIMfast related logical names 2) Update DCL tables 3) Load a valid license This can be done with the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO @SYS$STARTUP:BCF$STARTUP.COM SYSMAN> DO INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE SYSMAN> DO LICENSE LOAD BASESTAR ! or any valid license SYSMAN> EXIT %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ********************************************************* Remember to define the logical name BSTR_REALM to specify the BASEstar realm you want to use. For instance, DEFINE BSTR_REALM MY_REALM ********************************************************* Beginning CIMfast BASEstar Open Support IVP ------------------------------------------- Logical name BSTR_REALM temporarily defined as IVP 4-4 Installing BASEstar CIMfast BASEstar Open Server V3.2 Copyright © Digital Equipment Corporation 1993,1999 All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. BASEstar Open Server V3.2 Copyright © Digital Equipment Corporation 1993,1999 All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. BASEstar Open Server V3.2 Copyright © Digital Equipment Corporation 1993,1999 All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. The node VONALB has already been set up Executing BSTR_NODE_START ... 4-5 Installing BASEstar CIMfast BASEstar Open Server V3.2 Copyright © Digital Equipment Corporation 1993,1999 All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. Checking the environment Calling BSTR$ROOT:[ETC.HOST_STARTUP]CHECK_COM.COM;1 ... Cleanup Calling BSTR$ROOT:[ETC.HOST_STARTUP]CLEANUP_COM.COM;1 ... Cleaning the communication directory. Cleaning the communication name table. 4 phases will be executed Startup phase 0 Calling BSTR$ROOT:[ETC.HOST_STARTUP]START00_LOG.COM;2 ... Starting up the LOG Server. %RUN-S-PROC_ID, identification of created process is 000004C2 Synchronizing after phase 0 Calling BSTR$ROOT:[ETC.HOST_STARTUP]SYNC00_LOG.COM;2 ... Waiting for the LOG Server to start... Startup phase 1 Calling BSTR$ROOT:[ETC.HOST_STARTUP]START01_COM.COM;1 ... Creating the node table. Starting the Watchdog. %RUN-S-PROC_ID, identification of created process is 000004C3 Synchronizing after phase 1 Calling BSTR$ROOT:[ETC.HOST_STARTUP]SYNC01_COM.COM;1 ... Waiting for the Watchdog to start... Startup phase 2 Calling BSTR$ROOT:[ETC.HOST_STARTUP]START02_COM.COM;1 ... Starting the LNS. Starting LNS for name space BSTR %RUN-S-PROC_ID, identification of created process is 000004C4 Synchronizing after phase 2 Calling BSTR$ROOT:[ETC.HOST_STARTUP]SYNC02_COM.COM;1 ... Waiting for the LNS to start... 4-6 Installing BASEstar CIMfast Startup phase 3 Calling BSTR$ROOT:[ETC.HOST_STARTUP]START03_COM.COM;1 ... Starting the LNS monitor for VMS Starting LNS for name space BSTR %RUN-S-PROC_ID, identification of created process is 000004C6 Synchronizing after phase 3 Calling BSTR$ROOT:[ETC.HOST_STARTUP]SYNC03_COM.COM;1 ... Waiting for the LNS monitor for VMS. All phases completed Executing BSTR_REALM_SETUP_NODE ... Executing BSTR_REALM_START_NODE ... Configuring AMS objects ... Executing IVP CEL file ... Executing BSTR_REALM_SHUT_NODE ... Executing BSTR_REALM_UNSET_NODE ... Executing BSTR_NODE_SHUT ... Environment correctly restored IVP TERMINATED SUCCESSFULLY Installation of BCFAXP V2.2 completed at 10:32 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]BCFAXP022.VMI_DATA Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 10:33 $) 4-7 Part II _________________________________________________________________ Installing the Device Connection Manager This part consists of three chapters that explain how to install the Device Connection Manager: o Before Installing the BASEstar Classic Device Manager o Installing the BASEstar Classic Device Manager o After Installing the BASEstar Classic Device Manager 5 _________________________________________________________________ Before Installing the BASEstar Classic Device Manager 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 cluster installation. 5.1 Overview The BASEstar installation procedures allow you to customize each BASEstar system by installing only those system components you want for the target system. You can install BASEstar software on a single node or on a cluster 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, BASEstar data management capabilities and BASEstar external data support. 5.2 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. 5-1 Before Installing the BASEstar Classic Device Manager 5.3 Installation of the Device Connection Management Software 5.3 Installation of the Device Connection Management Software 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. The BASEstar device connection management installation procedure will conditionally install its menu interface component if 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, DECnet and TCP/IP networks, and the DECdevice device communication module. Refer to the BASEstar Open Guide to DCM-Modeled Device Connectivity for information on how to configure and use these DAS modules. 5.4 Distribution Kit The DCM software is available with the BASEstar Open kit, as the following software savesets: o BCCM033 - BASEstar application integration software o DCMM033 - BASEstar device connection management 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. 5.5 Pre-requisite Hardware Refer to Section 1.4 for more information on the hardware required for the installation of DCM with BASEstar Open. 5.6 Pre-requisite and Optional Software Refer to Section 1.5 for more information on the software required for the installation of DCM with BASEstar Open. 5-2 Before Installing the BASEstar Classic Device Manager 5.7 Pre-installation Steps 5.7 Pre-installation Steps Perform these tasks before installing BASEstar software: 1. Ensure OpenVMS, Version 5.3 or higher is installed on the system. OpenVMS VAX Version, 5.3 or higher must be 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. 3. Install the BASEstar Open product license. Before you install and run the DCM software on a newly licensed node or cluster, you must first ensure that valid license for BASEstar Open has been installed. Table 5-1 shows the statuses of the licenses listed during the main BASEstar installation. Table_5-1_BASEstar_Licenses________________________________ License__________Availability______________________________ BASESTAR Available BASESTAR-RT Available BASESTAR-CU Available BASESTAR-LTD No longer available 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 DCM installation, it is necessary to preload the licenses you want to use to authorize the use of DCM on the target node. A new license called BASESTAR-CU has been added for BASEstar Version 3.2. This license allows you to license a BASEstar system 5-3 Before Installing the BASEstar Classic Device Manager 5.7 Pre-installation Steps 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. 4. Verify minimum run-time system parameters. Table 5-2 describes the system parameter values recommended for the minimum run-time BASEstar configuration. Table_5-2_BASEstar_Minimum_System_Parameter_Values_________ 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________________________________________________ Since 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. For example, if you are using BASEstar library management and need to use large libraries, use the following steps to adjust the system parameter GBLPAGES: 5. Stop interactive processes and disable logins. 5-4 Before Installing the BASEstar Classic Device Manager 5.7 Pre-installation Steps 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: $ SET LOGINS/INTERACTIVE=0 Re-enable logins after the installation is complete. Refer to the OpenVMS System Manager's Manual for more information on logins. 6. Stop batch queues. To stop the batch queues, enter: $ STOP/QUEUE/NEXT batch_queue_name 7. 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 8. Check VMSINSTAL requirements. VMSINSTAL requires that the system account used to install BASEstar software have a minimum of the following quotas: o ASTLM=24 o BIOLM=18 o BYTLM=18,000 o DIOLM=18 o ENQLM=30 o FILLM=20 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. 9. Back up the system disk. 5-5 Before Installing the BASEstar Classic Device Manager 5.7 Pre-installation Steps 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. 10.Review release notes. To read or print out the release notes included in the BASEstar distribution kit, invoke VMSINSTAL in the following manner: @SYS$UPDATE:VMSINSTAL BCCM033 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]: Select an option when the installation procedure prompts for release note options. 5-6 6 _________________________________________________________________ Installing the BASEstar Classic Device Manager 6.1 The Installation Procedure Before you begin installing BASEstar Open, make sure that your system meets the requirements outlined in Chapter 1 and Chapter 5. This chapter describes the step-by-step installation of the Device Connection Manager software. BASEstar software components are installed using a combination of four procedures: o Main BASEstar Open (single node or VAXcluster) - BCCM o Device connection management (single node or VAXcluster) - DCMM Read the instructions for installing BASEstar software. Follow the instructions for the installation of BASEstar device connection management, Refer to Appendix F for a sample installation procedures. All installation procedures will perform both new and upgrade installations. 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 ____________Local_name_file_estimated_size_________________ During the installation procedure, you are prompted to respond to questions. Type Y for yes or N for no and press Return or just press Return to select the default response. 6-1 Installing the BASEstar Classic Device Manager 6.1 The Installation Procedure You can type a question mark and press Return after any prompt to receive on-line 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. ______________________________________________________ 6.2 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 BCCM033 ddcu: where BCCM033 is the BASEstar product name and version and ddcu: is the name of the disk, tape drive or CD containing the software kit. The system displays the following: VAX/VMS Software Product Installation Procedure V5.5-1 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. 6-2 Installing the BASEstar Classic Device Manager 6.2 Installing BASEstar Software %VMSINSTAL-W-ACTIVE, The following processes are still active: DECW$WM_1 DECW$TE_1 _TWA2: _TWA3: _TWA4: _TWA9: * Do you want to continue anyway [NO]? 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 OpenVMS System Management Utilities Reference Manual. If satisfied with your backup, press Return to continue. 5. Mount the media. If you are installing from a tape, you are prompted as follows: Please mount the first volume of the save set on Nodename:: * Are you ready? Y The installation continues with the following: The following products will be processed: BCCM V3.2 Beginning installation of BCCM V3.2 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. 6. Respond to license registration queries. BASEstar Reduced Kernel V3.2 Installation Procedure ---------------------------------------------------- BASEstar requires one of these licenses to be registered and loaded on all nodes on which BASEstar will run: 6-3 Installing the BASEstar Classic Device Manager 6.2 Installing BASEstar Software Product Producer Version --------------- -------- ------- [1] BSTROPEN-DEVELOP DEC 3.1 [2] BSTROPEN-RUNTIME DEC 3.1 [3] BSTROPEN-DEVELOP-USER DEC 3.1 [4] BSTROPEN-RUNTIME-USER DEC 3.1 [5] BASESTAR-DCM DEC 3.2 * Which of the above licenses will be used? [1]: Product: BASESTAR-DEVELOP Producer: DEC Version: 3.1 Release Date: * Does this product have an authorization key registered and loaded? y The procedure prompts to ensure 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: The DECnet node ID found for this node is: node-id 8. 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]]: 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 different directory 6-4 Installing the BASEstar Classic Device Manager 6.2 Installing BASEstar Software name for each node within the VAXcluster system. Verify the directory name specified: The directory entered is: SYS$SPECIFIC:[BCC$SPECIFIC] * Is this correct [YES]? 9. 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$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]]: The directory entered is: SYS$COMMON:[BCC$COMMON] * Is this correct [YES]? 10.Read informational messages. __________________________________ 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. __________________________________ 1 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 the BSTAR commands must be granted the BCC$USER rights identifier, as well as having certain Authorized privileges set. 6-5 Installing the BASEstar Classic Device Manager 6.2 Installing BASEstar Software >> 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. -------------------------------------------------------------- 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 ... __________________________________ 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:[SYSn.BCC$SPECIFIC]. %BCC-I-STARTCORE, BASEstar CORE installation 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. %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 Reduced Kernel V3.2 Installation Verification Procedure (IVP) $ DEFINE/NOLOG/PROCESS BCC$SYSDATA SYS$SPECIFIC:[BCC$SPECIFIC] $ DEFINE/NOLOG/PROCESS BCC$SYSTEM VMI$ROOT:[BCC$COMMON] $ set noverify %BCCIVP-I-CORESTART, CORE verification starting on node NODENAME. 6-6 Installing the BASEstar Classic Device Manager 6.2 Installing BASEstar Software %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. BASEstar Reduced Kernel V3.2 IVP completed successfully. 11.End the installation procedure. Installation of BCCM V3.2 completed at hh:mm VMSINSTAL procedure done at hh:mm 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 7 for post- installation tasks. 6.3 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. # @SYS$UPDATE:VMSINSTAL DCMM033 ddcu: where DCMM033 is the device connection management product name and version and ddcu: is the disk or tape drive containing the software kit. The system displays the following: VAX/VMS Software Product Installation Procedure V5.4-3 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. 6-7 Installing the BASEstar Classic Device Manager 6.3 Installing BASEstar Device Connection Management Software 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: DECW$WM_1 DECW$TE_1 _TWA3: _TWA4: _TWA5: _TWA6: * Do you want to continue anyway [NO]? 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 OpenVMS System Management Utilities Reference Manual. If satisfied with your backup, press Return to continue. The installation continues with the following: The following products will be processed: DCMM V3.2 Beginning installation of DCMT V3.2 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... BASEstar Device Connection Management (DCMM) V3.2 Installation Procedure ----------------------------------------------------------------------- 5. Existing BASEstar Installation Message 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 T3.n 6. Respond to node information The procedure determines if the executing node is a member of a multinode VAXcluster. If the executing node is a standalone node or clustered with only one active member, the following message is displayed: 6-8 Installing the BASEstar Classic Device Manager 6.3 Installing BASEstar Device Connection Management Software This node is not a member of a multi-node VAXcluster. 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 VAXcluster. 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 DCMM on just this node [YES]? If you answer N, the following text is displayed: ----------------------------------------- A cluster installation has been selected. ----------------------------------------- The current node, NODENAME, will be processed first. Checking node NODENAME:: ... BASEstar is installed on this node. The file SYS$SPECIFIC:[SYS$STARTUP]BCC$STARTUP.COM was found. The node passed all checks. 7. 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: 6-9 Installing the BASEstar Classic Device Manager 6.3 Installing BASEstar Device Connection Management 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 . (Enter Control-Y to abort the installation, if necessary.) Current node name list is: NODENAME * Enter another node name (or to end the list): NODENAME2 Checking node NODENAME2:: ... BASEstar is installed on this node. The file SYS$SPECIFIC:[SYS$STARTUP]BCC$STARTUP.COM was found. ----------------------------------------------- Wait -- using SYSMAN utility to check certain logical names on cluster member ... ... Done. ----------------------------------------------- The node passed all checks. Current node name list is: NODENAME1, NODENAME2 Enter another node name (or to end the list): 2 valid node names were entered: NODENAME1, NODENAM2 * Is this list correct? y The installation continues: __________________________________ Processing node 1, NODENAM1:: __________________________________ The BASEstar Menu System is present. The DCM Menu System will be installed on this node. 8. Choose size of file. You must choose a initial size for the PHYSICAL POINT data file: ILAN$PHYPOINT_FILE ___________________ Initial Allocation Extend Allocation File Size 6-10 Installing the BASEstar Classic Device Manager 6.3 Installing BASEstar Device Connection Management Software [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]: Select a file size for the physical point data file. Enter the correct choice from the menu and press Return. 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. 9. Read informational messages. 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 this VAX system, the system startup command procedure SYS$MANAGER:SYSTARTUP_V5.COM 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: Press RETURN to continue $ @ 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. ---------------------------------------------------------- 6-11 Installing the BASEstar Classic Device Manager 6.3 Installing BASEstar Device Connection Management Software __________________________________ Installing DCM on node NODENAME1:: ... __________________________________ Creating DCM data files for this node ... Providing images to BCC$SYSTEM ... Providing DCM example PL/I programs to sub-directory of BCC$SYSTEM ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DUA0:[SYS0.S YSCOMMON.BCC$COMMON.DCM_EXAMPLE]. Providing RS232 DAS source files to sub-directory of BCC$SYSTEM ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory $1$DUA0:[SYS0.S YSCOMMON.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 $1$DUA0:[SYS0.S YSCOMMON.BCC$COMMON.NCT_EXAMPLE]. ... Done. Checking the BASEstar Parameter file for "ILAN$*" (DCM) parameters ... ... Done. 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: %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... IVP phase beginning on node NODENAME1 ... %SYSMAN-I-ENV, current command environment: Individual nodes: NODENAME1 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 NODENAME1 6-12 Installing the BASEstar Classic Device Manager 6.3 Installing BASEstar Device Connection Management Software $ @SYS$STARTUP:ILAN$STARTUP.COM $ @SYS$TEST:ILAN$IVP.COM ---------------------------------------------------------------------- BASEstar DCM V3.2 Installation Verification Procedure (IVP) starting. ---------------------------------------------------------------------- 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-I-PASS, 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 DCMM V3.2 IVP completed successfully. ---------------------------------------------------------------------- If you are performing a cluster installation, the IVP messages for each node in the cluster are displayed. 10.End the installation procedure. Installation of DCMT V3.2 completed at hh:mm VMSINSTAL procedure done at hh:mm 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 7 for post- installation tasks. 6-13 7 _________________________________________________________________ After Installing the BASEstar Classic Device Manager This chapter describes the Device Connection Manager post- installation tasks. 7.1 The Device Connection Manager Post-installation Procedures When you have completed the Device Connection Manager installation procedures, log in to the system manager's account and perform the following steps: 1. Delete BASEstar Ada files if not needed (optional). Certain Ada declarations files are rather large; if no Ada programming will be done at your site, you may want to delete the file SYS$COMMON:[SYSLIB]BCC_.ADA (~1400 blocks) and the ILAN*.ADA files in that same directory. 2. Back up the system disk. Back up the system disk after installing BASEstar software. The procedure for backing up the system disk