DEComni_API_for_Digital_UNIX________________________ Installation Guide Order Number: AA-Q0NZC-TE March 1997 This manual describes the prerequisites and procedures for installing the DEComni Application Programming Interface (API) software on Digital UNIX platforms. Revision/Update: This is a new document for the current release. Operating System: Digital UNIX Version 4.0 Software Version: DEComni API Version 3.1 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ First printing, June 1994 Revised, February 1996 Revised, March 1997 © Digital Equipment Corporation 1997. Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, BASEstar, DEC, DECmessageQ, DECnet, DECnet-DOS, DECosap, DEComni, DIGITAL, DIGITAL UNIX, FMS, LN03, MicroVAX, NAS, OpenVMS, OpenVMS Alpha, PATHWORKS, PDAS, Rdb/VMS, ReGIS, ThinWire, TK, ULTRIX, VAX, VAXcluster, VAX COBOL, VAX FORTRAN, VAX Pascal, VAX RMS, VMS/ULTRIX Connection, VT, and the DIGITAL logo. The following are third-party trademarks: Excel is a registered trademark of Microsoft Corporation. IBM is a registered trademark of IBM Corp. INGRES is a trademark of Ingres Corp. LOTUS 1-2-3 is a registered trademark of Lotus Development Corp. MS, Microsoft, and MS-DOS are registered trademarks of Microsoft Corporation. Network File System and NFS are trademarks of Sun Microsystems, Inc. ORACLE is a trademark of Oracle Corp. PostScript is a registered trademark of Adobe Systems Incorporated. SINEC AP, SINEC H1, SICOMP, Simatic, SINEC, SINUMERIK and SIROTEC are registered trademarks of Siemens, AG. UNIX is a registered trademark licensed exclusively by X /Open Company Ltd. Windows, Windows NT and Windows 95 are trademarks of Microsoft Corporation. Wonderware InTouch is a registered trademark of Wonderware Corporation. X/Open is a registered trademark of the X/Open Company Limited This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Pre-installation Requirements 1.1 System Hardware Requirements..................... 1-2 1.2 System Software Requirements..................... 1-2 1.3 System Software Subset Requirements.............. 1-2 1.4 Determining Where to Load the Reference Page Subsets.......................................... 1-3 1.5 License Registration............................. 1-4 1.6 Installation Time................................ 1-5 1.7 Installation Privileges.......................... 1-5 1.8 Required Disk Space.............................. 1-5 1.9 Determining Disk Space Availability.............. 1-6 1.10 Increasing Available Disk Space.................. 1-8 1.11 Backing Up the System Disk....................... 1-8 2 Installing DEComni API on Digital UNIX Systems 2.1 Installation Considerations...................... 2-1 2.1.1 Installation Error Messages ................... 2-1 2.1.2 Stopping the Installation ..................... 2-2 2.1.3 Accessing the Release Notes ................... 2-2 2.2 Installation Procedure........................... 2-2 2.2.1 Starting the Installation ..................... 2-2 2.2.2 Selecting the Installation Subsets ............ 2-3 2.3 Installation Error Messages...................... 2-5 iii 3 Post-installation Considerations 3.1 Running the Installation Verification Procedure.. 3-1 3.2 DEComni Startup Script........................... 3-1 3.3 Setting Up a DEComni User Account................ 3-2 3.4 Example Programs................................. 3-2 3.5 Deinstalling DEComni............................. 3-2 3.6 Reporting Software Problems...................... 3-2 A Dialogue Samples A.1 Installation Dialogue Sample..................... A-1 B Files Added During Installation B.1 Application Program Interface Files.............. B-1 B.2 Reference Page Files............................. B-5 Index iv _________________________________________________________________ Preface This document covers the installation of the DEComni API (Application Programming Interface) software on a Digital UNIX system. Keep this document with your distribution kit. You may need it to install maintenance updates or to reinstall the DEComni API software. For more information about DEComni API features and functions, refer to the DEComni API Software Product Description (SPD) in your software distribution kit. Intended Audience This document is for system and network managers and Digital personnel who must plan or perform an installation of the DEComni API software on a Digital UNIX system. Document Structure This manual is organized as follows: o Chapter 1, Pre-installation Requirements, describes the hardware and software requirements that must be met before you can install the DEComni API software. o Chapter 2, Installing DEComni API on Digital UNIX Systems, describes the system environment required to install and run the DEComni API software. This chapter also provides the DEComni API installation procedures and guidelines. o Chapter 3, Post-installation Considerations, describes how to start or stop the DEComni API process and access the release notes after the installation.The chapter also provides more information about the installed product. v o Appendix A, Dialogue Samples, provides a sample installation dialogue. o Appendix B, Files Added During Installation, lists directories and files added to the system during the installation process. Associated DEComni Documents The following documents provide detailed information about using the DEComni API system: o DEComni API and DEComni MMS User Guide o Guide to Using Omni Directory Services Related ISO/IEC Documents The following documents provide information about the ISO /IEC standard Manufacturing Message Specification (MMS): Industrial Automation Systems - Manufacturing Message Specification Service Definition, ISO/IEC 9506-1 Industrial Automation Systems - Manufacturing Message Specification Protocol Specification, ISO/IEC 9506-2 Related System Documents See your Digital UNIX system documentation for information about software installation and licensing procedures. Conventions This manual uses the following conventions: ___________________________________________________________ Convention_________Meaning_________________________________ DEComni The term "DEComni" refers to the DEComni API product or to functions and services provided by the DEComni API software. Digital UNIX The term " Digital UNIX" refers to the Digital UNIX product or to operations and functions performed by the Digital UNIX operating system. vi ___________________________________________________________ Convention_________Meaning_________________________________ # The pound sign is the default Digital UNIX superuser prompt. NODE> The Digital UNIX user prompt is the system name followed by a right angle bracket (>). UPPERCASE, The system differentiates between lowercase uppercase and lowercase characters. Literal strings that appear in descriptions, examples, or command syntax must be entered exactly as shown. Boldface Type This bold typeface emphasizes user input to system prompts. system output This typeface indicates system output in interactive examples. In Digital UNIX descriptions, it also specifies the exact name of a command, option, partition, pathname, directory, or file. setld(8) Cross-references to online reference pages include the section number in parentheses. For example, setld(8) indicates that the information can be found on the setld command in section 8 of the reference pages. / / Slash marks are part of the directory specification /directory_name/ on Digital UNIX systems. / Indicates to hold down the key while you press another key, indicated here by . n A lowercase italic n indicates the generic use of a number. x A lowercase italic x indicates the generic use of a letter. italic type Italic type emphasizes important or unique information or the complete titles of documents. vii ___________________________________________________________ Convention_________Meaning_________________________________ . Vertical ellipses (dots) in examples . represent data that has been omitted for .__________________clarity.________________________________ viii 1 _________________________________________________________________ Pre-installation Requirements This chapter lists the minimum system hardware and software environment required to install and run the DEComni API software on Digital UNIX. Verify that the installation kit contains all items listed on the Bill of Materials (BOM). Contact your Digital representative if there are any problems or missing items. The software distribution kit generally contains the following items: o Installation media (CD-ROM) containing the DEComni API installation software o Product Authorization Key (PAK) for registering the DEComni API software o DEComni API installation and user documentation o Online release notes are included on the installation media. Directions for accessing the release notes are provided in Section 2.1.3. ________________________ Note ________________________ Digital recommends that you read the release notes before installing or running the DEComni API software. ______________________________________________________ The DEComni installation process creates DEComni API file systems that are subordinate to the /usr/opt and /usr/var /opt directories, then loads the DEComni API subsets. To perform the procedures described in this chapter: 1. Log in as superuser (login name root). 1-1 2. Ensure that you are at the root directory (/) by entering the command: # cd / 1.1 System Hardware Requirements You require a minimum hardware configuration to perform the installation as described in the DEComni Software Product Description (SPD). This minimum configuration is as follows: o A supported Alpha processor (see the DEComni API Software Product Description for details) o An online terminal with access to the system. Refer to the DEComni API SPD to determine whether there are additional hardware requirements that apply to your application. 1.2 System Software Requirements Your system requires the following minimum software versions: o Mandatory: - Digital UNIX Version 4.0 or 4.0 o Optional: - DECnet OSI for Digital UNIX Version 4.0 or 4.0 - DECwindows Motif Version 1.2-(needed if you want to run the OmniView application) Pre-requisite software and software versions may change. Refer to the current DEComni API Software Product Description (SPD) for the latest pre-requisite information. 1.3 System Software Subset Requirements Your system requires that the following subsets be loaded from the pre-requisite system software: OSFBASE320 Always required or OSFBASE400 OSFDCMT320 Only required to install the online or OSFDCMT400 reference pages. 1-2 Enter the following commands to determine whether the system subsets are loaded: # /user/sbin/setld -i | grep OSFBASE # /user/sbin/setld -i | grep OSFDCMT The displayed rows list the name of the relevant subset and any patches. The word "installed" appears after the subset identifier if the subset is loaded. If the word "installed" does not appear in the row (the second column is blank), the subset or patch is not loaded and you must load the missing software before installing the DEComni API software. 1.4 Determining Where to Load the Reference Page Subsets The DEComni API subsets are named as follows: o DEComni Application Program Interface (API) - DOUBASE310 o DEComni API Reference Pages - DOUMAN310 DEComni API provides a common device interconnect application program interface that is based on the MMS model. Refer to the DEComni Software Product Description (SPD) for more information about DEComni API features and functions. You can load the DEComni Reference Pages subset only if the Digital UNIX reference page subset is already loaded on your system. If users on the system where DEComni is being installed plan to use reference pages that are nfs mounted from another system: 1. Load the DEComni API reference pages on the other system (rather than on the system where you will be installing the DEComni API software). 2. Do not request the reference page subset during the DEComni API installation procedure. 3. After the installation is complete, log in on the system where the Digital UNIX reference pages are installed and load only the DEComni API reference pages subset on that system. 1-3 See the setld(8) reference page for information about loading specific subsets. 1.5 License Registration You must register the Product Authorization Key (PAK) in the License Database (LDB) using the License Management Facility (LMF). The PAK is shipped with the kit if you order the license and media together. Otherwise, it is shipped separately to the location specified on your license order. If you are installing DEComni API as an update on a node that is already licensed for the software, you have already completed the PAK registration requirements. ________________________ Note ________________________ PAK registration is required only for nodes that will actually run the DEComni API software. If you are installing DEComni API on a node that will only function as a server, it is not necessary to register the PAK. ______________________________________________________ To register a new PAK in the LDB, use the Digital UNIX License Management Facility (LMF). This utility requires you to fill in an online form. You can register the PAK either before or after you install DEComni API. If you register before the installation, the PAK registration template is empty and you must enter all of the PAK data. If you register after the installation, some of the data will have been entered by the installation procedure. Either way, you can perform the registration procedure as follows: 1. Invoke the License Management Facility (LMF) using one of the following commands: o If DEComni API has not been installed: # lmf register 1-4 Edit the empty PAK template and add all of the information from your PAK. o If DEComni API has been installed: # lmf register - < /usr/var/adm/lmf/DECOMNI-API Edit the partially completed PAK template, adding all of the unique license information from your PAK. 2. After registering the license, copy the license details from the License Database (LDB) to the kernel cache: # lmf reset 3. Exit from the LMF utility. For more information about the Digital UNIX License Management Facility, refer to the Digital UNIX Version 3.2 Guide to Software Licensing or the lmf(*) reference page. 1.6 Installation Time Installing DEComni from CD-ROM and running the Installation Verification Procedure (IVP) on your target system takes approximately 2 minutes, depending on the system and media configuration. Installation may take longer on a system that is dependent on network activity during the installation. 1.7 Installation Privileges You must be able to log in as superuser on the system where you are installing DEComni API (login name root). You have sufficient privileges to install the DEComni API software only when you are logged in as superuser. 1.8 Required Disk Space The tables that follow list the disk space requirements for installing and running the DEComni API software subsets on Digital UNIX systems. These tables indicate the disk space requirements by file system for the convenience of personnel doing installations on systems where these file systems are mount points for different disk partitions. 1-5 ______DEComni_API_Subset_Sizes_(kilobytes)_(Installation)________ Root File System /usr /usr/var Subset_Title_______Subset_Name_______(/)______/opt____/opt_______ DEComni DOUBASE310 0 36,100 300 Application Program Interface DEComni API DOUMAN310 1,300 400 200 Reference Pages Totals:______________________________(1,300)__(36,500)(500)______ ______DEComni_API_Subset_Sizes_(kilobytes)_(Permanent)___________ Root File System /usr /usr/var Subset_Title_______Subset_Name_______(/)______/opt____/opt_______ DEComni DOUBASE310 0 36,100 200 Application Program Interface DEComni API DOUMAN310 0 400 0 Reference Pages Totals:______________________________(0)______(36,500)(200)______ 1.9 Determining Disk Space Availability Use the tables in Section 1.8 to determine how much disk space is required to install the DEComni subsets. Compare this value with the free space currently available on the disks where the DEComni files will reside. To determine the current amount of free disk space for a directory path, log in on the system where you plan to install DEComni. You can then: 1. Determine which file systems are mounted and where they are located by displaying the file /etc/fstab: 1-6 # more /etc/fstab /dev/rd0a:/:rw:1:1:ufs:: /dev/rd0g:/usr:rw:1:2:ufs:: /usr/staff/rl/leslie@bigsys:/usr/staff/rl/leslie:rw:0:0:nfs:bg: /usr/man@bigsys:/usr/man:ro:0:0:nfs:bg: This display indicates that /usr (mounted to /dev/rd0g) is the only mount point that affects where the DEComni files will reside. The system only has one local disk drive. The /usr/opt and /usr/var/opt file systems reside in the g partition of the disk on that drive. 2. Enter the df command to determine the total space and free space for the one or two file systems where the DEComni files will reside. Based on the previous display of the /etc/fstab file, which shows that only usr is a mount point, you would only need to determine free space in the usr system as follows: # df -k /usr Filesystem Total kbytes kbytes % node kbytes used free used Mounted on /dev/rd0g 122598 54447 75892 49% /usr This display indicates that there are 75,892 free kilobytes. This free space must accommodate the subset space required to run as listed in Section 1.8 for both the /usr/opt and /usr/var/opt file systems. 3. On systems where /usr/opt and /usr/var/opt are mounted to different devices from /usr, enter the following command: # df -k /usr/opt /usr/var/opt Here, you must compare the space required for the DEComni files in /usr/opt with the free space displayed in the first line of the df output list. You must also compare the space required for the DEComni files in /usr/var/opt with the free space displayed in the second line of the list. The space used under /usr/var/opt will increase as the Omni Directory Services (ODS) database is populated. 1-7 1.10 Increasing Available Disk Space The DEComni installation procedure creates the following directories and loads files into subordinate directories: /usr/opt/DOUBASE310 /usr/var/opt/DOUBASE310 If the DOUBASE310 directory node in these paths does not exist, the installation procedure creates it. If the path already exists, the installation procedure uses it. If you find that there is insufficient disk space for the DEComni API subsets, and you know that you have additional space on alternative disks or disk partitions for your system, you can do the following: 1. Create the directory /usr/opt/DOUBASE310 or /usr/var/opt /DOUBASE310 or both. 2. In the /etc/fstab file, specify one or more of the newly created directories as mount points to new disk partitions where there is additional space. 3. Enter the mount -a command so the new mount points take effect. 1.11 Backing Up the System Disk Digital recommends that you do a full system disk backup before you start any installation procedures. Use the backup procedures established for your site. For information about performing a system disk backup, refer to your Digital UNIX documentation. 1-8 2 _________________________________________________________________ Installing DEComni API on Digital UNIX Systems This chapter provides the requirements and procedures for installing the DEComni Application Programming Interface (API) software on a Digital UNIX system. 2.1 Installation Considerations This section provides information you may require during the installation process. 2.1.1 Installation Error Messages If errors occur during the installation, the system displays failure messages. For example, if the installation fails due to insufficient disk space, the procedure displays messages similar to the following: There is not enough file system space for subset DOUBASE310 DEComni Application Programming Interface (API) (DOUBASE310) will not be loaded. There is not enough file system space for subset DOUMAN310 DEComni API Reference Pages (DOUMAN310) will not be loaded. An error may occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software version is incorrect. o The system parameter values for successful installation are insufficient. For descriptions of the error messages generated by these conditions, refer to the Digital UNIX documentation on system messages, recovery procedures, and Digital UNIX software installation. Refer to Section 1.2 for further information about system software requirements. 2-1 Section 3.6 describes the actions you can take if an error occurs while using the DEComni API software. 2.1.2 Stopping the Installation You can stop the installation at any time by pressing + . However, any files created up to that point are not deleted and must be manually deleted. Appendix B lists the files and directories created during the installation process. 2.1.3 Accessing the Release Notes DEComni API release notes are in an online ASCII text file that you can read or print before or after the installation. The release notes contain information about known problems or restrictions that apply to the current version of the product. ________________________ Note ________________________ Digital recommends that you read the release notes before you install or run the DEComni API software. ______________________________________________________ After installing the DEComni API software, you can access the online release notes with the following command: # more /usr/opt/DOUBASE310/docs/DEComni310.release_notes 2.2 Installation Procedure This section describes the procedures for installing the DEComni API software. To perform the installation, you must be logged in on the system manager's account, or an account with the appropriate privileges. 2.2.1 Starting the Installation Use the following steps to start the DEComni API installation: 1. Log in as superuser (login name root). 2. Ensure that you are in the root (/) directory by entering the following command: # cd / 2-2 3. Perform one of the following procedures as appropriate for your installation medium. Installing from CD-ROM a. Mount the CD-ROM on the drive. b. Specify the /mnt directory to be the mount point for the distribution file system on the drive. For example, if your drive is rz4c, enter the following command: # mount -dr /dev/rz4c /mnt c. Enter a setld command that requests the load function (-l) and identifies the directory in the mounted file system where the DEComni API subsets are located. For example, if the directory location for the subsets is /mnt/DOUBASE310, enter the following command: # setld -l /mnt/DOUBASE310 d. Continue the installation at Section 2.2.2. Installing Over the Network from an RIS Server a. Enter a setld command that requests the load function and identifies the system where the DEComni subsets are located. For example, if you are loading DEComni subsets from a RIS distribution area on node bigsys, enter the following command: # setld -l bigsys: b. If you receive an error, contact your site administrator to determine if your node is registered as a client on that RIS node. c. Continue the installation at Section 2.2.2. 2.2.2 Selecting the Installation Subsets When the installation process has started: 1. The procedure displays the names of the DEComni API subsets, then asks you to specify the subsets to be loaded: 2-3 (C) Digital Equipment Corporation. 1997. All Rights Reserved. The subsets 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) DEComni Application Programming Interface (API) 2) DEComni Reference Pages 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): 3 If you specify more than one number at the prompt, separate each number with a space (not a comma). 2. The process verifies your choice. For example, if you enter 3 at the "Choices" prompt, it displays the following: You are installing the following subsets: DEComni Application Programming Interface (API) DEComni Reference Pages Is this correct? (y/n): y Enter y if the displayed subsets are the ones you want to load. If the displayed subsets are not the ones you intended to install, enter n. The subset selection menu displays again and you can correct your choice of optional subsets. 3. The procedure continues without asking any more questions and displays messages that report the progress of the installation: 2-4 Checking file system space required to install selected subsets: File system space checked OK. . . . DOUBASE310 - now running catman, please wait... catman has completed. Appendix A provides a complete sample installation dialogue. Chapter 3 discusses the postinstallation requirements specified in final informational messages from the procedure. 2.3 Installation Error Messages If you encounter errors from the setld utility during the installation, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take. If the verification process fails, see the /var/adm/smlogs /fverify.log file to find information that can help you diagnose the problem. 2-5 3 _________________________________________________________________ Post-installation Considerations This chapter explains how to start, verify, and stop the DEComni Application Programming Interface (API) software, and provides account process information. 3.1 Running the Installation Verification Procedure The Installation Verification Procedure (IVP) verifies that DEComni API is correctly installed and ready to use. For example, you may want to run the IVP independently after the installation to verify that the software is correctly installed and ready to use. You may also want to run the IVP after a system failure to ensure that users can access the DEComni API software. To run the IVP, enter the following command: # setld -v DOUBASE310 Appendix A provides a sample of the DEComni IVP listing. 3.2 DEComni Startup Script A startup script is provided as part of the DEComni API (DOUBASE310) software installation. The script file is located in /usr/sbin/omni_startup.sh after the installation. You can manually invoke the script or enter a script in the /sbin/rc3.d directory that invokes the startup script every time the system is booted. Be sure that DECnet is started before /usr/sbin/omni_startup.sh is invoked. Refer to the op_sys System Management Guide) for information about setting up system startup files. 3-1 3.3 Setting Up a DEComni User Account For each DEComni user, the environment variable NLSPATH should at least be set to /usr/lib/nls/msg/%N. 3.4 Example Programs The installation kit with the DEComni API BASE subset (DOUBASE310) contains some examples of DEComni API usage. The files are located in the /usr/opt/DOUBASE310/examples directory. 3.5 Deinstalling DEComni If it is necessary to deinstall the DEComni API software from your system, you must delete each installed subset. To delete DEComni API subsets: 1. Log in as superuser (login name root). 2. Ensure that you are at the root directory (/) with the command: # cd / 3. Enter the following form of the setld command: # setld -i | grep DOU 4. Look for the word "installed" in the listing, then delete the installed subsets. For example: # setld -d DOUBASE310 # setld -d DOUMAN310 3.6 Reporting Software Problems If an error occurs while using the DEComni API, and you believe that the error is caused by a problem with the product, you can take one of the following actions: o If you have a basic or DECsupport Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). 3-2 o If you purchased DEComni within the last 90 days, and you think the problem is caused by a software error, you can submit an SPR. Please follow these steps if you submit an SPR: o Describe the state of the system as accurately as possible and the circumstances under which the problem occurred. o Concisely state the problem. o Illustrate the problem with specific examples. o Report only one problem per SPR to ensure a quick response. o Notify the Digital Software Services representative, who will then submit your SPR. Experience shows that many SPRs do not contain sufficient information to duplicate or identify the problem. Complete and concise information helps Digital give accurate and timely service to software problems. 3-3 A _________________________________________________________________ Dialogue Samples This appendix provides sample installation sessions from a Digital UNIX system using disk media. The appendix includes the following: o Installation Dialogue Sample o Installation Verification Procedure Dialogue Sample A.1 Installation Dialogue Sample The following example shows an installation from disk media: # setld -l /mnt/DOUBASE310 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) DEComni Application Programming Interface (API) 2) DEComni Reference Pages 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):3 You are installing the following optional subsets: DEComni Application Programming Interface (API) DEComni Reference Pages A-1 Is this correct? (y/n): Checking file system space required to install selected subsets: File system space checked OK. Copyright (C) Digital Equipment Corporation. 1996. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. DEComni Application Programming Interface (API) Copying from . (disk) Working....Tue Jan 16 12:27:14 MET 1996 Verifying Copyright (C) Digital Equipment Corporation. 1996. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. DEComni Reference Pages Copying from . (disk) Verifying Installation procedure for DOUBASE310. DOUBASE310 software successfully installed. Configuring "DEComni Application Programming Interface (API)" (DOUBASE310) Installation configuration procedure for DOUBASE310. Checking for required directories ... Checking for required files ... A-2 Checking cache area /ods/cache/ ... Required file /ods/cache/ods_cache_0.dat not found -- creating anew... Required file /ods/cache/ods_cache_1.dat not found -- creating anew... Required file /ods/cache/ods_cache_2.dat not found -- creating anew... Required file /ods/cache/ods_cache_3.dat not found -- creating anew... Required file /ods/cache/ods_cache_4.dat not found -- creating anew... Required file /ods/cache/ods_cache_5.dat not found -- creating anew... Required file /ods/cache/ods_cache_6.dat not found -- creating anew... Required file /ods/cache/ods_cache_7.dat not found -- creating anew... Required file /ods/cache/ods_cache_8.dat not found -- creating anew... Required file /ods/cache/ods_cache_9.dat not found -- creating anew... Required file /ods/cache/ods_cache_10.dat not found -- creating anew... Required file /ods/cache/ods_cache_11.dat not found -- creating anew... Required file /ods/cache/ods_cache_12.dat not found -- creating anew... Required file /ods/cache/ods_cache_13.dat not found -- creating anew... Required file /ods/cache/ods_cache_14.dat not found -- creating anew... Required file /ods/cache/ods_cache_15.dat not found -- creating anew... Checking Schema area /ods/local/ ... Valid Schema definitions found in the attribute schema database as: OC ALIASED_NAME CN C L S O OU P_ADDR APC OWNER APT AEQ MAPV Valid Schema definitions found in the object class schema database as: TOP ALIAS C L O OU AP AE DSA DEVICE ODS_STARTUP: Normal completion. omni_schema.sh: Normal Completion. DOUBASE310 software successfully installed and configured. Please read the supplied online release notes file (ASCII text format). ./usr/opt/DOUBASE310/docs/DEComni310.release_notes DOUMAN300 software successfully installed. Configuring "DEComni Reference Pages" (DOUMAN310) DOUMAN310 - now running catman, please wait... catman has completed. 3 *) DECOMNI API 31 INSTALLATION VERIFICATION PROCEDURE A-3 # setld -v DOUBASE310 DEComni Application Programming Interface (API) (DOUBASE310) Copyright (C) Digital Equipment Corporation. 1997. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Installation Verification Procedure DEComni for Digital UNIX V4.0 - Starting IVP Startup procedure for: DEComni for Digital UNIX V4.0 ****************************************************** * omni_startup now calling the ods_startup procedure * ****************************************************** Checking for required directories ... Checking for required files ... Checking cache area /ods/cache/ ... Checking Schema area /ods/local/ ... Valid Schema definitions found in the attribute schema database as: Valid Schema definitions found in the object class schema database as: TOP ALIAS C L O OU AP AE DSA DEVICE TAE OAE AS VMD DOMAIN PI NVAR UNVAR ODS_STARTUP: Normal completion. ****************************************************** * omni_startup now calling the omni_schema procedure * ****************************************************** omni_schema.sh: Normal Completion. ************************************************* * omni_startup now registering the omniview VMD * ************************************************* A-4 © Digital Equipment Corporation. 1997. All Rights Reserved. ODSCL (Register Directory) On Tuesday 25-MAR-97 12:38:46 Successfully added name: /vn=omni_local_vmd With attributes: /oc=VMD/aprof=iso-mms/vendor=Digital/APPSN=(/cn=OMNI_LOCAL_AE) Exiting ODSCL ************************************************************** * omni_startup now registering the omniview common name (CN) * ************************************************************** © Digital Equipment Corporation. 1997. All Rights Reserved. ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:46 Successfully added name: /CN=OMNI_LOCAL_AE With attributes: /OC=TAE/P_ADDR=OMNI.VIEW.OMNI./APC={1 0 9506 2 1}/apt={1 2 3}/aeq=11 Exiting ODSCL ******************************************************** omni_startup: now starting the omni_server daemon...DONE. pid: 15094 ******************************************************** The DEComni for Digital UNIX V4.0 startup has successfully completed. Installation Verification Procedure for: DEComni for Digital UNIX V4.0 ( subset BASEBASE310) ************************************************** * omni_ivp.sh: Now calling /usr/sbin/ods_ivp.sh * ************************************************** Beginning ODS IVP at Tue Mar 25 11:32:51 MET 1997 The ODS IVP consists of 3 simple tests. 1. The first test ADDs an object to the ODS directory. 2. The second READs the object from the ODS directory. 3. Finally, the object is DELETEd from the ODS directory. Test 1 Operation ADD: Adding object /CN=ayrton.mln.dec.com_root with entry attributes /OC=AE/P_ADDR=A.B.C.39840F454E450000AA0004000B0721 ... A-5 ODS_IVP: SUCCESS on ADD Test 2 Operation READ : Reading object /CN=ayrton.mln.dec.com_root ... Copy used; entry is: Name: CN (Common Name) = ayrton.mln.dec.com_root Entry: OC (Object Class) = 7 (Application Entity) P_ADDR (Presentation Address) = A.B.C.39840F454E450000AA0004000B0721 ODS_IVP: SUCCESS on READ Test 3 Operation DELETE : Deleting object /CN=ayrton.mln.dec.com_root ... ODS_IVP: SUCCESS on DELETE ODS IVP Successfully completed at Tue Mar 25 11:32:55 MET 1997 ********************************************************** * omni_ivp.sh: Registering the DEComni IVP Applications * ********************************************************** © Digital Equipment Corporation. 1997. All Rights Reserved. ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 Successfully added name: /VN=OMNI_IVP_RESP_VMD With attributes: /OC=VMD/APPSN=(/CN=OMNI_IVP_RESP_AE)/VENDOR=Digital ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 Successfully added name: /CN=OMNI_IVP_RESP_AE With attributes: /OC=TAE/AEQ=11/APC={1 0 9506 2 3}/P_ADDR=0x01.0x01.0x01.490000A A000400000021 ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 A-6 Successfully added name: /VN=OMNI_IVP_INIT_VMD With attributes: /OC=VMD/APPSN=(/CN=OMNI_IVP_INIT_AE)/VENDOR=Digital ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 Successfully added name: /CN=OMNI_IVP_INIT_AE With attributes: /OC=TAE/AEQ=11/APC={1 0 9506 2 3}/P_ADDR=0x01.0x01.0x01.490000A A000400000021 ODSCL> Exiting ODSCL ************************************************************ * omni_ivp.sh: De-registering the DEComni IVP Applications * ************************************************************ © Digital Equipment Corporation. 1997. All Rights Reserved. ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 Successfully removed name: /VN=OMNI_IVP_RESP_VMD ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 Successfully removed name: /CN=OMNI_IVP_RESP_AE ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 Successfully removed name: /VN=OMNI_IVP_INIT_VMD ODSCL> ODSCL (Register Directory) On Tuesday 25-MAR-97 11:32:56 Successfully removed name: /CN=OMNI_IVP_INIT_AE ODSCL> Exiting ODSCL A-7 The DEComni IVP has completed successfully. This product is now ready for use. DEComni for Digital UNIX V3.0 - IVP successfully terminated DOUBASE300 software successfully installed and configured. # A-8 B _________________________________________________________________ Files Added During Installation This appendix lists the directories and files that are added to a Digital UNIX system by the DEComni API installation procedure. The files are divided into two groups: o Application Programming Interface files o Reference page files B.1 Application Program Interface Files The following directories and files are added by the DEComni Application Program Interface installation procedure: /usr/opt/DOUBASE310/bin: omni_app_prof omni_registry omni_server omniview /usr/opt/DOUBASE310/docs: DEComni310.release_notes DEComni310.release_notes.ps /usr/opt/DOUBASE310/etc: omni_config.csh omni_get_lib.sh omni_ivp.sh omni_schema.sh omni_startup.sh /usr/opt/DOUBASE310/examples: omnitest.c B-1 /usr/opt/DOUBASE310/include: int omni_api_protos.h omni_codes.h omni_defs.h omni_integrators_defs.h /usr/opt/DOUBASE310/include/int: omni_basic_types.h omni_config.h omni_debug.h omni_exceptions.h omni_ident.h omni_int_prepost.h omni_integrator_protos.h omni_ioi_def.h omni_queue.h omni_shared_types.h omni_sync.h /usr/opt/DOUBASE310/lib: libomniapi.a libomniapi.so libomniclt.a libomniclt.so libomnisrv.a libomnisrv.so /usr/opt/DOUBASE310/local: omniview.uid omniview_help.txt /usr/opt/DOUBASE310/msg: omni_codes.cat /usr/opt/DOUBASE310/ods/examples: ods_example.c /usr/opt/DOUBASE310/ods/exe: ods_cache_utility ods_rehash_directory ods_schema_utility ods_tester odscl B-2 /usr/opt/DOUBASE310/ods/help: odscl_add_expression.txt odscl_attr_abbrev.txt odscl_attr_expression.txt odscl_attr_prompt.txt odscl_command_elements.txt odscl_command_syntax.txt odscl_commands.txt odscl_continuation.txt odscl_deregister.txt odscl_deregister_examples.txt odscl_deregister_syntax.txt odscl_directory_prompt.txt odscl_displays.txt odscl_exit.txt odscl_file_prompt.txt odscl_help.idx odscl_help.txt odscl_invoking.txt odscl_list.txt odscl_list_examples.txt odscl_list_syntax.txt odscl_local_directory.txt odscl_match_expression.txt odscl_match_prompt.txt odscl_modify.txt odscl_modify_examples.txt odscl_modify_prompt.txt odscl_modify_syntax.txt odscl_name_expression.txt odscl_name_prompt.txt odscl_oc_abbrev.txt odscl_option_abbrev.txt odscl_path_expression.txt odscl_path_prompt.txt odscl_prompts.txt odscl_read.txt odscl_read_examples.txt odscl_read_syntax.txt odscl_register.txt odscl_register_examples.txt odscl_register_syntax.txt odscl_remove_expression.txt B-3 odscl_replace_expression.txt odscl_set.txt odscl_set_examples.txt odscl_set_syntax.txt odscl_show.txt odscl_show_examples.txt odscl_show_syntax.txt odscl_to_file_expression.txt odscl_to_prompt.txt odscl_with_expression.txt odscl_with_prompt.txt /usr/opt/DOUBASE310/ods/include: ods_defs.h ods_msg.h /usr/opt/DOUBASE310/ods/lib: libods.a libods.so /usr/opt/DOUBASE310/ods/scripts: ods_ivp.sh ods_startup.sh /usr/var/opt/DOUBASE310: omni_registry.tab /usr/var/opt/DOUBASE310/ods/cache: ods_cache_0.dat ods_cache_1.dat ods_cache_10.dat ods_cache_11.dat ods_cache_12.dat ods_cache_13.dat ods_cache_14.dat ods_cache_15.dat ods_cache_2.dat ods_cache_3.dat ods_cache_4.dat ods_cache_5.dat ods_cache_6.dat ods_cache_7.dat ods_cache_8.dat ods_cache_9.dat B-4 /usr/var/opt/DOUBASE310/ods/local: ods_known_attribute_types.dat ods_known_object_classes.dat ods_version.dat odscl_parse_tbl.bin B.2 Reference Page Files The following directories and files are added by the DEComni Reference Page installation procedure: /usr/share/man/man3: omni_accept omni_delete_definition omni_event_notify omni_get_application_profile omni_get_profiles omni_group_variable_list omni_lookup_value omni_print_value B-5 _________________________________________________________________ Index A______________________________ E______________________________ Account privileges, 1-1, 1-5, Error messages, 2-5 3-2 Example programs, 3-2 Application Program Interface (API) F______________________________ files added, B-1 Files added during B installation, Appendix B _______________________________ Backup for system disk, 1-8 H______________________________ C Hardware requirements, 1-2 _______________________________ Customer Support Center (CSC), I______________________________ 3-2 Installing DEComni, Chapter 2 D Installation _______________________________ files added, Appendix B Dialogue samples, Appendix A of product, Chapter 2 DEComni pre-requisites, Chapter 1 deinstallation, 3-2 considerations, 2-1 example programs, 3-2 dialogue sample, A-1 installation procedure, 2-2 error messages, 2-1, 2-5 setting up a user account kit, 1-1 setup, 3-2 privileges, 1-1, 1-5 startup script, 3-1 procedure, 2-2 Deinstalling DEComni, 3-2 process stop, 2-2 Determine free disk space, subsets, 2-3 1-6, 1-8 time, 1-5 Disk space requirements, 1-5 Installation Verification Distribution kit, 1-1 Procedure (IVP), 3-1 privileges, 3-2 Index-1 Reference page subsets, 1-3 L______________________________ Release notes, 1-1, 2-2 License Database (LDB), 1-4 S License Management Facility _______________________________ (LMF), 1-4 Sample dialogues, Appendix A Selecting installation subsets O______________________________ , 2-3 Online release notes, 1-1 Setting up a user account, 3-2 Software Performance Report P (SPR), 3-2, 3-3 _______________________________ Software requirements, 1-2 Post-installation Starting the installation, 2-2 considerations, Chapter 3 Startup script, 3-1 Pre-installation requirements, Stop installation process, 2-2 Chapter 1 Subset requirements, 1-2 Product Authorization Key System disk backup, 1-8 (PAK), 1-4 System subset requirements, Product subsets, 1-3 1-2 _______________________________ V______________________________ Reference page files added, Verify free disk space, 1-6, B-5 1-8 Index-2