TeMIP for DIGITAL UNIX OSI Management Toolkit OSI_Access_Module______________________________ Run-Time Kit Installation Guide Order Number: AA-QEMRG-TE This guide describes how to install the TeMIP OSI Access Module on your DIGITAL UNIX system. Revision/Update Information: V3.2.0 This edition supersedes all V3.1 editions. Operating System: DIGITAL UNIX Software Version: TeMIP OSI Management Toolkit V3.2 ________________________________________________________________ July 1998 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used and copied only in accordance with the terms of such license. Digital Equipment Corporation assumes no responsibility for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. This document defines the management and service interfaces provided by this Management Module and, if applicable, the services that this module requires of other TeMIP Framework Management Modules. It is provided to ensure that new Management Modules developed for the TeMIP Framework system will work in concert with this TeMIP Framework module or module package. It is not intended to be used as an aid in cloning or duplicating the functionality or service interfaces described and such use is expressly forbidden. Except as may be expressly agreed upon by Digital in writing, the purchase, receipt, or any use of this document or its contents does not in any way create, by implication or otherwise, any express or implied license under any of Digital Equipment Corporation's patent, trademark, copyright or trade secret rights for the ideas, techniques, or concepts herein. © Digital Equipment Corporation 1997, 1998. All rights reserved. Printed in Europe. Trademarks: Alpha AXP, AXP, AlphaServer, AlphaStation, AlphaGeneration and the AlphaGeneration design mark, TeMIP, TeMIP Framework, DECcmi, DECnet, DECnet-Plus, DECsafe, DECterm, DECwindows, TruCluster, ULTRIX and the DIGITAL Logo are trademarks of Digital Equipment Corporation. C-ISAM is a registered trademark of Informix Software, Inc. INGRES is a registered trademark of Ingres Corporation. Motif is a registered trademark of Open Software Foundation, Inc. ORACLE, SQL*Net and SQL*Plus are registered trademarks of Oracle corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. OSIAM is a trademark of MARBEN Produit. Rogue Wave and h++ are registered trademarks and Tools.h++ is a trademark of Rogue Wave Software, Inc. Solaris is a registered trademark of Sun Microsystems, Inc. SQL Server is a trademark of Sybase, Inc. Sun is a registered trademark of Sun Microsystems, Inc. SunLink is a registered trademark of Sun Microsystems, Inc. SunOS is a registered trademark of Sun Microsystems, Inc. SYBASE is a registered trademark of Sybase, Inc. Transact-SQL is a registered trademark of Sybase, Inc. X/Open is a trademark of X/Open Company, Ltd. UNIX[R] - UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. DIGITAL UNIX V3.2 is an X/Open UNIX 93 branded product. DIGITAL UNIX V4.0 is a UNIX 95 branded product. DIGITAL This document is available on CD-ROM. This document was prepared using DEC DOCUMENT, Version 3.2. ________________________________________________________________ Contents ................................................... v Preparing to Install the TeMIP OSI AM Run-Time Kit 1.1 Types of Installation......................... 1-1 1.1.1 Local Installation........................ 1-1 1.1.2 RIS Installation.......................... 1-1 1.2 Installation Requirements..................... 1-2 1.2.1 Hardware and Software..................... 1-2 1.2.2 Run-Time Kit Software Subsets............. 1-2 1.2.3 Time Required to Install.................. 1-3 1.2.4 Logging On................................ 1-3 1.2.5 Backing Up the System Disk................ 1-3 1.2.6 Checking the Required Software Subsets.... 1-3 1.2.7 Disk Space Requirements................... 1-4 1.2.8 Using the Director User Account........... 1-6 1.3 License Registration.......................... 1-7 1.4 Aborting the Installation and Recovering from Errors........................................ 1-8 Installing the TeMIP OSI AM Run-Time Kit 2.1 Starting the Installation Procedure Locally... 2-2 2.2 System Configuration.......................... 2-2 2.3 Local Installation of the OSI Protocol Stack......................................... 2-3 2.4 Local Installation of the OSI Management Toolkit Release Notes......................... 2-3 2.5 Local Installation of the OSI AM.............. 2-5 2.6 RIS Server Update............................. 2-10 iii 3 After Installing the TeMIP OSI AM Run-Time Kit 3.1 Configuring your System for the OSI AM........ 3-1 3.2 Verifying the Run-Time Kit Installation....... 3-2 3.2.1 IVP Overview.............................. 3-2 3.2.2 Symbols and Files Used by the IVP......... 3-3 3.2.3 Names Reserved for the IVP................ 3-4 3.2.4 Example Log of a Successful IVP........... 3-5 3.3 Deleting the TeMIP OSI AM Run-Time Kit from Your System................................... 3-8 A Pre-Installation Checklist A.1 Local Installation............................ A-1 A.2 Installation on a RIS Server.................. A-3 A.3 Installation from a RIS Server................ A-3 B Files Installed on your System B.1 OSI Management Toolkit Release Notes Subset... B-1 B.2 OSI AM Subset................................. B-1 B.2.1 OSI AM Subset Links....................... B-4 C Recovering from Errors C.1 Failures During Product Installation ......... C-1 C.2 Failures During Product Use................... C-2 Index Tables 1-1 Disk Space Requirements................... 1-4 B-1 Directory /usr/kits/temip/NOE320/help..... B-1 B-2 Directory /usr/kits/temip/NOE320.......... B-2 B-3 Directory /usr/kits/temip/NOE320/temip_osi_am....... B-2 B-4 Directory /usr/kits/temip/NOE320/temip_osi_am/bin... B-2 B-5 Directory /usr/kits/temip/NOE320/temip_osi_am/examples.. B-2 B-6 Directory /usr/kits/temip/NOE320/temip_osi_am/files.. B-3 B-7 Directory /var/kits/temip/temip_osi_am.... B-3 iv B-8 Directory /var/kits/temip/temip_osi_am/install...... B-3 v _________________________________________________________________ Preface This guide describes how to install the TeMIP OSI AM Run- Time Kit software on a DIGITAL UNIX[R] + system. Keep this guide with your distribution kit. You will need it to install maintenance updates or to reinstall the TeMIP OSI AM Run-Time Kit for any other reason. Intended Audience This guide is intended for personnel who are responsible for installing the TeMIP OSI AM Run-Time Kit on a DIGITAL UNIX system, for example: o A system manager installing the TeMIP on the local system o A system manager installing the TeMIP from the Remote Installation Services (RIS) server area of a remote system o A RIS manager installing the TeMIP on a RIS server area. It is assumed that the reader has an understanding of the shell concept of DIGITAL UNIX and is familiar with the mounting of peripheral devices. ____________________ + UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. v Structure of This Guide The guide is structured as follows: o Chapter 1 describes the requirements for installing the TeMIP OSI AM Run-Time Kit software. o Chapter 2 describes the installation of the TeMIP OSI AM Run-Time Kit files locally, or on a RIS server area. o Chapter 3 describes how to configure your system, how to verify the installation, and how to delete installed subsets. o Appendix A provides a check list of pre-installation requirements. o Appendix B provides a list of the TeMIP OSI AM Run-Time Kit files installed. o Appendix C provides information to help you deal with failure or errors that might occur during the TeMIP OSI AM Run-Time Kit installation. vi Document Conventions The following conventions are used in this guide: ___________________________________________________________ Convention_______Meaning___________________________________ # The UNIX[R] superuser default prompt. Ctrl/x Indicates that you must hold down the key labelled Ctrl while you press another key or a pointing device button. In examples and procedures, a key combination is enclosed in a box. Indicates that you press the Return key to execute a command line. Boldface Indicates the first use of a term, and user input in examples. Italics Italic text is used to indicate the following: o The title of a document to which reference is made. o The directory paths and file names in text. ___________________________________________________________ Associated Documents o TeMIP Planning Guide o TeMIP Director Configuration and Management Guide o TeMIP for DIGITAL UNIX Installation Guide o DECcmi for DIGITAL UNIX Installation and Configuration Guide o DECcmi for Sun Solaris Installation and Configuration Guide o DIGITAL UNIX Guide to Remote Installation Services o DIGITAL System Administration documentation vii 1 _________________________________________________________________ Preparing to Install the TeMIP OSI AM Run-Time Kit This chapter describes the requirements and preparations for installing the TeMIP OSI AM Run-Time Kit. The installation procedures described in this guide apply only to TeMIP OSI AM Run-Time Kit V3.2. Release Notes are provided with the installation kit and DIGITAL strongly recommends that you read these notes before proceeding with the installation. You can find more information in: o Types of Installation, Section 1.1 o Installation Requirements, Section 1.2 o License Registration, Section 1.3 o Aborting the Installation and Recovering from Errors, Section 1.4 1.1 Types of Installation Installation can be done locally, or on a Remote Installation Services (RIS) server. The procedure for each type of installation is fully described in Chapter 2. 1.1.1 Local Installation The TeMIP OSI AM Run-Time Kit can be installed directly on your local system. 1.1.2 RIS Installation The TeMIP OSI AM Run-Time Kit can also be installed from a RIS server area of a remote system. If you intend to install the TeMIP OSI AM Run-Time Kit on your system in this way, ensure the following: o A TeMIP OSI AM Run-Time Kit is installed on the RIS server. Preparing to Install the TeMIP OSI AM Run-Time Kit 1-1 o You know the name of the RIS server. o Your system is registered as a RIS client. For further details refer to the DIGITAL UNIX Guide to Remote Installation Services. 1.2 Installation Requirements The installation requirements for the TeMIP OSI AM Run-Time Kit are described in Section 1.2.1 to Section 1.2.8 and a checklist is provided in Appendix A. 1.2.1 Hardware and Software The minimum hardware and software requirements for the installation of the TeMIP OSI AM Run-Time Kit are as follows. Hardware You can install the TeMIP OSI AM Run-Time Kit on any AlphaGeneration machine. Software To install the TeMIP OSI AM Run-Time Kit you require the DIGITAL UNIX V4.0d operating system, running on an AlphaGeneration machine along with its Software Development Utilities and Internationalization Development Environment. TeMIP Version 3.2 should also be installed. You should not install the TeMIP OSI AM Run-Time Kit on a system configured as a TeMIP client director, because this type of director cannot run Access Modules. For more information, see the TeMIP Planning Guide. 1.2.2 Run-Time Kit Software Subsets Your kit should contain the following TeMIP OSI AM Run-Time Kit software subsets. If any of the subsets are missing, contact your DIGITAL representative: o TeMIP OSI AM Run-Time Kit V3.2 for DIGITAL UNIX (NOEOSIAMV320) o TeMIP OSI AM Run-Time Kit V3.2 Release Notes for DIGITAL UNIX (NOERELV320) o OSI Protocol Stack V3.02 for DIGITAL UNIX (CMACMV302). 1-2 Preparing to Install the TeMIP OSI AM Run-Time Kit 1.2.3 Time Required to Install Local installation of the TeMIP OSI AM Run-Time Kit takes approximately 15 minutes, depending on the system configuration. The Installation Verification Procedure (IVP) takes only an additional few seconds. Installation from a RIS server should take about the same time as a local installation, depending on the amount of traffic in the network. 1.2.4 Logging On You must have superuser privileges to install the TeMIP OSI AM Run-Time Kit software and register the license. You can set the current working directory to the top level (or root) directory using the following command: # cd / 1.2.5 Backing Up the System Disk DIGITAL strongly recommends that you back up your complete system disk or at least the /var and /usr partitions. Installation of the TeMIP OSI AM Run-Time Kit involves writing to these partitions. ________________________ Note ________________________ On DIGITAL UNIX, the /var partition is located at /usr /var. ______________________________________________________ 1.2.6 Checking the Required Software Subsets You require at least the following DIGITAL UNIX V4.0 and TeMIP Framework software subsets: o OSFBASE425, DIGITAL UNIX Base System Software o TFRBASEV320, TeMIP Framework Basic Management System o TFRSERVERV320, TeMIP Framework Server o TRFTNSCLRV320, TeMIP Framework Name Server Clerk o TFRLICV320, TeMIP Framework Licensing Sofware Preparing to Install the TeMIP OSI AM Run-Time Kit 1-3 To find the following information: o The additional required DIGITAL UNIX subsets o The required DECnet-Plus+ subsets. Refer to the TeMIP for DIGITAL UNIX Installation Guide, the TeMIP Director Configuration and Management Guide, and the DECcmi for DIGITAL UNIX Installation and Configuration Guide. To check that these subsets are present enter the following commands: # /etc/setld -i | grep OSF # /etc/setld -i | grep TFR The subsets installed are displayed along with any related patch names. If a subset is not present, the word installed is not displayed. 1.2.7 Disk Space Requirements The TeMIP OSI AM Run-Time Kit software subsets require different amounts of disk space as shown in Table 1-1. The values shown are approximate, since user-provided files are included when the Run-Time OSI AM is built. The first column shows the disk space required if you copy the subsets to a directory on your disk before installing them, and the other columns show the disk space required for the installed files. Table_1-1__Disk_Space_Requirements_________________________ Subset /usr Software_Subset_________________Copy______/kits_____/var___ OSI AM for DIGITAL UNIX 1800 KB 3200 KB OSI AM Release Notes for 50 KB 3200 KB DIGITAL UNIX OSI Protocol Stack (see note below)_____________________________________________________ ___________________ + Formerly known as DECnet/OSI. 1-4 Preparing to Install the TeMIP OSI AM Run-Time Kit ________________________ Note ________________________ For values concerning the OSI Protocol Stack see the DECcmi for DIGITAL UNIX Installation and Configuration Guide. ______________________________________________________ The installation procedure creates the following directories if they do not already exist: o /usr/kits/temip/NOE320 o /usr/var/kits/temip/temip_osi_am The link /var is defined on the directory /usr/var. The TeMIP OSI AM Run-Time Kit executable files must be in the /usr/kits/temip/NOE320 directory tree. However, you can mount a separate file system on /usr/kits/temip/NOE320 if you want to keep the executable files separate from the rest of the /usr file system. It is recommended that you have at least 10 MB of additional disk space available in the /usr/var/kits/temip /temip_osi_am partition for collecting data and reports. ___________________ Recommendation ___________________ To avoid problems with disk full situations, it is strongly recommended that you mount another partition on /usr/var. ______________________________________________________ Determine the amount of free disk space on your system as follows: o Using the appropriate column(s) in Table 1-1, total the values for the subsets you intend to load. o Determine the current amount of free space available to the directories /usr/kits and /var/kits/ using the following command: # df -k /usr/kits /var/kits This displays the total space and total free space on the disk partitions in use. Preparing to Install the TeMIP OSI AM Run-Time Kit 1-5 An example of the output with AdvFS and a separate fileset mounted on /usr/var is shown below. Filesystem 1024-blocks Used Avail Capacity Mounted on usr_domain#usr 1025424 948458 55344 94% /usr usr_domain#usr1 271848 246704 25144 91% /usr/var ________________________ Note ________________________ The usr_domain#usr fileset is mounted on the /usr directory mount point and the usr_domain#usr1 fileset is mounted on the the /usr/var directory mount point with the link /var defined to /usr/var. ______________________________________________________ If there is not enough free disk space to install the TeMIP OSI AM Run-Time Kit, you have to increase the disk space available for installation or change the operating system configuration to mount another file system on the /usr/kits or /var/kits/ directory mount point. Refer to the DIGITAL UNIX System Administration documentation for details of how to increase free disk space and mount file systems. 1.2.8 Using the Director User Account Before installing the TeMIP OSI AM Run-Time Kit, the TeMIP Framework must be configured using the temip_setup script. This script allows you to specify a Director User Account, which will be used at TeMIP OSI AM Run-Time Kit installation time. The Director User Account can have any user_id you want, but it must be a member of the same group as all other users of the TeMIP OSI AM Run-Time Kit software. For example, if all users of the TeMIP OSI AM Run-Time Kit belong to the group users, then the Director User Account must also be created as a member of the group users. The Director User Account will be the owner of the directories /usr/var/kits/temip/temip_osi_am and /usr/kits /temip/NOE320/temip_osi_am/bin. 1-6 Preparing to Install the TeMIP OSI AM Run-Time Kit For details of how to create a user account, refer to the DIGITAL UNIX System Administration documentation. ________________________ Note ________________________ If a version of TeMIP is already installed, the Director User Account has already been created. ______________________________________________________ 1.3 License Registration The TeMIP OSI Management Toolkit uses FLEXlm as license manager. The FLEXlm setup is part of the TeMIP Framework installation as described in the TeMIP for DIGITAL UNIX Installation Guide. In brief, the requirements are: o The TeMIP Licensing Software (TRCLICV320) subset must be installed. o The /usr/mcc/licenses/temip_licenses_setup script must be run to configure the license server or client. For more information, please consult the TeMIP for DIGITAL UNIX Installation Guide. The OSI features required to run the TeMIP OSI Management Toolkit are: ___________________________________________________________ Subset_____________Feature_________________________________ OSI AM TEMIP-OSI-AM-DV-OSF1 or TEMIP-OSI-AM-RT-OSF1 OSI Protocol TEMIP-OSI-AM-DV-OSF1 Stack or TEMIP-OSI-AM-RT-OSF1 Release_Notes______No_feature_required_____________________ To take the OSI features into account, proceed as follows: o Add the OSI features to the end of the /usr/mcc/licenses /licenses.dat file o Inform the FLEXlm license server or client of the new OSI features by entering the command: # /usr/mcc/lmreread -c usr/mcc/licenses/licenses.dat Preparing to Install the TeMIP OSI AM Run-Time Kit 1-7 1.4 Aborting the Installation and Recovering from Errors To abort the installation at any time press Ctrl/c. If you abort the installation, files created up to that point are not deleted. The directories and files created during the TeMIP OSI AM Run-Time Kit installation are listed in Appendix B. You can use the following command to delete a partially installed subset: # setld -d Subset_Name where Subset_Name represents the software subset you were installing. If an error occurs during the installation, the system displays an error message. The following list gives possible reasons for errors that can occur during the installation: o The operating system version is incorrect. o The prerequisite software version is incorrect. o The amount of available disk space is insufficient. o No software license was registered. For a description of error messages generated by these conditions and a description of corrective actions, refer to the DIGITAL UNIX Documentation on system messages, recovery procedures, and DIGITAL UNIX software installation. See also Appendix C. 1-8 Preparing to Install the TeMIP OSI AM Run-Time Kit 2 _________________________________________________________________ Installing the TeMIP OSI AM Run-Time Kit This chapter describes how to install the TeMIP OSI AM Run-Time Kit software subsets on your local system. The RIS server procedure assumes that you have created a server environment and are ready to install the TeMIP OSI AM Run-Time Kit. ________________________ Note ________________________ 1. If a subset is already installed you must deinstall it before installing a new version, see Section 3.3. 2. The RIS server procedure assumes that you have created a server environment and are ready to install the TeMIP OSI AM Run-Time Kit. ______________________________________________________ You can find more information in: o Starting the Installation Procedure Locally, Section 2.1 o System Configuration, Section 2.2 o Local Installation of the OSI Protocol Stack, Section 2.3 o Local Installation of the OSI AM Release Notes, Section 2.4 o Local Installation of the OSI AM, Section 2.5 o RIS Server Update, Section 2.6 Installing the TeMIP OSI AM Run-Time Kit 2-1 2.1 Starting the Installation Procedure Locally The way the installation procedure is started locally depends on the type of installation and the type of media, but in all cases you must must load the TeMIP OSI AM Run- Time Kit subsets while logged in as superuser. You can start the installation procedure in the following ways: From a System Directory If you are installing the TeMIP OSI AM Run-Time Kit from a system directory, enter the following command from the directory in which the files are located: # setld -l . From a TK50 Tape If you are installing the TeMIP OSI AM Run-Time Kit from a TK50 tape, include the device special name of the tape drive where the media is mounted. In this example the tape drive is known as rmt0h: # setld -l /dev/rmt0h From a RIS Server To install the TeMIP OSI AM Run-Time Kit subsets that reside in a /var/adm/ris distribution area of a remote system, include the name of the RIS server system where the TeMIP OSI AM Run-Time Kit subsets are located. For example, if you are loading the TeMIP OSI AM Run-Time Kit subsets from a RIS distribution area on the node bigsys, enter the following command: # setld -l bigsys: 2.2 System Configuration During the installation you are asked if you want to configure your system as part of the procedure or after the installation is complete. You are asked this question only for the OSI Access Module subset (NOEOSIAMV320). If you choose to configure your system after installation, a message is displayed that tells you how to do this. For further details refer to Section 3.1. 2-2 Installing the TeMIP OSI AM Run-Time Kit 2.3 Local Installation of the OSI Protocol Stack The OSI Protocol stack must be installed before any other subsets. Install the OSI Protocol stack as follows: o Start the installation procedure and select the OSI Protocol Stack option from the menu. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) OSI Protocol Stack 2) TeMIP OSI Mgt Toolkit Release Notes version V3.2 (level 1 rev A) 3) TeMIP OSI Access Module version V3.2 (level 1 rev A) Or you may choose one of the following options: 4) ALL of the above 5) CANCEL selections and redisplay menus 6) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 1 o Enter 1 and press . The installation procedure displays the subsets you have chosen and asks you to confirm your choice: You are installing the following subsets: OSI Protocol Stack Is this correct? (y/n): y Answer Y, then refer to the DECcmi for DIGITAL UNIX Installation and Configuration Guide. 2.4 Local Installation of the OSI Management Toolkit Release Notes The Release Notes contain the latest information about the product, plus any changes to the installation procedure that may have been made too late for inclusion in the Installation Guide. The Release Notes must be installed before continuing with the TeMIP OSI AM Run-Time Kit Installing the TeMIP OSI AM Run-Time Kit 2-3 installation. You can read the Release Notes online or print out a hardcopy. Install the OSI AM Release Notes as follows: o Start the installation procedure and select the OSI AM Release Notes option from the menu: The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) TeMIP OSI Mgt Toolkit Release Notes version V3.2 (level 1 rev A) 2) TeMIP OSI Access Module version V3.2 (level 1 rev A) Or you may choose one of the following options: 3) ALL of the above 4) CANCEL selections and redisplay menus 5) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 1 o Enter 1 and press . The installation procedure displays the subsets you have chosen and asks you to confirm your choice: You are installing the following optional subsets: TeMIP OSI Mgt Toolkit Release Notes version V3.2 (level 1 rev A) Is this correct? (y/n): y o If the information is correct, enter y and press , otherwise enter n, press and re- enter your choice. The procedure displays the result of a file system space check and copyright information before proceeding to install the subset. Checking file system space required to install specified subsets: File system space checked OK Copyright (c) Digital Equipment Corporation, 1998. All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. 2-4 Installing the TeMIP OSI AM Run-Time Kit The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. RESTRICTED RIGHTS LEGEND 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, as applicable. TeMIP OSI Mgt Toolkit Release Notes version V3.2 (level 1 rev A) Copying from . (disk) Verifying o The procedure configures the Release Notes Configuring "TeMIP OSI Mgt Toolkit Release Notes version V3.2 (level 1 rev A)" (NOERELV3.2) The Release Notes are installed in the directory: /usr /kits/temip/NOE320/help. The names of the files are: temip_osi_rel_notes.doc temip_osi_rel_notes.ps 2.5 Local Installation of the OSI AM Install the OSI AM locally as follows (in this example, temip is the Director User Account): o Start the installation procedure and select the OSI Access Module option from the menu. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) TeMIP OSI Access Module version V3.2 (level 1 rev A) Or you may choose one of the following options: Installing the TeMIP OSI AM Run-Time Kit 2-5 2) ALL of the above 3) CANCEL selections and redisplay menus 4) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 1 o Enter 1 and press . The installation procedure displays the subsets you have chosen and asks you to confirm your choice: You are installing the following subsets: TeMIP OSI Access Module version V3.2 (level 1 rev A) Is this correct? (y/n): y o If the information is correct, enter y and press , otherwise enter n, press , then re- enter your choice. The procedure displays the result of a file system space check and copyright information before proceeding to install the subset. Checking file system space required to install specified subsets: File system space checked OK Starting installation of NOE OSI Access Module V320. ...Software Copyright declaration... TeMIP OSI Access Module NOEOSIAMV3.2 will use the 'temip' user account with the following characteristics : 'temip' user id : 357 'temip' group : users Note that TeMIP OSI Access Module users should belong to the 'users' group in order to access the TeMIP OSI Access Module files. Note also that all DIGITAL UNIX users belonging to the 'users' group will have read and write access to the TeMIP OSI Access Module files. See TeMIP OSI Access Module Installation Guide for more information. Do you want to continue [y/n]? y There will be no more pre-installation questions. 2-6 Installing the TeMIP OSI AM Run-Time Kit TeMIP OSI Access Module version V3.2 (level 1 rev A) Copying from . (disk) Verifying o The procedure now configures the subset. Get the Director User account ... This procedure will now update the TeMIP Framework dictionary. Please wait while dictionary files are updated. Updating TeMIP Framework dictionary... Loading TeMIP OSIAM self management subclass mcc_msl - Info: Loading existing binary MIR database file "/usr/mcc/mcc_system/mcc_fdictionary.dat" mcc_msl - Info: Checking the Built-In Data Types file version "/usr/mcc/mcc_system/builtin_types.dat" mcc_msl - Info: Removing Entity-Class '1 3 12 2 1011 2 22 1 7 81' mcc_msl - Warning: OID (1 3 12 2 1011 2 22 1 7 81) does not exactly specify a MI R object. No Remove done. mcc_msl - Info: File /usr/mcc/mcc_system/mcc_fdictionary.dat is a link to /usr/m cc/en_US.ISO8859-1/mcc_fdictionary.dat mcc_msl - Info: /usr/mcc/en_US.ISO8859-1/mcc_fdictionary.dat file saved into /us r/mcc/en_US.ISO8859-1/mcc_fdictionary.dat.bak mcc_msl - Info: Generating Binary Output to "/usr/mcc/en_US.ISO8859-1/mcc_fdicti onary.dat" mcc_msl - Info: Loading existing binary MIR database file "/usr/mcc/mcc_system/mcc_fdictionary.dat" mcc_msl - Info: Checking the Built-In Data Types file version "/usr/mcc/mcc_system/builtin_types.dat" mcc_msl - Info: Compiling MSL file "temip_osi_am_mgmt_if.ms" mcc_msl - Info: Ending Compilation of MSL file (938 lines) mcc_msl - Info: File /usr/mcc/mcc_system/mcc_fdictionary.dat is a link to /usr/m cc/en_US.ISO8859-1/mcc_fdictionary.dat mcc_msl - Info: /usr/mcc/en_US.ISO8859-1/mcc_fdictionary.dat file saved into /us r/mcc/en_US.ISO8859-1/mcc_fdictionary.dat.bak mcc_msl - Info: Generating Binary Output to "/usr/mcc/en_US.ISO8859-1/mcc_fdicti onary.dat" Loading IVP classes ... Installing the TeMIP OSI AM Run-Time Kit 2-7 mcc_msl - Info: Loading existing binary MIR database file "/usr/mcc/mcc_system/mcc_fdictionary.dat" mcc_msl - Info: Checking the Built-In Data Types file version "/usr/mcc/mcc_system/builtin_types.dat" mcc_msl - Info: Removing Entity-Class '1 3 12 2 1011 2 22 1 1999' mcc_msl - Warning: OID (1 3 12 2 1011 2 22 1 1999) does not exactly specify a MI R object. No Remove done. mcc_msl - Info: File /usr/mcc/mcc_system/mcc_fdictionary.dat is a link to /usr/m cc/en_US.ISO8859-1/mcc_fdictionary.dat mcc_msl - Info: /usr/mcc/en_US.ISO8859-1/mcc_fdictionary.dat file saved into /us r/mcc/en_US.ISO8859-1/mcc_fdictionary.dat.bak mcc_msl - Info: Generating Binary Output to "/usr/mcc/en_US.ISO8859-1/mcc_fdicti onary.dat" mcc_msl -I/usr/kits/NOE310/temip_osi_am/files/ temip_osi_am_ivp.ms mcc_msl - Info: Loading existing binary MIR database file "/usr/mcc/mcc_system/mcc_fdictionary.dat" mcc_msl - Info: Checking the Built-In Data Types file version "/usr/mcc/mcc_system/builtin_types.dat" mcc_msl - Info: Compiling MSL file "temip_osi_am_ivp.ms" mcc_msl - Info: Ending Compilation of MSL file (487 lines) mcc_msl - Info: File /usr/mcc/mcc_system/mcc_fdictionary.dat is a link to /usr/m cc/en_US.ISO8859-1/mcc_fdictionary.dat mcc_msl - Info: /usr/mcc/en_US.ISO8859-1/mcc_fdictionary.dat file saved into /us r/mcc/en_US.ISO8859-1/mcc_fdictionary.dat.bak mcc_msl - Info: Generating Binary Output to "/usr/mcc/en_US.ISO8859-1/mcc_fdicti onary.dat" Loading User class mcc_msl -r"1 3 12 2 1011 2 22 1 26" mcc_msl - Info: Loading existing binary MIR database file "/usr/mcc/mcc_system/mcc_fdictionary.dat" mcc_msl - Info: Checking the Built-In Data Types file version "/usr/mcc/mcc_system/builtin_types.dat" 2-8 Installing the TeMIP OSI AM Run-Time Kit mcc_msl - Info: Removing Entity-Class '1 3 12 2 1011 2 22 1 26' mcc_msl - Warning: OID (1 3 12 2 1011 2 22 1 26) does not exactly specify a MIR object. No Remove done. mcc_msl - Info: File /usr/mcc/mcc_system/mcc_fdictionary.dat is a link to /usr/m cc/en_US.ISO8859-1/mcc_fdictionary.dat mcc_msl - Info: /usr/mcc/en_US.ISO8859-1/mcc_fdictionary.dat file saved into /us r/mcc/en_US.ISO8859-1/mcc_fdictionary.dat.bak mcc_msl - Info: Generating Binary Output to "/usr/mcc/en_US.ISO8859-1/mcc_fdicti onary.dat" mcc_msl -I/usr/kits/NOE310/temip_osi_am/files/ temip_osi_pm_system_efd_log.ms mcc_msl - Info: Loading existing binary MIR database file "/usr/mcc/mcc_system/mcc_fdictionary.dat" mcc_msl - Info: Checking the Built-In Data Types file version "/usr/mcc/mcc_system/builtin_types.dat" mcc_msl - Info: Compiling MSL file "temip_osi_pm_system_efd_log.ms" mcc_msl - Info: Ending Compilation of MSL file (2414 lines) mcc_msl - Info: File /usr/mcc/mcc_system/mcc_fdictionary.dat is a link to /usr/m cc/en_US.ISO8859-1/mcc_fdictionary.dat mcc_msl - Info: /usr/mcc/en_US.ISO8859-1/mcc_fdictionary.dat file saved into /us r/mcc/en_US.ISO8859-1/mcc_fdictionary.dat.bak mcc_msl - Info: Generating Binary Output to "/usr/mcc/en_US.ISO8859-1/mcc_fdicti onary.dat" Building the parse table ... This procedure will now enroll the OSI Access Module. Please wait until enrollment completion. Enrolling temip_osi_am ... Successful enrolling This procedure will now create the OSI Access Module application. Please wait until creation completion. Director is running Create and Start the OSI_AM application ... Successful creation Installing the TeMIP OSI AM Run-Time Kit 2-9 NOE OSI Access Module V3.2 installation complete. Configuring "TeMIP OSI Run-time Access Module version V3.2 Level 1 Rev A" (NOEOSIAMV3.2) The next question asks you to confirm that you are ready to configure your system to run NOE OSI Access Module V3.2 at this time. If you answer 'no' to this question, you will be told how you can configure NOE OSI Access Module V3.2 at a later time. Do you want to configure your system to run NOE OSI Access Module [y/n]? y Starting NOE OSI Access Module V3.2 configuration. Get the Director User account ... There will be no more configuration questions. NOE OSI Access Module V3.2 Configuration Procedure complete. o You are now asked to confirm that you are ready to run the IVP. If you answer 'no' to this question, you will be told how you can run the IVP for NOE OSI AM V320 at a later time. Would you like to run the NOEOSIAM320 IVP? (y/n) [y] n o Press to accept the default (y), or enter n and press to run the IVP later. 2.6 RIS Server Update You can install the TeMIP OSI AM Run-Time Kit subsets in an environment controlled by Remote Installation Services by using the DIGITAL UNIX RIS Utility. The installation procedure described in this section uses an existing area named ris0.mips as an example. Before starting the installation, note the device special name of the distribution device. To install the TeMIP OSI AM Run-Time Kit, complete the following tasks: o Mount the media on the distribution device. o Invoke the RIS Utility by entering the following command: # /usr/sbin/ris 2-10 Installing the TeMIP OSI AM Run-Time Kit The RIS Utility Menu is displayed: Choices without key letters are not available. a) ADD a client d) DELETE software products i) INSTALL software products ) LIST registered clients ) MODIFY a client ) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: o Enter i and press . The RIS Utility Software Installation Menu is displayed: RIS Software Installation Menu: 1) Install software into a new area 2) Add software into an existing area 3) Return to previous menu Enter your choice: o Enter 2 and press . If you select option 1, the RIS Utility creates the new area automatically. You have chosen to add a product to an existing environment. The existing environment is /var/adm/ris/ris0.alpha. Enter the device special file name or the path of the directory where the software is located (for example, /dev/rmt0h): o Enter the directory name and press . An options menu is displayed. Choose one of the following options: 1) Extract software from /usr/users/osiam/kit/install 2) Create symbolic link to /usr/users/osiam/kit/install Enter your choice: Installing the TeMIP OSI AM Run-Time Kit 2-11 o Enter 2 and press . The TeMIP OSI AM Run-Time Kit OSI AM is now added as an installation choice for RIS clients. The RIS Utility menu reappears and asks you to enter your choice: ** RIS Utility Main Menu *** Choices without key letters are not available. a) ADD a client d) DELETE software products i) INSTALL software products ) LIST registered clients ) MODIFY a client ) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: o If you have nothing more to install, enter x and press . 2-12 Installing the TeMIP OSI AM Run-Time Kit 3 _________________________________________________________________ After Installing the TeMIP OSI AM Run-Time Kit This chapter explains how to configure your system and how to run the Installation Verification Procedure (IVP), and delete installed subsets. You can find more information in: o Configuring your System for the OSI AM, Section 3.1 o Verifying the Run-Time Kit Installation, Section 3.2 o Deleting the TeMIP OSI AM Run-Time Kit from your System, Section 3.3 3.1 Configuring your System for the OSI AM If you did not configure your system during installation, you can carry out this operation as follows: o Start the configuration by entering the following command: # setld -c NOEOSIAMV320 config The configuration procedure displays the following: Configuring NOEOSIAMV320 The next question asks you to confirm that you are ready to configure your system to run NOE OSI Access Module V320 at this time. If you answer 'no' to this question, you will be told how you can configure NOE OSI Access Module V320 at a later time. Do you want to configure your system to run NOE OSI Access Module [y/n]? After Installing the TeMIP OSI AM Run-Time Kit 3-1 o Enter y and press to continue: Starting NOE OSI Access Module V320 configuration. There will be no more configuration questions. NOE OSI Access Module V320 Configuration Procedure complete. 3.2 Verifying the Run-Time Kit Installation To verify that the OSI AM has been correctly installed and configured, the installation procedure runs the TeMIP OSI AM Run-Time Kit OSI AM IVP (Installation Verification Program). 3.2.1 IVP Overview The IVP program performs a comprehensive verification of the OSI AM installation. Not only does it verify the license authorization and installed files, but also validates the full configuration of the system used by the OSI AM. The IVP can be run over OSI or TCP/IP. The user is asked to select the required transport driver the beginning of the IVP procedure. The extent of verification carried out by the IVP makes this tool extremely useful to system support personnel, who can use it to locate configuration errors. Support Software The TeMIP OSI AM Run-Time Kit OSI AM relies on the services provided by a number of standard DIGITAL communication products, including: o DIGITAL UNIX o TeMIP Framework o DECcmi providing a dual OSI and/or RFC1006 (OSI over TCP/IP) protocol stack. DECnet-Plus is not required if you choose RFC1006 mode. In order to use the support software products the TeMIP OSI AM requires that: o Licenses are active 3-2 After Installing the TeMIP OSI AM Run-Time Kit o Symbols, initialization files, and paths are correctly set o The lower layer processes (DECnet-Plus (optional)) are started and usable. If verification fails due to any of the prerequisites quoted above not being correct, the IVP gives the maximum of information about the problem found. In practice, the IVP uses each item in a realistic way to ensure that the system is correctly configured. IVP Procedure The IVP will try to start an IVP TeMIP OSI AM Client and manage an agent IVP, using the following procedure: 1. Set the necessary symbols if not done 2. Get and use default configuration files if not present 3. Ask the user to select either OSI or TCP/IP transport to run the IVP 4. Create the OSI AM application if not already done (by calling temip_osi_setup) 5. Start the support processes if not already active 6. Send management requests through the Framework Command Line interface 3.2.2 Symbols and Files Used by the IVP The following symbols and file names are used by the IVP: o Symbols needed by DECcmi: - OSIROOT - XDSROOT - CMISE_INBOUND. o Path needed: - /usr/kits/temip/NOE320/temip_osi_am/bin (to start the TeMIP OSI AM Run-Time Kit) - /usr/bin (to call cmi_srv) - /usr/etc (to call cmi_startup). After Installing the TeMIP OSI AM Run-Time Kit 3-3 o Files needed by DECcmi: - /var/cmip/conf/cmi_profile.txt - /var/cmip/conf/xom.ini - /var/cmip/conf/xom.oid - /etc/nsaps. ________________________ Note ________________________ xmp.ini is used by the DECcmi stack, but only for the agent IVP. ______________________________________________________ o Files that may be modified during the execution of the IVP: - /var/kits/temip/temip_osi_am/dOSIAM_d.dat - /var/kits/temip/temip_osi_am/dOSIAM_d.idx - /var/kits/temip/temip_osi_am/dOSIAM_d.lck - /var/kits/temip/temip_osi_am/iOSIAM_i.dat - /var/kits/temip/temip_osi_am/iOSIAM_i.idx - /var/kits/temip/temip_osi_am/iOSIAM_i.lck - /var/kits/temip/temip_osi_am/temip_osi_am_ configuration.dat. 3.2.3 Names Reserved for the IVP Certain names are reserved for the TeMIP OSI AM Run-Time Kit OSI AM IVP, and if used for other purposes may cause the IVP to fail. o DECnet-Plus template name: - osiamivp o NSAP name (/etc/nsaps): - NOEIVP o TeMIP Framework agent names: - agentivp1 - agentivp2 3-4 After Installing the TeMIP OSI AM Run-Time Kit o Process file names: - temip_osi_am_agent_ivp (process name for the agent) - temip_osi_am_ivp (process name for the client) - temip_osi_am_ivp.dat (file name for the TeMIP OSI AM Run-Time Kit OSI AM Dictionary) o Log files created during the IVP: - /tmp/temip_osi_am_ivp.result - /tmp/temip_osi_am_ivp.remove - /tmp/temip_osi_am_ivp_start 3.2.4 Example Log of a Successful IVP The following is an example log of a successful execution of the TeMIP OSI AM Run-Time Kit OSI AM IVP. The two warnings shown in this example appear because the root account has not set the DECcmi environment variables. The IVP uses the default values and sets them. It is also important to note that the user root owns the same TeMIP Framework environment as the user temip. This the normal default case; otherwise the TeMIP Framework dictionaries may be different and the installation incorrect, even if the IVP is successful. # setld -v NOEOSIAMV320 OSI Access Module (NOEOSIAMV320) .... Software Copyright Declaration .... TeMIP OSI Access Module (level 1 rev C) (NOEOSIAMT320) TeMIP OSIAM Server is not running (temip_osi_server) Verifying the prerequisite files -------------------------------- Files verified. Verifying the prerequisite Symbols ---------------------------------- Include /usr/kits/NOE320/temip_osi_am/bin in PATH Include /usr/bin in PATH, to call cmi_srv Include /usr/etc in PATH, to call cmi_startup After Installing the TeMIP OSI AM Run-Time Kit 3-5 Do you want to run IVP over TCP/IP or OSI transport ? Select: [T] for TCP/IP [O] for OSI O Verifying the running processes ------------------------------- DECnet is started TeMIP OSIAM Client is not running (temip_osi_am) Director is not running (Framework_Watchdog) Verifying values used by DECnet/OSI ----------------------------------- OSI Transport state = On Creating osiamivp template ... Enable DECnet OSI transport NSAP correctly initialized. Verifying the values used by DECcmi ----------------------------------- Network address NOEIVP re-defined ... WARNING: files : /usr/var/cmip/conf/xom.ini /usr/var/cmip/conf/cmi_profile.txt will be customized according to selected transport using cmi_setup. These files are saved to: /usr/var/cmip/conf/xom.ini_save.ivp /usr/var/cmip/conf/cmi_profile.txt_save.ivp They are restored at the end of the IVP. If the IVP is stopped abruptly (CTRL'C) be careful to restore your files. Configure cmi_srv to full OSI using cmi_setup -o Starting DECcmi server Initializing shared memory Loading cmi_srv process DECcmi - Control and Management Utility [V3.01] ----------------------------------------------- 3-6 After Installing the TeMIP OSI AM Run-Time Kit CMU [0079] 1) Process cmi_srv started CMU [0083] 2) MBX cmi_srv opened CMU [0061] 3) Sending ADM_REQ to cmi_srv CMU [0016] Command mode is DEFAULT Prefix CMU [0001] *** Received ADM_CNF from TASK cmi_srv CMU [0065] Sending ADM_CAU to cmi_srv CMU [0035] waiting for ADM_CAUCF from process cmi_srv CMU [0004] *** Received ADM_CAUCF from TASK cmi_srv CMU [0042] Command mode is EXPLICIT Prefix Starting cmi_srv process ... ********************** Bind OK **************************** ********************** Bind OK **************************** Set cmi_srv with I125,I126,CI127,CI128 presentation address ... Verifying values used by TeMIP OSIAM server ------------------------------------------- temip_osi_am_configuration.dat is OK Start the necessary processes ----------------------------- Executing /usr/kits/NOE320/temip_osi_am/bin/temip_osi_setup Director is not running Start Director executing temip_start ... Director is running Remove OSI AM application from Dispatch Table ... OSI AM application successfully removed Enroll the OSI AM Client ... OSI AM Client /usr/mcc/mmexe/temip_osi_am sucessfully enrolled Application osi_am already exists Application osi_am already started OSI AM Set Up has been successfully executed Successful completion of temip_osi_setup /usr/mcc/mmexe/temip_osi_am Client is now running ... After Installing the TeMIP OSI AM Run-Time Kit 3-7 Starting temip_osi_server ... TeMIP OSIAM Server started Get the Director User account ... Starting the agents ... Testing OSIAM server ... Stopping temip_osi_am_agent_ivp ... Stopping DECcmi server ... Stopping temip_osi_server ... Stopping temip_osi_am client ... The TeMIP Framework OSI_AM application is not removed, but only stopped Stopping TeMIP Framework Director (temip_stop) ... Restoring /usr/var/cmip/conf/cmi_profile.txt and /usr/var/cmip/conf/xom.ini from saved files. +-------------------------------------------------+ | TeMIP OSIAM IVP has been successfully executed! | +-------------------------------------------------+ 3.3 Deleting the TeMIP OSI AM Run-Time Kit from Your System If you need to remove a version of the TeMIP OSI AM Run- Time Kit from your system, delete each subset that has been previously installed. To delete subsets: 1. Log in as superuser 2. Enter the following command: setld -i | grep "NOE" 3. Look for the word "installed" in the listing produced, and then delete the installed subsets. For example: setld -d NOERELV320 3-8 After Installing the TeMIP OSI AM Run-Time Kit The following information is displayed: No particular configuration was necessary on your system to run NOE OSIAM Release Notes V320. Deleting "OSI AM Release Notes" (NOERELV320). setld -d NOEOSIAMV320 This procedure will now update the TeMIP Framework dictionary. Please wait while dictionary files are updated. Updating TeMIP Framework dictionary... Deleting classes ... delete class mcc subclass osi_am mirc - ... mirc - ... mirc - ... mirc - ... Deleting classes ... delete /usr/kits/temip/NOE320/temip_osi_am/files/osi_am_myentity.make mcc_msl ... mirc - ... mirc - ... mirc - ... mirc - ... NOE OSI Access Module V320 Deletion Procedure complete. NOE OSI Access Module deletion terminated at Thu Jul 7 09:51:32 MET DST 1994 Saving temip_osi_am_configuration.dat as temip_osi_am_configuration.dat.save in /tmp Deleting "OSI Access Module" (NOEOSIAMV320). _______________________ Warning _______________________ The temip_osi_am_configuration.dat file is saved in /tmp with the .save extension before being removed from the /var/kits/temip/temip_osi_am directory. Remember that the directory /tmp will be removed in the event of a reboot. ______________________________________________________ After Installing the TeMIP OSI AM Run-Time Kit 3-9 3-10 After Installing the TeMIP OSI AM Run-Time Kit A _________________________________________________________________ Pre-Installation Checklist This appendix summarizes the various operations required before installation of the TeMIP OSI AM Run-Time Kit. After you have completed each task, use the box at the left of the page to check it off the list. You can find more information in: o Local Installation, Section A.1 o Installation on a RIS Server, Section A.2 o Installation from a RIS Server, Section A.3 A.1 Local Installation Before starting a local installation, do the following: < Check that the distribution kit is complete. < Ensure that you have an AlphaGeneration machine with the correct version of the DIGITAL UNIX operating system installed and running. < Back up the system disk. < Ensure that TeMIP is installed and running. < Ensure that you have sufficient disk space. < Create the Director User Account if it does not already exist. Pre-Installation Checklist A-1 < Load the distribution media. < Register the license for the product. < Install and read the online Release Notes. A-2 Pre-Installation Checklist A.2 Installation on a RIS Server Before starting installation on a RIS server, do the following in addition to the local installation checks: < Note the device special name of the distribution device. A.3 Installation from a RIS Server Before starting installation from a RIS server, do the following: < Ensure that TeMIP OSI AM Run-Time Kit is installed and running on the RIS server. < Determine the name of the RIS server. < Ensure that your system is registered as a RIS client. Pre-Installation Checklist A-3 B _________________________________________________________________ Files Installed on your System The following is a complete list of the files installed when you install the TeMIP OSI AM Toolkit V3.2. For each subset the list gives the permissions, the owner and the file names. You can find more information in: o OSI Management Toolkit Release Notes Subset, Section B.1 o OSI AM Subset, Section B.2. B.1 OSI Management Toolkit Release Notes Subset Table B-1 shows the Release Notes files placed in the /usr /kits/temip/NOE320/help directory when the OSI Management Toolkit Release Notes are installed: Table_B-1_Directory_/usr/kits/temip/NOE320/help____________ Permissions__Owner____Files________________________________ -rw-r-r- root temip_osi_rel_notes.ps -rw-r-r-_____root_____temip_osi_rel_notes.doc______________ B.2 OSI AM Subset Table B-2 shows the directories created under the /usr/kits /temip/NOE320 directory: Files Installed on your System B-1 Table_B-2__Directory_/usr/kits/temip/NOE320________________ Permissions__Owner____Files________________________________ drwxr-xr-x root help drwxr-xr-x___root_____temip_osi_am_________________________ Table B-3 shows the directories created under the /usr/kits /temip/NOE320/temip_osi_am directory: Table_B-3__Directory_/usr/kits/temip/NOE320/temip_osi_am___ Permissions__Owner____Files________________________________ drwxr-xr-x root bin drwxr-xr-x root examples drwxr-xr-x___root_____files________________________________ Table B-4 shows the files placed in the /usr/kits/temip /NOE320/temip_osi_am/bin directory: Table_B-4__Directory_/usr/kits/temip/NOE320/temip_osi_am/bin Permissions__Owner____Files________________________________ -rwxr-xr-x root temip_osi_am -rwxr-r- temip temip_osi_server -rwxr-r- temip temip_osi_shutdown -rwxr-r- temip temip_osi_startup -rwxr-r-_____temip____temip_osi_setup______________________ Table B-5 shows the files placed in the /usr/kits/temip /NOE320/temip_osi_am/examples directory: Table B-5 Directory /usr/kits/temip/NOE320/temip_osi_am ___________/examples_______________________________________ Permissions__Owner____Files________________________________ -rw-r-r- root temip_osi_am_configuration.dat -rw-r-r- root xom.ini -rw-r-r-_____root_____xom.oid______________________________ B-2 Files Installed on your System Table B-6 shows the files placed in the /usr/kits/temip /NOE320/temip_osi_am/files directory: Table B-6 Directory /usr/kits/temip/NOE320/temip_osi_am __________/files___________________________________________ Permissions__Owner____Files________________________________ -rw-r-r- root mcc_osiamivp_icon.dat -rw-r-r- root temip_osi_am_catalog.cat -rw-r-r- root all user-generated .ms files -rw-r-r- root all user-generated .dat files -rw-r-r-_____root_____all_user-generated_.make_files_______ Table B-7 shows the files placed in the /var/kits/temip /temip_osi_am directory: Table_B-7_Directory_/var/kits/temip/temip_osi_am___________ Permissions__Owner____Files________________________________ drwxr-xr-x temip error drwxr-xr-x temip install drwxr-xr-x temip ivp -rw-r-r- temip all user-generated .dat files -rw-r-r- temip temip_osi_am_configuration.dat drwxr-xr-x___temip____trace________________________________ Table B-8 shows the files placed in the /var/kits/temip /temip_osi_am/install directory. Table_B-8_Directory_/var/kits/temip/temip_osi_am/install___ Permissions__Owner____Files________________________________ -rw-r-r- temip install.NOEOSIAMV320 -rw-r-r-_____temip____install.NOERELV320___________________ Files Installed on your System B-3 B.2.1 OSI AM Subset Links No links are provided. B-4 Files Installed on your System C _________________________________________________________________ Recovering from Errors This appendix provides information to help you deal with failures or errors that might occur during product installation or product use. You can find more information in: o Failures During Product Installation, Section C.1 o Failures During Product Use, Section C.2 C.1 Failures During Product Installation If errors occur during the installation, the system displays failure messages. For example, if the installation fails due to insufficient disk space, the following message appears: The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) OSI Protocol Stack 2) TeMIP OSI Mgt Toolkit Release Notes version V3.2 (level 1 rev A) 3) TeMIP OSI Access Module version V3.2 (level 1 rev A) Or you may choose one of the following options: 4) ALL of the above 5) CANCEL selections and redisplay menus 6) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 2 /usr: write failed, file system is full Recovering from Errors C-1 Errors can occur during the installation, if any of the following conditions exist: o The operating system version is incorrect. o The prerequisite software version is incorrect. o There is insufficient disk space. o A license is not correctly registered. For descriptions of error messages generated by these conditions, refer to the DIGITAL UNIX Documentation on system messages, recovery procedures, and DIGITAL UNIX software installation. C.2 Failures During Product Use If an error occurs while the TeMIP OSI AM Run-Time Kit is in use and you believe the error is caused by a problem with the product, take one of the following actions: o If you have a Software Product Services Support Agreement, contact your Customer Support Center (CSC) by telephone or by using the electronic means provided with your support agreement (such as DSNlink). The CSC provides telephone support for high-level advisory and remedial assistance. When you initially contact the CSC, indicate the following: - The name and version number of the operating system you are using - The version number of the TeMIP OSI AM Run-Time Kit you are using - The hardware system you are using (such as a model number) - A brief description of the problem (one sentence if possible) - How critical the problem is. o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). C-2 Recovering from Errors o If you do not have any type of software services support agreement and you purchased the TeMIP OSI AM Run-Time Kit within the past year, you can submit an SPR if you think the problem is caused by a software error. When you submit an SPR, 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 the TeMIP OSI AM Run-Time Kit being used. Demonstrate the problem with specific examples. 2. Reduce the problem to as small a size as possible. 3. Remember to include listings of any command files, INCLUDE files, or relevant data files, and so on. 4. Report only one problem per SPR. This will facilitate a faster response. 5. Mail the SPR package to DIGITAL. If the problem is related to the TeMIP OSI AM Run-Time Kit documentation, you can report the problem to the CSC (if you have a Software Product Services Support Agreement and the problem is severe). Recovering from Errors C-3 _________________________________________________________________ Index A______________________________ H______________________________ Aborting the installation, 1-8 Hardware requirements, 1-2 After installing TeMIP OSI AM Run-Time Kit, 3-1 to 3-10 I______________________________ B Installation _______________________________ aborting, 1-8 Backing up the system disk, checklist, A-1 1-3 local, 2-5 of Release Notes, 2-3 C______________________________ of TeMIP OSI AM Run-Time Kit, Checklist 2-1 to 2-12 See Installation checklist on a RIS, 2-10 Configuring the system, 2-2, recovering from errors, 1-8 3-1 starting the, locally, 2-2 Creating a TeMIP Director User Installation Verification Account, 1-6 Procedure, 3-2 Installing D from a RIS server, 2-2 _______________________________ from a system directory, 2-2 Deleting TeMIP OSI AM Run-Time from a TK50 tape, 2-2 Kit subsets, 3-8 the RIS Utility, 2-10 Director User Account, 1-6, IVP (Installation Verification 2-5 Program), 3-2 Disk space, 1-4 L______________________________ F______________________________ License Files installed, B-1 registration, 1-7 Release Notes Subset, B-1 List of files installed, B-1 TeMIP OSI AM Subset, B-1 Local installation, 2-5 Index-1 Logging on, 1-3 Starting the local installation procedure, M______________________________ 2-2 Menu Subsets, 3-1 RIS Utility, 2-11 checking, 1-3 RIS Utility Software choosing, 2-5 Installation, 2-11 choosing OSI Protocol Stack, 2-3 P System backup, 1-3 _______________________________ System configuration, 2-2, 3-1 Preparing to install TeMIP OSI AM Run-Time Kit, 1-1 to 1-8 T______________________________ R TeMIP Director User Account, _______________________________ 1-6 Recovering from installation Time requirements, 1-3 errors, 1-8 Release Notes directory, 2-5 files installed, 2-5 installing, 2-3 Requirements disk space, 1-4 hardware, 1-2 license registration, 1-7 operating system, 1-2 software, 1-2 software subsets, 1-3 subsets, 1-2 system backup, 1-3 TeMIP, 1-2 time, 1-3 RIS installation, 2-10 Utility, 2-10 Utility Menu, 2-11 Utility Software Installation Menu, 2-11 S______________________________ Software requirements, 1-2 Index-2