HP OpenVMS Management Station Installation Guide July 2006 This guide contains instructions for installing OpenVMS Management Station on the OpenVMS operating system and on a PC. Revision/Update Information: This guide supersedes the OpenVMS Management Station Installation Guide, OpenVMS Management Station Version 3.2-D. Software Versions: OpenVMS Management Station Version 3.3 OpenVMS Vax Version 6.2 or higher OpenVMS Alpha Version 6.2 or higher OpenVMS I64 Version 8.2 or higher Hewlett-Packard Company Palo Alto, California ------------------------------------------------------------------------------- July 2006 (C) Copyright 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. All Java and Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. Oracle is a US registered trademark of Oracle Corporation, Redwood City, California. OSF and Motif are trademarks of The Open Group in the US and other countries. UNIX is a registered trademark of The Open Group. Microsoft and Windows are US registered trademarks of Microsoft Corporation. The following are trademarks of Hewlett-Packard Development Company, L.P.: Alpha, Bookreader, DECdirect, DECwindows, DIGITAL, OpenVMS, OpenVMS Cluster, TeamLinks, VAX, VAXcluster, VMS, VMScluster, and the HP logo. The following are third-party trademarks: Adobe, Adobe Illustrator, Display POSTSCRIPT, and POSTSCRIPT are registered trademarks of Adobe Systems Incorporated. X/Open is a registered trademark, and the X device is a trademark of X/Open Company Ltd. in the UK and other countries. TCPware is a registered trademark of Process Software Corporation. All other trademarks and registered trademarks are the property of their respective holders. Printed in the US ZK6391 The HP OpenVMS documentation set is available on CD-ROM. ------------------------------------------------------------------------------- Contents Preface Chapter 1 1 Before Installing the OpenVMS Management Station Server 1.1 Saving Your Existing Database Before You Install 1.2 Do You Need to Install the Server? 1.3 Prerequisite Components 1.3.1 Volume Shadowing Remedial Kit is Required 1.4 Time Required for Installation 1.5 Required Tasks 1.5.1 License Registration 1.5.2 Logging in to a Privileged Account 1.5.3 Server Account Quotas 1.5.4 Disabling Disk Quotas for Server Installation 1.6 Recommended Tasks 1.6.1 Read the Release Notes 1.6.2 Back Up Your System Disk Chapter 2 2 Installing the OpenVMS Management Station Server 2.1 Starting the Installation 2.2 Unzipping the Server Kit 2.3 Installing the Server 2.3.1 Getting Installation Help 2.3.2 Stopping the Installation Procedure 2.3.3 Restarting the Installation 2.4 Determining and Solving Problems 2.4.1 Why Errors Occur 2.4.2 Deciphering Error Messages Chapter 3 3 After Installing the OpenVMS Management Station Server 3.1 Important Note for Multiple System Disk Clusters 3.2 Start the Server on Other Nodes 3.3 Error Log Information 3.4 Update the Printer and Storage Database 3.5 Edit the System Files 3.6 Allow OpenVMS Management Station to Control the Printer and Storage Environment 3.7 Keep Your Printer Environment Up to Date 3.7.1 When is the Database Updated? 3.7.2 Do You Need to Run TNT$UTILITY.COM Manually? 3.7.3 Are There Any Requirements for Running TNT$UTILITY.COM? 3.8 Keeping Your Storage Environment Up to Date 3.9 Enabling Disk Quotas 3.10 Caching Storage Configuration Data 3.11 Running Third-Party TCP/IP Stacks 3.12 Determining and Reporting Problems 3.13 Removing the OpenVMS Management Station Server 3.14 Next Step Chapter 4 4 Installing the OpenVMS Management Station Client on a PC 4.1 Before Installing the Client Software 4.1.1 Required Disk Space 4.1.2 Distribution Files 4.1.3 Required Software 4.1.4 Time Required for Installation 4.2 Installing the Client Software on Your PC 4.2.1 Installation Directory 4.2.2 Installation Procedure 4.2.3 Recovering from Errors 4.3 After Installing the Client Software on Your PC 4.3.1 Defining TCP/IP Nodes 4.4 Uninstalling Version 2.1 of the OpenVMS Managemen Station Client 4.5 Uninstalling OpenVMS Management Station Chapter 5 5 Getting Started With OpenVMS Management Station 5.0.1 Accessing Online Help Appendix A Sample Installation Appendix B Files Installed on Your System B.1 Files Created on OpenVMS Examples A-1 Sample OpenVMS VAX Installation Tables 1-1 Prerequisites for Installing Server Software 1-2 Process Quotas for Running the Server Preface OpenVMS Management Station has two components: - Server software for an OpenVMS system - Client software for the PC This guide describes how to install OpenVMS Management Station server software on your OpenVMS system and client software on a PC. You will find complete instructions and examples for setting up and using this application in both OpenVMS Management Station online help on your PC and the OpenVMS Management Station Overview and Release Notes. Who Should Use This Manual This manual is intended for system managers who are responsible for installing and configuring OpenVMS Management Station. How to Use This Manual If you have not yet installed OpenVMS Management Station, you'll find it helpful to read the whole manual. If you just need a refresher on postinstallation and configuration tasks, check the table of contents for the appropriate sections. Thanks for using OpenVMS Management Station! How This Manual Is Organized This guide is organized as follows: - Chapter 1 describes operating system requirements, hardware requirements, and related procedures that you should complete before installing the OpenVMS Management Station server software on an OpenVMS system. - Chapter 2 gives step-by-step instructions for the server installation. - Chapter 3 describes postinstallation procedures for the server. - Chapter 4 contains preinstallation, installation, and postinstallation requirements for successfully installing OpenVMS Management Station client software on a PC. - Appendix A contains a sample OpenVMS Management Station server installation. - Appendix B contains the list of files that are installed on your OpenVMS system when OpenVMS Management Station is installed. Related Documents +-----------------------------------------------------------------------------+ | For more | | | information | See... | | about... | | |---------------+-------------------------------------------------------------| |OpenVMS |OpenVMS Management Station Help. All information for using | |Management |OpenVMS Management Station is contained in online help on | |Station |your PC. | |---------------+-------------------------------------------------------------| |OpenVMS System |OpenVMS System Manager's Manual and OpenVMS System Management| |Management |Utilities Reference Manual. | |---------------+-------------------------------------------------------------| |OpenVMS System |OpenVMS System Messages and Recovery Procedures Reference | |Error Messages |Manual or the online HELP/MESSAGE facility. | +-----------------------------------------------------------------------------+ For additional information on the HP Open Systems Software Group (OSSG) products and services, access the HP OpenVMS World Wide Web site at the following address: http://www.hp.com/go/openvms Reader's Comments HP welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_COMMENTS.TXT and send us your comments by: +----------------------------------------------------------------------+ |Internet|openvmsdoc@hp.com | |--------+-------------------------------------------------------------| |Fax |603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08 | |--------+-------------------------------------------------------------| | |Hewlett-Packard Company, OSSG Documentation Group, ZKO3-4/U08| |Mail |110 Spit Brook Rd. | | |Nashua, NH 03062-2698 | +----------------------------------------------------------------------+ How To Order Additional Documentation Use the following World Wide Web address to order additional documentation: http://www.hp.com/go/openvms/doc/order If you need help deciding which documentation best meets your needs, call HP. Conventions The name of the OpenVMS AXP operating system has been changed to the OpenVMS Alpha operating system. Any references to OpenVMS AXP or AXP are synonymous with OpenVMS Alpha or Alpha. The following conventions are also used in this manual: +-----------------------------------------------------------------------------+ | |A sequence such as Ctrl/ x indicates that you must hold down the | |Ctrl/ x |key labeled Ctrl while you press another key or a pointing device | | |button. | |---------+-------------------------------------------------------------------| | |A sequence such as PF1 x or GOLD x indicates that you must first | | |press and release the key labeled PF1 or GOLD and then press and | |PF1 x or |release another key or a pointing device button. | |GOLD x | | | |GOLD key sequences can also have a slash (/), dash (--), or | | |underscore (_) as a delimiter in EVE commands. | |---------+-------------------------------------------------------------------| | |In examples, a key name enclosed in a box indicates that you press | |[Return] |a key on the keyboard. (In text, a key name is not enclosed in a | | |box.) | |---------+-------------------------------------------------------------------| | |In command format descriptions, parentheses indicate that, if you | |( ) |choose more than one option, you must enclose the choices in | | |parentheses. | |---------+-------------------------------------------------------------------| | |In command format descriptions, brackets indicate optional | | |elements. You can choose one, none, or all of the options. | |[ ] |(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 command format descriptions, braces indicate a required choice | | |of options; you must choose one of the options listed. | |---------+-------------------------------------------------------------------| | |Boldface text represents the introduction of a new term or the name| |boldface |of an argument, an attribute, or a reason. | |text | | | |Boldface text is also used to show user input in Bookreader | | |versions of the manual. | |---------+-------------------------------------------------------------------| | |Italic text indicates important information, complete titles of | |italic |manuals, or variables. Variables include information that varies in| |text |system output (Internal error number), in command lines (/PRODUCER=| | |name), and in command parameters in text (where device-name | | |contains up to five alphanumeric characters). | |---------+-------------------------------------------------------------------| |UPPERCASE|Uppercase text indicates a command, the name of a routine, the name| |TEXT |of a file, or the abbreviation for a system privilege. | |---------+-------------------------------------------------------------------| | |Monospace type indicates code examples and interactive screen | | |displays. | |Monospace| | |type |In the C programming language, monospace type in text identifies | | |the following elements: keywords, the names of independently | | |compiled external functions and files, syntax summaries, and | | |references to variables or identifiers introduced in an example. | |---------+-------------------------------------------------------------------| | |A hyphen at the end of a command format description, command line, | |- |or code line indicates that the command or statement continues on | | |the following line. | |---------+-------------------------------------------------------------------| | |All numbers in text are assumed to be decimal unless otherwise | |numbers |noted. Nondecimal radixes---binary, octal, or hexadecimal---are | | |explicitly indicated. | +-----------------------------------------------------------------------------+ Chapter 1 Before Installing the HP OpenVMS Management Station Server This chapter describes the tasks required prior to the installation of the HP OpenVMS Management Station server. +---------------------------------------------------------------------------+ | Component | Description | |------------------+--------------------------------------------------------| |Prerequisite Tasks|Distribution Kit | |------------------+--------------------------------------------------------| | |Required Operating System Components and Server Software| |------------------+--------------------------------------------------------| | |Time Required to Install | |------------------+--------------------------------------------------------| |Required Tasks |License Registration | |------------------+--------------------------------------------------------| | |Product Registration | |------------------+--------------------------------------------------------| | |Logging in to a Privileged Account | |------------------+--------------------------------------------------------| | |Process Account Quotas | |------------------+--------------------------------------------------------| | |Disk Quotas | |------------------+--------------------------------------------------------| |Recommended Tasks |Reading Release Notes | |------------------+--------------------------------------------------------| | |Backing Up Your System Disk | +---------------------------------------------------------------------------+ 1.1 Saving Your Existing Database Before You Install When it first starts up, the OpenVMS Management Station server updates an existing Version 2.1 database and journal to Version 3.3 status. This update cannot be reversed and will render the files unusable with Version 2.1. To protect your existing database, the installation makes backup copies of the following files: - TNT$ACS.DAT (TNT$ACS.DAT-SAVE) - TNT$JOURNAL.TNT$TRANSACTION_JOURNAL (TNT$JOURNAL.TNT$TRANSACTION_JOURNAL-SAVE) These files are located in the SYS$COMMON:[SYSEXE] directory. 1.2 Do You Need to Install the Server? If you install this version of the client software on your PC, you must install this version of the OpenVMS Management Station server on all of the OpenVMS systems you want to manage. Upgrading both the client and server software ensures the best compatibility and ease of use. 1.3 Prerequisite Components Table 1-1 provides information about the software that must be installed on your system before installing the OpenVMS Management Station server software. Note ------------------------------------------------------------------------------- This release of OpenVMS Management Station manages and displays only disks that are visible to all nodes in a cluster. This means that you will not be able to display or manage public volumes mounted on "unmanaged" devices, such as an infoserver device. It also means that OpenVMS Management Station does not manage SCSI disks connected to VAX systems. You can manage user accounts and printers on these systems, however. Table 1-1 Prerequisites for Installing Server Software +-----------------------------------------------------------+ | Product | Function | |-----------------------------------+-----------------------| |OpenVMS VAX Version 6.2 or higher | | |or | | |OpenVMS Alpha Version 6.2 or higher|Operating system | |or | | |OpenVMS I64 Version 8.2 or higher | | |-----------------------------------+-----------------------| |HP TCP/IP Services for OpenVMS ^1 | | |and, optionally |Client/server operation| |DECnet for OpenVMS | | +-----------------------------------------------------------+ ------------------------------------------------------------------------------- ^1Additional TCP/IP stacks for OpenVMS have not been tested. However, TCP/IP stacks that are 100% compliant with the QIO interface for HP TCP/IP Services for OpenVMS should also work. Contact your TCP/IP vendor for additional information and support issues. ------------------------------------------------------------------------------- 1.3.1 Volume Shadowing Remedial Kit is Required If you are running Version 6.2 of OpenVMS and plan to manage shadow volumes, the following remedial kits are required: - For OpenVMS VAX systems, VAXCLUSIO01_062 and VAXSHAD06_062. These kits are available from www.itrc.hp.com - For OpenVMS Alpha systems, ALPCLUSIO01_062 and ALPSHAD14_062. These kits are available from www.itrc.hp.com . The OpenVMS saveset or PCSI installation file is stored in a self-expanding compressed file. (The name of the compressed file is kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.) Once you copy the file to your system, RUN it to expand it. The resultant file will be the OpenVMS saveset or PCSI installation file. 1.4 Time Required for Installation The time required to install the OpenVMS Management Station server depends on the media type, the CPU type, and your system configuration. In general, the procedure requires approximately 10 minutes. 1.5 Required Tasks 1.5.1 License Registration Use of OpenVMS Management Station is included when you register the OpenVMS operating system license. A separate license for OpenVMS Management Station is not required. However, for OpenVMS Management Station on OpenVMS for Integrity servers license is included with the Enterprise Operating Environment (EOE) and Mission Critical Operating Environment (MCOE) license bundle. Please refer to the (HP Operating Enivironments for OpenVMS Industry Standard 64 for Integrity servers) Software Product Description (SPD 82.34.xx) for ordering information. FOE Customers can purchase OMS separately. Software Media: Foundation Operating Environment Media, BA322AA, or Enterprise Operating Environment Media, BA323AA, or Mission Critical Operating Environment Media, BA324AA 1.5.2 Logging in to a Privileged Account To install OpenVMS Management Station server software, log in to an account that has SETPRV or at least the following privileges: - AUDIT - CMKRNL - DETACH - NETMBX - SYSNAM - SYSPRV - TMPMBX - PRMMBX - OPER - SECURITY - SYSLCK - SHARE - PHY_IO The POLYCENTER Software Installation utility turns off the BYPASS privilege at the start of the installation. 1.5.3 Server Account Quotas The TNT$STARTUP.COM command that starts the OpenVMS Management Station server uses the quotas shown in Table 1-2. Make sure that these quotas do not exceed the system limits you set with SYSGEN. Table 1-2 Process Quotas for Running the Server +------------------------------+ |Process Quota|Minimum Setting | |-------------+----------------| |ASTLM |300 | |-------------+----------------| |BIOLM |200 | |-------------+----------------| |BYTLM |1638400 | |-------------+----------------| |DIOLM |200 | |-------------+----------------| |ENQLM |6000 | |-------------+----------------| |FILLM |200 | |-------------+----------------| |PGFLQUO |200000 | |-------------+----------------| |WSDEF |16384 | |-------------+----------------| |WSQUO |16384 | |-------------+----------------| |WSEXTENT |32800 | +------------------------------+ If you start the OpenVMS Management Station server using the RUN command, the account you are using must also have these quotas. If you need to change the quotas, use the OpenVMS Authorize utility (AUTHORIZE) to verify and change the process quotas for the account in the user authorization file (SYSUAF.DAT). For example, to verify and then change the BYTLM quota for the account-name account, follow these steps: +-----------------------------------------------------------------------------+ |Step| Action | |----+------------------------------------------------------------------------| | |Invoke the Authorize utility by entering the following commands: | | | | | |$ SET DEFAULT SYS$SYSTEM | |1 | | | |$ RUN SYS$SYSTEM:AUTHORIZE | | | | | | | | | | |----+------------------------------------------------------------------------| | |Show the account quotas: | | | | | |UAF> SHOW | |2 |account-name | | | | | | | | | | |----+------------------------------------------------------------------------| | |Modify the BYTLM quota: | | | | | |UAF> MODIFY | |3 |account-name /BYTLM=1638400 | | | | | | | | | | |----+------------------------------------------------------------------------| | |Exit the Authorize utility: | | | | |4 |UAF> EXIT | | | | | | | | | | |----+------------------------------------------------------------------------| |5 |Activate the change in privileges by logging out and then logging in | | |again. | +-----------------------------------------------------------------------------+ 1.5.4 Disabling Disk Quotas for Server Installation The OpenVMS Management Station server requires disk quotas to be disabled on the SYSTEM disk (UIC [1,4] and UIC [1,1]). Note ------------------------------------------------------------------------------- If the DISKQUOTA parameter remains enabled with a low limit during the startup procedure, the SYSTEM disk may not have enough disk space to create or extend the log files and the user accounts database. The server must be able to create log files and extend the user account database in order for the server to start and work properly. Follow these steps to determine the status of the disk quotas and to disable the disk quotas if they are enabled. +-----------------------------------------------------------------------------+ |Step| Action | |----+------------------------------------------------------------------------| | |Check whether disk quotas are disabled by entering the following | | |command: | | | | | |$ SHOW QUOTA | |1 | | | |%SYSTEM-F-QFNOTACT, disk quotas not enabled on this volume | | | | | | | | | | |----+------------------------------------------------------------------------| | |If disk quotas are enabled, disable them by entering the following | | |commands: | | | | | |$ RUN SYS$SYSTEM:DISKQUOTA | | | | |2 |DISKQUOTA> DISABLE | | | | | |DISKQUOTA> EXIT | | | | | | | | | | +-----------------------------------------------------------------------------+ 1.6 Recommended Tasks 1.6.1 Read the Release Notes Reading the release notes that are included in the server software can help you find out more about the product before you begin the installation. You can extract the release notes file before installing OpenVMS Management Station by entering the following commands at the DCL prompt: $ DEFINE PCSI$SOURCE source-drive:[TNT033.KIT] where source-drive:[TNT033.KIT] is the location of the kit. $ PRODUCT EXTRACT RELEASE_NOTES TNT - _$ /VERSION=V3.3 /FILE=NOTES.TXT 1.6.2 Back Up Your System Disk HP recommends that you back up your system disk before installing any software. Use the backup procedures that are established at your site. Chapter 2 Installing the OpenVMS Management Station Server This chapter describes the following tasks required for installing the OpenVMS Management Station server: +-----------------------------------------------------------------------------+ | Topic | Description | |------------------------------+----------------------------------------------| |Starting the Installation |Using the POLYCENTER Software Installation | | |utility | |------------------------------+----------------------------------------------| |Installing the Server |Using the DCL Interface | |------------------------------+----------------------------------------------| | |Getting Installation Help | |------------------------------+----------------------------------------------| | |Stopping the Installation Procedure | |------------------------------+----------------------------------------------| | |Restarting the Installation | |------------------------------+----------------------------------------------| |Determining and Solving |Why Errors Occur | |Problems | | |------------------------------+----------------------------------------------| | |Deciphering Error Messages | +-----------------------------------------------------------------------------+ 2.1 Starting the Installation If you have not already done so, stop the OpenVMS Management Station server. If you are installing the server on an OpenVMS Cluster system, stop the server on all nodes that share the SYS$COMMON: directory. (Generally, this means to stop the server on all nodes in the OpenVMS Cluster on which you plan to install the server.) $ @SYS$STARTUP:TNT$SHUTDOWN.COM 2.2 Unzipping the Server Kit To unzip the kit, use UNZIP on the OpenVMS system to unzip the files. See /cd/ unzip/ for the location of UNZIP for VAX and Alpha systems. Note that UNZIP is also available on the OpenVMS Freeware CD.) You must define a foreign symbol for the UNZIP image before you can use it. For example, if the UNZIP image is in your SYS$SYSTEM directory, you would use the following commands from the directory containing the server kit: For OpenVMS VAX: $ UNZIP :== $SYS$SYSTEM:UNZIP-VAX.EXE $ UNZIP DEC-VAXVMS-TNT-V033-1.ZIP For OpenVMS Alpha: $ UNZIP :== $SYS$SYSTEM:UNZIP-AXP.EXE $ UNZIP DEC-AXPVMS-TNT-V033-1.ZIP 2.3 Installing the Server Once you have unzipped the server kit, follow these steps to install it: 1. At the DCL prompt ($), enter the following command: $ DEFINE PCSI$SOURCE source-drive:[TNT033.KIT] where source-drive: is the device name (for example, DKA500:) and [TNT033.KIT] is the directory containing the server kit. Note that the colon (:) following the device name is considered part of the device name. Include the colon (:) when you enter the name of the device. 2. If it is not already mounted, mount the distribution media by entering the following command at the DCL prompt: $ MOUNT/OVERRIDE=ID source-drive: 3. At the DCL prompt, enter the PRODUCT command, the name of the task to be performed, and the product name: $ PRODUCT INSTALL TNT/VERSION=V3.3 Note that if OpenVMS Management Station Version 2.1 was previously installed it will be removed by the Version 3.3 installation. As the installation begins, text similar to the following is displayed. product install tnt /version=V3.3 The following product has been selected: DEC VAXVMS TNT V3.3 Layered Product Do you want to continue? [YES] Y 4. Press Return to answer Yes (the default). The installation progresses. Note ----------------------------------------------------------- It might take several minutes or more after the pcsi ..90% complete status message is displayed before the installation progresses. The OpenVMS Management Station server uses this time to analyze your printer and storage configuration. ***DEC VAXVMS TNT V3.3: DEC OpenVMS Management Station Copyright: Hewlett-Packard Development Company, L.P. All rights reserved. Hewlett-Packard Development Company This product uses the PAK: VAX-VMS * This product does not have any configuration options. Execution phase starting ... The following product will be installed to destination: DEC VAXVMS TNT V3.3 DISK$OPENVMS062:[VMS$COMMON.] Portion done: 0%...30%...70%...80%...90%...100% The following product has been installed: DEC VAXVMS TNT V3.3 Layered Product %PCSI-I-IVPEXECUTE, executing test procedure for DEC VAXVMS TNT V3.3 ... %PCSI-I-IVPSUCCESS, test procedure completed successfully DEC VAXVMS TNT V3.3: DEC OpenVMS Management Station Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @SYS$STARTUP:TNT$STARTUP.COM Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @SYS$STARTUP:TNT$SHUTDOWN.COM Release notes for OpenVMS Management Station available See the installation guide for post installation information. Congratulations! You have successfully installed OpenVMS Management Station. Note that the installation automatically starts OpenVMS Management Station server on this node. 2.3.1 Getting Installation Help For a description of all the features you can request when starting an installation, such as purging files and configuring the installation, refer to DCL help for the PRODUCT INSTALL command. The following DCL help options are available: +-----------------------------------------------------------------------------+ |Option| Action | |------+----------------------------------------------------------------------| |1 |Include the /HELP qualifier in the PRODUCT INSTALL command line. | |------+----------------------------------------------------------------------| |2 |Press the Help key in response to a question from the POLYCENTER | | |Software Installation utility. | |------+----------------------------------------------------------------------| |3 |Type the DCL command HELP PRODUCT, followed by the name of a command | | |(for example, HELP PRODUCT INSTALL). | +-----------------------------------------------------------------------------+ 2.3.2 Stopping the Installation Procedure Use the following procedure if you need to stop the installation procedure at any time: 1. Press Ctrl/Y. 2. Enter the PRODUCT REMOVE command to reverse any changes to the system that occurred during the partial installation. Result: This action deletes all files created up to that point and causes the installation procedure to end. 2.3.3 Restarting the Installation If the installation fails, begin the installation procedure again. 2.4 Determining and Solving Problems If the installation procedure fails, the following message is displayed: %POLYCENTER Software Installation utility INSTAL-E-INSFAIL, The installation of OpenVMS Management Station Version 3.3 has failed. 2.4.1 Why Errors Occur An error can occur during the installation if one or more of the following conditions exist: - The operating system version is incorrect. - The prerequisite software version is incorrect. - Quotas necessary for successful installation are inadequate (see Chapter 1). 2.4.2 Deciphering Error Messages If you receive an error message that begins with %PCSI-E-INSTAL, refer to the DCL HELP/MESSAGE utility for POLYCENTER Software Installation utility information and a possible solution to the problem. Chapter 3 After Installing the OpenVMS Management Station Server After you install the OpenVMS Management Station server, perform the following postinstallation tasks. +-------------------------------------------------------------------------+ |Task| Description | |----+--------------------------------------------------------------------| |1 |Start the server on other nodes. | |----+--------------------------------------------------------------------| |2 |Update the printer database. | |----+--------------------------------------------------------------------| |3 |Edit the system files. | |----+--------------------------------------------------------------------| |4 |Allow OpenVMS Management Station to control the printer environment.| |----+--------------------------------------------------------------------| |5 |Keep your printer environment up to date. | +-------------------------------------------------------------------------+ This chapter describes how to perform these tasks as well as other management functions. 3.1 Important Note for Multiple System Disk Clusters The OpenVMS Management Station server creates several configuration files: - TNT$UADB.DAT - TNT$ACS.DAT - TNT$JOURNAL.TNT$TRANSACTION_JOURNAL - TNT$MONITOR.DAT - TNT$MONITOR.TNT$MONITOR_JOURNAL - TNT$EMERGENCY_MOUNT.COM In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required. However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the files on those disks. Rules: The following rules apply: - Disks holding common resources must be mounted early in the system startup procedure, such as in the SYLOGICALS.COM procedure. - You must ensure that the disks are mounted with each cluster reboot. Follow these steps to coordinate files: 1. Decide where to locate the files. In a cluster with multiple system disks, system management is much easier if the common system files are located on a single disk that is not a system disk. 2. Copy TNT$UADB.DAT, TNT$ACS.DAT, TNT$MONITOR.DAT, TNT$MONITOR.TNT$MONITOR_JOURNAL, TNT$EMERGENCY_MOUNT.COM, and TNT$JOURNAL.TNT$TRANSACTION_JOURNAL to a location other than the system disk. 3. Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM on each system disk and define logical names that specify the location of the cluster common files. Example: If the files will be located on $1$DJA16, define logical names as follows: $ DEFINE/SYSTEM/EXEC TNT$ACS - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DAT TNT$EMERGENCY_MOUNT.COM will be created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if the logical exists. $ DEFINE/SYSTEM/EXEC TNT$UADB - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT $ DEFINE/SYSTEM/EXEC TNT$JOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL $ DEFINE/SYSTEM/EXEC TNT$MONITOR - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR $ DEFINE/SYSTEM/EXEC TNT$MONITORJOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.TNT$MONITOR_JOURNAL 4. To ensure that the system disks are mounted correctly with each reboot, follow these steps: 1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to the [VMS$COMMON.SYSMGR] directory, and edit it for your configuration. 2. Edit SYLOGICALS.COM and include commands to mount, with the appropriate volume label, the system disk containing the shared files. Example: If the system disk is $1$DJA16, include the following command: $ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM - _$ $1$DJA16: volume-label 3.2 Start the Server on Other Nodes If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without a reboot, you must start the server on those nodes. Use SYSMAN to start the server as follows: $ @SYS$STARTUP:TNT$STARTUP.COM or, you can log into each node that shares the SYS$COMMON: directory and enter the following command: $ @SYS$STARTUP:TNT$STARTUP.COM If you are performing an upgrade or a reinstallation and OpenVMS Management Station is already running on the node, add the RESTART parameter to the startup command, as follows: $ @SYS$STARTUP:TNT$STARTUP.COM RESTART 3.3 Error Log Information OpenVMS Management Station writes error log information to the file TNT$SERVER_ERROR.LOG. This error log is created in the SYS$SPECIFIC:[SYSEXE] directory. If you start the OpenVMS Management Station server on multiple nodes in a cluster, which is recommended, there will be multiple server error logs. 3.4 Update the Printer and Storage Database When you installed OpenVMS Management Station, the installation started the OpenVMS Management Station server on the installation node. If this installation was an upgrade, the server converts the existing OpenVMS Management Station database to the V3.3 format. If this was a new installation, the server creates an initial version of the database file TNT$ACS.DAT and invokes the update functions automatically. To complete the database, start the OpenVMS Management Station server on each node in your cluster. The instances of the server communicate with each other to determine device, queue, and volume information, and the server must be running on each node for this communication to take place. 3.5 Edit the System Files To start the OpenVMS Management Station server from your system startup files, insert one of the following commands into your system startup procedures (probably SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Manager and network are started, but immediately prior to the ENABLE AUTOSTART/QUEUES. Note ----------------------------------------------------------- Remove any other invocations of TNT$STARTUP you might have added in previous releases of the OpenVMS Management Station. OpenVMS Management Station cannot start until the network has started. If you start your network using a batch process, OpenVMS Management Station might start before the batch process completes and the network is started. +-----------------------------------------------------------------------------+ | Command |Parameter|Parameter| Description | | | 1 | 2 | | |------------+---------+---------+--------------------------------------------| |@TNT$STARTUP|blank |N.A. |Starts the server. Does not start printer | | | | |queues or mount volumes. | |------------+---------+---------+--------------------------------------------| | | | |Shuts down a running server, then starts the| |@TNT$STARTUP|RESTART |N.A. |server. Does not start printer queues or | | | | |mount volumes. | |------------+---------+---------+--------------------------------------------| | | | |Starts the server. Starts any printer queues| | | | |that are not yet started and are managed by | |@TNT$STARTUP|BOOT |blank |OpenVMS Management Station. Does not mount | | | | |volumes managed by OpenVMS Management | | | | |Station. | |------------+---------+---------+--------------------------------------------| | | | |Starts the server. Starts any printer queues| | | | |that are not yet started and are managed by | |@TNT$STARTUP|BOOT |ALL |OpenVMS Management Station. Mounts any | | | | |volumes that are not yet mounted and are | | | | |managed by OpenVMS Management Station. | |------------+---------+---------+--------------------------------------------| | | | |Starts the server. Starts any printer queues| | | | |that are not yet started and are managed by | |@TNT$STARTUP|BOOT |PRINTERS |OpenVMS Management Station. Does not mount | | | | |volumes managed by OpenVMS Management | | | | |Station. | |------------+---------+---------+--------------------------------------------| | | | |Starts the server. Mounts any volumes that | |@TNT$STARTUP|BOOT |STORAGE |are not yet mounted and are managed by | | | | |OpenVMS Management Station. Does not start | | | | |any printer queues. | +-----------------------------------------------------------------------------+ Note that the effect of TNT$STARTUP BOOT, with no second parameter, has not changed from earlier releases. This command starts any printer queues that are not yet started and are managed by OpenVMS Management Station, but does not mount any volumes. Add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @SYS$STARTUP:TNT$SHUTDOWN.COM 3.6 Allow OpenVMS Management Station to Control the Printer and Storage Environment It is not necessary to remove your existing queue startup and volume mount DCL procedures immediately. The OpenVMS Management Station server will recognize that you started a queue or mounted a volume with your command procedures and will assume that you want it that way. As you become familiar with the server's management ability, you can remove or comment out the DCL commands and procedures that perform these tasks and allow OpenVMS Management Station to control your printer and storage environment. In addition, the OpenVMS Management Station server periodically (every 24 hours) generates a DCL command procedure that includes the commands to mount all of the volumes managed by OpenVMS Management Station. If you are familiar with DCL, you can look at this command procedure to see what actions OpenVMS Management Station performs for you. And, in the event of an unforeseen system problem or a corrupt server database (SYS$SYSTEM:TNT$ACS.DAT), you could use this command procedure to mount the volumes. The name of the generated file is TNT$EMERGENCY_MOUNT.COM. TNT$EMERGENCY_MOUNT.COM is created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if that logical name exists. The OpenVMS Management Station server limits TNT$EMERGENCY_MOUNT.COM to seven versions. 3.7 Keep Your Printer Environment Up to Date The OpenVMS Management Station server installation creates a file named SYS$STARTUP:TNT$UTILITY.COM. This command procedure scans the OpenVMS system and updates the database of known printers, queues, and related devices. 3.7.1 When is the Database Updated? The database is updated: - As part of the OpenVMS Management Station installation. - When you specifically invoke TNT$UTILITY.COM. - At periodic intervals as a server background thread. Two logical names control how often this server thread runs: +-------------------------------------------------------------------------+ | Logical Name | Description | |------------------------------+------------------------------------------| | |How often the thread should run, in | | |minutes, from when the server was last | |TNT$PRINTER_RECON_INTERVAL |started on this node. If you do not define| | |this logical, the default value is 1440 | | |minutes (24 hours). | |------------------------------+------------------------------------------| | |The minimum number of minutes that must | | |elapse before the thread should run again,| |TNT$PRINTER_RECON_INTERVAL_MIN|starting from when the database was last | | |updated. If you do not define this | | |logical, the default value is 60 minutes | | |(1 hour). | +-------------------------------------------------------------------------+ You can think of these logicals as meaning "run the thread this often (TNT$PRINTER_RECON_INTERVAL), but make sure this much time has elapsed since the database was last updated (TNT$PRINTER_RECON_INTERVAL_MIN)." Because you can run TNT$UTILITY.COM yourself, and because the OpenVMS Management Station server also updates the database, the TNT$PRINTER_RECON_INTERVAL_MIN logical prevents the database from being updated more frequently than is actually needed. If you want to change the defaults for one of these logicals, define the logical on all nodes on which the OpenVMS Management Station server is running. 3.7.2 Do You Need to Run TNT$UTILITY.COM Manually? If you use OpenVMS Management Station to make all of the changes to your printer configuration, the configuration files are immediately modified to reflect the changes and you probably do not need to specifically run TNT$UTILITY.COM. However, if you or someone else uses DCL to make a change --- for example, if you use the DELETE /QUEUE command to delete a queue --- the configuration files will not be synchronized. In this case, the OpenVMS Management Station client will advise you to run TNT$UTILITY.COM to resynchronize the database. Run the following procedure on one node in the cluster to make the database match your system: $ @SYS$STARTUP:TNT$UTILITY.COM UPDATE PRINTERS For example, if you or someone else used DCL to delete a queue, you need to delete that queue from the database. TNT$UTILITY.COM assumes that your system is set up and running the way that you want it to, so you should fix any problems before you run TNT$UTILITY.COM. 3.7.3 Are There Any Requirements for Running TNT$UTILITY.COM? You need the SYSNAM privilege to run TNT$UTILITY.COM. TNT$UTILITY.COM connects to the OpenVMS Management Station server on the current OpenVMS system to determine device and queue information. Therefore, the OpenVMS Management Station server must be running on the node where you run TNT$UTILITY.COM. The OpenVMS Management Station server then connects to the other OpenVMS Management Station servers in the OpenVMS Cluster to determine device and queue information. It is generally a good idea to keep the OpenVMS Management Station server running on the other nodes in an OpenVMS Cluster to keep the database up to the minute. However, if the OpenVMS Management Server is not able to connect to the OpenVMS Management Station server on a given node, it uses the known information about that OpenVMS node from the database. That is, in the absence of a valid connection to that OpenVMS node, the information in the database is assumed to be correct. 3.8 Keeping Your Storage Environment Up to Date The TNT$UTILITY.COM utility accepts parameters (UPDATE STORAGE) to update the storage database. However, the storage database is updated dynamically every time you use the OpenVMS Management Station client to perform a storage management operation. Therefore, you do not need to run TNT$UTILITY.COM to update the storage database. 3.9 Enabling Disk Quotas Before installing OpenVMS Management Station, you might have disabled disk quotas on the SYSTEM disk. If so, you should reenable the quotas and then rebuild to update quota information by entering the following commands: $ RUN SYS$SYSTEM:DISKQUOTA DISKQUOTA> ENABLE DISKQUOTA> REBUILD DISKQUOTA> EXIT 3.10 Caching Storage Configuration Data OpenVMS Management Station uses two logical names to determine how often to refresh cached (in-memory) storage configuration data. - TNT$PURGE_CYCLE_LATENCY---Determines how often to wait (in seconds) after purging stale device reports before purging again. This value affects how frequently the cluster-wide data (maintained by a "master server" is updated in memory. min = 180 default = 1800 (30 minutes) max = 18000 (5 hours) -TNT$LOCAL_SURVEY_LATENCY---Determines the delay (in seconds) from one node-specific device survey to the next. This value is independent of cluster-wide surveys requested by the "master server" when performing a purge. min = 6 default = 60 (1 minute) max = 600 (10 minutes) For both logical names, smaller values result in the OpenVMS Management Station server consuming more CPU cycles in periodic purges or surveys. If you do not accept the defaults, you might find that larger OpenVMS Cluster systems behave better with values on the high end of the allowed range. If you do not define these logicals, the OpenVMS Management Station server uses the default values. If you do define these logical names, the values are used only if they are within the minimum to maximum range. 3.11 Running Third-Party TCP/IP Stacks HP TCP/IP Services for OpenVMS Version 3.2 or higher is the only supported TCP/ IP stack. Additional stacks have not been tested. However, TCP/IP stacks that are 100% compliant with the QIO interface for TCP/IP Services for OpenVMS should also work. (Contact your TCP/IP vendor for additional information and support issues.) For the best chance of success, check the following: - Make sure that the QIO service (for example, UCXQIO) is enabled. - For TCPware, also make sure that TCPware's UCX$IPC_SHR.EXE is an installed image. 3.12 Determining and Reporting Problems If you encounter a problem while using OpenVMS Management Station, please report it to HP. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: - If your software contract or warranty agreement entitles you to telephone support, call HP. - If the problem is related to OpenVMS Management Station documentation, use the Internet address printed in front of this book to send us your comments. 3.13 Removing the OpenVMS Management Station Server When you execute the OpenVMS Installation or upgrade procedure, the OpenVMS Management Station server software is automatically installed on your OpenVMS system disk. If this server software is later reinstalled using another kit (for example, a kit downloaded from the web or a patch kit), you have the option to remove the OpenVMS Management Station. If you use the POLYCENTER Software Installation utility to remove the OpenVMS Management Station from the OpenVMS system, the following files are not removed : - TNT$ACS.DAT - TNT$JOURNAL.TNT$TRANSACTION_JOURNAL - TNT$SERVER_ERROR.LOG - TNT$UADB.DAT - TNT$EMERGENCY_MOUNT.COM Do not delete these files unless you have already removed OpenVMS Management Station. 3.14 Next Step After completing these postinstallation tasks for the server software, proceed to Chapter 4 for information about installing the client software on your PC. Chapter 4 Installing the OpenVMS Management Station Client on a PC This chapter discusses the following topics for installing the OpenVMS Management Station client on a PC: +-----------------------------------------------------------------------------+ | Topic | Description | |-------------------------------------+---------------------------------------| |Before Installing the Client Software|Required Memory and Disk Space | |-------------------------------------+---------------------------------------| | |Required Software | |-------------------------------------+---------------------------------------| | |Time Required for Installation | |-------------------------------------+---------------------------------------| | |Backing up the Installation Disks | |-------------------------------------+---------------------------------------| |Installing the Client Software |Installation Procedure | |-------------------------------------+---------------------------------------| | |Recovering from Errors | |-------------------------------------+---------------------------------------| | |Uninstalling OpenVMS Management Station| |-------------------------------------+---------------------------------------| | |Reporting Problems | +-----------------------------------------------------------------------------+ 4.1 Before Installing the Client Software 4.1.1 Required Disk Space Your PC requires 20 MB of free disk space to install the OpenVMS Management Station client software. 4.1.2 Distribution Files The OpenVMS Management Station client kit, TNT033.EXE for Intel systems can be installed on Windows 2000 or Windows XP operating systems. 4.1.3 Required Software To install the OpenVMS Management Station client kit, either Windows 2000 or Windows XP (Intel only) must be installed on your PC. The version of Microsoft Management Console (MMC) included in this baselevel requires files provided by Microsoft Internet Explorer Version 3.02 or later must be present on the system. 4.1.4 Time Required for Installation The time required to install the OpenVMS Management Station client software is approximately 5 minutes. 4.2 Installing the Client Software on Your PC 4.2.1 Installation Directory The installation procedure allows you to select the installation directory, and suggests \Program Files\OpenVMS Mgmt Station\ as the default. 4.2.2 Installation Procedure If you copied the OpenVMS Management Station client kit from the World Wide Web field test site, copy the file TNT033.EXE as appropriate to a temporary directory and run it. These are self-extracting executable files that automate the OpenVMS Management Station installation. 4.2.3 Recovering from Errors If an error occurs during installation, you will receive an error message describing the problem. This information can help you determine the cause of the problem. An error can occur during the installation if one or more of the following conditions exist: - The operating system version is incorrect. - Disk space and memory necessary for successful installation are inadequate. 4.3 After Installing the Client Software on Your PC When you create an OpenVMS Cluster or OpenVMS Node object in an OpenVMS Management Domain, you select the transport you want to use for all connections to that system. You can choose DECnet Phase IV or TCP/IP. OpenVMS Management Station uses this transport for all communications between the PC and this system, or between any other OpenVMS system that is running the OpenVMS Management Station server and this system. Note ----------------------------------------------------------- The OpenVMS Management Station client supports only TCP/IP connections for primary servers. That is, the connection between the PC and the OpenVMS system uses only TCP/IP. Therefore, at least one OpenVMS system must be running TCP/ IP. ----------------------------------------------------------- You do need to make sure that your PC can connect to the primary-server systems, as described in the following sections. OpenVMS Management Station connects your PC to the primary-server system and then routes management operations to the target systems. 4.3.1 Defining TCP/IP Nodes Your hosts file or name server must be able to resolve the IP name or address of all primary-server systems. If you can successfully ping the primary-server systems from your PC, then this condition is met. 4.4 Uninstalling Version 2.1 of the OpenVMS Management Station Client Version 3.0 or later of the OpenVMS Management Station client are not dependent on Version 2.1 and do not share any files with this prior version. After installing the Version 3.0 or later client, you can uninstall Version 2.1 client software. 4.5 Uninstalling OpenVMS Management Station If you need to uninstall the OpenVMS Management Station client software, make sure you first exit OpenVMS Management Station. The uninstallation fails if OpenVMS Management Station is currently running. If you run the OpenVMS Management Station Help, the following files might be created: - VMSMGMT.FTS - VMSMGMT.GID - VMSPRINT.FTS - VMSPRINT.GID - VMSSCOPE.FTS - VMSSCOPE.GID - VMSSTORE.FTS - VMSSTORE.GID - VMSACNT.FTS - VMSACNT.GID The OpenVMS Management Station Uninstall program does not delete these files. To complete the uninstall: 1. Delete these files 2. Delete the OpenVMS Management Station directory Note that the OpenVMS Management Station Uninstall program does not uninstall the Microsoft Management Console (MMC) support files. Chapter 5 Getting Started With OpenVMS Management Station All information about getting started, setting up, and using OpenVMS Management Station is contained in online help and the OpenVMS Management Station Overview and Release Notes. 5.0.1 Accessing Online Help Select OpenVMS Management Station Help from the Start menu to access the OpenVMS Management Station online help. Appendix A Sample Installation This appendix contains a sample installation of the OpenVMS Management Station server on an OpenVMS VAX Version 6.2 system. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. Example A-1 Sample OpenVMS VAX Installation $ PRODUCT INSTALL TNT/VERSION=V3.3 The following product has been selected: DEC VAXVMS TNT V3.3 Layered Product Do you want to continue? [YES] Y Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC VAXVMS TNT V3.3: DEC OpenVMS Management Station ? Copyright: Hewlett-Packard Development Company, L.P. All rights reserved. Hewlett-Packard Development Company This product uses the PAK: VAX-VMS * This product does not have any configuration options. Execution phase starting ... The following product will be installed to destination: DEC VAXVMS TNT V3.3 DISK$OPENVMS062:[VMS$COMMON.] Portion done: 0%...30%...70%...80%...90%...100% The following product has been installed: DEC VAXVMS TNT V3.3 Layered Product %PCSI-I-IVPEXECUTE, executing test procedure for DEC VAXVMS TNT V3.3 ... %PCSI-I-IVPSUCCESS, test procedure completed successfully DEC VAXVMS TNT V3.3: DEC OpenVMS Management Station Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @SYS$STARTUP:TNT$STARTUP.COM Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @SYS$STARTUP:TNT$SHUTDOWN.COM Release notes for OpenVMS Management Station available See the installation guide for post installation information. Appendix B Files Installed on Your System The OpenVMS Management Station installation procedure installs a number of files on your OpenVMS system. The following section lists the installed files. B.1 Files Created on OpenVMS The following files are created on your OpenVMS system when the OpenVMS Management Station server is installed: - SYS$SYSTEM:TNT$SERVER.EXE - SYS$SYSTEM:TNT$HELPER.EXE - SYS$STARTUP:TNT$STARTUP.COM - SYS$STARTUP:TNT$SHUTDOWN.COM - SYS$STARTUP:TNT$UTILITY.COM - SYS$TEST:TNT$IVP.COM - SYS$COMMON:[SYSTEST.TNT]TNT$SERVER_IVP.EXE - SYS$HELP:TNT032D.RELEASE_NOTES These files are created when the server is started: - SYS$COMMON:[SYSEXE]TNT$UADB.DAT - SYS$COMMON:[SYSEXE]TNT$ACS.DAT - SYS$COMMON:[SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL - SYS$COMMON:[SYSEXE]TNT$MONITOR.DAT - SYS$COMMON:[SYSEXE]TNT$MONITOR.TNT$MONITOR_JOURNAL