Compaq_ACMSxp_for_Tru64_UNIX________________________ Installation Guide Order Number: AA-Q1NUH-TE June 1999 This guide describes how to install Compaq ACMSxp for Tru64 UNIX software on an Alpha architecture system running the Compaq Tru64 UNIX operating system. Revision/Update Information: This is a revised guide. Software Version: Compaq ACMSxp V3.2A Compaq Computer Corporation Houston, Texas ________________________________________________________________ June 1999 The information in this publication is subject to change without notice. COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. THIS INFORMATION IS PROVIDED "AS IS" AND COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AND EXPRESSLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, GOOD TITLE, AND AGAINST INFRINGEMENT. This publication contains information protected by copyright. No part of this publication may be photocopied or reproduced in any form without prior written consent from Compaq Computer Corporation. © 1999 Digital Equipment Corporation. All Rights Reserved. The software described in this guide is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of the agreement. Compaq and the Compaq logo are registered in the United States Patent and Trademark Office. ACMS, ACMS Desktop, ACMSxp, ACMSxp Desktop, AlphaServer, AltaVista, DEC, DECnet, DECthreads, DIGITAL, OpenVMS, Tru64 UNIX, VAX, and VMS are trademarks of Compaq Computer Corporation. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation. UNIX and X/Open are registered trademarks and The Open Group is a trademark of The Open Group in the United States and other countries. Other product names mentioned herein may be trademarks and /or registered trademarks of their respective companies. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... vii 1 Preparing for ACMSxp Installation 1.1 Reading the Online Release Notes.............. 1-1 1.2 Registering Your Software License............. 1-1 1.3 Checking the Software Distribution Kit........ 1-2 1.4 Checking Installation Procedure Requirements.................................. 1-2 1.4.1 Checking Login Privileges................. 1-3 1.4.2 Checking Hardware Requirements............ 1-3 1.4.3 Checking Software Requirements............ 1-3 1.4.3.1 Software Subsets Required............... 1-3 1.4.3.2 Checking Whether Subsets Are Loaded..... 1-4 1.4.4 Determining Which Subsets to Load......... 1-5 1.4.5 Determining Disk Space Requirements....... 1-5 1.4.5.1 Checking Current Disk Space............. 1-6 1.5 Installing from Media or Using RIS............ 1-7 2 Preinstallation Tasks 2.1 Reconfiguring the Kernel...................... 2-1 2.1.1 Modifying Dynamic Kernel Attributes....... 2-1 2.1.1.1 Changing a Kernel Attribute Run-time Value................................... 2-3 2.1.1.2 Editing the Kernel Attribute Configuration File...................... 2-4 2.1.2 Rebuilding the Kernel..................... 2-5 2.2 DCE Procedures for the IVP.................... 2-6 iii 3 Installing ACMSxp Software 3.1 Backing Up Your System Disk................... 3-1 3.2 Stopping the Installation..................... 3-1 3.3 Keeping a Record of the Installation.......... 3-1 3.4 Using CD-ROM Consolidated Distribution Media......................................... 3-2 3.5 Using an RIS Distribution Area................ 3-2 3.6 Responding to Installation Procedure Prompts....................................... 3-3 3.6.1 Selecting Subsets......................... 3-3 3.6.2 Monitoring Displays During the Subset Loading Process........................... 3-5 4 After Installation 4.1 Installing the ACMSxp Management GUI Option... 4-1 4.1.1 Prerequisite Software..................... 4-1 4.1.2 System Requirements....................... 4-2 4.1.3 Procedures to Install the ACMSxp Management GUI............................ 4-2 4.1.4 Installing on a Japanese Windows NT System.................................... 4-3 4.2 Setting Up ACMSxp Software with Japanese Language Support.............................. 4-3 4.3 Running the Installation Verification Procedure..................................... 4-4 4.3.1 IVP Overview.............................. 4-4 4.3.2 Preparing the IVP......................... 4-5 4.3.3 Invoking the IVP.......................... 4-5 4.4 Deleting ACMSxp Software from Your System..... 4-8 4.5 Running a TPsystem from the root Account...... 4-8 A Sample Listings A.1 Installing Release Notes...................... A-1 A.2 Sample ACMSxp Installation.................... A-2 A.3 Sample Installation Verification Procedure.... A-5 iv B Files Installed on an ACMSxp System B.1 /ascii_docs Directory......................... B-1 B.2 /bin Directory................................ B-1 B.3 /include Directory............................ B-2 B.3.1 /include/encina Directory................. B-3 B.3.2 /include/threadTid Directory.............. B-3 B.3.3 /include/tmxa............................. B-3 B.3.4 /include/tran Directory................... B-3 B.4 /lib Directory................................ B-3 B.5 /man Directory................................ B-4 B.5.1 /man/man1 Directory....................... B-4 B.5.2 /man/man3 directory....................... B-4 B.5.3 /man/man8 Directory....................... B-5 B.6 /msg Directory................................ B-6 B.6.1 /msg/C Directory.......................... B-7 B.6.2 /msg/en_US.ISO8859-1 Directory............ B-8 B.6.3 /msg/en_US.sdeckanji...................... B-9 B.7 /sample Directory............................. B-9 B.7.1 /sample/add Directory..................... B-9 B.7.2 /sample/avertz_vm Directory............... B-10 B.7.3 /sample/avertz_vr Directory............... B-10 B.7.4 /sample/employee Directory................ B-11 B.7.5 /sample/ivp Directory..................... B-11 B.7.6 /sample/std Directory..................... B-12 B.7.7 /sample/std_tpc Directory................. B-12 B.8 /shlib Directory.............................. B-13 C Recovering from Errors C.1 Failures During Product Installation.......... C-1 C.2 Failures During Product Use................... C-2 Index v Examples 3-1 Installation Subset Selection Display..... 3-3 3-2 Selecting Subsets......................... 3-4 3-3 Verifying Subset Selection................ 3-4 3-4 Subset Loading Process.................... 3-6 A-1 Installing Release Notes.................. A-1 A-2 Installing All ACMSxp Options............. A-2 A-3 IVP Sample................................ A-5 C-1 Sample Installation Failure Message....... C-1 Tables 1-1 Tru64 UNIX Subsets Required by ACMSxp..... 1-3 1-2 ACMSxp Subset Sizes Required.............. 1-5 2-1 Kernel Configuration Minimum Values....... 2-2 4-1 Prerequisite Software Version Numbers..... 4-2 vi _________________________________________________________________ Preface This installation procedure creates a Compaq ACMSxp for Tru64 UNIX disk directory structure subordinate to the /usr/opt and /var/opt directories. The installation enables multiple versions of ACMSxp to be installed on the same system. Keep this guide with your distribution kit. You will need both the guide and the kit to install maintenance updates or to reinstall ACMSxp for any other reason. Intended Audience This guide is intended for system managers who install Compaq ACMSxp for Tru64 UNIX software. Operating System Information Information about the versions of the Compaq Tru64 UNIX operating system and other software compatible with this version of ACMSxp software is included in this manual. For information on the relationship of other software products with this version of ACMSxp, refer to the Software Product Description (SPD). Use the SPD to verify which versions of your operating system are compatible with this version of ACMSxp. Structure This manual has the following components, as shown in the following table: vii ___________________________________________________________ Component___Description____________________________________ Chapter 1 Describes preparations and requirements necessary for installing Compaq ACMSxp for Tru64 UNIX software, including dependent software. Chapter 2 Describes tasks you may have to perform before you install the software, for example, reconfigure dynamic kernel attributes or modify a global keyword. Chapter 3 Describes how to install ACMSxp locally (using CD-ROM) or from a server area. Chapter 4 Explains what you may need to do after the installation, for example, to make ACMSxp ready for use and to delete versions from your system. Appendix A Provides sample listings for installing different subsets. Appendix B Lists the directories and the files created ____________during_the_ACMSxp_installation.________________ Associated Documentation Refer to the following documents for a description of the ACMSxp features and capabilities. ___________________________________________________________ Title______________________Purpose_________________________ Compaq ACMSxp Software Introduces ACMSxp concepts. It System Overview describes concepts and terms you should be familiar with when you use the other manuals in the ACMSxp documentation set and in related product documentation sets. viii ___________________________________________________________ Title______________________Purpose_________________________ Compaq ACMSxp Getting Provides a step-by-step tutorial Started for developing a simple application with the ACMSxp software. This manual enables you to get started with the ACMSxp software on a platform featuring a supported operating system: the Windows NT system, the Compaq Tru64 UNIX system, or the OpenVMS Alpha system. Compaq ACMSxp STDL Contains conceptual, Encyclopedia programming, and reference material for the X/Open Structured Transaction Definition Language (STDL) application programming interface to the ACMSxp portable transaction processing monitor. The main users of this manual are programmers writing ACMSxp transaction processing applications. Compaq ACMSxp Developing Presents information about and Managing Applications designing, developing, and managing STDL applications on ACMSxp systems running on the Tru64 UNIX, OpenVMS, and Windows NT platforms. This manual is intended for those who define the business requirements to be addressed by the ACMSxp application, determine the design of the ACMSxp application, program the ACMSxp application, or manage and maintain the ACMSxp ___________________________application.____________________ Additional information is available at the following web sites: http://www.software.digital.com/acmsxp ix http://www.software.digital.com/tpwebconnect Conventions The following conventions are used in this guide: ___________________________________________________________ Convention_____Meaning_____________________________________ # A pound sign (#) is the default superuser prompt. % A percent sign (%) is the default user prompt. In examples, a boxed symbol indicates that you press the named key on the keyboard. Ctrl/C This symbol indicates that you press the Ctrl key while you simultaneously press another key (in this case, C). italic type Italic type in text indicates product names or sub-brands and complete titles of manuals. user input In interactive examples, user input appears in bold type. filesystem In text, this typeface indicates the exact name of a command, routine, partition, path name, directory, or file. This typeface is also used in interactive examples and other screen displays. UPPERCASE The Tru64 UNIX operating system lowercase differentiates between lowercase and uppercase characters. Examples, syntax descriptions, function definitions, and literal strings that appear in text must be typed exactly as shown. x ___________________________________________________________ Convention_____Meaning_____________________________________ setld(8) Cross references to on line reference pages include the appropriate section number in parentheses. For example, setld(8) indicates that you can find the material on the setld command in Section 8 of the reference pages. [y] In a prompt, square brackets indicate that the enclosed item is the default response. For example, [y] means that the default _______________response_is_Yes.____________________________ xi 1 _________________________________________________________________ Preparing for ACMSxp Installation Your distribution kit includes a letter titled Read Before Installing Compaq ACMSxp for Tru64 UNIX . This letter discusses important information that might not be included in this guide. Read this letter before proceeding with the installation. 1.1 Reading the Online Release Notes ACMSxp provides this printed installation guide describing how to install and verify the software and an online Release Notes describing restrictions to installing and using the product. Compaq strongly recommends that you read the Installation Guide and Release Notes before using the product. The Release Notes may contain information about changes to the installation process or requirements for installation. Install the Release Notes subset option (number 3) to install only the Release Notes for ACMSxp. The kit installs an ASCII text format of the Release Notes in the following location: /usr/opt/ACMSXPV321/ascii_docs/ACMSxp_release_notes_321.txt See Example 3-1. 1.2 Registering Your Software License ACMSxp includes support for the License Management Facility (LMF). You must register your License Product Authorization Key (License PAK) in the License Database (LDB) in order to use ACMSxp on a newly licensed node. The License PAK may be shipped with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. Preparing for ACMSxp Installation 1-1 If you are installing ACMSxp as an update on a node already licensed for this software, you have already completed the License PAK registration requirements. If you are installing prerequisite or optional software along with ACMSxp, review the PAK status and install the PAKs for any prerequisite or optional software before you install ACMSxp. To register a license under the Tru64 UNIX operating system, first log in as superuser. After you register your license, use the following lmf reset command to copy the license details from the License Database (LDB) to the kernel cache: # lmf reset For complete information on using LMF, refer to Guide to Software License Management and the lmf(8) reference page. 1.3 Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your ACMSxp software distribution kit. In addition to this guide, the software distribution kit includes the following: o CD-ROM optical disk for systems with optical disk drives o CD-ROM booklet o CD-ROM Read Before Installing letter If your software distribution kit is damaged or incomplete, contact your Compaq representative. 1.4 Checking Installation Procedure Requirements This section discusses various requirements for installing ACMSxp. Installing ACMSxp and running the Installation Verification Procedure (IVP) take approximately 10 to 15 minutes, depending on your type of media and system configuration. 1-2 Preparing for ACMSxp Installation 1.4.1 Checking Login Privileges You must have superuser privileges to install the ACMSxp software and to register the license PAK. 1.4.2 Checking Hardware Requirements To install ACMSxp, you need the following hardware: o Software distribution device (if installing from media) Locate the CD-ROM drive for the CD-ROM software distribution media. The CD-ROM booklet or the documentation for the CD-ROM drive you are using explains how to load the CD-ROM media. o Terminal You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. Refer to ACMSxp Software Product Description (SPD) for additional hardware requirements. 1.4.3 Checking Software Requirements ACMSxp requires Compaq Tru64 UNIX Version 4.0D platforms. Future ACMSxp releases may require higher versions. Refer to Read Before Installing letter (included on the CD- ROM) or the online Release Notes for information about the minimum version of the operating system required. 1.4.3.1 Software Subsets Required ACMSxp also requires that the Tru64 UNIX software subsets shown in Table 1-1 be loaded on the system where you install ACMSxp. Table_1-1_Tru64_UNIX_Subsets_Required_by_ACMSxp____________ Subset_Name______Version_____Comments______________________ OSFBASE 4.25 The "Base System" subset OSFPGMR 4.25 The Software Development Environment (continued on next page) Preparing for ACMSxp Installation 1-3 Table_1-1_(Cont.)_Tru64_UNIX_Subsets_Required_by_ACMSxp____ Subset_Name______Version_____Comments______________________ DCE 3.0 ECO1 Some supported configuration of DCEADK, DCECDS, DCERTS, and _____________________________DCESEC_on_the_system__________ 1.4.3.2 Checking Whether Subsets Are Loaded To check whether the required subsets listed in Table 1-1 are loaded, follow these steps: 1. Log in to the system where you are installing ACMSxp. 2. Enter the following command to check for subsets on the system. For example: # setld -i | egrep 'OSFBASE|OSFPGMR|DCERTS' If you do not log in as superuser (login name root), enter the full path of the command. For example: % /usr/sbin/setld -i | egrep 'OSFBASE|OSFPGMR|DCERTS' 3. Check the displayed rows for the name of the relevant subset and any related patches. For example: DCERTS300 installed DCE Runtime Services V3.0 DCERTSECO1030 installed DCE Runtime Services V3.0 ECO 1 OSFBASE425 installed Base System (- Required -) OSFPGMR425 installed Standard Programmer Commands (Software Development) The word installed appears in a row after the subset identifier when a subset is loaded. 4. If the word installed does not appear (the second column in a row is blank), the subset is not loaded. Load the missing Tru64 UNIX software before installing ACMSxp. (For information on how to load the operating system software, refer to Tru64 UNIX Installation Guide.) 1-4 Preparing for ACMSxp Installation 1.4.4 Determining Which Subsets to Load You must choose the ACMSxp subsets you want to load: o ACMSxp Version 3.2A for Tru64 UNIX Base Contains the development and run-time code. o ACMSxp Version 3.2A for Tru64 UNIX Man Pages o ACMSxp Version 3.2A for Tru64 UNIX Release Notes You can choose any combination of these subsets, or choose ALL, CANCEL, or EXIT. See Appendix A for an example of the installation script. 1.4.5 Determining Disk Space Requirements Table 1-2 lists the disk space requirements for loading the ACMSxp software subset. Table_1-2_ACMSxp_Subset_Sizes_Required_____________________ Megabytes Subset_Title__________Subset_Name___________(MB)___________ ACMSxp Base ACMSXPVBASE321 56 ACMSxp Man Pages ACMSXPVMAN321 1 ACMSxp Release ACMSXPVRELNOTES321 1 Notes Totals:_____________________________________58_____________ ACMSxp software is installed in the directories /usr /opt and /var/opt. The directory /var/opt contains only the TPsystems registry file and requires minimal space. (The file is created when you create your first TPsystem and stores data related to all TPsystems on your ACMSxp system.) In general, the requirements are listed by directory. This is convenient if you are doing installations on systems where these directories are mount points for different disk partitions. In the case of ACMSxp, there is only one directory/mount point. Note that following the installation, the IVP requires a further ten megabytes in the user's own directory. Preparing for ACMSxp Installation 1-5 Using these disk space requirements, total the values for the subsets you plan to load in each directory. Compare the space required for subsets with the free space currently on the disks where ACMSxp files will reside to be sure that you have enough disk space to complete the installation. 1.4.5.1 Checking Current Disk Space To check the current amount of free space for a directory path, log in to the system where you are installing ACMSxp. You can check which directories are mounted and where they are by viewing the /etc/fstab file. For example: # more /etc/fstab /dev/rd0a:/:rw:1:1:ufs:: /dev/rd0g:/usr:rw:1:2:ufs:: /usr/staff/r1/leslie@bigsys:/usr/staff/r1/leslie:rw:0:0:nfs:bg: /usr/man@bigsys:/usr/man:ro:0:0:nfs:bg: The display indicates that /usr (mounted to /dev/rd0g) is the only mount point that affects where ACMSxp files are to reside; the system has only one local disk drive, and the /usr/lib and file system resides in the g partition of the disk on that drive. To check the total space and the free space for the directories where ACMSxp is to reside, enter the df command. For example: # df /usr Filesystem 512-blocks Used Available Capacity Mounted on /dev/rd0g 1603526 1223890 219282 85% /usr Given the previous display of the /etc/fstab file, which shows that only /usr is a mount point, you need to check free space only in the /usr file system. The output shows that there are 219 282 kilobytes free. This free space must accommodate the subset requirements listed in Table 1-2. 1-6 Preparing for ACMSxp Installation 1.5 Installing from Media or Using RIS Someone from your site must perform at least one ACMSxp installation from the distribution media. Your site system manager can then decide whether to make an ACMSxp distribution kit available online so that subsequent installations of ACMSxp can use the Remote Installation Service (RIS). For information on extracting ACMSxp subsets to an RIS distribution area, refer to Tru64 UNIX Sharing Software on a Local Area Network. If you expect to use ACMSxp subsets from the RIS area of a remote system for installation on your local system, first check with your site system manager to ensure that: o The ACMSxp network kit is available for use. o Your system is registered as an RIS client. If ACMSxp subsets are available to you on an RIS server system, you must know the name of that system. For more information on installing ACMSxp from an RIS distribution area, see Section 3.5. Preparing for ACMSxp Installation 1-7 2 _________________________________________________________________ Preinstallation Tasks Before you install ACMSxp software on a system for the first time, you may have to do the following: o Reconfigure dynamic kernel attributes (see Section 2.1 o Modify a global keyword (which requires rebuilding the kernel; see Sections 2.1.1 and 2.1.2) o Perform Distributed Computing Environment (DCE) procedures to run the IVP (see Section 2.2) 2.1 Reconfiguring the Kernel To ensure that the system has the resources required by ACMSxp software, you might have to do one or both of the following: o Reconfigure dynamic kernel attributes. o Modify the global keyword maxusers for the kernel. Because most of the kernel attributes are dynamic, you can modify them as described in Section 2.1.1, without rebooting your system. To determine whether to modify the global keyword and rebuild the kernel, see Section 2.1.2. If you rebuild the kernel, you need to reboot your system. 2.1.1 Modifying Dynamic Kernel Attributes To check the current values for the dynamic kernel attributes, perform the following steps: 1. Display the attributes and values of the related loaded and configured subsystems. a. Show the attributes and values for the proc subsystem. For example: # /sbin/sysconfig -q proc Preinstallation Tasks 2-1 b. Show the attributes and values for the vm subsystem. For example: # /sbin/sysconfig -q vm c. Show the attributes and values of arguments for messages, semaphores, and shared memory. For example: # /sbin/sysconfig -q ipc 2. Check the displayed values on the current system against the minimum values of the dynamic kernel attributes in Table 2-1. Table_2-1_Kernel_Configuration_Minimum_Values______________ Attribute Minimum Dynamic__________Static___________Value_______Subsystem____ max-per-proc- vm_initial_ 33554432 proc stack-size limit_ stack.rlim_ max max-proc-per- maxuprc 256 proc user max-threads- Not applicable 4096 proc per-user sem-mni semmni 100 ipc sem-msl semmsl 50 ipc shm-seg shmseg 64 ipc vm-vpagemax______vpagemax____________32767____vm___________ If any displayed value is less than the minimum value shown in Table 2-1, change the current kernel attribute value in one of the following ways: o Change the run-time value directly and use it to update the boot-time values. See Section 2.1.1.1. Some run-time values cannot be changed directly. Refer to Tru64 UNIX System Administration Guide. o Edit the kernel attribute database file to set the boot- time value to the new minimum values and synchronize the run-time values. See Section 2.1.1.2. 2-2 Preinstallation Tasks o Edit the system configuration file and rebuild the kernel. See Section 2.1.2. ________________________ Note ________________________ These are only minimum values that allow you to run the IVP. You must take into account the system requirements of your ACMSxp application and increase these minimum values accordingly. ______________________________________________________ 2.1.1.1 Changing a Kernel Attribute Run-time Value To change the run-time value of a kernel attribute directly, proceed as follows: 1. To see whether you can change the run-time value of the kernel attribute directly, refer to Tru64 UNIX System Administration Guide. If you cannot directly change the particular value, follow the steps in Section 2.1.1.2. 2. Log in as root or become superuser. 3. Use a command in the following format with the dynamic attribute name to change the current run-time value: /sbin/sysconfig -r subsystem-name dynamic-attribute- name=new-value This command changes the run-time value of the dynamic kernel attribute. You can specify multiple attributes on the same command. 4. After you change all the run-time values, change the default values on the system to the new minimum value that you set in the runtime. Use sysconfig for each subsystem in which you made changes to write out the list of kernel attributes of each subsystem to a file. Use the following format: /sbin/sysconfig -q subsystem-name > temp-file-name This command stores the current run-time values in the temporary file you specify. Preinstallation Tasks 2-3 5. For each subsystem, update the attributes in the kernel attribute file /etc/sysconfigtab with a command in the following format, using the temporary file created for each subsystem: /sbin/sysconfigdb -u -f temp-file-name subsystem-name This command stores the current values so that the next time the system boots, the new values take effect. Proceed to Section 2.1.2 to see whether you must rebuild the kernel. 2.1.1.2 Editing the Kernel Attribute Configuration File You can edit the /etc/sysconfigtab file to change the boot- time values of the kernel attributes to reflect the minimum values. If you edit the kernel attribute database file, proceed as follows: 1. Log in as root or become superuser. 2. Use your favorite editor to modify the /etc/sysconfigtab file. Use the dynamic attribute name shown in Table 2-1 and a value equal to or greater than the minimum shown. For each subsystem, the format is: subsystem-name: dynamic-attribute-name = new-value ... Place each value on a separate line. 3. After you exit the editor, run the following command: # /sbin/sysconfigdb -s # This command updates the memory-resident copy with the values in the file, and thus synchronizes both boot-time and run-time values. Proceed to Section 2.1.2 to see whether you must rebuild the kernel. 2-4 Preinstallation Tasks 2.1.2 Rebuilding the Kernel To run ACMSxp software, set the maxusers argument in /sys/conf/machine_name to the minimum value. To check the current value and possibly change it, follow these steps: 1. Change directory to the kernel configuration file directory. For example: # cd /sys/conf 2. Use the grep command, the search string maxusers, and the name of the system to access the file containing the arguments. For example: # grep maxusers GREEN maxusers 64 # The command shows 64 as the maxusers value. If the value is 256 or more, you do not have to edit the kernel configuration file. If the value for maxusers is less than 256 or you have to set a minimum value for a kernel attribute as described in Section 2.1.1, you must edit the kernel configuration file. Increase the value of maxusers to 256 or more. If you do not edit the configuration file, you do not have to rebuild the kernel. To run the installation verification procedure (IVP), follow the steps in Section 2.2. If you do not want to run the IVP, proceed to Chapter 3 to install the software. If you edit the configuration file, change maxusers and use the static names in Table 2-1 to set minimum values if necessary. After you close the configuration file, follow these steps to rebuild the kernel: 1. From the directory containing the kernel configuration file, enter the doconfig command. For example: # doconfig -c GREEN Do not edit the configuration file again. When the new kernel is complete, the software tells you where the new file is. Preinstallation Tasks 2-5 2. To use the new kernel, shut the system down to single user mode and copy the new kernel. For example: # /usr/sbin/shutdown now 3. Mount the file systems so that you can modify them. For example: # bcheckrc 4. Copy the old kernel. For example: # cp /vmunix /vmunix.old 5. Move the new kernel to root so that it is used for bootstrapping. Use a command in the following format: mv new_kernel_name /vmunix For example: # mv NEWABC /vmunix 6. Reboot the system. For example: # /usr/sbin/shutdown -r now When the new kernel starts, follow the procedures in Section 2.2 to set up DCE for the IVP. If you do not want to run the IVP, proceed to Chapter 3 to install the software. 2.2 DCE Procedures for the IVP The Installation Verification Procedure (IVP) allows you to check that the ACMSxp software has been installed successfully and that all dependent products are set up as needed. The IVP depends on a certain DCE setup to run. If you want to run the IVP, follow the procedures described in this section to set up DCE for the IVP. The DCE setup for the IVP applies only to the IVP and is not necessary for running ACMSxp applications. The procedures described in this section to set up a DCE environment for running the IVP create the following items: o Server principal acmsxp_svr o SFS server principal acmsxp_svr_sfs 2-6 Preinstallation Tasks o Server keys for each server principal in the following directory: /krb5/acmsxp o User principal(s) in the DCE group called users under which to run the IVP Follow these steps: 1. Log in to DCE as cell_admin. csh> dce_login cell_admin Enter Password: csh> The command logs you in to DCE and gives you the proper credentials to execute the security operations. The password you supply is chosen for cell_admin after DCE is installed. For further information about DCE setup, see DCE for Tru64 UNIX Installation and Configuration Guide. ________________________ Note ________________________ All DCE commands are case sensitive. ______________________________________________________ 2. Create a DCE group called users under which the IVP runs. csh> rgy_edit Current site is: registry server at /.../avertz_cell rgy_edit=> domain group Domain changed to: group rgy_edit=> add users -f "IVP access" rgy_edit=> exit bye. csh> The add subcommand creates the DCE group called users. The exit subcommand returns control to the shell. 3. Provide namespace directory creation access for group users. In the commands shown, replace the cell name avertz_cell with the name of your cell. Preinstallation Tasks 2-7 csh> acl_edit /.../avertz_cell -m group:users:rwdtcia csh> acl_edit /.../avertz_cell -ic -m group:users:rwdtcia csh> acl_edit /.../avertz_cell -io -m group:users:rwdtc csh> cdscp show cell /.: SHOW CELL /.../avertz_cell AT 1998-7-28-16:27:01 Namespace Uuid = e484c407-d0b8-11cd-835b-08002b187bb3 Clearinghouse Uuid = e2a64d26-d0b8-11cd-835b-08002b187bb3 Clearinghouse Name = /.../avertz_cell/avertz_ch Replica Type = Master Tower = ncacn_ip_tcp:16.119.0.166[] Tower = ncadg_ip_udp:16.119.0.166[] csh> acl_edit /.../avertz_cell/avertz_ch -m group:users:rwdtc csh> The first command modifies the parent directory ACL in the cell namespace with a group entry of users, allowing all permissions to any principal that is a member of the group. The second and third commands modify the initial container creation ACL and initial object creation ACL similarly to the first command so that any subdirectories and objects subsequently created have the appropriate permissions. The fourth command displays the name of the clearinghouse to be used in the fifth command. The fifth command modifies the clearinghouse directory in the cell with a group entry of users, allowing the w permission to any principal that is a member of that group. Any principal belonging to the group can specify a namespace directory during TP system creation. For example, this access allows a member principal to create the ACMSxp default namespace directory in the cell avertz_cell. 4. Create the DCE server principal and account for the IVP and Encina SFS. In the commands shown, replace the occurrences of Celladmin_Passwd and SvrPasword with the cell_admin and server passwords in the cell. 2-8 Preinstallation Tasks csh> rgy_edit Current site is: registry server at /.../avertz_cell rgy_edit=> domain principal Domain changed to: principal rgy_edit=> add acmsxp_svr -f "IVP TPsystem default server principal" rgy_edit=> add acmsxp_svr_sfs -f "SFS server principal" rgy_edit=> domain account Domain changed to: account rgy_edit=> add acmsxp_svr -g users -o none -mp Celladmin_Passwd -pw SvrPasword rgy_edit=> add acmsxp_svr_sfs -g users -o none -mp Celladmin_Passwd -pw SvrPasword rgy_edit=> exit bye. csh> The add subcommands create the acmsxp_svr and acmsxp_ svr_sfs server principals in the namespace and adds accounts for the server principals. The string Celladmin_Passwd on the -mp option is the cell_admin account password. The string SvrPasword on the -pw option is the acmsxp_svr account password. Use this same password when you create the server key in the local directory. 5. Create the local directory for the server key files and provide access to the directory. a. Login as root. b. Create the local directory. For example: # mkdir /krb5/acmsxp # c. Provide access to the directory for the operating system account under which the IVP TPsystem is to be created. For example: # chmod 777 /krb5/acmsxp # d. Logout of root. 6. While still logged in to DCE under cell_admin, create the server keys in the local directory for each server principal. In the commands shown, replace the server password SvrPasword with the acmsxp_svr and acmsxp_svr_ sfs account passwords. For example: Preinstallation Tasks 2-9 csh> rgy_edit Current site is: registry server at /.../avertz_cell rgy_edit=> ktadd -p acmsxp_svr -f /krb5/acmsxp/acmsxp_svr -pw SvrPasword rgy_edit=> ktadd -p acmsxp_svr_sfs -f /krb5/acmsxp/acmsxp_svr_sfs -pw SvrPasword rgy_edit=> ktlist -p acmsxp_svr -f /krb5/acmsxp/acmsxp_svr /.../avertz_cell/acmsxp_svr 1 rgy_edit=> ktlist -p acmsxp_svr_sfs -f /krb5/acmsxp/acmsxp_svr_sfs /.../avertz_cell/acmsxp_svr_sfs 1 rgy_edit=> exit bye. csh> The ktadd subcommand with the -p option gives the name of the server principal (acmsxp_svr and acmsxp_svr_sfs) and with the -f option specifies the key file for the TPsystem server principal. Specify the same name for the key file and the name of the server principal. The string SvrPasword on the -pw option is the acmsxp_ svr and acmsxp_svr_sfs account passwords. The utility verifies the password and creates the server key for the principal in the named key file. Supply the same password here that you supply when you create the DCE account for the server principal. This ensures that the key in the DCE registry is the same as the key in the local file. 7. Provide access to the server key files for the operating system account under which the IVP TPsystem is to be created. For example: csh> chmod 777 /krb5/acmsxp/acmsxp_svr csh> chmod 777 /krb5/acmsxp/acmsxp_svr_sfs csh> 8. Create DCE user principals and accounts for IVP users. Do one of the following to provide DCE security for an IVP user or all users on the system: o Establish a single DCE user principal and account for the IVP. Use the rgy_edit utility to create the principal and the account in the group users. a. Set the domain to principal and use the add subcommand to create the principal. For example: 2-10 Preinstallation Tasks rgy_edit=> domain principal Domain changed to: principal rgy_edit=> add user12 -f "IVP user" rgy_edit=> The add subcommand creates the principal user12. b. Set the domain to account and use the rgy_edit add subcommand to create a DCE user account. (The name user12 is used in this example.) In the command shown, replace the occurrences of Celladmin_ Passwd and SvrPasword cell_admin and user account passwords in the cell. For example: rgy_edit=> domain account Domain changed to: account rgy_edit=> add user12 -g users -o none -mp Celladmin_Passwd -pw 2knighttwoknight rgy_edit=> The add subcommand creates an account for the user principal user12 and places the principal in the DCE group users. The string Celladmin_Passwd on the -mp option is the cell_admin account password. The string 2knighttwoknight on the -pw option is the user12 account password. (Do not use the password shown in the example. You will not have a secure account if you use a published password.) Use your specified password when logging in to DCE under the account user12 before you run the IVP. o Use an established DCE user principal for the IVP. Use the rgy_edit utility member subcommand to add a currently existing user principal to the group users. a. Set the domain to group. For example: rgy_edit=> domain group Domain changed to: group rgy_edit=> b. Use the member subcommand in the following format to add user principals to the group users: member users -a principal-name[,...] The member subcommand with the -a option adds the specified user principals to the group users. Preinstallation Tasks 2-11 c. Use the view subcommand to list the members of the group users. For example: rgy_edit=> view users -m users 2 members user12, user2 rgy_edit=> The view subcommand with the -m option displays the members of the group users. o Create DCE user principals and accounts for all user accounts on your system. Use dce_import and place the user principals in the group named users that you created. Consult the DCE documentation for guidelines on using dce_import. 9. Terminate DCE access. rgy_edit=> exit bye. csh> kdestroy csh> The commands erase the cell_admin security credentials from the network. Refer to Compaq DCE for Tru64 UNIX Release Notes for information on UCX TCP settings and to Compaq DCE for Tru64 UNIX Installation and Configuration Guide for cell configuration information. After you configure DCE for the IVP, proceed to Chapter 3 to follow the installation procedures. 2-12 Preinstallation Tasks 3 _________________________________________________________________ Installing ACMSxp Software This chapter describes how to install ACMSxp software. Before you start the installation, read Chapter 1. You can install ACMSxp locally (using CD-ROM) or from a server area. If you encounter any failures during installation, see Appendix C. 3.1 Backing Up Your System Disk Compaq recommends that you back up your system disk before installing any software. For information about backing up your system disk, see the Tru64 UNIX system documentation. 3.2 Stopping the Installation To stop the installation procedure at any time, press Ctrl/C. You must delete files created up to this point before you can restart the installation. The directories and files created during the ACMSxp installation are as follows (including the entire subdirectory tree): /usr/opt/ACMSXPV321 /var/opt/ACMSXPV321 3.3 Keeping a Record of the Installation Compaq recommends that you keep a permanent record of the installation. Either use a hardcopy terminal or log the installation in a file. To keep a log file, use the script command. For example: # script installog The script command writes to the file installog in the current working directory. Installing ACMSxp Software 3-1 3.4 Using CD-ROM Consolidated Distribution Media This procedure loads ACMSxp files on to a disk belonging to the system on which you perform the installation. When ACMSxp is run, its executable images are mapped into memory on your system. Follow these steps to install ACMSxp from CD-ROM: 1. Mount the CD-ROM on the appropriate drive. 2. Log in as superuser (login name root) to the system where you are installing ACMSxp. 3. Make sure that you are at the root (/) directory by entering the following command: # cd / 4. Specify the /cdrom directory to be the mount point for the distribution file system on the drive. If your drive is ra1, enter the following command: # mount -dr /dev/ra1c /cdrom 5. Enter a setld command that requests the load function (-l) and identifies the directory in the mounted file system where ACMSxp subsets are located. For example, if the directory location for these subsets is /cdrom/acm321/kit, enter the following command: # setld -l /cdrom/acm321/kit The installation procedure now displays the names of ACMSxp subsets and asks you to specify the subsets you want to load. See Section 3.6 to continue the installation. 3.5 Using an RIS Distribution Area If you are installing ACMSxp subsets that reside in an /etc /ris RIS distribution area on a remote system, follow these steps: 1. Log in as superuser (login name root) to the system where you are installing ACMSxp. 2. Make sure that you are at the root directory (/) by entering the following command: # cd / 3-2 Installing ACMSxp Software 3. Enter a setld command that requests the load function (-l option) and identifies the system where the ACMSxp subsets are located. For example, if you are loading ACMSxp subsets from an RIS distribution area on node orion, enter the following: # setld -l orion: Remote Installation Services now displays a menu that lists all the software subsets available to you and asks you to specify the subsets you want to load. See Section 3.6 to continue the installation. 3.6 Responding to Installation Procedure Prompts This section explains the installation procedure prompts and displays. 3.6.1 Selecting Subsets You are always asked to specify which product subsets you want to load. ACMSxp consists of three subsets as shown in Example 3-1. Example 3-1 Installation Subset Selection Display 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) ACMSxp V3.2-1 for Tru64 UNIX Base 2) ACMSxp V3.2-1 for Tru64 UNIX Man Pages 3) ACMSxp V3.2-1 for Tru64 UNIX Release Notes 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): Installing ACMSxp Software 3-3 Next, the script lets you verify your choice. For example, if you enter 4 in response to the previous prompt, you see the display shown in Example 3-2. Example 3-2 Selecting Subsets Choices (for example, 1 2 4-6): 4 You are installing the following optional subsets: ACMSxp V3.2-1 for Tru64 UNIX Base ACMSxp V3.2-1 for Tru64 UNIX Man Pages ACMSxp V3.2-1 for Tru64 UNIX Release Notes Is this correct? (y/n): If the displayed subsets are not the ones you intended to choose, enter n. The software displays the subset selection menu again and you can correct your choice of subsets. If the displayed subsets are the ones you want to load, enter y as shown in Example 3-3. Example 3-3 Verifying Subset Selection Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. (C) Copyright Digital Equipment Corporation. 1993, 1999. All Rights Reserved. The OK message indicates that there is sufficient space and the software loads the files. 3-4 Installing ACMSxp Software 3.6.2 Monitoring Displays During the Subset Loading Process The installation procedure asks no more questions, and loads and verifies the selected ACMSxp subsets. Example 3-4 shows a display from the point where you selected and confirmed the ACMSxp subset. Installing ACMSxp Software 3-5 Example 3-4 Subset Loading Process (C) Copyright Digital Equipment Corporation. 1993, 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ACMSxp V3.2-1 for Tru64 UNIX Base Copying from . (disk) Working....Thu Mar 6 11:54:41 EST 1998 Verifying Working....Thu Mar 6 11:55:39 EST 1998 (C) Copyright Digital Equipment Corp. 1993, 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ACMSxp V3.2-1 for Tru64 UNIX Man Pages Copying from . (disk) Verifying (C) Copyright Digital Equipment Corp. 1993, 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. (continued on next page) 3-6 Installing ACMSxp Software Example 3-4 (Cont.) Subset Loading Process ACMSxp V3.2-1 for Tru64 UNIX Release Notes Copying from . (disk) Verifying ACMSxp for Tru64 UNIX (BASE) successfully installed. Configuring "ACMSxp V3.2-1 for Tru64 UNIX Base" (ACMSXPVBASE321) ACMSxp for Tru64 UNIX (MAN) successfully installed. Configuring "ACMSxp V3.2-1 for Tru64 UNIX Man Pages" (ACMSXPVMAN321) Release notes may be found in /usr/opt/ACMSXPV321/ascii_docs/ACMSxp_release_notes_321.txt ACMSxp for Tru64 UNIX (RELNOTES) successfully installed. Configuring "ACMSxp V3.2-1 for Tru64 UNIX Release Notes" (ACMSXPVRELNOTES321) When you see the Verifying message during the subset installation, the installation procedure is checking to see that the files are copied correctly; it is not an IVP message. During the installation, if you get errors from the setld utility, see the Diagnostics section of the setld(8) reference page for an explanation of the errors and the appropriate actions to take. Chapter 4 explains how to run the IVP after installation, and how to delete old ACMSxp subsets before installing a new version of ACMSxp. Installing ACMSxp Software 3-7 4 _________________________________________________________________ After Installation This chapter describes actions to take after the installation to make ACMSxp ready for use and delete versions from your system. 4.1 Installing the ACMSxp Management GUI Option With the Compaq ACMSxp for Tru64 UNIX software, you have an option for the ACMSxp Administration Graphic User Interface (GUI) that you can install on a Windows NT Intel platform and use to manage your ACMSxp applications. This software provides ACMSxp system management capabilities for a PC Windows environment. Referred to as the ACMSxp Management GUI, the software provides easy access to similar functionality available through the ACMSxp Command Line Interface (CLI) director. The GUI comes with an extensive Windows Help file. 4.1.1 Prerequisite Software Before you install the GUI option, ensure that you do the following on the Windows NT Intel system: o Configure the Windows NT system to use the TCP/IP protocol. This can be a local configuration. o Establish a local disk, either NTFS or FAT, with long file names. o Install either the Compaq DCE for Windows NT Runtime Services kit or the Compaq DCE for Windows NT Application Developer's kit. o Establish access to a DCE CDS server and a DCE security server either locally or on your network. After Installation 4-1 The versions of the prerequisite software are shown in Table 4-1. Table_4-1_Prerequisite_Software_Version_Numbers____________ Software______________Version_Number_______________________ Compaq DCE 2.0 Windows_NT____________4.0_with_Service_Pack_3______________ 4.1.2 System Requirements Install the GUI software on Windows NT Intel platforms only. The software requires: o A minimum screen resolution of 800x600 pixels. o 20 megabytes of free disk space during the installation. o 10 megabytes of disk space after installation. 4.1.3 Procedures to Install the ACMSxp Management GUI To install the ACMSxp Management GUI option on the Windows NT Intel system, perform the following steps. 1. On the Windows NT system, create a new disk directory to contain the GUI option set-up software. 2. On the Windows NT system, change directory to the newly created directory. 3. From the system on which you installed the ACMSxp software, copy the self-expanding file containing the GUI option set-up software to the newly created directory. Named gui_kit_intel.exe, this file resides in the directory to which the ACMS_SYS_DIR environment variable points. 4. From the newly created directory on the Windows NT system, run the gui_kit_intel.exe file to extract the set-up files. 5. From the newly created directory on the Windows NT system, run the setup.exe program to install the ACMSxp Management GUI. 4-2 After Installation The setup.exe program asks you to choose either the companion or the standalone software option. The standalone software option is designed to run on a Windows NT system that does not have ACMSxp software installed. If you do not have ACMSxp base software installed on the Windows NT system, install the GUI standalone software option. Because the standalone software option registers environment variables that are used by other ACMSxp components, do not install this option if you have any version of ACMSxp software installed on the Windows NT system. The companion software option is designed to run on a Windows NT system with Compaq ACMSxp for Windows NT software also running. The gui_kit_readme_intel.txt file in the directory to which the ACMS_SYS_DIR environment variable points contains more information about the options. 4.1.4 Installing on a Japanese Windows NT System During the installation of the ACMSxp management GUI on a Japanese Windows NT platform, a dialog box may appear with the following error message: There is not enough disk space in one or more drives. If this message appears, click Install Now and the installation proceeds normally. 4.2 Setting Up ACMSxp Software with Japanese Language Support If you are running on an ACMSxp system with the Japanese language environment, you need to check for the existence of catalog files. If the ACMSxp catalog files do not exist, adjust your environment. 1. Determine the ACMSxp product root directory for the version that you installed. 2. Set the ACMSxp version to the one you installed. On the C shell, for example: csh> source /user1/ACMSXPV321/bin/acms_set_version.csh ACMSxp V3.2-1 for Tru64 UNIX Copyright (c) 1993, 1999 by Digital Equipment Corporation. All Rights Reserved. Using ACMSxp in /user1/ACMSXPV321/bin csh> After Installation 4-3 3. Locate the ACMSxp catalog files in a language-specific subdirectory of the msg directory under the ACMSxp root directory to which the ACMS_SYS_DIR environment variable points. On the C shell: csh> ls $ACMS_SYS_DIR/msg/ja_JP.sdeckanji/ tps_api_locale.cat csh> The ACMSxp catalog files tps.cat and tps_api.cat should be in the subdirectory for the Japanese language. 4. If the files are not in the directory, set a new value for NLSPATH environment variable as follows: csh> setenv NLSPATH "/user1/acmsxpv321/msg/%L/%N:/user1/acmsxpv321/msg/en_US.ISO8859-1/%N" csh> This setting allows access to the ACMSxp default English-language catalogs. If the files are in the directory, do not change NLSPATH. 4.3 Running the Installation Verification Procedure After installing ACMSxp, you can run the Installation Verification Procedure (IVP) independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to be sure that users can access ACMSxp. 4.3.1 IVP Overview The ACMSxp kit includes a simple IVP application. This application needs to be run separately from a normal user account, because dependencies on underlying products mean that it cannot easily be automated. As a result, the IVP is not run back-to-back with the installation from root, or from the setld utility. For ACMSxp, the command setld -v is a null operation. The IVP is self-contained, and performs cleanup operations itself, so it can be rerun whenever necessary. The IVP application itself consists of a single STDL task called ivp_task that performs a record assignment. There is no exchange I/O. 4-4 After Installation The purpose of the IVP is to check that the installation was successful and also to verify that all the dependent products are set up as needed. The IVP verifies the installation as follows: o Builds an IVP application o Creates a TP system o Starts a TP system o Shows the TP system o Creates a task server o Sets ACLs on the task server o Starts the task server o Calls a task o Stops the task server o Deletes the task server o Stops the TP system o Deletes the TP system 4.3.2 Preparing the IVP Before running the IVP, ensure that the following principals and directory are set up: o TPsystem principal name: acmsxp_svr o SFS principal name: acmsxp_svr_sfs o TPsystem and SFS key file directory: /krb5/acmsxp See Section 2.2 for the procedures to set up the DCE environment for running the IVP. 4.3.3 Invoking the IVP To run the IVP: 1. Log in as any user except for superuser (login name root). 2. Create a directory to hold the source files. For example: /usr/users/user-name/ivp_test After Installation 4-5 The string user-name is name of the login account under which you run the IVP. 3. Change to that directory: % cd /usr/users/user-name/ivp_test 4. Copy the IVP files from the ACMSxp installation area, including subdirectories, using the following command: % cp -Rp /usr/opt/ACMSXPV321/sample/ivp/* . Note that -p preserves the permissions on the files and keeps your IVP clean. 5. To obtain authenticated access, perform a dce_login as a principal that can create new namespace directories if necessary (a by-product of creating a TP System). Use the dce_login command in the following format: % dce_login user12 Enter Password: % Use the DCE user account that you created in Section 2.2 or any DCE user account whose principal is in the DCE group users. Do not log in to DCE as cell_admin or log in to the operating system as root when running the IVP. 6. Set the ACMSxp version. Bourne shell: $ . /usr/opt/ACMSXPV321/bin/acms_set_version.sh C shell: % source /usr/opt/ACMSXPV321/bin/acms_set_version.csh The software displays some information as it sets the version: ACMSxp V3.2-1 for Tru64 UNIX Copyright (c) 1993, 1998 by Digital Equipment Corporation. All Rights Reserved. Using ACMSxp in /usr/opt/ACMSXPV321/bin When the software completes, control returns to the shell prompt. 4-6 After Installation 7. Check the value of the LANG environment variable. For example: % echo $LANG LANG: Undefined variable. % If it is not set to C, proceed to the next step. If it is set to C, unset the variable because ACMSxp does not run with LANG environment variable set to C, the default UNIX setting. Bourne shell: $ unset LANG C shell: % unsetenv LANG 8. Run the IVP. For example: % . ivp.sh There is only a Bourne shell IVP. 9. The IVP runs noninteractively, performing the tasks listed in Section 4.3.1. Success of each of the tasks is checked internally by the script ivp.sh. If you receive the following message, the IVP failed: "IVP terminating for ACMSxp V3.2-1 for Tru64 UNIX". This message is preceded by an explanation. For example: Error building IVP application using make, see ./ivp_build.log In addition, output from the ACMSxp commands can help in diagnosing the cause of error. 10.Though changing names is not necessary, if you wish to change the name of either the TPsystem, the configuration database (CDB), or the namespace, edit the IVP file ivp_setup.sh and substitute one of the first three environment variables. When you rerun ivp.sh, the new names are used. After Installation 4-7 11.If the IVP runs without error, it displays the following message: "ACMSxp IVP successfully completed." If the IVP fails, fix the problem and re-run the IVP. If the IVP continues to fail and there appears to be a problem with the TPsystem registry, open the registry file in the /var/opt product directory and delete the entry for the IVP TPsystem from the file. After you close the registry file, re-run the IVP. 4.4 Deleting ACMSxp Software from Your System If you must remove a version of ACMSxp from your system, delete the subset that you previously installed. To delete subsets: 1. Log in as superuser (login name root). 2. Make sure that you are at the root directory (/) by entering the following command: # cd / 3. Enter the following form of the setld command: # setld -i | grep ACMSXP 4. Look for the word installed in the listing produced, and delete any versions that match the version you want to delete and whose status is listed as installed. For example: # setld -d ACMSXPVBASE321 ACMSXPVMAN321 ACMSXPVRELNOTES321 4.5 Running a TPsystem from the root Account If you plan to create your TPsystems to run under root, softlink ACMSxp and application message catalogs into DCE default directories. To do the softlink, log in as root and use the ln -s command. For example: # ln -s /usr/opt/ACMSXPV321/msg/en_US.ISO8859-1/* /usr/lib/nls/msg/en_US.ISO8859-1 # ln -s /usr/opt/ACMSXPV321/msg/C /usr/lib/nls/msg # 4-8 After Installation The following extract from the catopen manpage explains the need for the softlink. ___________________ catopen extract ___________________ When running in a process whose effective user ID is root, the catopen() function ignores the NLSPATH setting and searches for message catalogs by using the default path /usr/lib/nls/msg/%L/%N. Therefore, if a program (like acmslog or acmsadmin) runs with an effective user ID of root, either the program message catalogs or links to its message catalogs must reside in default directories. This restriction exists to ensure system security. ______________________________________________________ After Installation 4-9 A _________________________________________________________________ Sample Listings This appendix provides sample listings for the following procedures: o Installation of ACMSxp release notes o Installation of ACMSxp using disk media o Installation Verification Procedure (IVP) A.1 Installing Release Notes Example A-1 shows a sample of installing release notes. Example A-1 Installing Release Notes # setld -l . 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) ACMSxp V3.2-1 for Tru64 UNIX Base 2) ACMSxp V3.2-1 for Tru64 UNIX Man Pages 3) ACMSxp V3.2-1 for Tru64 UNIX Release Notes 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): 3 (continued on next page) Sample Listings A-1 Example A-1 (Cont.) Installing Release Notes You are installing the following optional subsets: ACMSxp V3.2-1 for Tru64 UNIX Release Notes Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. (C) Copyright Digital Equipment Corporation. 1993, 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ACMSxp V3.2-1 for Tru64 UNIX Release Notes Copying from . (disk) Verifying Release notes may be found in /usr/opt/ACMSXPV321/ascii_docs/ACMSxp_release_notes_321.txt ACMSxp for Tru64 UNIX (RELNOTES) successfully installed. Configuring "ACMSxp V3.2-1 for Tru64 UNIX Release Notes" (ACMSXPVRELNOTES321) # It is good practice to read the release notes before installing the other subsets. A.2 Sample ACMSxp Installation Example A-2 shows a sample of installing all ACMSxp options from CDROM. Example A-2 Installing All ACMSxp Options (continued on next page) A-2 Sample Listings Example A-2 (Cont.) Installing All ACMSxp Options # setld -l /cdrom/AXP/acmsxp/bin 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) ACMSxp V3.2-1 for Tru64 UNIX Base 2) ACMSxp V3.2-1 for Tru64 UNIX Man Pages 3) ACMSxp V3.2-1 for Tru64 UNIX Release Notes 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): 4 You are installing the following optional subsets: ACMSxp V3.2-1 for Tru64 UNIX Base ACMSxp V3.2-1 for Tru64 UNIX Man Pages ACMSxp V3.2-1 for Tru64 UNIX Release Notes Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. (C) Copyright Digital Equipment Corporation. 1993, 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. (continued on next page) Sample Listings A-3 Example A-2 (Cont.) Installing All ACMSxp Options ACMSxp V3.2-1 for Tru64 UNIX Base Copying from . (disk) Working....Thu Mar 6 11:54:41 EST 1998 Verifying Working....Thu Mar 6 11:55:39 EST 1998 (C) Copyright Digital Equipment Corporation. 1993, 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ACMSxp V3.2-1 for Tru64 UNIX Man Pages Copying from . (disk) Verifying (C) Copyright Digital Equipment Corporation. 1993, 1999. All Rights Reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ACMSxp V3.2-1 for Tru64 UNIX Release Notes Copying from . (disk) Verifying ACMSxp for Tru64 UNIX (BASE) successfully installed. Configuring "ACMSxp V3.2-1 for Tru64 UNIX Base" (ACMSXPVBASE321) ACMSxp for Tru64 UNIX (MAN) successfully installed. Configuring "ACMSxp V3.2-1 for Tru64 UNIX Man Pages" (ACMSXPVMAN321) (continued on next page) A-4 Sample Listings Example A-2 (Cont.) Installing All ACMSxp Options Release notes may be found in /usr/opt/ACMSXPV321/ascii_docs/ACMSxp_release_notes_321.txt ACMSxp for Tru64 UNIX (RELNOTES) successfully installed. Configuring "ACMSxp V3.2-1 for Tru64 UNIX Release Notes" (ACMSXPVRELNOTES321) # A.3 Sample Installation Verification Procedure Example A-3 shows a sample of running the IVP. Example A-3 IVP Sample % . ivp.sh ACMSxp V3.2-1 for Tru64 UNIX Copyright (c) 1993, 1999 by Digital Equipment Corporation. All Rights Reserved. Using ACMSxp in /usr/opt/ACMSXPV321 Installation Verification Procedure beginning for ACMSxp V3.2-1 for Tru64 UNIX IVP work subdirectory acms_work_dir does not exist. Creating it... ----------------------------------------------------------------------- Building IVP application, please wait a couple of minutes... Build complete. ----------------------------------------------------------------------- Creating the TPsystem... ACMSxp V3.2-1 for Tru64 UNIX Creating registry /staves/u2/ivp_test/acms_work_dir/acms_tpsystems.dat (continued on next page) Sample Listings A-5 Example A-3 (Cont.) IVP Sample TPsystem name [/.:/acms321/ivp]: Default namespace profile [/.:/acms321/ivp_profile]: TPsystem work directory (absolute path) [/staves/u2/ivp_test/acms_work_dir]: Configuration database [ivp]: Use file or raw disk for txn log volume? [file|disk] (file): Size of log file (in megabytes)? [4]: TPsystem Principal Name [acmsxp_svr]: TPsystem key file directory (absolute path) [/krb5/acmsxp]: TPsystem username [user1]: Create SFS Server ? [y|n] (y): SFS Principal Name [acmsxp_svr_sfs]: Creating TPsystem with: TPsystem name: /.:/acms321/ivp default namespace profile: /.:/acms321/ivp_profile work directory: /staves/u2/ivp_test/acms_work_dir configuration database: ivp transaction log file: /staves/u2/ivp_test/acms_work_dir/ivp_txnlog transaction log file size: 4 principal name: acmsxp_svr TPsystem key file directory: /krb5/acmsxp username: user1 default server username: user1 Create New SFS server: Yes SFS principal name: acmsxp_svr_sfs SFS Server Name: /.:/acms321/sfs/ivp_sfssvr SFS Logical Volume Name: ivp_sfsdatavol Creating namespace directory /.:/acms321 Setting ACLs on namespace directory /.:/acms321 Creating namespace directory /.:/acms321/sfs Creating namespace directory /.:/acms321/trpc setting ACLs on /.:/acms321/sfs setting ACLs on /.:/acms321/trpc (continued on next page) A-6 Sample Listings Example A-3 (Cont.) IVP Sample Creating the CDB... Creating TPsystem /.:/acms321/ivp ... 1 09807 96/06/05:10:48:02.272304 a8083837 W EPM: resource's name is too long (VOL_READS{/staves/u2/ivp_test/acms_work_dir/ivp_txnlog}), /gnochi/twrk01/encina/m14a/source/src/server/vol/volPhysical.c:598 1 09807 96/06/05:10:48:02.286944 a8083837 W EPM: resource's name is too long (VOL_WRITES{/staves/u2/ivp_test/acms_work_dir/ivp_txnlog}), /gnochi/twrk01/encina/m14a/source/src/server/vol/volPhysical.c:598 TPsystem successfully created ----------------------------------------------------------------------- Starting the TPsystem... ACMSxp V3.2-1 for Tru64 UNIX Press return for a list of TPsystems TPsystem name [ivp]: The SFS server is up. Starting the tpsystem /.:/acms321/ivp Waiting for servers to start up.... TPsystem successfully started ----------------------------------------------------------------------- Showing the TPsystem... TPsystem /.:/acms321/ivp AT 1998-03-05-10:49:50.802-04:00I----- Status Start Time = 1998-03-05-10:49:17.911-04:00I----- Processing State = Started Current Servers Started = 2 Software Version = "V3.2-1" Current Requests = 0 Peak Requests = 0 Peak Request Time = 1998:49:17.911-04:00I----- Characteristics (continued on next page) Sample Listings A-7 Example A-3 (Cont.) IVP Sample ACL = { "user:user1:rwxcid" } Default Namespace Profile = "/.:/acms321/ivp_profile" Default Log = "DEFAULT" Event Filter = { Audit , Fault , Security , Status } Maximum Servers Started = 30 Node = "pickup.tay1.dec.com" Principal Name = "acmsxp_svr" Key File Directory = "/krb5/acmsxp" TPsystem Username = "user1" Default Server Username = "user1" System Monitoring = False Next Transaction Logid = 7 Counters Security Events = 0 Requests Processed = 0 Reset Time = 1998:49:17.911-04:00I----- Creation Time = 1998:48:00.817-04:00I----- Show successful ----------------------------------------------------------------------- Creating the Task Server... Create successful ----------------------------------------------------------------------- Starting the Task Server... Start successful (continued on next page) A-8 Sample Listings Example A-3 (Cont.) IVP Sample Please wait... Task Server successfully started ----------------------------------------------------------------------- Invoking the task... Task ivp_task successfully invoked. ----------------------------------------------------------------------- Stopping the TPsystem... Stop successful Please wait... TP system successfully stopped ----------------------------------------------------------------------- Deleting the TPsystem... ACMSxp V3.2-1 for Tru64 UNIX Press return for a list of TPsystems TPsystem name [ivp]: Deleting TPsystem ivp ... The SFS server is up. Tpsystem ivp deleted ----------------------------------------------------------------------- ACMSxp IVP successfully completed. % Sample Listings A-9 B _________________________________________________________________ Files Installed on an ACMSxp System This appendix lists the directories and the files created during the ACMSxp installation under the ACMSxp root directory (/usr/opt/ACMSXPV321 in this example). The root directories are: ascii_docs lib sample bin man shlib include msg An ACMSxp product directory is created under the following directory: /var/opt For this release, the /var/opt/ACMSXPV321 directory holds the systemwide TPsystem registry acms_tpsystems.dat (which is created when you create your first TPsystem entity). B.1 /ascii_docs Directory ACMSxp_release_notes_321.txt acmsxp_error_messages.txt B.2 /bin Directory acms acms_foreign_server acms_create_foreign_server acms_idents.sh acms_create_tpsystem acms_product_banner.txt acms_delete_foreign_server acms_product_version.txt acms_delete_tpsystem acms_queue_svr Files Installed on an ACMSxp System B-1 acms_event_svr acms_queue_svr.idf acms_event_svr.idf acms_recqu_svr acms_recqu_svr.idf acmsadmin_help.txt acms_rsend_svr acmsdbx acms_rsend_svr.idf acmslog acms_send_errors_1_0.idf gwlog acms_set_version.csh interpretTrace acms_set_version.sh rpcutil acms_setup_cdb sfs acms_setup_tpsystem sfsadmin acms_start_tpsystem ssr acms_txnlog_svr stdl acms_txnlog_svr.idf tkadmin acms_update_tpsystem tpcontroller acms_update_tpsystems tps_smi_literal.cat acms_verify_principal translateError acmsadmin B.3 /include Directory eclass.cob tps_pthread_exc.h eclass.h tps_que.h einfo.cob tps_rec.h einfo.h tps_rec_agent.h einfo_mf.cob tps_rpc.h encina tps_rpc_apinfo_idl.h liblist tps_rpc_apinfo_idl.idl stdl_system_wksp.stdl tps_rpc_context.h stdl_system_wksp_x.stdl tps_rpc_context.idl stdldefs.h tps_rqs.h stdldefs_gs.h tps_rqs_invoke.h threadTid tps_rqs_types.h tmxa tps_sec.h tps.h tps_shm.h tps_cdb.h tps_si.h tps_cfe.h tps_si_i18n.h stdldefs_gs.h tps_sm.h threadTid tps_sma.h tmxa tps_srtl.h tps_common.h tps_stdl.h tps_common_idl.h tps_stdl.idl B-2 Files Installed on an ACMSxp System tps_common_idl.idl tps_svr.h tps_cos.h tps_tas.h tps_evt.h tps_txn.h tps_fil.h tps_txn_gw_idl.h tps_forms_def_osf.h tps_txn_gw_idl.idl tps_lst.h tps_txn_rpc_idl.h tps_msg.h tps_txn_rpc_idl.idl tps_ps.h tps_vdb.h tps_ps_decforms.h tps_wrm.h tps_ps_idl.h tran tps_pthread.h B.3.1 /include/encina Directory c_epilogue.h encina.h c_prologue.h encina_arch.h c_prologue_local.h symbols.h enc_status.h B.3.2 /include/threadTid Directory threadTid.h B.3.3 /include/tmxa tmxa.h xa.h tmxa_status.h B.3.4 /include/tran Directory tra_status.h tran.h B.4 /lib Directory libmia.a librqs.a tps_set_einfo_dec.o libsrtl.a tps_set_einfo_mf.o libtps.a tps_txn_ingres_xainit.c libtpsextfh.a tps_txn_ingres_xainit.o libxopen.a tps_txn_xainit.c tps_get_einfo_dec.o tps_txn_xainit.o tps_get_einfo_mf.o Files Installed on an ACMSxp System B-3 B.5 /man Directory man1 man3 man8 B.5.1 /man/man1 Directory acms.1 acmsdbx.1 acms_create_tpsystem.1 acmslog.1 acms_delete_tpsystem.1 acmsxp_introduction.1 acms_set_version.1 assignment.1 acms_start_tpsystem.1 audit.1 acmsadmin.1 block.1 call_presentation.1 enqueue_record.1 call_procedure.1 exception.1 call_task.1 exception_handler.1 cancel_task_submit.1 exit_block.1 conditional_statements.1 exit_task.1 data_type_definition.1 get_message.1 dequeue_record.1 goto.1 restart_transaction.1 gwlog.1 statement.1 message_group.1 statement_block.1 preprocessor_directives.1 stdl.1 presentation_group.1 stdl_syntax.1 presentation_procedure.1 submit_task.1 processing_group.1 task_argument.1 processing_procedure.1 task_attribute.1 queue_specification.1 task_definition.1 raise_exception.1 task_group.1 read_queue.1 transaction_block.1 reraise_exception.1 workspace.1 workspace_field.1 B.5.2 /man/man3 directory isbegin.3 tisam_SetCaching.3 iscommit.3 tisam_SetVolume.3 isrollback.3 tisam_interface_t.3 tisam_DumpState.3 tisam_intro.3 tisam_ErrorToString.3 tisam_issettimeout.3 tisam_Initialize.3 tmxa_RegisterRMI.3 B-4 Files Installed on an ACMSxp System B.5.3 /man/man8 Directory interpretTrace.8 sfsadmin_query_lvol.8 sfs.8 sfsadmin_query_ofd.8 sfsadmin.8 sfsadmin_query_server.8 sfsadmin_add_index.8 sfsadmin_query_tranlock.8 sfsadmin_add_lvol.8 sfsadmin_rebuild_index.8 sfsadmin_copy_file.8 sfsadmin_rename_file.8 sfsadmin_create_clusteredfile.8 sfsadmin_rename_index.8 sfsadmin_create_relativefile.8 sfsadmin_reorganize_file.8 sfsadmin_create_sequentialfile.8 sfsadmin_set_recordlimit.8 sfsadmin_deactivate_index.8 sfsadmin_terminate_ofd.8 sfsadmin_delete_index.8 tkadmin.8 sfsadmin_destroy_file.8 tkadmin_abort_ transaction.8 sfsadmin_empty_file.8 tkadmin_add_mirror.8 sfsadmin_expand_file.8 tkadmin_backup_lvol.8 sfsadmin_expand_index.8 tkadmin_clear_ exclusiveauthority.8 sfsadmin_export_file.8 tkadmin_create_logfile.8 sfsadmin_help.8 tkadmin_create_lvol.8 sfsadmin_import_file.8 tkadmin_create_pvol.8 sfsadmin_list_files.8 tkadmin_delete_disk.8 sfsadmin_list_lvols.8 tkadmin_delete_logfile.8 sfsadmin_list_ofds.8 tkadmin_delete_lvol.8 sfsadmin_query_export.8 tkadmin_delete_pvol.8 sfsadmin_query_file.8 tkadmin_disable_lvol.8 sfsadmin_query_filelock.8 tkadmin_disable_ mediaarchiving.8 sfsadmin_query_index.8 tkadmin_dump_component.8 tkadmin_map_lvol.8 tkadmin_dump_product.8 tkadmin_move_pvol.8 tkadmin_dump_ringbuffer.8 tkadmin_query_application.8 tkadmin_enable_archfile.8 tkadmin_query_authorization.8 Files Installed on an ACMSxp System B-5 tkadmin_enable_logfile.8 tkadmin_query_backup.8 tkadmin_enable_lvol.8 tkadmin_query_bufferpoolsize.8 tkadmin_enable_mediaarchiving.8 tkadmin_query_checkpointinterval.8 tkadmin_enable_server.8 tkadmin_query_component.8 tkadmin_expand_lvol.8 tkadmin_query_disk.8 tkadmin_expand_pvol.8 tkadmin_query_exclusiveauthority.8 tkadmin_flush_lvol.8 tkadmin_query_identity.8 tkadmin_force_checkpoint.8 tkadmin_query_keyfile.8 tkadmin_force_transaction.8 tkadmin_query_logvol.8 tkadmin_help.8 tkadmin_query_lvol.8 tkadmin_init_disk.8 tkadmin_query_mediaarchiving.8 tkadmin_init_logvol.8 tkadmin_query_minprotectlevel.8 tkadmin_list_components.8 tkadmin_query_principal.8 tkadmin_list_disks.8 tkadmin_query_process.8 tkadmin_list_lvols.8 tkadmin_query_product.8 tkadmin_list_products.8 tkadmin_query_pvol.8 tkadmin_list_pvols.8 tkadmin_query_redirect.8 tkadmin_list_redirect.8 tkadmin_query_restore.8 tkadmin_list_trace.8 tkadmin_query_trace.8 tkadmin_list_transactions.8 tkadmin_query_transaction.8 tkadmin_list_versions.8 tkadmin_query_workingdirectory.8 tkadmin_recover_lvols.8 tkadmin_set_exclusiveauthority.8 tkadmin_recreate_lvol.8 tkadmin_set_minprotectlevel.8 tkadmin_redirect_trace.8 tkadmin_stop_server.8 tkadmin_remap_lvol.8 tkadmin_sync_mirrors.8 tkadmin_remove_mirror.8 tkadmin_trace_component.8 tkadmin_rename_lvol.8 tkadmin_trace_product.8 tkadmin_rename_pvol.8 tkadmin_trace_specification.8 tkadmin_restore_logvol.8 tkadmin_truncate_backup.8 tkadmin_restore_lvols.8 tkadmin_unmap_lvol.8 tkadmin_retain_backups.8 tkadmin_untrace_component.8 tkadmin_set_arrivaltimequality.8 tkadmin_untrace_product.8 tkadmin_set_authorization.8 translateError.8 tkadmin_set_checkpointinterval.8 B.6 /msg Directory C ja_JP.sdeckanji en_US.ISO8859-1 B-6 Files Installed on an ACMSxp System B.6.1 /msg/C Directory adl_status.sym trace_afac.tpp adm_status.sym trace_area.tpp admin_status.sym trace_bde.tpp alf_status.sym trace_cmdline.tpp bde_status.sym trace_dceutils.tpp dceacl.sym trace_diag.tpp dceaud.sym trace_enconsole.tpp dcecds.sym trace_epm.tpp dcecdscp.sym trace_extfh.tpp dcecfg.sym trace_flt.tpp dcedb.sym trace_lock.tpp dcedce.sym trace_log.tpp dcedced.sym trace_ots.tpp dcedhd.sym trace_ppc.tpp dcedts.sym trace_ppc_cpic.tpp dceept.sym trace_ppc_gwy.tpp dceevt.sym trace_ppc_rsn.tpp dcegss.sym trace_ppc_sna.tpp dcegssdce.sym trace_ppc_snp.tpp dcelib.sym trace_ppc_tcp.tpp dcemsg.sym trace_private.tpp dcerpc.sym trace_rec.tpp dcesec.sym trace_restart.tpp dcesvc.sym trace_rqs.tpp dcesvr.sym trace_rqs_admin.tpp dcetwr.sym trace_sfs.tpp dceutils.sym trace_sfs_admin.tpp dceuuid.sym trace_sfs_btree.tpp default_status.sym trace_sfs_ddt.tpp dss_status.sym trace_sfs_dir.tpp eai_status.sym trace_sfs_ems.tpp ema_status.sym trace_sfs_es.tpp enc_status.sym trace_sfs_ie.tpp encina_status.sym trace_sfs_rel.tpp enconsole_status.sym trace_sfs_svr.tpp enp_status.sym trace_status.sym epm_status.sym trace_sutils.tpp flt_status.sym trace_tc.tpp lck_status.sym trace_threadTid.tpp lock_status.sym trace_tidl.tpp log_status.sym trace_tkadmin.tpp mon_status.sym trace_tmxa.tpp Files Installed on an ACMSxp System B-7 ots_status.sym trace_tpm.tpp ppc_status.sym trace_tran.tpp rec_status.sym trace_tranLog.tpp restart_status.sym trace_trdce.tpp ros_status.sym trace_trpc.tpp rqs_status.sym trace_tx.tpp rsa_status.sym trace_vendor_bpg.tpp rst_status.sym trace_vol.tpp sec_status.sym tran_status.sym sfs_status.sym trc_status.sym tc_status.sym trf_status.sym tmx_status.sym trp_status.sym tmxa_status.sym trpc_status.sym tra_status.sym tx_status.sym trace_admin.tpp txx_status.sym vol_status.sym B.6.2 /msg/en_US.ISO8859-1 Directory adl_status.cat tmx_status.cat adm_status.cat tps.cat alf_status.cat tps_api.cat bde_status.cat tps_api_locale.cat dss_status.cat tra_status.cat eai_status.cat trace_admin.cat ema_status.cat trace_afac.cat enc_status.cat trace_area.cat enconsole_help.cat trace_bde.cat enp_status.cat trace_cmdline.cat epm_status.cat trace_diag.cat flt_status.cat trace_enconsole.cat im_msg_strings.cat trace_epm.cat lck_status.cat trace_flt.cat log_status.cat trace_log.cat monJam_strings.cat trace_nls.cat mon_status.cat trace_ots.cat monadmin_strings.cat trace_ppc.cat ots_status.cat trace_ppc_cpic.cat ppc_status.cat trace_ppc_gwy.cat rec_status.cat trace_ppc_rsn.cat rqs_status.cat trace_ppc_sna.cat rsa_status.cat trace_ppc_snp.cat rst_status.cat trace_ppc_tcp.cat sec_status.cat trace_private.cat B-8 Files Installed on an ACMSxp System sfs_status.cat trace_rec.cat trace_restart.cat trace_rqs.cat trace_tmxa.cat trace_rqs_admin.cat trace_tpm.cat trace_sfs.cat trace_tran.cat trace_sfs_admin.cat trace_tranLog.cat trace_sfs_btree.cat trace_trdce.cat trace_sfs_dir.cat trace_trpc.cat trace_sfs_ems.cat trace_tx.cat trace_sfs_ie.cat trace_vol.cat trace_sfs_svr.cat trc_status.cat trace_sutils.cat trf_status.cat trace_tc.cat trp_status.cat trace_threadTid.cat txx_status.cat trace_tidl.cat vol_status.cat trace_tkadmin.cat B.6.3 /msg/en_US.sdeckanji tps_api_locale.cat B.7 /sample Directory add ivp avertz_vm std avertz_vr std_tpc employee B.7.1 /sample/add Directory add.make add_procedure.c add_client.c add_setup.csh add_number.stdl add_task_group.stdl add_proc_group.stdl add_tasks.stdl Files Installed on an ACMSxp System B-9 B.7.2 /sample/avertz_vm Directory /usr/opt/ACMSXPV321/sample/avertz_vm client server /usr/opt/ACMSXPV321/sample/avertz_vm/client avertz.exe avertz.hlp /usr/opt/ACMSXPV321/sample/avertz_vm/server avertz.dat sites_wksp.stdl avertz.make start_server_avertz.csh cleanup_avertz.csh stop_server_avertz.csh control_wksp.stdl vehicle_rental_history_wksp.stdl create_server_avertz.csh vehicles_array_wksp.stdl create_table_avertz.sql vehicles_wksp.stdl cu_array_wksp.stdl vm_add_task.stdl customers_wksp.stdl vm_display_task.stdl delete_server_avertz.csh vm_get_list_proc.sc destination_wksp.stdl vm_get_vehicle_proc.sc hist_wksp.stdl vm_list_task.stdl list_control_wksp.stdl vm_load_vehicles.sc ora_add_user_avertz vm_modify_task.stdl ora_create_db_avertz vm_msg_group.stdl rental_classes_wksp.stdl vm_proc_group.stdl reservations_wksp.stdl vm_ro_proc_group.stdl rs_array_wksp.stdl vm_store_vehicle_proc.sc set_avertz.csh vm_task_group.stdl set_env_avertz.csh vm_update_vehicle_proc.sc si_array_wksp.stdl B.7.3 /sample/avertz_vr Directory B-10 Files Installed on an ACMSxp System vr_check_ve_avail_task.stdl vr_menu_task.stdl vr_checkin_task.stdl vr_menu_wksp.stdl vr_checkout_task.stdl vr_mod_ve_avail_task.stdl vr_control_wksp.stdl vr_msg_grp.stdl vr_count_rs_task.stdl vr_rent_task_grp.stdl vr_do_ckout_or_cncl_task.stdl vr_reserve_task.stdl vr_find_cu_task.stdl vr_resv_task_grp.stdl vr_find_rs_cu_task.stdl vr_rs_ro_proc_grp.stdl vr_find_rs_task.stdl vr_rs_rw_proc_grp.stdl vr_find_si_task.stdl vr_store_cu_task.stdl vr_find_ve_task.stdl vr_update_rs_task.stdl vr_get_ve_data_task.stdl vr_ve_ro_proc_grp.stdl vr_get_ve_hist_task.stdl vr_ve_rw_proc_grp.stdl vr_getresv_task.stdl vr_ve_task_grp.stdl vr_hist_proc_grp.stdl vr_write_rs_task.stdl B.7.4 /sample/employee Directory /usr/opt/ACMSXPV321/sample/employee client server /usr/opt/ACMSXPV321/sample/employee/client employee.exe employee_uwc.h employee_cli.make res employee_uwc.c /usr/opt/ACMSXPV321/sample/employee/client/res This directory is reserved for future use. /usr/opt/ACMSXPV321/sample/employee/server acms_create_employee_db employee_record.stdl admin_setup.csh employee_server_oracle.make control_record.stdl employee_setup.csh empl_msg_grp.stdl employee_setup_oracle.sql employee_proc_grp.stdl employee_task_grp.stdl employee_procs_oracle.sc employee_tasks.stdl B.7.5 /sample/ivp Directory Makefile ivp_setup.sh ivp.c ivp_task.stdl ivp.sh ivp_task_group.stdl workspaces.stdl Files Installed on an ACMSxp System B-11 B.7.6 /sample/std Directory Makefile READ_ME_UNIX.TXT std7.csh STDMFCOBOL.cob std8.csh STD_MC_COBOL.COB std9.csh add_acmsxp_principals.sh std_cwp.stdl check_for_oracle_db.csh std_mt_uwc.c create_oracle_db.csh std_proc_dec_cob.stdl employee.h std_proc_mf_cob.stdl profile.h std_proc_svr_a.stdl std10.csh std_read_sql.sco std14.csh std_setup.csh std15.csh std_sql.sc std16.csh std_task_groups.stdl std18.csh std_task_groups_a.stdl std18_uwc_uwp.c std_task_groups_b.stdl std19.csh std_task_svr.stdl std19_uwc_uwp.c std_task_svr_a.stdl std20.csh std_task_svr_b.stdl std3.csh std_uwc.c std3a_uwc_uwp.c std_uwp.c std5.csh std_wait.csh std6.csh std_wksp_def.stdl std6_uwc_uwp.c std_write_sql.sco std6a.csh temp std6a_uwc_uwp.c twrk /usr/opt/ACMSXPV321/sample/std/temp /usr/opt/ACMSXPV321/sample/std/twrk These directories are empty after installation. B.7.7 /sample/std_tpc Directory std_clean_up.csh std_startup.csh std_setup_tpc.csh temp std_shutdown.csh twrk /usr/opt/ACMSXPV321/sample/std_tpc/temp /usr/opt/ACMSXPV321/sample/std_tpc/twrk These directories are empty after installation. B-12 Files Installed on an ACMSxp System B.8 /shlib Directory libEncClient.so librqs.so libEncServer.so libsrtl.so libEncSfs.so libtps.so libEncSfsExtfh.so libtpsextfh.so libEncina.so libxopen.so libcrl.so stdl_cnv_stdlwire.so libmia.so Files Installed on an ACMSxp System B-13 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. If you find an error in the documentation, fill out and submit a report on the document that contains the error. Include the section and page number of the error. 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 shown in Example C-1 appears. Example C-1 Sample Installation Failure Message There is not enough space for subset ACMSXPVBASE321 ACMSXPVBASE321 will not be loaded. 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 The values for kernel attributes are insufficient. For descriptions of error messages generated by these conditions, see the Tru64 UNIX documentation on system messages, recovery procedures, and Tru64 UNIX software installation. For information on system software requirements, see Section 1.4.3. Recovering from Errors C-1 C.2 Failures During Product Use If an error occurs while ACMSxp software 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: - Name and version number of the operating system you are using - Version number of ACMSxp you are using - Hardware system you are using (such as a model number) - 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). o If you do not have any type of software services support agreement and you purchased ACMSxp 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 ACMSxp software being used. Demonstrate the problem with specific examples. 2. Reduce the problem to as small a size as possible. 3. Include listings of any command files, INCLUDE files, or relevant data files, and so forth. 4. Provide a listing of the program. C-2 Recovering from Errors 5. Report only one problem per SPR. This facilitates a faster response. 6. Mail the SPR package to Compaq Computer Corporation. Recovering from Errors C-3 _________________________________________________________________ Index A Directories (cont'd) _______________________________ var, B-1 ascii_docs directory, B-1 Disk space, 1-5 Attributes checking, 1-6 kernel minimums, 2-2 IVP, 1-5 modifying kernel, 2-1 doconfig, 2-5 B______________________________ E______________________________ bcheckrc, 2-6 Errors Bill of materials, 1-2 installation, C-1 bin directory, B-1 IVP, 4-7 messages text file, B-1 C______________________________ product use, C-2 CD-ROM, 1-2, 1-3, 3-2 recovering, C-1 celladmin setld, 3-7 login, 2-7 F______________________________ D______________________________ fstab, 1-6 DCE IVP G______________________________ keys for server, 2-9 GUI server principal and installing management, 4-1 account, 2-8 procedures, 4-2 set-up for IVP, 2-6 Japanese system, 4-3 Directories prerequisite software, 4-1 ascii_docs, B-1 system requirements, 4-2 bin, B-1 gui_kit_intel.exe file, 4-2 include, B-2 lib, B-3 man, B-4 msg, B-6 sample applications, B-9 shlib, B-13 Index-1 msg directory, B-6 H______________________________ softlink for, 4-8 Hardware requirements, 1-3 P______________________________ I______________________________ Privileges include directory, B-2 login, 1-3 Installation CDROM use, 3-2 R______________________________ errors, 3-7, C-1 Reboot failures during, 3-1 procedure for, 2-6 keeping a record, 3-1 Release notes loading subsets, 3-2 online, 1-1 prompts, 3-3 RIS release notes, A-1 distribution area, 3-2 requirements, 1-2 to 1-6 using, 1-7 RIS, 3-2 Root account, 4-8 sample, A-2 selecting subsets, 3-3 S______________________________ stopping, 3-1 sample directories, B-9 time required, 1-2 setld IVP -d, 4-8 DCE procedures, 2-6 errors, 3-7 description, 4-4 -i, 1-4 sample, A-5 -l, 3-2, 3-3 K -v, 4-4 _______________________________ setup.exe program, 4-2 Kernel shlib directory, B-13 copying old, 2-6 shutdown, 2-6 license in cache, 1-2 Software modifying attributes, 2-1 checking contents, 1-2 rebuilding, 2-5 license, 1-1 requirements, 1-3 L______________________________ SPR, C-2 lib directory, B-3 Storage License backing up system disk, 3-1 copying to kernel cache, 1-2 free disk space, 1-6 software, 1-1 Subsets ACMSxp, 1-5 M checking, 1-4 _______________________________ deleting, 4-8 man directory, B-4 required, 1-3 maxusers selecting, 3-3 determining value, 2-5 Index-2 Support, C-2 System reboot, 2-6 V______________________________ var directory, B-1 Index-3