Digital DEC/EDI Installation Compaq Computer Corporation Houston, Texas Revised for Software Version: Digital DEC/EDI V4.0 November 2001 (c)Compaq Computer Corporation 1990,2001 Compaq, the Compaq logo, and VMS Registered in U.S. Patent and trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX is a trademark of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. This document is the property of, and is proprietary to Compaq Computer Corporation. It is not to be disclosed in whole or in part without the express written authorization of Compaq Computer Corporation. No portion of this [enter document] shall be duplicated in any manner for any purpose other than as specifically permitted herein. Compaq service tool software, including associated documentation, is the property of and contains confidential technology of Compaq Computer Corporation. Service customer is hereby licensed to use the software only for activities directly relating to the delivery of, and only during the term of, the applicable services delivered by Compaq or its authorized service provider. Customer may not modify or reverse engineer, remove, or transfer the software or make the software or any resultant diagnosis or system management data available to other parties without Compaq's or its authorized service provider's consent. Upon termination of the services, customer will, at Compaq's or its service provider's option, destroy or return the software and associated documentation in its possession. Printed in the U.S.A. The following are trademarks of Compaq Computer Corporation : DEC, DEC/EDI, DIGITAL, OpenVMS, and the Compaq logo. Adobe is a registered trademark of Adobe Systems Incorporated. BT is a registered trademark of British Telecommunications plc. InstallShield is a registered trademark of InstallShield Corporation. MS and Windows are registered trademarks, and Windows 95, Windows 98, Windows NT and Windows 2000 are trademarks, of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation. SAP is a registered trademark of SAP AG. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks not listed above are acknowledged as the the property of their respective holders. Contents Preface Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii How to Use this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Digital DEC/EDI Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Digital DEC/EDI InfoCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Related Third Party Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Chapter 1 Preparing to Install Digital DEC/EDI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Digital DEC/EDI System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Application Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Product Installation Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Digital DEC/EDI User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Digital DEC/EDI INTERCHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Establishing the Configuration of Your System . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Single Node System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Multi-node Client/Server System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Cockpit and CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 iv Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Communication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Digital DEC/EDI Message Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Application Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Tru64 UNIX, Sun Solaris, HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Application Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Tru64 UNIX, Sun Solaris, HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 RedHat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Cockpit and CommandCenter Configuration . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Windows NT, Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Database Configuration (ODBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Server Communications Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 Chapter 2 Installation Activities Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Setting Up the Server and Local Application Clients . . . . . . . . . . . . . . . . . . . 2-3 Setting Up Remote Application Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Setting Up the CommandCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Setting Up the Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Configuring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 v Part I Network Configuration Chapter 3 Configuring the Network Interfaces Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Configuring the Digital DEC/EDI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 TCP/IP Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Pre-Configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Post-Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 For Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 TCP/IP Port Server Monitoring Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Configuring the Digital DEC/EDI Application Client . . . . . . . . . . . . . . . . . . . 3-8 TCP/IP Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 Pre-Configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Post-Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 For Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Part II Database Administration Chapter 4 Configuring the Database Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Account Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Open VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Configurations Covered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Setting Up Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 A - Deciding Where to Locate the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Oracle8i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Typical Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 OpenVMS Oracle Rdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Performance Limiting Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 B - Creating the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 All Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 vi Typical Oracle 8i Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Typical Oracle Rdb Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Migrating the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Creating User Accounts for Database Access . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Digital DEC/EDI Access Control Editor . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Tru64 UNIX Oracle8i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 OpenVMS Oracle Rdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Oracle User Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Configuring the Database Network Connectivity . . . . . . . . . . . . . . . . . . . . . 4-12 OpenVMS Oracle SQL Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Tru64 UNIX Oracle 8i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 Part III Software Installation Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Preparing to Install Digital DEC/EDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Additional Information on Digital DEC/EDI Subsets . . . . . . . . . . . . 5-6 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 Registering Your Software Licenses on Digital Systems . . . . . . . . . . . . . 5-8 Registering Licenses on Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . 5-10 Installation Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Database Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Run Time Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 vii TCP/IP Link Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Checking Tru64 UNIX Documentation Subset is Installed . . . . . . . . 5-14 Checking that Oracle8i is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Setting Oracle8i Environment Variables . . . . . . . . . . . . . . . . . . . . . . 5-16 Running the Oracle8i Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16 Checking for Individual Oracle8i Components . . . . . . . . . . . . . . . . . 5-16 Checking for the Server Manager and DBMS . . . . . . . . . . . . . . . . . . 5-17 Checking for Oracle8i SQLPLUS . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Checking for TCP/IP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Checking Mailbus 400 is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Checking DEC X.25 is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Checking the Digital DEC/EDI account . . . . . . . . . . . . . . . . . . . . . . 5-18 Adding a Digital DEC/EDI Account . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19 Determining Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20 Deleting Digital DEC/EDI from Your System . . . . . . . . . . . . . . . . . . . . . 5-21 Backing Up Your System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22 Installing Digital DEC/EDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Stopping the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Time Required for Complete Installation . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 Installing From CD-ROM Consolidated Distribution Media . . . . . . . . . . 5-24 Installing From a Remote Installation Services (RIS) Distribution Area . 5-25 Running the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26 Specifying Subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26 Messages Displayed During the Loading Process . . . . . . . . . . . . . . . 5-28 Problems During Product Installation . . . . . . . . . . . . . . . . . . . . . . . . 5-28 Files Created During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29 After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29 Installation Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29 Running the Installation Verification Procedure . . . . . . . . . . . . . . . . . . . 5-30 Setting Up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Problems After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32 Chapter 6 OpenVMS - Installation of Server and Client Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Prerequisites - All Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 viii Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Software Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Mapping Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 OpenVMS Alpha Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Mandatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Pedi Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 3780Plus Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Application Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Supported Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 OpenVMS Alpha Application Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Mandatory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Software Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Privileges For The Installing Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Disk Space Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Determining Diskspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10 Checking System Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11 Calculating Values for GBLPAGES and GBLSECTIONS . . . . . . . . . . . 6-12 Changing System Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Account Quotas For The Installing Account . . . . . . . . . . . . . . . . . . . . . . . . . 6-14 Changing Account Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 Other Pre-Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Accessing the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16 Files and Logical Names Added to Your System . . . . . . . . . . . . . . . . . . 6-16 Running the Installation Verification Procedure (IVP) . . . . . . . . . . . . . . 6-16 VMSINSTAL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Aborting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Time to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Information Needed During Installation . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Upgrades Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18 Installation: Client On Top Of Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19 Installation: Server On Client-Only System . . . . . . . . . . . . . . . . . . . . . . . . . 6-19 Upgrading to V4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 ix General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Installing on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 Migration Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20 All Services on a Single Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21 Multinode System with Translation and Communications all on One Node 6-21 The Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22 Starting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23 About Client-Only Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25 Warning if you are Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25 Remainder of the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27 Installation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28 Completing the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29 Installing the Message Update Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30 After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31 Editing the System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32 System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32 Network and Rdb Monitor Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33 Defining Digital DEC/EDI Logical Names . . . . . . . . . . . . . . . . . . . . . . . 6-33 Using the Correct Pascal Run-Time Library . . . . . . . . . . . . . . . . . . . . . . 6-34 Modifying the System Page File Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34 Re-booting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35 Re-naming the Digital DEC/EDI Error Log . . . . . . . . . . . . . . . . . . . . . . . 6-35 Modifying User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36 Page File Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36 Access From a Local Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36 Adding Symbols to User's LOGIN.COM . . . . . . . . . . . . . . . . . . . . . 6-36 Determining and Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . 6-37 The DECEDI Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38 Increasing Disk Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39 Calculating the Required Number of Processes . . . . . . . . . . . . . . . . . 6-40 Modifying Quota for the DECEDI Account . . . . . . . . . . . . . . . . . . . . . . . 6-41 Calculating the WSEXTENT Value . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41 Calculating the ENQLM Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41 Ownership of the DECEDI Account . . . . . . . . . . . . . . . . . . . . . . . . . 6-42 Account privileges on the DECEDI Account . . . . . . . . . . . . . . . . . . 6-42 x Defining Mapping Service Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43 The Rights Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44 FBR$SUPERVISOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44 FBR$DEVELOPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45 FBR$OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46 Upgrades - Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46 Files Created During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46 Chapter 7 Other Platforms - Installation of Digital DEC/EDI Application Client Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Preparing to Install on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . 7-2 Checking Installation Procedure Requirements . . . . . . . . . . . . . . . . . 7-2 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Determining Which Subsets to Load . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . 7-3 Backing Up Your System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Preparing to Install on Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Checking Installation Procedure Requirements . . . . . . . . . . . . . . . . . . . . 7-5 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Determining Which Subsets to Load . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . 7-6 Backing Up Your System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 Installing the Digital DEC/EDI Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8 Installing From CD-ROM Consolidated Distribution Media . . . . . . . . . . 7-8 Installing From an RIS Distribution Area . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 Running the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 Specifying Subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10 xi Messages Displayed During the Loading Process . . . . . . . . . . . . . . . 7-10 After Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11 After the Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11 Running the Installation Verification Procedure . . . . . . . . . . . . . . . . . . . 7-11 Deleting Digital DEC/EDI Application Client from Your System . . . . . 7-12 DIGITAL DEC/EDI Application Client on Redhat Linux . . . . . . . . . . . . . . . 7-12 Preparing to Install on Redhat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Checking the Installation Procedure Requirements . . . . . . . . . . . . . . . . . 7-13 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Backing up your System Disk: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14 Installing from the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14 After Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15 Configuring the Applicatin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15 Deleting DEC/EDI Application Client from your System . . . . . . . . . . . . 7-15 DIGITAL DEC/EDI Application Client on Windows NT/ 2000 . . . . . . . . . . 7-16 Preparing to Install on Windows NT/ 2000 . . . . . . . . . . . . . . . . . . . . . . . 7-16 Reading the Online Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking the Software Distribution Kit . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking the Installation Procedure Requirements . . . . . . . . . . . . . . . . . 7-16 Checking Login Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 Checking Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Determining Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Installing from the Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Chapter 8 Managing Message Updates Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Using the Message Update Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Tru64 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Tru64 UNIX and OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 xii Installing New Versions of EDI Standards . . . . . . . . . . . . . . . . . . . . . 8-3 Copying Existing Versions to New Ones . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Copying Data Labels Between Versions . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Deleting a Version of an EDI Standard . . . . . . . . . . . . . . . . . . . . . . . 8-4 Dealing with Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Where to Look If Things Go Wrong . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Check your Cockpit or CommandCenter Kit . . . . . . . . . . . . . . . . . . . . . . 9-1 CommandCenter Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Cockpit Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Check for Prerequisite Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 Check for Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Backup your Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Additional Notes on Installing Pre-requisite Software . . . . . . . . . . . . . . . 9-5 Pre-Installation Tasks for Oracle 8i on the PC . . . . . . . . . . . . . . . . . . . . . 9-5 Checking for the Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Time to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Server Configuration Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12 Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13 General Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13 Tru64 UNIX Server - Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . 9-15 TCP/IP Network Interface related Problems . . . . . . . . . . . . . . . . . . 9-15 OpenVMS Server - Problem Solving . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 ODBC-related problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 Getting More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 The Digital DEC/EDI Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 ODBC Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19 SQL/Services Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19 Network Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 xiii TCP/IP Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21 Part IV System Verification Chapter 10 UNIX System Verification Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Beyond the Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3 An Example Application File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4 Preparation Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 A: Installing the Software and EDI Definitions . . . . . . . . . . . . . . . . . . . . . . . 10-6 B: Configuring the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9 Configure Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9 Register the Client Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10 Define Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11 C: Compiling the Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12 D: Defining Gateway and Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Defining the Gateways: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Creating the Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13 Enabling the Gateway and Connection . . . . . . . . . . . . . . . . . . . . . . . . . 10-14 E: Adding Trading Partner Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15 F: Restart the Digital DEC/EDI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17 G: Running the Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18 Sending the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18 Network Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20 Troubleshooting Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21 Tracing in the TCP/IP Client/Server Interface . . . . . . . . . . . . . . . . . . . . 10-21 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21 ODBC-related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21 Chapter 11 OpenVMS System Verification Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 xiv Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 About the Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Beyond the Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3 An Example Application File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4 Preparation Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5 A: Installing the Software and EDI Definitions . . . . . . . . . . . . . . . . . . . . . . . 11-6 B: Configuring the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8 Granting User Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8 Configure Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9 C: Compiling the Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10 D: Configuring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 Registering the Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 Registering the Business Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11 Registering a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12 E: Adding Trading Partner Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13 F: Start the Digital DEC/EDI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14 G: Running the Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15 Sending the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15 Network Tester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17 Troubleshooting Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18 ODBC Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18 SQL/Services Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19 Tracing in the TCP/IP Client/Server Interface . . . . . . . . . . . . . . . . . . . . 11-19 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19 ODBC-Related Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21 Appendix A OpenVMS Server and Client Log of New Server and Client Installation on OPEN VMS AXP . . . . . . . . . . A-1 Log of Migration of Server and Client on OPEN VMS AXP . . . . . . . . . . . . . A-9 Appendix B OpenVMS Client only Log of New Client Installation of OPEN VMS AXP . . . . . . . . . . . . . . . . . . . B-1 Log of Migration of Client on OPEN VMS AXP . . . . . . . . . . . . . . . . . . . . . . B-4 xv Appendix C OpenVMS Message Updates Kit Appendix D Digital UNIX Server and Client Installtion Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Deinstalltion Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Appendix E DIGITAL UNIX Client only Appendix F DIGITAL UNIX Message Updates Appendix G Sun Solaris Client Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Deinstallation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Directory and File listing for SUN Solaris Client . . . . . . . . . . . . . . . . . . . . . . . 32 Appendix H HP-UX Client Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Installtion Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Configuration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Deinstallation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Directory and File listing for HP-UX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Appendix I RedHat Linux Client Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Configuration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Deinstallation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Directory and File listing for Redhat Linux Client . . . . . . . . . . . . . . . . . . . . . . 43 xvi Appendix J Directory and File listing for Windows NT/2000 Client Appendix K UNIX Installation - Directory and File Listing Appendix L OpenVMS Installation - Directory and File Listing Preface Purpose For Digital DEC/EDI Version 4.0 This book describes how to install the following Digital DEC/EDI components: • Server • Application Client • Message Updates • Cockpit • CommandCenter Enables you to perform basic system configuration, to ensure that Digital DEC/EDI is installed and configured correctly, and can communicate with other Digital DEC/EDI components installed within the same network. Audience This document is for anyone who wants to install, configure or support a Digital DEC/EDI installation.The audience for this book may be described in terms the activities required for a successful installation and basic configuration of a Digital DEC/EDI system. These activities may be performed by one or more people within your organization. Software Installation System Managers and Administrators who are responsible for installing Digital DEC/EDI and its related components on the required operating system. Network Configuration Network administrators who are responsible for performing any network configuration required to enable Digital DEC/EDI components located within the same network to communicate with one another. Database Administration Database administrators who are responsible for setting up the required user accounts, access rights or ODBC drivers for the database used by the Digital DEC/EDI software. For detailed configuration of Digital DEC/EDI and its external communications components please refer to the Digital DEC/EDI: User's Guides (Digital UNIX and Open VMS) Structure • Part 1 - describes the preparation necessary before starting installation. • Part 2 - describes network configuration • Part 3 - describes database installation and configuration • Part 4 - covers the Client and Server software installation • Part 5 - describes basic system verification • Part 6 - provides a set of appendices giving installation examples and a listing of the files installed. How to Use this Book This book details the preparation, installation, post-installation and basic configuration tasks that must be completed in order to successfully install the Digital DEC/EDI software components on the supported hardware and software platforms. The book also provides sample installation logs and screen captures for your guidance during the installation process. An existing user of the Digital DEC/EDI product wishing to upgrade or migrate to this version of Digital DEC/EDI, must read the chapter on upgrading and migration. Completion of all tasks stipulated is essential to successful upgrading or migration from a previous version of Digital DEC/EDI. The book is organized to enable easy location of information relating to the installation activities for the required Digital DEC/EDI configuration. Read Part I of this book from start to finish, and then read the sections that relate to the required Digital DEC/EDI configuration. Digital DEC/EDI Documentation This is one of a set of Digital DEC/EDI books. The complete list is as follows: • Digital DEC/EDI: Introduction This book introduces general EDI concepts, and Digital's EDI system, Digital DEC/EDI. It describes the main components of the Digital DEC/EDI system, and how business documents are processed and communicated to trading partners. The book seeks to establish the concepts and terms used by Digital DEC/EDI. These are also summarized in a glossary. You are strongly recommended to become familiar with the material in this book before proceeding to install or use Digital DEC/EDI. • Digital DEC/EDI: Installation This book describes how to install the Digital DEC/EDI software, how to perform basic system configuration and how to verify such an installation. It describes how to install the Application Client, Server, Cockpit and CommandCenter components. • Digital DEC/EDI: Application Development This book describes the Application Client interfaces and the means of connecting business applications to the Application Client. It also details the creation and deployment of mapping tables as part of the process of integrating applications with Digital DEC/EDI. • Digital DEC/EDI: User's Guides (Digital UNIX and Open VMS) These guides contain information on setting up and operating Digital DEC/EDI systems. They also contain information covering configuration, maintenance and problem solving. The term User's Guides is used throughout this book to refer to the following books which are provided along with the Digital DEC/EDI Server they describe. Digital UNIX Digital DEC/EDI: UNIX User Support Manual OpenVMS Digital DEC/EDI: OpenVMS User Support Manual - Volume 1 Digital DEC/EDI: OpenVMS User Support Manual - Volume 2 • Release Notes Further to the above, each software kit contains a set of release notes applicable to that software. These release notes contain information about known product problems (with workarounds where appropriate) and any operational tips or hints not provided as part of the above documentation set. You are strongly recommended to review these release notes before installing the software. Refer to the appropriate installation guide for information on how to locate the release notes. • On-line Documentation Comprehensive on-line documentation is supplied with the Digital DEC/EDI software: for example, on-line help libraries and UNIX man page help information. In addition the Digital DEC/EDI Cockpit and CommandCenter kits contains the Digital DEC/EDI: Error Messages Help Library. This contains all error messages the product may log along with a description of why the message occurred and what to do about it. It is provided in MS-Windows help library format. In addition, the CD-ROM provides on-line versions of all Digital DEC/EDI books in Adobe Acrobat format. Digital DEC/EDI InfoCenter For further information on Digital's EDI and Electronic Commerce Solutions and Services, please visit the EDI InfoCenter on the World Wide Web. The location is: http://www.decedi.com Related Third Party Documentation Refer to the documentation provided with third-party products for installation and configuration details. Typographical Conventions Some information within this guide is specific to the database product you are using in conjunction with Digital DEC/EDI. The following conventions are used to indicate such text: Oracle8 This indicates the adjoining paragraph contains information specific to running Digital DEC/EDI with the Oracle8 database. Similar conventions are used to indicate text specific to other components. For example: • Rdb refers to the Oracle(r) Rdb(tm) database. • V4.0 refers to Cockpit Version V4.0. Chapter 1 Preparing to Install Digital DEC/EDI This chapter describes what actions are necessary prior to installation of Digital DEC/EDI. Overview Before installing Digital DEC/EDI there are a number of things which need to be determined about your system, and the configuration in which you intend to run Digital DEC/EDI. It is not necessary to know everything about all the systems on which you will be using Digital DEC/EDI at this stage, as you may add further components or systems at a later date. Digital DEC/EDI System Configuration The collection of systems within the same network, on which Digital DEC/EDI and its components are installed, is known as the Digital DEC/EDI system configuration. The different parts are described on the following pages. Server The Server acts as a communications gateway, providing EDI mapping, translation and communications services for one or more Application Client systems. You may have one or more Server systems within your Digital DEC/EDI system configuration. 1-2 Digital DEC/EDI User Interfaces PREPARING TO INSTALL DIGITAL DEC/EDI A typical system configuration may have one Server for live EDI transactions, and another for backup or development use. Application Client The Application Client provides a file based interface to your business application, and may operate either via a command line or script- based interface, or via API calls directly from the business application. One or more Application Clients may communicate with the Server. The Application Client may reside on the same system as the Server, or may be on another system within the same network. A typical system may have many Application Clients communicating with a Server. Product Installation Documentation Installation instructions are provided in the documentation associated with each product described in this chapter. Digital DEC/EDI product documentation is described in Digital DEC/EDI Documentation on page -xv of the Preface. Digital DEC/EDI User Interfaces Cockpit The Cockpit is a monitoring and basic audit administration tool which runs on a PC connected to the Server. The Cockpit can be used to monitor multiple Servers simultaneously. Access controls enable you to restrict the data which may be either viewed or modified by a particular user of the Cockpit. A typical system may have multiple Cockpit installations for a number of users, each responsible for monitoring a particular set of business applications. CommandCenter The CommandCenter includes the Cockpit plus the ability to define Mapping Tables for integrating your business applications. The CommandCenter runs on a PC connected to the Server. For Tru64 UNIX Establishing the Configuration of Your System 1-3 PREPARING TO INSTALL DIGITAL DEC/EDI servers, the CommandCenter also includes a suite of applications for configuring and managing the Server. The CommandCenter may be used to manage one or more Servers simultaneously. A typical system may have multiple CommandCenter installations for a number of users, each responsible for integrating a particular set of business applications, or for configuring and managing one or more Servers. Digital DEC/EDI INTERCHANGE For OpenVMS servers, the INTERCHANGE user interface provides commands for configuring and managing the Server, and for monitoring EDI transactions. The INTERCHANGE user interface runs on the same system as the Server. Establishing the Configuration of Your System Digital DEC/EDI supports a number of different system configurations, and you must determine the desired system configuration before proceeding with the installation of Digital DEC/EDI and its components. The following section describes the supported configuration options, and directs you to the relevant parts of the Digital DEC/EDI documentation set that describe the installation of those options. Supported Configurations This section describes the supported configurations and interconnection options between the various components of Digital DEC/EDI. Single Node System Your business application runs on the same node as the Server, or you have a custom module which is responsible for transferring files to and from your business application. Your business application uses either the Application Client interface or one of the supported legacy interfaces (where available) to connect to the Server. The following figure shows a typical single node system configuration: 1-4 Establishing the Configuration of Your System PREPARING TO INSTALL DIGITAL DEC/EDI Figure 1-1 Single Node System Multi-node Client/Server System Your business application runs on a separate node from the Server and uses the Application Client interface to connect to the Server. The following figure shows a typical multi-node Client/Server system: Mapping Services Translation Services Communications Services Server Local Application Client Server System Data Label Translation API Bypass API Network Interface = Legacy interfaces, OpenVMS Only Trading Partners RedHat Linux Windows Client Application Client Application Client Establishing the Configuration of Your System 1-5 PREPARING TO INSTALL DIGITAL DEC/EDI Figure 1-2 Multi-node Client/Server system: Cockpit and CommandCenter In addition, you may install the Cockpit and CommandCenter GUI components on one or more PCs within the same network. A separate license is required for each PC on which the Cockpit or CommandCenter is installed. You may use the Cockpit and CommandCenter to monitor and configure one or more Server systems. The following figure shows a typical configuration with several Cockpit installations and a CommandCenter installation communicating with multiple Servers: Mapping Services Translation Services Communications Services Server Network Interface Local OpenVMS Tru64 UNIX Sun Solaris HP-UX Application Client Application Client Application Client Application Client Application Client Server System Remote Systems Trading Partners RedHat Linux Windows Client Application Client Application Client 1-6 Server Configuration PREPARING TO INSTALL DIGITAL DEC/EDI Figure 1-3 Cockpit and CommandCenter Configuration Server Configuration This section describes the components that you need to install on the designated Server node. Network Interface The network interface provides the means to exchange files and data between the Application Client, Cockpit or CommandCenter and the Server. The Server can support multiple simultaneous connections using any of the available network interfaces. Note: A network interface is required even on a single node system, to support interprocess communication between the Application Client and the Server. Development System Production System Supervisors Cockpit Cockpit Developer CommandCenter Cockpit Test Engineer Trading Partners Digital DEC/EDI Server Digital DEC/EDI Server Server Configuration 1-7 PREPARING TO INSTALL DIGITAL DEC/EDI OpenVMS On an OpenVMS Server, you must select the following Network interface: TCP/IP only The OpenVMS system must have DEC TCP/IP Services installed and configured. Tru64 UNIX On a Tru64 UNIX Server, you must select the following Network interface: TCP/IP only The Tru64 UNIX system must be configured with the TCP/IP implementation supplied with Tru64 UNIX. Database The database provides the means of auditing application files, documents and transmission files processed by the Server system. On Tru64 UNIX, the database additionally provides the means of storing the Server configuration details. OpenVMS On an OpenVMS Server the following database components are required: ORACLE Rdb You need to have a minimum of the run-time components licensed and installed. ORACLE SQL/Services for Rdb This is required if you intend to use the Cockpit or CommandCenter to access the Server. Tru64 UNIX On a Tru64 UNIX Server you need to select the following database options: ORACLE 8i You need to install ORACLE 8i, and the required components to support the Cockpit and CommandCenter. Server Software OpenVMS On OpenVMS, the VMSINSTAL command is used to install Digital DEC/EDI from the supplied media. To install the Server, you must select the server installation option. 1-8 Application Client Configuration PREPARING TO INSTALL DIGITAL DEC/EDI The Server installation includes support for translation of ANSI X12, TDCC (UCS/WINS), EDIFACT, ODETTE and TRADACOMS standards, and industry-specific and trading partner specific variations of those standards. Tru64 UNIX On Tru64 UNIX, the setld command is used to install Digital DEC/EDI from the supplied media. You may select specific subsets to install, depending on the communications and translation options you require from the following: X12 This includes support for translation of ANSI X12 and TDCC (UCS/WINS) transactions, and industry-specific and trading partner specific variations. EDIFACT This includes support for translation of UN EDIFACT and ODETTE messages, and industry-specific and trading partner specific variations. TRADACOMS This includes support for translation of TRADACOMS messages, and industry-specific and trading partner specific variations. Communication Options Refer to Server Communications Options on page 1-11 for details of options available. Digital DEC/EDI Message Updates After installation of the Server system, you must install the versions of EDI standard dictionaries and messages that you require. You are recommended to install at least the following standard and version, which is required for performing the basic system configuration tests described in this book: EDIFACT Version 90.1 Application Client Configuration This section describes the components you need to install on any Application Client nodes. Application Client Configuration 1-9 PREPARING TO INSTALL DIGITAL DEC/EDI Network Interface The network interface provides the means to exchange files and data between the Application Client and the designated Server node. The same network interface must be installed and configured on both the application client and server systems. OpenVMS On an OpenVMS Application Client node, you must select the following Network interface: TCP/IP only The OpenVMS system must have DEC TCP/IP Services installed and configured. Tru64 UNIX, Sun Solaris, HP-UX On a Tru64 UNIX, Sun Solaris or HP-UX Application Client node, you must select the following network interface: TCP/IP only The system must be configured with the TCP/IP implementation supplied with the operating system. Application Client Software OpenVMS On OpenVMS, the VMSINSTAL command is used to install Digital DEC/EDI from the supplied media. The installation procedure provides the option to install only the Application Client components. Tru64 UNIX, Sun Solaris, HP-UX On Tru64 UNIX, Sun Solaris and HP-UX, the setld utility, which is provided with the installation kit where required, is used to install Digital DEC/EDI from the supplied media. You must install the application client subsets. Windows Client On Windows NT/2000, run the self extracting utility to install Digital DEC/EDI client from the supplied media. 1-10 Cockpit and CommandCenter Configuration PREPARING TO INSTALL DIGITAL DEC/EDI RedHat Linux On RedHat Linux, use the RPG package to instll Digital DEC/EDI client from the supplied media. Cockpit and CommandCenter Configuration This section describes the components that you need to install on any PCs running Cockpit or CommandCenter. The CommandCenter software includes the Cockpit, so you do not additionally need to install the Cockpit on those systems. Network Interface The network interface provides the means to exchange files and data between the Cockpit or CommandCenter and the Server. The same network interface must be installed and configured on both the PC and server systems, however as the server can support multiple simultaneous transport types, you can use more than one type of network if needed. Windows NT, Windows 2000 On Windows NT or Windows 2000 you must select the following Network Interface: TCP/IP only The PC must be configured with a supported TCP/IP implementation. Database Configuration (ODBC) The Cockpit and CommandCenter use Open Database Connectivity (ODBC) to communicate with the Digital DEC/EDI database on the Server. The Cockpit and CommandCenter may connect to multiple Servers, each of which may be using a different database. You must install the appropriate ODBC drivers and related software to support connection to the Digital DEC/EDI database on each of the Server systems. OpenVMS For connection to an OpenVMS Server, you must install the ODBC driver onto the PC. Server Communications Options 1-11 PREPARING TO INSTALL DIGITAL DEC/EDI ORACLE ODBC Driver for Rdb You need to install the appropriate driver for the operating system you are running on the PC. Tru64 UNIX For connection to a Tru64 UNIX Server, you must install one of the following ODBC drivers, and related connectivity software on the PC: You need to install ORACLE TCP/IP protocol adapter, ORACLE SQL*NET and the ORACLE 8i ODBC driver onto the PC. Software Installation Cockpit Cockpit is supplied on CD-ROM for Windows NT and Windows 2000. CommandCenter CommandCenter is supplied on CD-ROM for Windows NT and Windows 2000. Server Communications Options The Server supports a number of communications options, and you must install any pre-requisite hardware or software prior to installing Digital DEC/EDI. After installation, you must configure the communications components to enable Digital DEC/EDI to communicate with your trading partners. This section outlines the communications options that are available: OpenVMS On an OpenVMS Server, all communications options are installed by the Server installation procedure. Each communications option, apart from the Import/Export gateway, requires a license for its use. The following communications options are available: X.400 Communication You need to install DECnet/OSI, MAILbus 400 and DEC X.500 Directory Services. 1-12 Server Communications Options PREPARING TO INSTALL DIGITAL DEC/EDI OFTP Communication You need to install DECnet/OSI, and X.25 connector services. Bisynchronous Communication For Bisynchronous communications, you need to install the CLEO 3780Plus product together with SYNCcable+ and a compatible modem. X.25 VAN Communication For X.25 VAN communications with the TRADANET VAN, you need to install DECnet/OSI, and X.25 connector services. Import/Export Communication No additional licensing or software is required for use of the Import/Export gateway. Tru64 UNIX On a Tru64 UNIX Server, you may select specific communications subsets to install. Each communications option, apart from the Import/Export gateway, requires a license for its use. The following communications options are available: X.400 Communication You need to install DECnet/OSI, MAILbus 400 and DEC X.500 Directory Services. OFTP Communication You need to install DECnet/OSI, and X.25 connector services. Bisynchronous Communication For Bisynchronous communications, you need to install the CLEO 3780Plus product together with SYNCcable+ and a compatible modem. X.25 VAN Communication For X.25 VAN communications with the TRADANET VAN, you need to install DECnet/OSI, and X.25 connector services. Internet SMTP/MIME Communication For Internet SMTP/MIME Communication, the sendmail function provided with Tru64 UNIX must be installed, along with connection to a wide area network or Internet Service Provider. You may additionally wish to install a third party security or encryption product if communication over a public access network. Import/Export Communication Zero additional licensing or software is required for use of the Import/Export gateway. Server Communications Options 1-13 PREPARING TO INSTALL DIGITAL DEC/EDI Chapter 2 Installation Activities This chapter provides pre-installation information. Introduction The following pages show the Digital DEC/EDI Component Subsets. You should read through these pages and note which of the optional elements are required for your particular installation. This information will be required during the Installation process described in Part 4. 1. Setting up the Server, and any Application Clients local to it (See Setting Up the Server and Local Application Clients on page 2-3). 2. Setting up any remote Application Clients, that is, those on different nodes to the Server (See Setting Up Remote Application Clients on page 2-4). 3. Setting up any CommandCenter installations (See Setting Up the CommandCenter on page 2-4). 4. Setting up any Cockpit installations (See Setting Up the Cockpit on page 2-5). 5. Using the CommandCenter or INTERCHANGE (OpenVMS) to configure the Server (See Configuring the Server on page 2-5). 2-2 Introduction INSTALLATION ACTIVITIES Figure 2-1 Digital DEC/EDI System Components The first four tasks establish the Digital DEC/EDI system as a network of components. These activities are done only once, or repeated infrequently, for example, when you want to bring another node into the system. The final task deals with the detailed configuration of the Server. This may need more regular maintenance, for example, as you add new Trading Partners and applications. These separate stages are outlined in the following sections. The individual activities are listed for each task, along with the Digital DEC/EDI book where the activity is described in more detail. The majority of these activities need to be performed in all Digital DEC/EDI systems where normal routing is used. Where either bypass or applicationto- application routing is deployed, some of the Server configuration activities may not be needed, such as Translation services, and in the case of application-to-application routing, the Communications services. Likewise, the activities to install and configure remote Application Clients are needed only where you have a need to use such clients (as opposed to Application Clients located on the same node as the Server). Business Application Trading Partner Audit Trail CommandCenter Configuration Data Digital DEC/EDI Digital DEC/EDI Client Application DEC/EDI Digital Cockpit Server DEC/EDI Digital Setting Up the Server and Local Application Clients 2-3 INSTALLATION ACTIVITIES Setting Up the Server and Local Application Clients This task covers the physical installation of the Digital DEC/EDI software and any necessary prerequisite software. It also covers the initial configuration of the software sufficient to create the database, and configure the Network Interface for use by Digital DEC/EDI. The following list summarizes the steps to be performed on the Server node, the details are provided in the chapters detailed below: Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Chapter 6 OpenVMS - Installation of Server and Client Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter 1. Install Digital DEC/EDI product licenses, including CommandCenter license 2. Install and verify prerequisite software 3. (UNIX only) Create a decedi account for Digital DEC/EDI to use 4. Install and verify Digital DEC/EDI software 5. Create the database 6. Register Digital DEC/EDI with Network Interface 7. Configure Network Interface for remote access by Application Clients, Cockpit and CommandCenter 8. Create user accounts for database access by users of Cockpit and CommandCenter 9. Grant access to database for user accounts 10.(Oracle(r) Rdb(tm) only) Configure SQL/Services(tm) for database access by users of Cockpit and CommandCenter 2-4 Setting Up Remote Application Clients INSTALLATION ACTIVITIES Setting Up Remote Application Clients This task covers the physical installation and configuration of any Digital DEC/EDI Application Clients on nodes remote from the Server. The following list summarizes the steps to be performed on each separate node running an Application Client, the details are provided in the chapters detailed below: Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Chapter 6 OpenVMS - Installation of Server and Client The procedure is defined in the following list: 1. Install and verify prerequisite software 2. (UNIX only) Create a decedi account for Digital DEC/EDI to use 3. Install and verify Digital DEC/EDI software 4. Register Digital DEC/EDI with Network Interface 5. Configure Network Interface for remote access by Digital DEC/EDI Server Setting Up the CommandCenter This task covers the installation and configuration of the Digital DEC/EDI CommandCenter on a PC. Because the CommandCenter also contains a copy of the Digital DEC/EDI Cockpit, this task also covers that component where it is installed as part of the CommandCenter. The following activities need to be performed on each PC where the CommandCenter is to be used, the details are provided in the chapter detailed below: Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter 1. Install and verify prerequisite software 2. Install CommandCenter software Setting Up the Cockpit 2-5 INSTALLATION ACTIVITIES 3. Define the main Server that CommandCenter is to access 4. Verify CommandCenter link to the Server Setting Up the Cockpit This task covers the installation and configuration of the Digital DEC/EDI Cockpit on a PC where it is installed separately from the CommandCenter. The following activities need to be performed on each PC where the Cockpit is to be used, the details are provided in the chapter detailed below: Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter 1. Install and verify prerequisite software 2. Install Cockpit software 3. Define the main Server that Cockpit is to access 4. Verify Cockpit link to the Server Configuring the Server This task covers the configuration of the Digital DEC/EDI Server and the development and integration of the business applications that post data to, and fetch data from the Server. The following activities need to be performed on each Server and the details are provided in the chapters detailed below: Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client Chapter 6 OpenVMS - Installation of Server and Client 1. Select which Translation and Communications Services are to run 2. Define the EDI documents to be exchanged with your Trading Partners 3. Develop or modify your business applications 4. Develop Mapping Tables for your business applications 2-6 Configuring the Server INSTALLATION ACTIVITIES 5. Register your business applications with Digital DEC/EDI, and the nodes on which they run 6. Configure your communications links 7. Define your Trading Partner agreements 8. Start the Digital DEC/EDI system Part I Network Configuration This part describes the configuration, installation and verification of the network components. Introduction Describes installation of the network components, covering the following topics: • TCP/IP • Verifying the network. Intended Audience The audience is the network administrator for the following: • Digital DEC/EDI Server node • Digital DEC/EDI Application Client node(s). Chapter 3 Configuring the Network Interfaces This chapter describes how to configure the Digital DEC/EDI network interfaces. Introduction The Digital DEC/EDI Server can support connection from local and remote application clients, and remote PC's running the Digital DEC/EDI Cockpit or CommandCenter. The following network interfaces are supported for connection to the Digital DEC/EDI Server: Tru64 UNIX and OpenVMS Server • TCP/IP Network Interface The network interface is provided through a direct TCP/IP connection between the client and the server. This supports Windows 95 and NT. The Digital DEC/EDI Server may be configured to support simultaneous connections using one or more of these network interfaces. You must install and configure the Digital DEC/EDI Server network interface prior to configuring the client interfaces. Configuring the Digital DEC/EDI Server This section describes how to configure the network interface on the Digital DEC/EDI Server, and how to set up the local application client to use the network interface. 3-2 Configuring the Digital DEC/EDI Server CONFIGURING THE NETWORK INTERFACES TCP/IP Network Interface This section describes how to configure the TCP/IP network interface on the Digital DEC/EDI Server. Pre-Configuration tasks Prior to configuring the TCP/IP network interface, you should verify that the TCP/IP protocol is installed and is functioning correctly. Tru64 UNIX For example, this may be achieved by verifying that the host name of the computer you are installing on is registered with a local domain name server: # nslookup 'hostname' Server: dnsserver.company.com Address: 1.20.30.4 Name: mynode.company.com Address: 1.20.30.124 Alternatively, you may use the ping command to verify that the computer may connect to another node within the same network. Press CTRL+C to stop the ping command. # /sbin/ping clientnode.company.com PING clientnode.company.com (1.20.30.101): 56 data bytes 64 bytes from 1.20.30.101: icmp_seq=0 ttl=128 time=0 ms 64 bytes from 1.20.30.101: icmp_seq=1 ttl=128 time=0 ms ----1.20.30.101 PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/1 ms # OpenVMS The TCP/IP protocol must be provided by DIGITAL TCP/IP Services. You may verify that this has been installed correctly by running the Installation Verification Procedure for DIGITAL TCP/IP Services: $ @sys$test:ucx$ivp.com %%% UCX IVP: started %%% UDP/IP test started at 18-JUL-1997 11:33:27.63 UDP/IP test ended at 18-JUL-1997 11:33:39.12 UDP/IP transferred successfully in 11 seconds 4198400 bytes Configuring the Digital DEC/EDI Server 3-3 CONFIGURING THE NETWORK INTERFACES TCP/IP test started at 18-JUL-1997 11:33:39.17 TCP/IP test ended at 18-JUL-1997 11:33:48.04 TCP/IP transferred successfully in 8 seconds 4198400 bytes RAW_IP test started at 18-JUL-1997 11:33:48.08 RAW_IP test ended at 18-JUL-1997 11:33:49.25 RAW_IP transferred successfully in 1 seconds 251000 bytes %%% UCX IVP: completed successfully %%% Configuration Tasks Tru64 UNIX The Digital DEC/EDI Server configuration consists of the following steps: Step 1: From the root account, use the decedi_config command, and select the option to configure the TCP/IP Client-Server link. This procedure assigns the TCP/IP port numbers on which the Digital DEC/EDI Services will listen for and handle incoming client requests. This assigns unique port numbers for the Digital DEC/EDI Services within the TCP/IP services file /etc/services. # decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 1 Configuring the TCP/IP Client-Server link Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 2 Configuring Database Compaq DEC/EDI no longer contains a fixed database configuration utility. Instead, customers are encouraged to create 3-4 Configuring the Digital DEC/EDI Server CONFIGURING THE NETWORK INTERFACES their own databases using the Oracle 8i or later database environment. Required schemas and example configuration scripts are available in the /var/adm/decedi/db directory. This configuration procedure simply gathers the information from you on how to connect to your database. Please make sure you have created and tested your database before running this option. Do you want to continue (y/n) [n] : y Enter the database environment to be used (Ora) [Ora] : Enter the local ORACLE HOME directory [] : /usr/app/oracle/product/8.1.6 Enter the Compaq DEC/EDI database's TNS name [ediot_decedidb.world] : Enter the Oracle Username and Password (username/password) : Verifying database connectivity ... Database access verified and saved. Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 3 Configuring Memory Queues Enter the number of slots to hold in memory (10000- >300000) [10000] : 20000 Verifying memory availability... New queue size verified and saved. Press to continue. Step 2: Note down the TCP/IP port numbers that have been assigned to each of the Digital DEC/EDI Services in Step 1 using the Configuring the Digital DEC/EDI Server 3-5 CONFIGURING THE NETWORK INTERFACES following table: You may need to specify these values when configuring any remote application clients or setting up any Cockpit or CommandCenter installations to use the TCP/IP network interface. Note: The same TCP/IP port numbers must be used for all Digital DEC/EDI client and server installations within the same network. Step 3: You are asked whether you wish to use the TCP/IP link for local client access, for example: Do you wish to use TCP/IP for local client access ? [y or n] y TCP/IP Configuration Complete Press to continue. If you confirm this option, then the file /var/adm/decedi/decedi_servers.dat is automatically created with the following value: * LOCAL This ensures that any local applications will use the local Digital DEC/EDI Server to handle client requests. For further information on specifying the use of another Digital DEC/EDI Server node to handle client requests, refer to Configuring the Digital DEC/EDI Application Client on page 3-14 Table 3-1 Digital DEC/EDI Services TCP/IP Port Numbers Purpose Service Name Enter your Port Number here Digital DEC/EDI Post/Fetch Server decedi_csf Digital DEC/EDI Tracking Server decedi_cst Digital DEC/EDI GUI Server decedi_csg 3-6 Configuring the Digital DEC/EDI Server CONFIGURING THE NETWORK INTERFACES Post-Configuration Tasks Once you have configured the network interface, you may start up Digital DEC/EDI. This enables the Digital DEC/EDI Cockpit and CommandCenter, running on a suitably configured PC, to access the Digital DEC/EDI Server. Tru64 UNIX If this is a new installation then you need to copy the file /var/adm/decedi/decedi_servers.template to /var/adm/decedi/decedi_servers.dat. Edit the file and add name of any DEC/EDI Servers and their backups to use and the name of the application Ids (or a * for all) that should use these servers. Note that if you are configuring on a TruCluster Server or on a client that will use a TruCluster Server enabled DEC/EDI Server, you should use the Cluster Alias rather than the LOCAL name or the name of a node in the cluster. OpenVMS Once you have configured the Digital DEC/EDI Server, you may start up the Digital DEC/EDI Server, using the following command: $ @SYS$STARTUP:DECEDI$STARTUP For Further Information There are a number of logical names or environment variables which may be used to tune the behaviour of the TCP/IP network interface, and to monitor the network traffic and processes. For further information on the use of these environment variables and logical names, refer to the Digital DEC/EDI: User's Guides (Tru64 UNIX and Open VMS). Configuring the Digital DEC/EDI Server 3-7 CONFIGURING THE NETWORK INTERFACES TCP/IP Port Server Monitoring Tools There is now an additional tool which allows the TCP/IP Port server and its child process to be monitored and which can tell the Port Server to re-cache the control environment variables whilst it is running. This is useful when you want to change the tracing behaviour or increase the number of maximum child processes. The tool name is: OpenVMS @DECEDI$TOOLS:DECEDI$PS_CONTROL 3-8 Configuring the Digital DEC/EDI Application Client CONFIGURING THE NETWORK INTERFACES Configuring the Digital DEC/EDI Application Client This section describes how to configure the network interface on the Digital DEC/EDI Application Client, along with any steps that need to be performed on the Digital DEC/EDI Server, to enable connection from the remote application client. The Digital DEC/EDI Application Client may be configured using the TCP/IP network interface. TCP/IP Network Interface This section describes how to configure the TCP/IP network interface on the Digital DEC/EDI Application Client. The TCP/IP network interface may be used for connection from the following Digital DEC/EDI Application Client releases: • Digital DEC/EDI for Tru64 UNIX, Version 4.0 • Digital DEC/EDI for OpenVMS Alpha, Version 4.0 • Digital DEC/EDI Application Client for Sun Solaris, Version 4.0 • Digital DEC/EDI Application Client for HP-UX, Version 4.0 • Digital DEC/EDI Application Client for RedHat Linux, Version 4.0 • Digital DEC/EDI Application Client for Windows NT/2000, Version 4.0 The Application Client may be configured to connect to one or more Digital DEC/EDI Server systems, selected by application name, or to a default Digital DEC/EDI Server. In addition, one or more failover Digital DEC/EDI Servers may be specified to handle client requests, if the primary Digital DEC/EDI Server is not currently available. Configuring the Digital DEC/EDI Application Client 3-9 CONFIGURING THE NETWORK INTERFACES Pre-Configuration tasks Prior to configuring the TCP/IP network interface, you should verify that the TCP/IP protocol is installed and is functioning correctly. Step 1: Ensure that any Digital DEC/EDI Servers that will service requests from the application client have been configured to support the TCP/IP network interface as described in TCP/IP Network Interface on page 3-2. Step 2: Verify that the TCP/IP connection between the application client and the server nodes is functioning correctly. For example, this may be achieved by using the ping command as follows: Tru64 UNIX, Sun Solaris, HP-UX, RedHat Linux # ping myserver.company.com PING myserver.company.com (1.20.30.101): 56 data bytes 64 bytes from 1.20.30.101: icmp_seq=0 ttl=128 time=0 ms 64 bytes from 1.20.30.101: icmp_seq=1 ttl=128 time=0 ms ----1.20.30.101 PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/1 ms OpenVMS $ UCX UCX> PING myserver.company.com %UCX-I-LOOPACT, myserver.company.com is alive Windows NT/2000 C:\WINNT\SYSTEM32> ping myserver.company.com Pinging myserver.company.com [1.20.30.101] with 32 bytes of data: Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 Reply from 1.20.30.101: bytes=32 time<10ms TTL=64 3-10 Configuring the Digital DEC/EDI Application Client CONFIGURING THE NETWORK INTERFACES Configuration Tasks Tru64 UNIX, Sun Solaris, HP-UX, RedHat Linux, The Digital DEC/EDI Application Client configuration consists of the following steps: Step 1: From the root account, use the decedi_config command, and select the option to configure the TCP/IP Client-Server link. This procedure sets up the TCP/IP port numbers that are used on the Digital DEC/EDI Server for handling incoming client requests. The port numbers are defined within the TCP/IP services file /etc/services. Tru64 UNIX # /usr/sbin/decedi_config Sun Solaris, HP-UX, RedHat Linux # /usr/bin/decedi_config Configuring the TCP/IP Client-Server link To supply the server node information, create a file: /var/adm/decedi/decedi_servers.dat Use the template, /var/adm/decedi/decedi_servers.template . Do you wish to use TCP/IP for local client access ? [y or n] Configuring the Digital DEC/EDI Application Client 3-11 CONFIGURING THE NETWORK INTERFACES Step 2: The TCP/IP port numbers specified on the client must match those defined on the Digital DEC/EDI Server. Compare these with the values you have noted in the table Digital DEC/EDI Services TCP/IP Port Numbers on page 3-4. If the TCP/IP port numbers differ, edit the values stored in the file /etc/services, so that the same values are used for all client and server installations within the same network. Step 3: Specify the default Digital DEC/EDI Server that should be used for handling requests from the application client. Copy the template file /var/adm/decedi/decedi_servers.template to the file /var/adm/decedi/decedi_servers.dat, as follows: # cp /var/adm/decedi/decedi_servers.template \ /var/adm/decedi/decedi_servers.dat Edit the file /var/adm/decedi/decedi_servers.dat and add the following line to the end of the file. For example, if the server node name is myserver.company.com. * myserver.company.com ! default Digital DEC/EDI Server OpenVMS The Digital DEC/EDI Application Client configuration consists of the following step: Step 1: Specify the default Digital DEC/EDI Server that should be used for handling requests from the application client. Copy the Digital DEC/EDI Servers template file DECEDI$DATA:DECEDI_SERVERS.TEMPLATE, to the file DECEDI$DATA:DECEDI_SERVERS.DAT, as follows: $ COPY DECEDI$DATA:DECEDI_SERVERS.TEMPLATE - DECEDI$DATA:DECEDI_SERVERS.DAT Edit the file DECEDI$DATA:DECEDI_SERVERS.DAT and add the following to the end of the file. For example, if the server node name is myserver.company.com. * myserver.company.com ! default Digital DEC/EDI Server 3-12 Configuring the Digital DEC/EDI Application Client CONFIGURING THE NETWORK INTERFACES Post-Configuration Tasks If you wish, you may add additional Digital DEC/EDI Server definitions and specify which application names should access those servers. These must be placed within the Digital DEC/EDI Servers definition file prior to the line specifying the default Digital DEC/EDI Server. Tru64 UNIX Edit the file /var/adm/decedi/decedi_servers.dat OpenVMS Edit the file DECEDI$DATA:DECEDI_SERVERS.DAT In the following example, the applications DEC-DIRECT-UK-LTD and SHINY-NEW-SYSTEMS both use the primary Digital DEC/EDI Server on node myserver.com. In the event that the Digital DEC/EDI Server is unavailable, the backup Digital DEC/EDI Server on node backup.com is used. The application JOLLY-OLD-SYSTEMS uses the Digital DEC/EDI Server on node edidev as the primary Digital DEC/EDI Server. If this is unavailable, the backup server on edidev2 is tried, followed by edidev3. All other applications in this example use the primary server edigate.com and have no backup Digital DEC/EDI Server. DEC-DIRECT-UK-LTD myserver.com backup.com:5150:5151 SHINY-NEW-SYSTEMS myserver.com backup.com:5150:5151 JOLLY-OLD-SYSTEMS edidev edidev2 edidev3:5150:5151 * edigate.com:5150:5151 ! default Digital DEC/EDI Server For Further Information There are a number of logical names or environment variables which may be used to tune the behaviour of the TCP/IP network interface, and to monitor the network traffic and processes. For further information on the use of these environment variables and logical names, refer to the Digital DEC/EDI: User's Guides (Tru64 UNIX and Open VMS). Part II Database Administration This part describes the configuration and installation of the database components. Intended Audience The audience for this part is the database administrator for the following: • Digital DEC/EDI Server node • PC's running Cockpit or CommandCenter Describes installation of the database components, covering the following: • Oracle Rdb • Oracle 8i • ODBC • SQL network drivers. Chapter 4 Configuring the Database This chapter describes the configuration of the database on the Server node by the Database Administrator. Overview Configuration takes place in two stages. In the first stage, the connectivity software which links the Application Client to the Server, or the Cockpit/ CommandCenter to the Server is initialized. In the case of the Server this phase will also include creating the Digital DEC/EDI database and allowing access to it from the CommandCenter. The second phase of configuration is the detailed configuration of the Server by using the CommandCenter which is described in Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter. The alternative is to configure using INTERCHANGE when installed on OpenVMS servers. This chapter describes the first of these stages. 4-2 Overview CONFIGURING THE DATABASE Account Privileges Tru64 UNIX Note that many of the activities described in this section that involve running decedi_config, assume you have access to the root account on the Server node. Open VMS You will need an account with full system manager privileges. Configurations Covered The following configurations are covered • Tru64 UNIX Oracle 8i • OpenVMS Alpha Oracle Rdb Setting Up Process The setting up process which happens after the chosen database application has been installed, has two parts as shown below: • A - Decision process for location of the database • B - Creation of the database A - Deciding Where to Locate the Database 4-3 CONFIGURING THE DATABASE A - Deciding Where to Locate the Database When locating the database it is important that a location with sufficient resource is chosen. A badly located database can significantly reduce the performance of a Server, meaning you need to consider the disk space and room for expansion. Factors that can decrease the performance are further detailed later in Performance Limiting Aspects on page 4-5. Oracle8i You need to specify a directory location on disk with enough spare disk space, use the following formula to calculate the required size: maximum size = overhead + peak map size + peak doc size + peak comms size + standards size Where: overhead = 18MB +(((maximum size - 18MB)* 3)/10) peak map size = (peak live maps + peak archive maps)* 0.003 MB peak doc size = (peak live docs + peak archive docs) * 0.0015 MB peak comms size = (peak live comms + peak archive comms) * 0.003 MB standards size = number of standards * 5MB We recommend a minimum of 50MB for the Oracle8i database. Typical Example As an example, a user system which processes a 500 maps per weekday, generating or consuming 500 EDI documents which in turn go to, or come from 100 communications transmission files using two EDI standards, and where secondary archiving is done once a week, the calculation is as follows. We assume that be the end of the day all live documents are processed, so peak live size is peak daily rate, whilst the peak archive size is the cumulation of the five-day week's worth of data. The calculation includes some contingency, so that we double the peak live counts in case everything fails due to some disaster and we take a day to fix it, and we double the archive size in case we forget one weekend to do the secondary archive. 4-4 A - Deciding Where to Locate the Database CONFIGURING THE DATABASE We also double the number of standards we use to cater for near term expansion. So, we end up with a calculation of: maximum size = 18MB + (((maximum size -18MB) * 3) / 10) + (1000 + 5000) * 0.003 MB + (1000 + 5000) * 0.0015 MB + (200 + 1000) * 0.003 MB 4 * 5MB; = 85 MB (approximately) Having worked out the size, find a suitable directory, which resides on a disk with sufficient free space, and create a database directory for it. Set the ownership of this directory to be the main Oracle account. The main Oracle account is the account under which this instance of the Oracle8i RDBMS software was installed. For standard Oracle installations this is oracle by default, or if installed on behalf of another application it could be ora , for example orapd1. Note that the database size can be increased later by adding extra datafiles to the relevant tablespaces if a particular tablespace becomes full. NFS mounted disks Digital does not recommend placing the database for Digital DEC/EDI onto an NFS mounted disk. Access. The database account needs to have write access to the directory where your database is to be created. A - Deciding Where to Locate the Database 4-5 CONFIGURING THE DATABASE OpenVMS Oracle Rdb If you are on OpenVMS then Oracle Rdb will provide your database, and it will be created on the device on which you have elected as Digital DEC/EDI's top level directory. The default database is created of approximately 20 Mbytes in size which will allow it to hold information for: The tables within the database will automatically extend when you store more data in them that the original configuration can hold, but performance will be reduced the more the database becomes extended. Should the database become too small or if you wish to move the database to another device then a tool, DECEDI$TOOLS:DECEDI$TAILOR.COM, is provided to help you with this. Performance Limiting Aspects Disk Speed. The performance of your Server can easily be limited by the speed of access to the Digital DEC/EDI database. This means that you should avoid placing the database on slow disks. I/O Bottlenecks. During the software installation, you specified one or more disk locations for your store directories. These are directories used to hold the actual document and transmission files. By placing the database on a different physical disk to those holding store directories, you help to avoid the performance of individual disks being a bottleneck on overall system performance. NFS Mounted Disks Digital does not recommend placing the database for Digital DEC/EDI onto an NFS mounted disk. Access. The database account needs to have write access to the directory where your database is to be created. Number of documents in the Current Audit Trail 1000 Number of documents in the Archive Audit Trail 1000 Number of transmission files in the Current Audit Trail 1000 Number of transmission files in the Archive Audit Trail 1000 4-6 B - Creating the Database CONFIGURING THE DATABASE B - Creating the Database • Tru64 UNIX Oracle 8i • Alpha Oracle Rdb Tru64 UNIX All Databases This task is performed by using the Digital DEC/EDI configuration utility: decedi_config. To use this, you need to be logged in to your Server under the root account. Questions, Getting Help If you are unsure about how to reply to any of the questions asked by this utility, enter a question mark character followed by . Help text is displayed giving you more information about any choices you can make. Invoke the configuration utility, and select the option to configure the database, as in the following example: # decedi_config 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 1 Configuring the TCP/IP Client-Server link Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 2 Configuring Database Compaq DEC/EDI no longer contains a fixed database configuration utility. Instead, customers are encouraged to create their own databases using the Oracle 8i or later database environment. Required schemas and example configuration scripts are available in the /var/adm/decedi/db directory. This configuration procedure simply gathers the information from you on how to connect to your database. B - Creating the Database 4-7 CONFIGURING THE DATABASE Please make sure you have created and tested your database before running this option. Do you want to continue (y/n) [n] : y Enter the database environment to be used (Ora) [Ora] : Enter the local ORACLE HOME directory [] : /usr/app/oracle/product/8.1.6 Enter the Compaq DEC/EDI database's TNS name [ediot_decedidb.world] : Enter the Oracle Username and Password (username/password) : Verifying database connectivity ... Database access verified and saved. Press to continue. 1. Configure TCP/IP Client-Server Link 2. Configure database 3. Configure Memory Queues 4. Exit Configuration Select option [4] : 3 Configuring Memory Queues Enter the number of slots to hold in memory (10000->300000) [10000] : 20000 Verifying memory availability... New queue size verified and saved. Press to continue.You are asked what product is to be used to provide the database, and where the database is to be located. The device or directory to contain the database must already exist. The location of the file that is to contain the database for Oracle Rdb. The database creation procedure displays each individual statement executed in setting up the database. The database creation procedure may take several minutes to complete. Typical Oracle 8i Example Configuring Database Enter the database to be used (Rdb, Inf, Ora) [Inf] : Ora ...Creating /var/adm/decedi/config.dat Enter Oracle Home directory /usera/oracle] : 4-8 B - Creating the Database CONFIGURING THE DATABASE Enter Digital DEC/EDI Oracle 8 database location [/var/adm/decedi/db] : /userb/oracle/db ...Modifying /etc/oratab ...Modifying /var/adm/decedi/config.dat Enter Digital DEC/EDI Oracle 8 database size in KB [182671] : 100000 ******************************************************* Default oracle network templates have been generated in /userb/oracle/db/. The files being: listener.ora tnsnav.ora tnsnames.ora These files should be merged with those already on this server (in /etc), and those residing on any PC wishing to use the CommandCenter or Cockpit to access this server. ...Creating /usera/oracle/dbs/initdecedidb.ora ...Creating database /userb/oracle/db ...Loading system tables ...Creating schema ...Storing system version ...Setting Digital DEC/EDI Oracle password. Database Configuration Complete B - Creating the Database 4-9 CONFIGURING THE DATABASE OpenVMS The Digital DEC/EDI database is created during the installation process. Typical Oracle Rdb Example A typical installation detail example is provided below: =================================================== The following versions of Rdb/VMS are available: V7.0-3 * Please enter the Rdb/VMS version to be used by Digital DEC/EDI [V7.0-3]: At this point the installation will list the installed databases. The default is selected by pressing , should you need to use one of the alternates (when available) enter the version as displayed followed by . The example continues below assuming acceptance of the default: Current PROCESS Oracle Rdb environment is version V7.0-3 (STANDARD) Current PROCESS SQL environment is version V7.0-3 (STANDARD)Current PROCESS Rdb/Dispatch environment is version V7.0-3 (STANDARD) Database Version It is essential that the database version on your system is the same as that used by Digital DEC/EDI. Use the following command to establish the version currently in use: $@sys$library:rdbvms_shover To set the version, use the following command: $@sys$library:rdbvms_setver For example, to set the version to V7.0, use the following command: $@sys$library:rdbvms_setver v70 4-10 Migrating the Database CONFIGURING THE DATABASE Migrating the Database If you are installing Digital DEC/EDI over a previous version then the database structure needs migrating to the new structure. Tru64 UNIX After installing Digital DEC/EDI, run decedi_config from the root account. Select the option to configure the database. Select the database type being used and location of existing database, then select the [m]igrate option. The database is migrated to a structure compatible with the current version of the Server. If the current database is already in a compatible structure (that is, if there have not been any database structure changes between the version of the Server that was used to create/migrate the database to its current structure and the currently installed Server version) then no migration is needed and none takes take place. The database is then ready for use by the currently installed Server. OpenVMS The Digital DEC/EDI database will normally be migrated during the installation process. Creating User Accounts for Database Access 4-11 CONFIGURING THE DATABASE Creating User Accounts for Database Access Each PC running either the CommandCenter or the Cockpit accesses the Digital DEC/EDI database on the Server via ODBC(tm) on the PC. This needs to happen through an account on the Server. You can have a single account for all users of the CommandCenter and the Cockpit, or you can have individual accounts for each separate user of either PC product. Having a single account is easier to set up and maintain, and though inherently less secure, allows you to be more selective about what individual users can access. Digital DEC/EDI Access Control Editor This application, which is provided with the CommandCenter/Cockpit, enables you to define which users may access which data and the level of their access to the CommandCenter. Tru64 UNIX Oracle8i Oracle 8i maintains its own usernames and passwords. It can also support server accounts and passwords, but as these apply only when making requests from the server, they are of no value to CommandCenter and Cockpit users. To create Oracle8i accounts, use the decedi_config option described in the following section, Granting Database Access to User Accounts. In addition to defining the users, you will be prompted for the passswords associated with any new users. When you start any of the CommandCenter editors or the Cockpit, the account and password you are asked to specify are those of the user accounts you have now created on the Server. OpenVMS Oracle Rdb You create a user account on the Server by using the OpenVMS AUTHORIZE utility. You should do this from the 'system' account or another highly privileged account. 4-12 Oracle User Registration CONFIGURING THE DATABASE Oracle User Registration Tru64 UNIX All GUI users who log in, access an account on the Server machine which is authorized to access the database. Oracle8i is different in that it takes the username as being local to the machine from which the request was made; the GUI PC. This type of treatment reduces the effectiveness of the logging in procedure. To deal with this situation, you (as system administator) need to create user accounts within the Digital DEC/EDI Oracle database by using decedi_config. PC users can then use those accounts to access the database. OpenVMS Oracle SQL Services provides a number of mechanisms by which access to a database can be granted or revoked. By default, the Digital DEC/EDI database is protected via OpenVMS ACLs. To allow a user to access the Digital DEC/EDI databases, the Digital DEC/EDI INTERCHANGE command should be used to add the user. This in turn grants the user's account the correct ACLs to allow access to the Digital DEC/EDI database. Configuring the Database Network Connectivity OpenVMS Oracle SQL Services By default, when you install Oracle SQL Services it will create a class for the version of software you have installed for instance, if installing Oracle Rdb V5.1 then a 'V51' class will be automatically configured. As long as this class used by the CommandCenters and Cockpits trying to access the database then no further configuration is required. Options are: GENERIC, V51, V60, V61. Specify GENERIC if you have standard SQL Services installed on your OpenVMS Server. Specify one of the other options if you have multi-version SQL installed, to tell it which version to use. Configuring the Database Network Connectivity 4-13 CONFIGURING THE DATABASE Tru64 UNIX Oracle 8i As part of creating the Digital DEC/EDI Oracle 8i database, the following was reported: ******************************************************* Default oracle network templates have been generated in /userb/oracle/db/. The files being: listener.ora tnsnav.ora tnsnames.ora These files should be merged with those already on this server (in /etc), and those residing on any PC wishing to use the CommandCenter or Cockpit to access this server. This needs to be done, and the Oracle 8i TNS listener re-started for these to take effect. Merging Files Refer to the Digital DEC/EDI: User's Guides (Tru64 UNIX and Open VMS) for information on merging the files. Part III Software Installation This part describes the software installation onto a variety of platforms. Introduction Installation of the following software is covered: • Client/Server or Client software • Message Updates • CommandCenter and Cockpit. Intended Audience The audience of this part is the system manager or administrator of the following: • Digital DEC/EDI Server node • Digital DEC/EDI Application client node(s) • PCs running CommandCenter and/or Cockpit Supported Platforms This part also includes installation of the following on the Digital DEC/EDI Server node: The following servers running Digital DEC/EDI are covered • OpenVMS • Tru64 UNIX The following clients running Digital DEC/EDI are covered: • OpenVMS • Tru64 UNIX • Sun Solaris • HP-UX • RedHat Linux • Windows NT/2000 The following operating systems on PCs running CommandCenter and/or Cockpit are supported: • Windows NT/2000 Chapter 5 UNIX - Installation of Digital DEC/EDI Server and Application Client This chapter describes the preparation for and installation of Digital DEC/EDI Server and Application Client by the System Manager or Administrator, onto a Tru64 UNIX platform. Introduction This chapter is divided into sections as shown below: • Preparing to Install Digital DEC/EDI on page 5-2 • Installing Digital DEC/EDI on page 5-23 • After Installation on page 5-29 • Setting Up the System on page 5-31 5-2 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Preparing to Install Digital DEC/EDI Before attempting to proceed with the instructions contained within this book you should be familiar with the contents of Digital DEC/EDI Introduction and have decided on which components will be installed on this and any other nodes. Before attempting to install Digital DEC/EDI software on your system, complete the preparation requirements outlined in Chapters 1 and 2. You will need the Installation Checklist prepared from Chapter 2 to complete the preparation and installation described in this chapter. This section describes the activities that must be completed before starting the installation: • Reading the Online Release Notes on page 5-3 • Installation Options on page 5-4 • Checking the Software Distribution Kit on page 5-8 • Registering Your Software Licenses on Digital Systems on page 5-8 • Installation Pre-requisites on page 5-11 • Deleting Digital DEC/EDI from Your System on page 5-24 • # setld -d DEDICLT400 DEDICLTMAN400 on page 5-21 Preparing to Install Digital DEC/EDI 5-3 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Reading the Online Release Notes Digital DEC/EDI provides online release notes. Digital strongly recommends that you read the release notes before using the product. The release notes contain information about changes to the application that are not included in the standard published documentation set. The release notes for Digital DEC/EDI will be placed in the following location after installation: /usr/doc/DECEDI(subset_number).release_notes 5-4 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Installation Options Your media kit contains one or more Digital DEC/EDI components which are as follow: • Digital DEC/EDI Application Client. Select if applications on the installation platform are to either exchange files with Digital DEC/EDI Server, or track files in the Digital DEC/EDI Server using the Digital DEC/EDI Application Programming Interface (API) or the Digital DEC/EDI Command Line Interface (CLI). Necessary whether or not the Digital DEC/EDI Server is on the same platform as the applications. • Digital DEC/EDI Server. Select to provide Communications Services, EDI Translation Services, or Mapping Services on the installation platform. Necessary even to only use this platform as the common connection point for Application-to- Application routing. • Digital DEC/EDI Message Update Service. Select to install a new set of EDI message standards for use by the EDI Translation Services, or for use when developing mapping tables. It can only be installed on a platform with Digital DEC/EDI Server component. The components share some common subsets and have other subsets which are specific to themselves and which may be either mandatory or optional. Preparing to Install Digital DEC/EDI 5-5 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT The components, and their subsets are detailed below:. Table 5-1 Digital DEC/EDI Component Subsets Component (Digital DEC/EDI ...) Subset (Digital DEC/EDI ...) Install ? Application Client Base Mandatory Client Mandatory Client Man Pages Optional Server Base Mandatory Server Mandatory Server Man Pages Optional EDI Translation Services Optional Mailbus 400 Gateway Optional OFTP Gateway Optional SMTP/MIME Communications Gateway Optional 3780 (BISYNC) Communications Gateway Optional Message Update Service (MUS) Message Updates Base Mandatory Message Updates EDIFACT IMPDEF files Optional Message Updates ODETTE IMPDEF files Optional Message Updates X12 files Optional Message Updates TDCC files Optional Message Updates TRADACOMS files Optional 5-6 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Additional Information on Digital DEC/EDI Subsets The following provides additional information on the Digital DEC/EDI subsets: • The Digital DEC/EDI Client Man Pages optional subset should be selected if the man pages for the Digital DEC/EDI API and CLI calls are required. • The Digital DEC/EDI Server Man Pages optional subset should be selected if the man pages for the Digital DEC/EDI System Administrator Utilities, such as Secondary Archiving, are required. • The Digital DEC/EDI EDI Translation Services optional subset should be selected if any EDI Translation is required for either outgoing or incoming files. • The Digital DEC/EDI Mailbus 400 Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide X.400 or X.435 Communications Services. • The Digital DEC/EDI OFTP Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide OFTP Communications Services. • The Digital DEC/EDI SMTP/MIME Communications Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide SMTP/MIME Communications Services. • The Digital DEC/EDI 3780 (BISYNC) Communications Gateway optional subset should be selected if the Digital DEC/EDI Server is to provide 3780 (BISYNC) Communications Services. • The Digital DEC/EDI Message Updates Man Pages optional subset should be selected if the man pages for the Digital DEC/EDI Message Updates Service are required. • The Digital DEC/EDI Message Updates EDIFACT IMPDEF files optional subset should be selected if the Digital DEC/EDI Server requires that new EDIFACT tables need to be installed on the system or to replace existing tables already on the system. • The Digital DEC/EDI Message Updates ODETTE IMPDEF files optional subset should be selected if the Digital DEC/EDI Server requires that new ODETTE tables need to be installed on the system or to replace existing tables already on the system. Preparing to Install Digital DEC/EDI 5-7 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT • The Digital DEC/EDI Message Updates X12 files optional subset should be selected if the Digital DEC/EDI Server requires that new X12 tables need to be installed on the system or to replace existing tables already on the system. • The Digital DEC/EDI Message Updates TDCC files optional subset should be selected if the Digital DEC/EDI Server requires that new TDCC tables need to be installed on the system or to replace existing tables already on the system. • The Digital DEC/EDI Message Updates TRADACOMS files optional subset should be selected if the Digital DEC/EDI Server requires that new TRADACOMS tables need to be installed on the system or to replace existing tables already on the system. 5-8 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your Digital DEC/EDI software distribution kit. If your software distribution kit is damaged or incomplete, contact your Digital representative. Registering Your Software Licenses on Digital Systems Digital DEC/EDI includes support for the License Management Facility (LMF). You must register your License Product Authorization Key(s) (License PAK(s)) in the License Database (LDB) in order to use Digital DEC/EDI on a newly-licensed node. If you ordered the licenses and media together then the License PAK(s) will be shipped along with the kit. Otherwise, the License PAK(s) are shipped separately to a location described on your license order. Digital DEC/EDI supports a number of license types, depending on which Digital DEC/EDI component subsets you wish to use. The individual License PAK names, and what they control are shown on the following table. Preparing to Install Digital DEC/EDI 5-9 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Table 5-2 Digital DEC/EDI Component Licensing Important In addition, you must install the EDI-COMCEN license on the Server. This permits the Digital DEC/EDI CommandCenter to manage the Server node. If you are installing pre-requisite or optional software along with Digital DEC/EDI, review the PAK status and install the PAKs for them before you install Digital DEC/EDI. Subset (Digital DEC/EDI ...) Functionality LMF_PAK_Name Client Post, Fetch, Track via API or CLI This includes bypass translation EDI- APP-SERV or EDI X400 PACKAGE or EDI OFTP PACKAGE Server Import/Export Gateway. Runtime Mapper, Application to- Application Routing No license required EDI Translation Convert to EDI Format, Build EDI Transmissions, Split EDI Transmissions, Translate from EDI Format EDI-TRANSLATIONSERV or EDI-X400- PACKAGE or EDI-OFTP-PACKAGE Mailbus400 Gateway X.400 (84) P0 and P2, X.400 (88) P0 and P2, X.435 EDI EDI-X400-SERV or X400-PACKAGE OFTP Gateway OFTP send and receive EDI-OFTP-SERV or EDI OFTP- PACKAGE SMTP/MIME Communications Gateway SMTP send and receive EDI-SMTP LICENSE or EDI-SMTP-PACKAGE license 3780 (BISYNC) Communications Gateway 3780 send and receive EDI-BISYNC- LICENSE or EDI-BISYNC-PACKAGE license 5-10 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Registering Licenses on Tru64 UNIX To register a license under the Tru64 UNIX operating system: 1. Log in as superuser. 2. At the superuser prompt, enter the following command to edit your License PAK: # lmf register 3. An empty PAK template is displayed in a text editor. Enter all the information from the License PAK form supplied with your software. 4. After you register your license, use the following command to copy the license details from the LDB to the kernel cache: # lmf reset For complete information on using the License Management Facility, see the Guide to Software License Management. Preparing to Install Digital DEC/EDI 5-11 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Installation Pre-requisites This section discusses requirements for installing Digital DEC/EDI. Login Privileges You must have superuser privileges to install the Digital DEC/EDI software and to register the license PAK(s). Hardware Requirements To run the Digital DEC/EDI Application Client, Digital DEC/EDI Server or Digital DEC/EDI Message Update Service you need a Digital machine running the Tru64 UNIX Operating System. Please refer to the Digital DEC/EDI Software Product Description (SPD) for the additional details of the hardware models and supported versions of the operating system. To perform the installation, you need the following hardware: • A software distribution device (if installing from media). You need a distribution device that corresponds with the software distribution media. For example, if you have a CD-ROM, you need a CD-ROM drive. The documentation for the tape or disk drive explains how to load the media supplied with the software distribution kit. • A terminal. You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. If you wish to install the Digital DEC/EDI Mailbus 400 Gateway subset, you may require additional hardware that supports specific communication protocols to provide external connectivity. See the Mailbus 400 Software Product Description (SPD) for more information on these requirements. If you wish to install the Digital DEC/EDI OFTP Gateway subset, you may require additional hardware to provide the X.25 connectivity. See the DEC X.25 Software Product Description (SPD) for more information on these requirements. 5-12 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Checking Software Requirements The software requirements for Digital DEC/EDI are shown below. Table 5-3 Digital DEC/EDI Software Requirements Subset (Digital DEC/EDI ...) Software Install? Base Tru64 UNIX Mandatory TCP/IP Mandatory (included with O/S) Client Digital DEC/EDI Base Mandatory Client Man Pages Tru64 UNIX Documentation Subset Optional Server Digital DEC/EDI Base Mandatory Oracle 8i Mandatory if using Oracle 8i Oracle SQL*NET V2 Mandatory if using Oracle 8i Server Man Pages Tru64 UNIX Documentation Subset Optional Translation Services Digital DEC/EDI Server Optional Mailbus 400 Gateway Digital DEC/EDI Server Optional Mailbus 400 Base Optional OFTP Gateway Digital DEC/EDI Server Optional SMTP/MIME Communications Gateway Digital DEC/EDI Server Optional 3780 (BISYNC) Communications Gateway Digital DEC/EDI Optional DEC X.25 Base Optional Message Updates Base Digital DEC/EDI Server Optional Message Updates Man Pages Tru64 UNIX Documentation Subset Optional Preparing to Install Digital DEC/EDI 5-13 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Message Updates EDIFACT IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates ODETTE IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates X12 IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates TDCC IMPDEF files Digital DEC/EDI Message Updates Base Optional Message Updates TRADACOMS IMPDEF files Digital DEC/EDI Message Updates Base Optional Subset (Digital DEC/EDI ...) Software Install? 5-14 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Database Requirement The Server requires a database to hold its definitions and the following database type must be installed: • Oracle8i See the Digital DEC/EDI Software Product Description (SPD) for more information on software requirements such as version numbers. Run Time Libraries The following Tru64 UNIX Run Time Libraries must be installed. These are provided with the Tru64 UNIX operating system software distribution on CD-ROM: For example, to determine whether the subset is installed, use the following command: # setld -i | grep DFARTL DFARTL361 installed installed DIGITAL Fortran RTL #384 for DIGITAL UNIX Alpha Systems (f90 and f77) Network Interfaces TCP/IP Link Checking Check that the TCP/IP link works in both directions by pinging the other node you intend to use. The command is: # ping [remote node name] Use CTRL C to stop the test. Checking Tru64 UNIX Documentation Subset is Installed To check Tru64 UNIX Documentation Subset is installed, log in as the superuser (root), and enter the following command: # setld -i | grep OSFDCMT Subset Name Description DPORTL5nn DEC Pascal for Tru64 UNIX Alpha Runtime Support DFARTL3nn DEC Fortran for Tru64 UNIX Alpha Runtime Support Preparing to Install Digital DEC/EDI 5-15 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT This produces an output, with a mark against each version of the Tru64 UNIX Documentation Subset currently installed. Checking that Oracle8i is Installed Before you can check completely that all Oracle8i components have been installed, you need to set some environment variables specific to Oracle8i. Ensure that the Listener Services have been started from the Oracle account using the following command: # lsnrctl start 5-16 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Setting Oracle8i Environment Variables To set Oracle8i environment variables: 1. Check the /etc/passwd file to make sure that an Oracle8i account has been created. Note that the name of the account starts with the letters, ora. By default, the name is oracle. 2. Note the whole specification of its home directory, and switch to that user (for example, su - oracle). 3. Set the following environment variables as specified: • ORACLE_HOME-to home directory specification • ORACLE_SID-to decedidb • ORACLE_TERM-to vt100 After setting the environment variables, there are two ways in which you can check that Oracle8i and its components are installed: 1. Run the Oracle8i Installer This utility produces a listing of components and respective versions. 2. Check for individual Oracle8i components by using specific commands. In checking an installation by this method, you need to know what components should be installed. Running the Oracle8i Installer The Oracle8i Installer is located on the Oracle CD-ROM disk. Run the utility to give you a listing (with respective locations) of Oracle8i files installed on your system. This may take a few minutes. Checking for Individual Oracle8i Components You may check that individual components are installed by using commands that are specific to each one. You also have the option to list the version number of each component for which you check. Preparing to Install Digital DEC/EDI 5-17 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Checking for the Server Manager and DBMS From the Oracle account, and with the environment variables set as described in Setting Oracle8i Environment Variables on page 5-16, enter the following command: # svrmgrl This returns an output similar to the following: Oracle Server Manager Release 3.1.6.0.0 - Production Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved. Oracle8i Enterprise Edition Release 8.1.6.2.0 - Production JServer Release 8.1.6.2.0 - Production SVRMGR> exit Note that this shows that both the Server Manager and DBMS are installed. Their version numbers are also included in the output. Checking for Oracle8i SQLPLUS To check that the PL/SQL package is installed, enter the following command: migrgb.reo.dec.com> sqlplus An output similar to the following shows that it is installed: SQL*Plus: Release 8.1.6.0.0 - Production on Thu Mar 15 04:50:41 2001 (c) Copyright 1999 Oracle Corporation. All rights reserved. Enter user-name: Press CTRL C to escape. Checking for TCP/IP Services To check for the TCP/IP Services, enter the following command: # $ORACLE_HOME/bin/drivers This returns an output listing the installed SQL*Net Drivers To get their versions, enter the following commands: # $ORACLE_HOME/bin/lsnrctl LSNRCTL> version This produces an output listing the SQL*Net Drivers version numbers. 5-18 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Checking Mailbus 400 is Installed To check that Mailbus 400 is installed on Tru64 UNIX log in as the superuser (root), and enter the following command: # setld -i | grep MTAABASE This produces an output with a mark against each version of the Mailbus 400 Base subset currently installed. Checking DEC X.25 is Installed To check that DEC X.25 is installed on Tru64 UNIX log in as the superuser (root), and enter the following command: # setld -i | grep XXAACC This produces an output with a mark against each version of the DEC X.25 subset currently installed. Checking the Digital DEC/EDI account When installing the Digital DEC/EDI Server subset, some files will be assigned the ownership of decedi. This means that a decedi needs to be set up prior to installing the Digital DEC/EDI Server subset. To check that the decedi account has been set up, log in as the superuser (root), and enter the following command: # grep decedi /etc/passwd If the decedi account exists, then this will produce a line containing the account details. If no decedi account exists, no output will be generated. Adding a Digital DEC/EDI Account To add a decedi account, enter the following command: # adduser This will take you through a series of questions and then sets up the decedi account. Preparing to Install Digital DEC/EDI 5-19 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Disk Space Requirements The Table below lists the disk space requirements for loading each of the Digital DEC/EDI software subsets. The figures shown in these tables are peak requirements. After installation, slightly less disk space is required. Table 5-4 Disk Space Requirements Compare the space required for subsets with the free space currently on the disks where Digital DEC/EDI files will reside. Digital DEC/EDI Subset Space needed (Kb) Digital DEC/EDI Base 2,000 Digital DEC/EDI Client 2,500 Digital DEC/EDI Client Man Pages 150 Digital DEC/EDI Server 75,000 Digital DEC/EDI Server Man Pages 50 Digital DEC/EDI Translation Services 6,000 Digital DEC/EDI Mailbus 400 Gateway 1,500 Digital DEC/EDI OFTP Gateway 1,200 Digital DEC/EDI SMTP Gateway 500 Digital DEC/EDI BISYNC (3780) Gateway 50 Digital DEC/EDI Message Updates Base 1,200 Digital DEC/EDI Message Updates Man Pages 300 Digital DEC/EDI Message Updates TDCC files 8,000 Digital DEC/EDI Message Updates X12 files 21,000 Digital DEC/EDI Message Updates TRADACOMS files 500 Digital DEC/EDI Message Updates EDIFACT IMPDEF files 7,000 Digital DEC/EDI Message Updates ODETTE_IMPDEF_files 200 5-20 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Determining Disk Space To determine the amount of disk space available on your system, enter the following command: # df -k /usr This will produce an output similar to the example below: Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/re0g 1580378 970579 451761 68% /usr Note that this display shows that there are 451,761 KiloBytes available. Preparing to Install Digital DEC/EDI 5-21 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Deleting Digital DEC/EDI from Your System If you already have a Digital DEC/EDI subset installed on your system, and want to replace it with another version of that subset, you must delete the original subset first. For instance, if you are upgrading from one version of Digital DEC/EDI to another. Note that deleting the subset does not cause any user data to be lost, so on deleting a subset, and then installing a new subset no data will be lost. If you already have a version of Digital DEC/EDI from your system, and wish to re-install it, or replace it with a newer version, then you must delete each Digital DEC/EDI subset that you previously installed. To delete subsets: 1. Log in as superuser (login name, root). 2. Make sure you are at the root directory (/) by entering the following command: # cd / 3. Enter the following setld command (you may need to use the Bourne shell sh to run setld): # setld -i | grep DEDI This will return a list of subsets with a mark against installed items as shown in the following example: DEDICLT400 installed Digital DEC/EDI Tru64 UNIX Client DEDICLTMAN400 installed Digital DEC/EDI Tru64 UNIX Client Man Pages 4. Look for the word "installed" in the listing produced, and then delete the installed subsets. For example: # setld -d DEDICLT400 DEDICLTMAN400 5-22 Preparing to Install Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Backing Up Your System Disk Digital recommends that you back up your file systems before installing any software. For information about backing up your file systems, see the Tru64 UNIX system documentation. Installing Digital DEC/EDI 5-23 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Installing Digital DEC/EDI This section describes how to install Digital DEC/EDI. Before starting your installation, perform the pre-installation tasks listed in the previous section. The beginning of this section describes how to enter setld to start the installation procedure. The way you do this depends on whether you are installing: • From local CD-ROM media, see Installing From CD-ROM Consolidated Distribution Media on page 5-24 • From a Remote Installation Services (RIS) server area, see Installing From a Remote Installation Services (RIS) Distribution Area on page 5-25 It then explains the installation dialog during which you are prompted for details about how the installation is to take place. Stopping the Installation You can stop the installation procedure at any time by pressing Ctrl C. If you stop the installation, files created up to that point are not deleted. You must delete those files manually. To find out which Digital DEC/EDI files are on your system, enter the following command: # find / -name \*decedi\ Be careful of deleting data contained in /usr/var/adm/decedi or its subdirectories as this may cause Digital DEC/EDI configuration data to be lost. Time Required for Complete Installation The time taken to install each of the subsets from the Digital DEC/EDI kit varies depending on the size of your CPU and whether you are installing using local media, or from a Remote Installation Services (RIS) server area. In most cases, each subset should take only a few minutes to install. 5-24 Installing Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Installing From CD-ROM Consolidated Distribution Media This procedure loads Digital DEC/EDI files on to a disk belonging to the system where you perform the installation. When Digital DEC/EDI is run, its executable images are mapped into memory on your system. Follow these steps to install Digital DEC/EDI from CD-ROM media: 1. Mount the media on the appropriate disk drive. 2. Log in as superuser (login name, root) to the system where you will install Digital DEC/EDI. 3. Make sure 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. For example, if your drive is called ralc, enter the following command: # mount -dr /dev/ralc /cdrom 5. Enter a setld command that requests the load function (-l option) and identifies the directory in the mounted file system where the Digital DEC/EDI subsets are located. For example, if the directory location for these subsets is /cdrom/dedisubset_number/kit, enter the following command: # setld -l /cdrom/dedisubset_number/kit The installation procedure now displays the names of the Digital DEC/EDI subsets and asks you to specify the subsets you want to load. See Running the Installation Procedure on page 5-26 to continue the installation. Installing Digital DEC/EDI 5-25 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Installing From a Remote Installation Services (RIS) Distribution Area If you are installing Digital DEC/EDI subsets that reside in /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 will install Digital DEC/EDI. 2. Make sure you are at the root directory (/) by entering the following command: #cd / 3. Enter a setld command that requests the load function (-l) option and identifies the system where the Digital DEC/EDI subsets are located. For example, if you are loading Digital DEC/EDI subsets from a RIS distribution area on a node called orion, enter the following: #setld -l orion: RIS 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 Running the Installation Procedure on page 5-26 to continue the installation. 5-26 Installing Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Running the Installation Procedure Once you have entered the setld command to install the software, the system takes you through a dialog in which you are prompted for details about how the installation is to take place. These prompts are described on the following pages. At each prompt during the dialog, you can do any of the following: Enter your reply and press Return. Enter ? for more information about what is required. Abort the installation by pressing Ctrl/C. If you encounter any failures during the installation dialog, refer to Problems During Product Installation on page 5-28. Specifying Subsets You are prompted to specify which Digital DEC/EDI subsets you want to load. For example, when installing Digital DEC/EDI on Tru64 UNIX, the dialog is as follows: #setld -l /cdrom/dedi400/kit 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)Digital DEC/EDI 3780 Gateway 2)Digital DEC/EDI Base 3)Digital DEC/EDI Client Man Pages 4)Digital DEC/EDI Client 5)Digital DEC/EDI Internet SMTP/MIME Gateway 6)Digital DEC/EDI Mailbus 400 Gateway 7)Digital DEC/EDI Message Updates Base 8)Digital DEC/EDI Message Updates EDIFACT IMPDEF files 9)Digital DEC/EDI Message Updates Man Pages --MORE TO FOLLOW Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 2-4 10) Digital DEC/EDI Message Updates ODETTE IMPDEF files 11) Digital DEC/EDI Message Updates TDCC IMPDEF files 12) Digital DEC/EDI Message Updates TRADACOMS IMPDEF files Installing Digital DEC/EDI 5-27 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT 13) Digital DEC/EDI Message Updates X12 IMPDEF files 14) Digital DEC/EDI OFTP Gateway 15) Digital DEC/EDI Server Man Pages 16) Digital DEC/EDI Server 17) Digital DEC/EDI Translation Services The following choices override your previous selections: 18) ALL of the above 19) CANCEL selections and redisplay menus 20) EXIT without installing any subsets Add to your choices, choose an overriding action or press RETURN to confirm previous selections. Choices (for example, 1 2 4-6): 2-4 You are installing the following optional subsets: Digital DEC/EDI Base Digital DEC/EDI Client Man Pages Digital DEC/EDI Client Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. If you specify more than one number at the prompt, separate each number with a space, not a comma. Note If you are installing from a RIS distribution area, the number of subsets can vary, depending on which products are available in the RIS area, and on how many subsets they have. Also, if the subsets are already installed, they will not appear as a selectable option. Next, the dialog lets you verify your choice. For example, if you enter 18) in response to the previous prompt, you will see the following display: Digital DEC/EDI 3780 Gateway Digital DEC/EDI Base Digital DEC/EDI Client Man Pages Digital DEC/EDI Client Digital DEC/EDI Internet SMTP/MIME Gateway Digital DEC/EDI Mailbus 400 Gateway Digital DEC/EDI Message Updates Base Digital DEC/EDI Message Updates EDIFACT IMPDEF files Digital DEC/EDI Message Updates Man Pages Digital DEC/EDI Message Updates ODETTE IMPDEF files Digital DEC/EDI Message Updates TDCC IMPDEF files Digital DEC/EDI Message Updates TRADACOMS IMPDEF files Digital DEC/EDI Message Updates X12 5-28 Installing Digital DEC/EDI UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT IMPDEF files Digital DEC/EDI OFTP Gateway Digital DEC/EDI Server Man Pages Digital DEC/EDI Server Digital DEC/EDI Translation Services If the displayed subsets are the ones you want to load, enter y. If the displayed subsets are not the ones you intended to choose, enter n. In this case, the Subset Selection menu is displayed again, and you can correct your choice of optional subsets. Messages Displayed During the Loading Process The installation procedure loads and verifies the selected Digital DEC/EDI subsets. During this process, several messages are displayed. When you see the "Verifying" message during the subset installation, the installation procedure is checking that the files are copied correctly. Note that this is not an Installation Verification Procedure (IVP) message. If you see the "Broken pipe" message during the subsetinstallation, then this can be ignored as the subset will continue to be installed successfully Problems During Product Installation If errors occur during the installation, the system displays failure messages. For example, if the installation fails due to insufficient disk space, the following message appears: There is not enough space for subset DEDISERVsubset_number) DEDISERVsubset_number) will not be loaded. Errors can occur during the installation if any of thefollowing conditions exist: • The version of the operating system is incorrect. • A prerequisite software version is incorrect. • There is insufficient disk space. • The system parameter values for successful installation are insufficient. For descriptions of error messages generated by these conditions, refer to the relevant documentation on system messages, recovery procedures, and software installation. For information on system software requirements, refer to Table 5-3 Digital DEC/EDI Software Requirements on page 5-12 After Installation 5-29 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Files Created During Installation For more details of the files installed by an installation of Digital DEC/EDI, please refer to Appendix I UNIX Installation - Directory and File Listing. After Installation This Section explains what you need to do after the installation to make Digital DEC/EDI ready for use. Installation Checking Satisfactory installation is assumed if the files selected for the particular customer installation are found to be installed. The procedure for checking this is shown in Running the Installation Verification Procedure on page 5-30. 5-30 After Installation UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Running the Installation Verification Procedure After installing Digital DEC/EDI, you should 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 Digital DEC/EDI. The Digital DEC/EDI IVP verifies the installation by checking which Digital DEC/EDI subsets are installed. To run the IVP after an installation, enter the following command, where subsetname can be any Digital DEC/EDI subset: # setld -v subsetname If the verification process fails, look in the /var/adm/smlogs/fverify.log file for information to help diagnose the problem. Setting Up the System 5-31 UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Setting Up the System Before the system can be used for the first time, or after parts of the system have been changed, it must be set up. The Digital DEC/EDI system is comprised of both Application Clients, Servers, and PCs which monitor or configure the Digital DEC/EDI system. The setup activities need to be performed on the separate parts of the system in a particular order. The setup procedures are described in Part 3, Database Administration. 5-32 Setting Up the System UNIX - INSTALLATION OF DIGITAL DEC/EDI SERVER AND APPLICATION CLIENT Problems After Installation U.S. customers who encounter a problem while using Digital DEC/EDI can report it to Digital by telephoning the Digital Customer Support Center (CSC) at 1-800-354-9000. Customers with service contracts can also use an electronic means such as DSNlink. Customers without a service contract can arrange for per-call support. • The CSC will need the following information: • The name and version number of the operating system you are using. • The version of Digital DEC/EDI you are using. • The hardware system you are using (such as a model number). • A brief description of the problem (one sentence if possible). • Whether the problem is critical. • Any other information that may be helpful in trying to reproduce the problem, such as the specific commands you used to run the software, the error messages displayed, and source listings of the relevant software module or lines of code. If the problem is related to Digital DEC/EDI documentation, then report the problem to the CSC (if you have a service contract and the problem is severe). Chapter 6 OpenVMS - Installation of Server and Client This chapter describes the process of installing Server and Application Client, by a system manager or administrator, onto a OpenVMS Alpha platform. Preparation The following possibilities when installing Digital DEC/EDI V4.0 onto an OpenVMS system are described in this chapter: • it is a new installation onto a clean system • you are upgrading an earlier version Digital DEC/EDI V4.0 Server and Application Client can be installed together or separately, the Server can be on the same node as the Application Client, or could be on a different one. General It is assumed that the preparations detailed in Parts 1 and 2 have been completed satisfactorily, so that you have a checklist of the desired configuration. Check the Installation Kit is correct against the Bill of Materials (BOM) and indented bills report (BIL) which specify the number and contents of your media. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. Upgrading When upgrading your system to Digital DEC/EDI V4.0, existing files will be modified during the upgrade process. Backing up is recommended in the following instructions when appropriate. Examples All examples provided in this chapter are typical and are provided for information only. 6-2 Prerequisites - All Installations OPENVMS - INSTALLATION OF SERVER AND CLIENT Prerequisites - All Installations Operating System The following version of OpenVMS is needed for Digital DEC/EDI V4.0: • OpenVMS Alpha Version 7.2-1 Software Products The information contained in the following sections define which software products you will need in addition to Digital DEC/EDI for your selected configuration of the Digital DEC/EDI V4.0 products. More about Software Versions Software versions defined within this document were correct at time of publication, late changes are detailed in the Release Notes. For more information, contact your Digital Support representative. Mapping Services The Mapping Services are a separately licensed component of Digital DEC/EDI. OpenVMS Alpha Server 6-3 OPENVMS - INSTALLATION OF SERVER AND CLIENT OpenVMS Alpha Server This section describes the layered products which may be needed to run a Digital DEC/EDI server on an OpenVMS Alpha platform. Mandatory The following products are a mandatory requirement for all OpenVMS Alpha server installations: • OpenVMS Alpha • DECforms runtime • Oracle Rdb runtime TCP/IP • DEC TCP/IP Services In addition the Digital DEC/EDI Mapping Service may optionally extract record layouts from Oracle CDD/Repository. Gateway If you are using either of the OFTP or X.25 gateways, you need to have installed one of the following: • DECnet/OSI and X.25 • DECnet and DEC X.25 Client 6-4 OpenVMS Alpha Server OPENVMS - INSTALLATION OF SERVER AND CLIENT Pedi Gateway If you are using the Pedi Gateway, you would normally require the MAILbus 400 Message Transfer Agent. As there is no version of this currently available for OpenVMS Alpha, the Server contains an X.API component within the kit which needs to be separately installed. This X.API component allows Digital DEC/EDI to connect to a MAILbus 400 Message Transfer Agent (MTA) on another CPU using DECnet/OSI. 3780Plus Gateway When using the 3780Plus Gateway, you will need CLEO 3780Plus. Application Interface Your applications may interface to the V4.0 server on OpenVMS Alpha using one or more of the following interfaces: • Using a Digital DEC/EDI V4.0 Application Client, either on the same node as the server or on a separate node. If you are not expecting to use any of the above listed Application Clients, the choice of network layer to use will be influenced by which Digital DEC/EDI gateways you expect to run (or more specifically whether or not those gateways require DECnet/OSI). However all Application Clients must be connected using the same network layer. OpenVMS Alpha Server 6-5 OPENVMS - INSTALLATION OF SERVER AND CLIENT Supported Software Versions The table below shows versions of software products that are supported for use with Digital DEC/EDI V4.0 on OpenVMS Alpha. Table 6-1 OpenVMS Alpha Software Product Versions PRODUCT DESCRIPTION VERSION Mandatory OpenVMS Axp OS 7.2-1 DECForms Forms development env 3.0 Oracle RDB Oracle rdb 7.0.3 TCP/IP services 5.0A Optional Mailbus 400 MTA 2.0C X.25 1.4 DECnet-Plus/DECnet-OSI 5.01 X.500 directory services 4.0 6-6 OpenVMS Alpha Application Clients OPENVMS - INSTALLATION OF SERVER AND CLIENT OpenVMS Alpha Application Clients This section describes the layered products which are needed to run a Application Client on a OpenVMS Alpha platform. Some products are mandatory, others are optional and depend on which configuration options you select. Mandatory The following products are a mandatory requirement for all OpenVMS Alpha Application Client installations: • OpenVMS • A network transport: provided by DEC TCP/IP Services Software Licensing 6-7 OPENVMS - INSTALLATION OF SERVER AND CLIENT Software Licensing General Before you install and run Digital DEC/EDI V4.0 on a newly licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). License PAK The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing prerequisite or optional software along with Digital DEC/EDI, review the PAK status and install the PAKs for any prerequisite or optional software before you install Digital DEC/EDI. You should register your Digital DEC/EDI license before you do the installation. During the installation, the licenses are checked, and if any is missing you are asked if you want to continue. You can complete the installation, and run the IVP without having the license installed. However, you will not be able to run the Digital DEC/EDI software. Once you perform the license registration and have loaded an authorization key, you can use Digital DEC/EDI. Checking for Installed Licenses To check to see what licenses you already have loaded, use the command: $LICENSE LIST Registering a License To register a license under OpenVMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: 1. Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your Product Authorization Key (PAK). When it asks if you want to load the license, answer 'Yes'. 2. Issue the DCL command LICENSE REGISTER with the appropriate qualifiers that correspond to information on the PAK. If you choose this method, you must then use the LICENSE LOAD command to activate the license. More about License Management Facility For complete information on using LMF, see the manual on the License Management Utility in the OpenVMS documentation set. 6-8 Privileges For The Installing Account OPENVMS - INSTALLATION OF SERVER AND CLIENT Privileges For The Installing Account To install Digital DEC/EDI, you must be logged in to an account that has SETPRV, this will normally be the SYSTEM account. About the Examples Command examples used in this section assume that the installing account is SYSTEM. Checking Privileges To check to see what privileges you have, you can use the following command: $ SHOW PROCESS /PRIVILEGES Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. Disk Space Requirement 6-9 OPENVMS - INSTALLATION OF SERVER AND CLIENT Disk Space Requirement During installation working space is needed on the disk in excess of the space required just for the application. These requirements are detailed below: Table 6-2 Disk Space Requirements Determining Diskspace To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE Server/Client Disk During Installation After Installation OpenVMS Alpha Server System 90,000 75,000 ... for EDI data none 25,000 ... for Mapper none 22,000 OpenVMS Alpha Client System 9,000 1,800 ... for EDI data none 100 6-10 System Parameters OPENVMS - INSTALLATION OF SERVER AND CLIENT System Parameters Minimum values for the System Parameters when running Digital DEC/EDI are shown below. Higher values may be needed depending on other applications running at your site. Table 6-3 Minimum System Parameter Values The following paragraphs show you how to: • Check system parameter values with the OpenVMS System Generation Utility (SYSGEN) • Calculate values for the GBLPAGES and GBLSECTIONS system parameters • Change parameter values with the OpenVMS AUTOGEN command procedure System Parameter Client & Server Client Only CHANNELCNT 255 100 CLISYMTBL 500 250 DEFMBXMXMSG 256 256 DEFMBXBUFQUO 2,048 1,024 GBLPAGES 3,350 free global pages 1,500 free global pages GBLPAGFIL 9,216 8,192 GBLSECTIONS 84 free global sections 60 free global sections WSMAX 8,192 2,048 MAXBUF 2,048 1,024 MAXPROCESSCNT 64 20 VIRTUALPAGECNT 60,000 30,000 System Parameters 6-11 OPENVMS - INSTALLATION OF SERVER AND CLIENT Checking System Parameter Values The SYSGEN utility is used to check the system parameters. 1. Run the SYSGEN utility by using the following command: $ RUN SYS$SYSTEM:SYSGEN This will bring up the SYSGEN> prompt 2. Use the SHOW command to display selected parameter values with the following command: SYSGEN> SHOW nnnnnnn where nnnnnnn is the parameter name, for instance: SYSGEN> SHOW MAXBUF will give you the maximum buffer size. Repeat this process for all of the parameters listed in Table 6-3 Minimum System Parameter Values, noting the values which should equal or exceed the minimum values listed. 3. Type EXIT at the SYSGEN prompt to return to DCL level when you have finished checking the parameter values. More About SYSGEN For more information about using SYSGEN, see 'Guide to Setting Up an OpenVMS System' in the OpenVMS documentation on system management. 6-12 System Parameters OPENVMS - INSTALLATION OF SERVER AND CLIENT Calculating Values for GBLPAGES and GBLSECTIONS The values for GBLPAGES and GBLSECTIONS in Table 6-3 Minimum System Parameter Values, indicate how many unused pages or sections are available on your system. To check how many unused global pages and global sections your system has, carry out the following: 1. Use F$GETSYI to find out the number of global pages and global sections that are unused: $ unused_pages = f$getsyi("free_gblpages") $ unused_sections = f$getsyi("free_gblsects") 2. To display a summary of unused global pages and global sections, enter the following: $ WRITE sys$output unused_pages $ WRITE sys$output unused_sections 3. Determine if the number of unused pages is equal to or greater than the number specified in Table 6-3 Minimum System Parameter Values. If the number of unused pages is less than the number listed in the table, you need to increase the value for GBLPAGES. 4. Run the SYSGEN utility and use the SHOW command to determine the number of Global Sections (GBLSECTIONS) that have been allocated. $RUN SYS$SYSTEM:SYSGEN SYSGEN>SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic GBLSECTIONS 512 250 20 4095 Sections 5. Subtract the current free GBLSECTIONS value from the value shown in Table 6-3 Minimum System Parameter Values. The difference between the two is the amount by which you need to increase the current value obtained in Step 2. System Parameters 6-13 OPENVMS - INSTALLATION OF SERVER AND CLIENT Changing System Parameter Values Changes made to the System Parameters do not get updated until the AUTOGEN utility has been used. Next login after the AUTOGEN will use the updated values. Procedure To change value to the minimum value listed in Table 6-3 Minimum System Parameter Values: 1. Edit the file SYS$SYSTEM:MODPARAMS.DAT and add the following line for each parameter that needs changing: MIN_PARAMETERNAME = VALUE for example: MIN_MAXBUF = 2048 MIN_WSMAX = 8192 2. Run the AUTOGEN procedure to reset your system parameters. Note that AUTOGEN performs an automatic system shutdown and reboots when it has finished. Rebooting your system makes the new parameter values active. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK More About Autogen For more information about using AUTOGEN, see 'Guide to Setting Up an OpenVMS System' in the OpenVMS documentation on system management. 6-14 Account Quotas For The Installing Account OPENVMS - INSTALLATION OF SERVER AND CLIENT Account Quotas For The Installing Account The account you use to install Digital DEC/EDI must have sufficient quotas to enable you to perform the installation, these values are detailed below: Table 6-4 Process Account Quotas Account Server Client ASTLM 2,000 25 BIOLM 300 20 BYTLM 140,000 20,000 DIOLM 300 20 ENQLM 3,000 200 FILLM 1,000 100 JTQUOTA 2,048 1,024 PGFLQ 60,000 10,240 PRCLM 20 5 TQELM 1,000 10 WSDEF 2,048 1,024 WSEXTENT 8,192 4,096 WSQUO 4,096 2,048 Account Quotas For The Installing Account 6-15 OPENVMS - INSTALLATION OF SERVER AND CLIENT Changing Account Quotas User account quotas are stored in the file SYSUAF.DAT. You use the OpenVMS Authorize Utility to verify and change user account quotas. Changes are made using the following procedure: 1. Set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> 2. At the AUTHORIZE prompt (UAF>), use the SHOW command with the account you are going to use to install Digital DEC/EDI in order to check the particular account. For example: UAF> SHOW SYSTEM 3. To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: MODIFY account-name /quota-name=nnnn 4. The example below changes the FILLM quota for the SYSTEM account and then exits from the Authorize Utility: UAF> MODIFY SYSTEM /FILLM=1000 UAF> EXIT 5. After you exit from the utility, the OpenVMS system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. More about Account Quotas For more information on modifying account quotas, see the description of the AUTHORIZE utility in the OpenVMS System Manager's Manual. 6-16 Other Pre-Installation Information OPENVMS - INSTALLATION OF SERVER AND CLIENT Other Pre-Installation Information Accessing the Online Release Notes Digital DEC/EDI provides online Release Notes. If you specify OPTIONS N when you invoke VMSINSTAL, the installation procedure asks you if you want to display or print the Release Notes. The Release Notes question comes near the beginning of the installation. You should read the Release Notes before continuing with the installation. After Digital DEC/EDI has been installed, the Release Notes are in the file: SYS$HELP:DECEDI040.RELEASE_NOTES Files and Logical Names Added to Your System See Appendix I UNIX Installation - Directory and File Listing and Appendix J OpenVMS Installation - Directory and File Listing for lists of all the files and logical names the installation procedure adds to your system. Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for Digital DEC/EDI checks that the installation has been successful. During the installation, you are asked if you want to run the IVP as part of the installation. If you respond YES, VMSINSTAL runs the IVP. Digital recommends that you run the IVP to be sure that Digital DEC/EDI is installed correctly. After Digital DEC/EDI is installed, you can run the 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 Digital DEC/EDI is still installed correctly. Use the following command to run the IVP independently: $ @SYS$TEST:DECEDI$IVP.COM Other Pre-Installation Information 6-17 OPENVMS - INSTALLATION OF SERVER AND CLIENT VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: • Whether you are logged in to a privileged account • Whether you have adequate quotas for installation • Whether any users are logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you of the problem and asks if you want to continue the installation. In some instances, you can enter YES to continue. Stopping the Installation To stop the installation process and correct the situation, enter NO or press RETURN. Then correct the problem and restart the installation. Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. DIGITAL recommends that you do a system disk backup before installing any software on top of the operating system. Use the backup procedures that have been established at your site. More about Backup For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Manager's Manual. Aborting the Installation To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. 6-18 Other Pre-Installation Information OPENVMS - INSTALLATION OF SERVER AND CLIENT Time to Install The table below shows the approximate time it takes to carry out the installation. This varies depending on the type of media and system configuration. Table 6-5 Time taken to Instal Information Needed During Installation Digital DEC/EDI Account Details (UIC) The installation creates an account for use by Digital DEC/EDI. You must specify a unique user identification code (UIC) for the account. If the account already exists, because you are upgrading, then you are not asked to specify a UIC. Where To Put Files If you install the Server, the installation procedure asks you where to put the Server and the Mapper files. See Table 6-2 Disk Space Requirements, for details of how much space you need for these. Name of Server Node If you are installing a Client-only system, the installation procedure asks you for the name of the Server node and the name of the operating system the Server is running. Upgrades Only Shutting Down Digital DEC/EDI If you already have Digital DEC/EDI installed, you must shut down your Digital DEC/EDI system. The command to shut down Digital DEC/EDI is: $ @SYS$STARTUP:DECEDI$SHUTDOWN FULL Type of Installation Time to Install (minutes) OpenVMS Alpha Server and Client 7 to 15 OpenVMS Alpha Client only 2 to 5 Installation: Client On Top Of Server 6-19 OPENVMS - INSTALLATION OF SERVER AND CLIENT Installation: Client On Top Of Server You can install the Client on to a system that currently runs the Server and Client. If you do install the Client on to a Server node, the installation procedure warns you and asks if you want to continue: WARNING * Do you still want to proceed with this installation [YES]? Note that, if you choose to run the IVP after installing the Client on to a Server system, the IVP finds both the new Client files and the existing Server files, so that the total number of files it finds is much larger than for a normal Clientonly system. Installation: Server On Client-Only System You can install the Server on to a system that currently runs just the Client. When you do this, the installation procedures warns you that the Client is already installed and asks you if you want to continue. Client already exists on this node. Upgrading Client V3.2B to Server V4.0 * Do you still want to proceed with this installation [YES]? 6-20 Upgrading to V4.0 OPENVMS - INSTALLATION OF SERVER AND CLIENT Upgrading to V4.0 General Logicals Digital DEC/EDI stores logical names in three files: • SYS$MANAGER:DECEDI$LOGICALS.COM this file will be overwritten by future installations of Digital DEC/EDI. Do not change this file. • SYS$MANAGER:DECEDI$SYLOGICALS.COM this file will not be touched by future installations of Digital DEC/EDI. If you ever want to change any Digital DEC/EDI logical names, define them in this file. • SYS$COMMON:[SYSMGR]DECEDI$SYLOGICALS_.COM this file gets copied from SYS$COMMON:[SYSMGR]DECEDI$SYLOGICALS_NODE.TEMP LATE during the first startup after installation. This file contains node specific logicals like decedi$n_x12_trns_max whcih defines the maximum number of x12 translators allowed to start on a particular node. Procedure The procedure for upgrading by installing Digital DEC/EDI V4.0 over an earlier version is similar to the procedure for installing onto a 'clean' system. The process is detailed in The Installation on page 6-22. Installing on a Cluster You can install Digital DEC/EDI on a single node in a cluster and can run the same on any node in the cluster. Migration Upgrading If you have a Digital DEC/EDI environment, the order of upgrading to Digital DEC/EDI V4.0, is to upgrade any Cockpit installations, then the server followed by any remote application clients. After the installation of the server you need to migrate your audit database. For any configuration there are tasks which must be performed after the installation in order to migrate your audit database and applications. Upgrading to V4.0 6-21 OPENVMS - INSTALLATION OF SERVER AND CLIENT All Services on a Single Node Upgrade to a V4.0 server. Multinode System with Translation and Communications all on One Node Upgrade the server node (i.e. the node running translation and communications services) to a V4.0 server. 6-22 The Installation OPENVMS - INSTALLATION OF SERVER AND CLIENT The Installation This section describes the questions that appear during the installation of a Server and Client. Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example [YES]. If you want to give the default response, press the key. The following information is 'generic' and is intended to provide guidance through the installation process. Assistance is given when choices have to be made, but be aware that displayed information will vary from that provided both here and in the Appendices log examples. More about VMSINSTAL Options For further information on other VMSINSTAL options, see the OpenVMS documentation on software installation. The Installation 6-23 OPENVMS - INSTALLATION OF SERVER AND CLIENT Starting the Installation 1. To start the installation, log in to a privileged account, such as the SYSTEM account. 2. Type in the VMSInstall command line using the syntax described below: @SYS$UPDATE:VMSINSTAL [product] [device] OPTIONS N [product] - the installation name for the product. For Digital DEC/EDI Version 4.0, use the following installation name: On OpenVMS Alpha: DECEDIA040 [device] - the name of the device on which you have mounted the media which contains the product to install. For example, MTA0: is the device name for a tape drive. Note that [device] can also be a directory specification, if you have the save-sets on disk. Press to commence the installation. The installation will now continue with prompts being displayed when user input is required. * Are you satisfied with the backup of your system disk [YES]? You should always backup your system disk before performing an installation. If you are satisfied with the backup of your system disk, press the key. If not enter NO to terminate the installation. You will need to go back to Step 1 to restart the installation after you have completed backing up. * Where will the distribution volumes be mounted: Enter the device name. Note that the Digital DEC/EDI disk must be mounted. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above Select option [2]: Press to send the file to print, VMSINSTAL prompts you for a queue name, or you can accept the default print device. Enter 1 to display the Release Notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. 6-24 The Installation OPENVMS - INSTALLATION OF SERVER AND CLIENT Enter 3 to display the Release Notes immediately on the console terminal and then print the Release Notes. VMSINSTAL prompts you for a queue name for the printed version. Enter 4 followed by to ignore the Release Notes for the time being. * Do you want to continue the installation [NO]?: The default at this point is to abort installation by pressing . To continue, enter YES followed by . The Release Notes are then copied to a file in the SYS$HELP directory. For example: * Do you want to continue the installation [NO]?: YES %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. The Release Notes are in the following file: SYS$HELP:DECEDI040.RELEASE_NOTES The name of the Release Notes file installed by VMSINSTAL consists of the current product name and version number. Do you want to purge files replaced by this installation [YES]? Purging of files superseded by this installation is recommended; however, if you need to keep files from previous installations, enter NO in response to the question. You may need to keep some of the files in the DECEDI$DATA directory. * Do you want to run the IVP after the installation [YES]? It is recommended that you run the IVP; enter YES to do so, or NO if you do not want to run it. * Do you want to install the server [YES]? Press to accept the default and install the Server and Client, or type NO to install just the client. The Installation 6-25 OPENVMS - INSTALLATION OF SERVER AND CLIENT About Client-Only Installation If you have opted to install the only the Client, after identifying the directory device and UIC, you will be asked to identify where the Server will run. Once you have entered that location, the VMSInstall procedure will continue without any more input from you. The following Digital DEC/EDI component(s) are not licensed on this node Digital DEC/EDI OFTP Services V4.0 Digital DEC/EDI OFTP-Package Services V4.0 Note that the message does not necessarily mean that there is an error; the procedure checks both optional and mandatory software and licenses. When it has completed the checks, the installation procedure asks if you want to continue * Do you still want to proceed with this installation [YES]? Press to accept the default and continue, or type NO followed by to abort the installation. Warning if you are Upgrading If you are upgrading, you get a warning message at this point, telling you that the new installation will retain the integrity of existing data, because Digital DEC/EDI already exists on this node Press to accept the default and continue, or type NO followed by to abort the installation. You must have RDB/OpenVMS version 7.0.3 or later installed on your system to use Digital DEC/EDI V4.0, consequently you must take the default value by pressing . On what device should the DECEDI directories reside? Specify the Device and press . Data Directories Creation Once you have specified the device, VMSINSTAL creates a directory called [DECEDI] on that device, and then the data directories are created in that directory. In further questions in the installation procedure, the logical DECEDI$TOP points to the [DECEDI] directory. Directory/Disk Space See Table 6-2 Disk Space Requirements on page 6-9 to find out how much space you need for the files that the installation procedure puts in these directories. You need more space once your Digital DEC/EDI system is running. 6-26 The Installation OPENVMS - INSTALLATION OF SERVER AND CLIENT When Upgrading If the DECEDI account already exists, then the installation procedure uses the existing DECEDI directory specification. This installation procedure creates the directories (if they do not exist), and assigns an ACL list to the directories to allow access to the Mapper, and to users on this Server node who have been granted one of the Mapper rights identifiers: FBR$SUPERVISOR FBR$OPERATIONS FBR$DEVELOPMENT. * What is the UIC to be used for the Digital DEC/EDI account: Type in the UIC in the form [x,y]. For example: [123,4], and then press to action it and continue the installation. The Installation 6-27 OPENVMS - INSTALLATION OF SERVER AND CLIENT About the UIC The UIC chosen must: • not have a rights identifier already allocated to it • not be used by anything else. • be valid. • have a group number (the first value)greater than the SYSGEN parameter MAXSYSGROUP. This has a default value of 8. Any group number less than or equal to this value is regarded as a system UIC and Digital DEC/EDI will reject it. Remainder of the Installation The installation procedure displays a number of informational messages that report on the progress of the installation, and there are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you asked for files to be purged, they are purged now. On completion of a satisfactory installation the following message is displayed: Installation of Digital DEC/EDI succeeded. 6-28 The Installation OPENVMS - INSTALLATION OF SERVER AND CLIENT Installation Failure If errors occur during the installation, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of Digital DEC/EDI 4.0 has failed. About the IVP If you chose to run the IVP, VMSINSTAL runs it now and checks that all the specified files have been installed. One of the following messages will display: IVP was successful. or IVP for Digital DEC/EDI V4.0 has failed If the IVP fails, the following messages are displayed: IVP for Digital DEC/EDI V4.0 has failed to execute to completion. %VMSINSTAL-E-IVPFAIL, The IVP for Digital DEC/EDI V4.0 has failed. Errors can occur during the installation if any of the following conditions exist: • The operating system version is incorrect • A prerequisite software version is incorrect • Quotas necessary for successful installation are insufficient • System parameter values for successful installation are insufficient • The OpenVMS help library is currently in use More about Error Messages For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value). The Installation 6-29 OPENVMS - INSTALLATION OF SERVER AND CLIENT Displayed Files with Errors The IVP only displays files that have errors; it does not list them all. For each file that has an error, the IVP describes briefly what the problem is. If the IVP fails and displays too many files to be seen on a video terminal, you can restart it and output the results to a file with the following command: $ @SYS$TEST:DECEDI$IVP.COM /OUTPUT="file.ext" Completing the Installation Procedure Informational messages (similar to example below) indicate the installation procedure is complete: Installation of DECEDIA V4.0 completed at 14:05 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA040.VMI DATA VMSINSTAL procedure done at 14:06 $ LOGOUT SYSTEM logged out at 31-MAR-2001 25:09:17.62 VMSINSTAL deletes or changes entries in the process symbol tables during the installation, to continue using the System Manager's account and you want to restore these symbols, you should log-out and log-in. 6-30 Installing the Message Update Kit OPENVMS - INSTALLATION OF SERVER AND CLIENT Installing the Message Update Kit To install the Message Update Kit, repeat the installation procedure detailed in Starting the Installation on page 6-23. After Step 2 you will see a message similar to the following: Please select: 1 - To install EDI standards definitions. 2 - To re install Digital DEC/EDI V4.0. 3 - To abort this installation. * Option [1]: Press to accept the default and install the Standards Definitions. You can now select which standards you install from the steps that follow. When the selections have been completed, the installation will continue and complete itself without further input. After Installation 6-31 OPENVMS - INSTALLATION OF SERVER AND CLIENT After Installation After installing Digital DEC/EDI and the document standards , you may need to perform the following tasks: • Configure a Client/Server service • Edit the system startup and shutdown files • Reboot the system • Change account details for those people who are going to use the Digital DEC/EDI INTERCHANGE command • Migrate data if upgrading from a previous version of Digital DEC/EDI. 6-32 After Installation OPENVMS - INSTALLATION OF SERVER AND CLIENT Editing the System Files This section applies to Server systems. You must edit the system startup and shutdown files to provide for automatic startup and shutdown of Digital DEC/EDI when your system is rebooted. There are three possible Digital DEC/EDI modes of startup shown below: Table 6-6 Startup Modes [1] The command for a full startup must come after the command that starts Rdb Monitor. Add the command line that starts Digital DEC/EDI to the system startup file. You must position this new command line after the line that invokes the network startup command procedure. System Startup The following is the system startup command: SYS$MANAGER:SYSTARTUP_VMS.COM Mode Startup Command Startup [1] @SYS$STARTUP:DECEDI$STARTUP After Installation 6-33 OPENVMS - INSTALLATION OF SERVER AND CLIENT Network and Rdb Monitor Startup The following example shows the network startup and Rdb Monitor startup command lines, followed by the startup command line for Digital DEC/EDI: @SYS$MANAGER:STARTNET.COM @SYS$STARTUP:RMONSTART.COM @SYS$STARTUP:DECEDI$STARTUP.COM You need to add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @SYS$STARTUP:DECEDI$SHUTDOWN.COM Note that when you shutdown your system you must ensure that Digital DEC/EDI closes down before DECnet and/or P.S.I., and before Rdb Monitor. Digital DEC/EDI uses the symbols DECEDI$DEFINE and DECEDI$DEASSIGN to define and de-assign its logical names. The symbols and logical names, are defined by the command procedure SYS$MANAGER:DECEDI$LOGICALS.COM. Defining Digital DEC/EDI Logical Names Digital DEC/EDI stores logical names in three files: • SYS$MANAGER:DECEDI$LOGICALS.COM this file will be overwritten by future installations of Digital DEC/EDI. Do not change this file. • SYS$MANAGER:DECEDI$SYLOGICALS.COM this file will not be touched by future installations of Digital DEC/EDI. If you ever want to change any Digital DEC/EDI logical names, define them in this file. • SYS$COMMON:[SYSMGR]DECEDI$SYLOGICALS_.COM this file gets copied from SYS$COMMON:[SYSMGR]DECEDI$SYLOGICALS_NODE.TEMP LATE during the first startup after installation. This file contains node specific logicals like decedi$n_x12_trns_max whcih defines the maximum number of x12 translators allowed to start on a particular node. 6-34 After Installation OPENVMS - INSTALLATION OF SERVER AND CLIENT Using the Correct Pascal Run-Time Library You must have a Pascal run-time library if you intend to send or receive X12 or TDCC documents. To find out if you have the Pascal run-time library on your system, give the following command: $ DIRECTORY SYS$LIBRARY:PAS$RTL.EXE If the file does not exist, contact your Digital support center. Modifying the System Page File Size This section applies to: • Server systems. To maintain system performance, you should increase the size of your system page file. You should increase the page file size by 1000 blocks for each Digital DEC/EDI process that you run, up to a maximum of 20,000 blocks for 20 processes. You cannot do this until you have Digital DEC/EDI running, because the number of Digital DEC/EDI processes depends on your configuration. Once you have Digital DEC/EDI configured, you can find out how many Digital DEC/EDI processes there are on your system by using the DCL command SHOW SYSTEM. The name of every Digital DEC/EDI process begins with DECEDI$ so you need to count how many such processes you have. To change the size of the your page file, enter the following command: $ @SYS$UPDATE:SWAPFILES and at the following prompt: Enter the new size for paging file enter the required value. The new page file will take effect when you next boot your system. Once you have set the new page file size, run your system for a few days and then use AUTOGEN to provide values tailored to your particular system. Re-booting the System 6-35 OPENVMS - INSTALLATION OF SERVER AND CLIENT Re-booting the System A system reboot: • Enables you to get Digital DEC/EDI ready for use • (Server systems only) Ensures that the edits to the system startup command file are correct • Establishes any new parameter settings Note, however, that rebooting is optional. You can reboot your system after you have installed Digital DEC/EDI, edited the system startup and shutdown files, and reset the system parameters if necessary. Re-naming the Digital DEC/EDI Error Log This section applies to: Server systems. Digital DEC/EDI's main error log file on the Server is DECEDI$ERROR:DECEDI$ERRORS.LOG. This file can become quite large, so it is a good idea for you to rename it whenever you reboot your system. You may want to add a suitable command to your system startup procedure so that it renames this file. You can reduce the speed with which the error log grows by defining the logical name DECEDI$LOG SEVERITY to be "WARNING". This restricts Digital DEC/EDI to logging only those errors of severity WARNING and higher. You must add your definition to the following file: SYS$MANAGER:DECEDI$SYLOGICALS.COM 6-36 Modifying User Accounts OPENVMS - INSTALLATION OF SERVER AND CLIENT Modifying User Accounts This section applies to Server systems. Page File Quota You must make sure that the account for each person who is going to use the Digital DEC/EDI INTERCHANGE command has a paging file quota of at least 60,000. Access From a Local Client If you intend to use a local Client to communicate with the Server, then all user accounts that will use the Client interface must have the following: The Digital DEC/EDI FBR$OPERATIONS process rights identifier. The same minimum account quotas as for the DECEDI account, see Table 6-4 Process Account Quotas See Defining Mapping Service Rights on page 6-43 for a description of the following process rights identifiers: FBR$SUPERVISOR FBR$DEVELOPMENT FBR$OPERATIONS Adding Symbols to User's LOGIN.COM For the Digital DEC/EDI Mapper to function properly, each user must have the following symbol in the login.com file: $ FBR$DECEDI_EXTRACT :== $SYS$SHARE:FBR$DECEDI_EXTRACT Modifying User Accounts 6-37 OPENVMS - INSTALLATION OF SERVER AND CLIENT Determining and Reporting Problems If an error occurs while Digital DEC/EDI is being used and you believe that the error is caused by a problem with Digital DEC/EDI, take one of the following actions: • If you have a BASIC or DECsupport Software Agreement, you should call your Customer Support Center. (With these services, you receive telephone support that provides high-level advisory and remedial assistance.) • If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). • If you purchased Digital DEC/EDI within the past 90 days and you think the problem is caused by a software error, you can submit a Software Performance Report (SPR). When you find an error in the Digital DEC/EDI documentation, please fill out and submit the Reader's Comments form at the back of the document in which the error was found. Include the section and page numbers where the errors were found. 6-38 The DECEDI Account OPENVMS - INSTALLATION OF SERVER AND CLIENT The DECEDI Account This section applies to both Server and Client systems. The installation creates an account with a username of DECEDI. This account has only network access, and has the quotas listed below that are required to run Digital DEC/EDI. Note, the DECEDI account is used only by Digital DEC/EDI processes, not Digital DEC/EDI users. Table 6-7 Quotas for the DECEDI Account If you are planning to use the V4.0 Support Services, it may be necessary to increase the value of the DECEDI account quotas to suit the traffic. For a busy system where the maximum number of extra Copy, Rippleback, DECnet or Application fileserver processes is 1 or more, then it is recommended to at least double the account quotas, and possibly increase some of the system parameters. If messages appear in the error log file from any of the fileserver processes complaining that quotas are too low, or serious unexpected errors appear, for example from RMS or RDB, these are likely symptoms of low quotas. Quota Value ASTLM 2,000 BIOLM 300 BYTLM 200,000 DIOLM 300 ENQLM 10,000 FILLM 1,000 JTQUOTA 4,096 PGFLQ 60,000 PRCLM 20 TQELM 1,000 WSDEF 2,048 WSEXTENT 8,192 WSQUO 4,096 The DECEDI Account 6-39 OPENVMS - INSTALLATION OF SERVER AND CLIENT Increasing Disk Quota This section applies to Server systems. If disk quotas are enabled on the system disk, or any disk that you use for Digital DEC/EDI data, you need to make sure that the DECEDI account has a suitable amount of disk quota for those disks. The value depends on how busy your Digital DEC/EDI system is, but 100,000 free blocks is probably enough to start with. If you need to find out how much quota the DECEDI account has, or change its quota, use DISKQUOTA. For example, to find out the current quota: $RUN SYS$SYSTEM:DISKQUOTA DISKQ>SHOW DECEDI DISKQ>EXIT To give the DECEDI account a permanent quota of 100,000 blocks: $RUN SYS$SYSTEM:SYSMAN SYSMAN>DISKQUOTA MODIFY DECEDI/PERMANENT=100000 SYSMAN>EXIT 6-40 The DECEDI Account OPENVMS - INSTALLATION OF SERVER AND CLIENT Calculating the Required Number of Processes Once you have installed Digital DEC/EDI you may need to modify the quota depending upon the number of processes you wish to run. To calculate the required number of processes, determine the required number of extra: • EDIFACT converters (XEDIFC) and translators (XEDIFT) • X12 converters (XX12C) and translators(XX12T) • TRADACOMS converters (XTCOMC) and translators (XTCOMT) • Gateways The total number of Digital DEC/EDI processes is the sum of the processes in Table 6-8 Digital DEC/EDI Processes: Table 6-8 Digital DEC/EDI Processes You should add this total to the number of processes you normally run on your system and then add any extra processes required for layered products that you have installed with Digital DEC/EDI. Compare this total with your current setting for the maximum number of processes (MAXPROCESSCNT). If necessary, increase the values of MAXPROCESSCNT to the total you have just calculated. Process Number Data Server 1 Communication 1 Control Import/Export 1 (optional) Gateway 3780Plus Gateway 1 (optional) OFTP Gateway 1 (optional) X.25 Gateway 1 (optional) X.435 Gateway 1 (optional) EDIFACT Service 4 + XEDIFC + XEDIFT (optional) (incl. ODETTE) X12 Services (incl. 3 + XX12C + XX12T (optional) TDCC) TRADACOMS 2 + XTCOMC + XTCOMT (optional) The DECEDI Account 6-41 OPENVMS - INSTALLATION OF SERVER AND CLIENT Minimum Recommended Value We recommend that the minimum value for MAXPROCESSCNT is 64. Modifying Quota for the DECEDI Account When you have calculated the number of processes you need, you may need to increase some of the quotas. The following sections describe how to calculate certain quotas on Server systems. Calculating the WSEXTENT Value To calculate the value of WSEXTENT, do the following: To make sure the Digital DEC/EDI Converter has access to enough virtual memory, you should set the WSEXTENT value for the DECEDI account to at least the following value: • WSEXTENT = 8,192 + (external document size * 100) where: WSEXTENT sizes are in pages (512 bytes) external document size is the size, in Kbytes, of the external format file created by the converter. For example, for Digital DEC/EDI to handle a 70 kilobyte document efficiently, the quota should be as follows: WSEXTENT = 8,192 + (70*100) = 15192 pages If the value of WSEXTENT that you need is larger than the default values for the DECEDI account, see Table 6-4 Process Account Quotas, you should increase the DECEDI account value. If it is smaller, keep the default value because other Digital DEC/EDI components needs at least the default value for this process quota. If WSEXTENT exceeds the system parameter WSMAX you should increase WSMAX by adding the new value to MODPARAMS.DAT and use AUTOGEN to modify WSMAX. Calculating the ENQLM Value The EDIFACT and X12 transmission file builders lock each document when they place it in a transmission file. The lock is released when the file is successfully built. The ENQLM quota must be large enough to cope with the maximum number of documents allowed in a transmission file. 6-42 The DECEDI Account OPENVMS - INSTALLATION OF SERVER AND CLIENT EDIT PROFILE sets up various parameters which control the number of documents that can be placed in a transmission file. These are: • TPF MDPG L, Maximum documents per group • TPF MGPI L, Maximum groups per interchange • TPF MIPF L, Maximum interchanges per transmission The maximum number of locks therefore needed by the transmission file builder for a transmission to a particular trading partner is: MIPF l * MGPI L * MDPG L +1 (for the transmission file) For EDIFACT, if functional groups are not used, then MGPI L=1 Ownership of the DECEDI Account The installation procedure creates the DECEDI account with an owner of "DECEDI". You should not need to change this, but if you do so, do not include spaces in the name of the owner. If you put spaces there, any subsequent reinstallation of Digital DEC/EDI will fail. Account privileges on the DECEDI Account The installation procedure grants the following privileges to the DECEDI account: • NETMBX TMPBMX The NETMBX privilege is required so that Digital DEC/EDI processes can communicate. You should not need to modify the privileges granted to the DECEDI account. The DECEDI Account 6-43 OPENVMS - INSTALLATION OF SERVER AND CLIENT Defining Mapping Service Rights Mapping Service security facilities prevent accidental insertion or loss of documents and reduce the risk of fraudulent use of Mapping Service processing. Mapping Service security facilities make use of OpenVMS rights identifiers. You will need to make sure that each person who is going to use Mapping Service has been assigned at least one of the following rights. The installation procedure has already added them to the OpenVMS rights database, but they must be assigned to each Mapping Service user manually. • FBR$SUPERVISOR • FBR$DEVELOPMENT • FBR$OPERATIONS More on Authorize The OpenVMS documentation on the AUTHORIZE Utility explains how to assign an identifier to a user. 6-44 The DECEDI Account OPENVMS - INSTALLATION OF SERVER AND CLIENT The Rights Database The OpenVMS rights database provides the security facilities for Mapping Service. At most sites, the rights facility's system manager maintains this database. To use Mapping Service, you must be assigned one or more of the three Mapping Service rights categories: 1. FBR$SUPERVISOR This is the most privileged category. It provides special supervisory rights. With this assignment, you also have the rights permitted in the other two categories. 2. FBR$DEVELOPMENT This provides the next level of access development rights. This user can modify the Mapping Service table and run test runs, but cannot perform production tasks. 3. FBR$OPERATIONS Users assigned to this category generally only process documents in a production environment, preferably a production library. FBR$SUPERVISOR When assigned FBR$SUPERVISOR, you can edit the Mapping Service tables and set the TEST INDICATOR to LIVE. The FBR$SUPERVISOR category also includes the rights assigned by the FBR$DEVELOPMENT and FBR$OPERATIONS categories. A user with FBR$SUPERVISOR rights is the only one who can set the TEST INDICATOR to LIVE, and therefore allow a Mapping Service table to be used for production. As such, you must create and maintain one or more directories that contain specifications for the files and images used in processing. These specifications are listed below. Set the protection on this directory or set of directories with the DCL SET PROTECTION. Production specifications affect the following files and images: • Mapping Service tables. The TEST INDICATOR option in the Mapping Service table should not be set to LIVE until the table has been copied from the development environment into the production library. The supervisor must also set the options to enable the audit and history points as required by the installation, and then compile the Mapping Service table. The DECEDI Account 6-45 OPENVMS - INSTALLATION OF SERVER AND CLIENT • Audit Database. The audit database resides in the directory identified by the system logical, FBR$LIBRARY, which is defined at installation time. This directory should have READ permission for those with Mapping Service rights, plus any access for FBR$SUPERVISOR. The database must be created with granted rights of INSERT and READ for the EVENT relation. • Hook Shared Images. Since part of Mapping Service processing can be performed in the customization routines at hook points, these hook shared images must be protected from unauthorized modification. Put these images into their own directory. This should not be the FBR$LIBRARY directory but could be a subdirectory under FBR$HOME. You can define a system logical, for example FBR HOOKS, to point to this directory. The supervisor must set the Shared Image filename in the Mapping Service table to point to the appropriate directory before compiling the table. • History files. A directory should be created that has WRITE access for those with FBR$DEVELOPMENT and FBR$OPERATIONS rights. Specify this directory in the logical FBR$HISTORY to indicate where history files are to be written. FBR$DEVELOPMENT Assignment to the FBR$DEVELOPMENT category allows the user to create and modify Mapping Service tables using the User Interface, but the TEST INDICATOR option cannot be set to LIVE. This user can also execute the Mapping Service runtime program, but cannot use it with a Mapping Service table that has the TEST INDICATOR option set to LIVE. If for any reason a fetch for Digital DEC/EDI obtains a LIVE document, the document is assigned QUIT (allowing it to be placed back in the DEC /EDI Application Server Available Documents Pool) and the program is aborted with an error message. 6-46 Upgrades - Data Migration OPENVMS - INSTALLATION OF SERVER AND CLIENT FBR$OPERATIONS With this right, the user can execute the Mapping Service runtime program using a Mapping Service table that has the TEST INDICATOR set to LIVE. If the Mapping Service runtime program gets a document with a TEST INDICATOR not set to LIVE while processing documents with a Mapping Service table whose TEST INDICATOR is set to LIVE, the document will be aborted. This right does not imply FBR$DEVELOPMENT rights. If this user must also process TEST data, then the FBR$DEVELOPMENT right must also be granted. Upgrades - Data Migration Important! During upgrades, the database is automatically migrated during the upgrade to V4.0. Files Created During Installation For more details of the files installed by the installation of Digital DEC/EDI, please refer to Appendix J OpenVMS Installation - Directory and File Listing. Chapter 7 Other Platforms - Installation of Digital DEC/EDI Application Client This chapter describes installation of Digital DEC/EDI Application Client onto the following platforms: • Sun Solaris • HP-UX • RedHat Linux • Windows NT/2000 Introduction The preparations necessary for a successful installation are described and then the installation process is detailed. Some post-installation tasks are included for information. 7-2 Preparing to Install on HP-UX OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Preparing to Install on HP-UX This chapter describes the tasks that you should carry out before installing the Digital DEC/EDI Client on an HP-UX system. It also describes the prerequisites for installing the Digital DEC/EDI Client. Reading the Online Release Notes Digital DEC/EDI Application Client provides online release notes. Digital strongly recommends that you read the release notes before using the product. The release notes may contain information about changes to the application.The release notes for Digital DEC/EDI Application Client are in the following file: /usr/doc/DECEDI400.release_notes You can use the following command to read the release notes after Digital DEC/EDI Application Client is installed: # more /usr/doc/DECEDI400.release_notes Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your Digital DEC/EDI Application Client software distribution kit. If your software distribution kit is damaged or incomplete, contact your Digital representative. Checking Installation Procedure Requirements This Chapter discusses requirements for installing Digital DEC/EDI Application Client. Installing Digital DEC/EDI Application Client, including running the Installation Verification Procedure (IVP), which takes approximately 2 minutes, depending on your type of media and system configuration. Checking Login Privileges You must have superuser privileges to install the Digital DEC/EDI Application Client software. Preparing to Install on HP-UX 7-3 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Checking Hardware Requirements To install Digital DEC/EDI Application Client, you need the following hardware: • Terminal You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. See the Digital DEC/EDI Application Client Software Product Description (SPD) for additional hardware requirements. Checking Software Requirements Digital DEC/EDI Application Client V4.0 requires the HP-UX operating system Version 10.20. This operating system includes TCP/IP, which must be configured as described in an applicable HP UNIX installation guide. Digital DEC/EDI Application Client also requires that an Network Interface subset is loaded on the system where you install Digital DEC/EDI Application Client. Refer to the Software Product Description (SPD) for details about the version number required for this release. Refer to the SPD for details of the version number. Determining Which Subsets to Load You must choose which Digital DEC/EDI Application Client subsets you want to load. The subsets have the following titles: • Digital DEC/EDI V4.0 HP-UX Client. The Client software. • Digital DEC/EDI V4.0 HP-UX Client Man Pages. Reference manual pages for Client's command line interface. Determining Disk Space Requirements The Table below list the disk space requirements for loading Digital DEC/EDI Application Client software subsets: you need this space available on the disks where you choose to load the software subsets. The figures shown are peak requirements. After installation, slightly less disk space is required. The tables list the disk space requirements per directory which is relevant if you are doing installations on systems where these directories are mount-points for different disk partitions. 7-4 Preparing to Install on HP-UX OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Table 7-1 Space Required for Client and Client Man Pages Using these disk space requirements, total the values for the subsets you will load in each directory. Compare the space required for subsets with the free space currently on the disks where Digital DEC/EDI Application Client files will reside. To determine the amount of disk space available on your system, enter the df command. The available spacelisted must accommodate the requirements listed in the tables above. Backing Up Your System Disk Digital recommends that you back up your file systems before installing any software. For information about backing up your file systems, see the HPUX system documentation. Directory Client (Kb) Client Man Pages (Kb) /usr 500 100 /var 110 - /etc 50 - Total 660 100 Preparing to Install on Sun Solaris 7-5 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Preparing to Install on Sun Solaris This section describes the tasks that you should carry out before installing the Digital DEC/EDI Client on an Sun Solaris system. It also describes the prereqisites for installing the Digital DEC/EDI Client. Reading the Online Release Notes Digital DEC/EDI Application Client provides online release notes. DIGITAL strongly recommends that you read the release notes before using the product. The release notes may contain information about changes to the application. The release notes for Digital DEC/EDI Application Client are in the following file: /usr/doc/DECEDI400.release_notes You can use the following command to read the release notes after Digital DEC/EDI Application Client is installed: # more /usr/doc/DECEDI400.release_notes Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your Digital DEC/EDI Application Client software distribution kit. If your software distribution kit is damaged or incomplete, contact your DIGITAL representative. Checking Installation Procedure Requirements This Chapter discusses requirements for installing Digital DEC/EDI Application Client. Installing Digital DEC/EDI Application Client, including running the Installation Verification Procedure (IVP), takes approximately 1 minute, depending on your type of media and system configuration. Checking Login Privileges You must have superuser privileges to install the Digital DEC/EDI Application Client software. 7-6 Preparing to Install on Sun Solaris OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Checking Hardware Requirements To install Digital DEC/EDI Application Client, you need the following hardware: • Terminal You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. See the Digital DEC/EDI Application Client Software Product Description (SPD) for additional hardware requirements. Checking Software Requirements Digital DEC/EDI Application Client V4.0 requires the Sun Solaris operating system V2.6. or above. This operating system includes TCP/IP, which must be configured as described in the applicable Sun Solaris installation guidebook. Determining Which Subsets to Load You must choose which Digital DEC/EDI Application Client subsets you want to load. The subsets have the following titles: • Digital DEC/EDI V4.0 Sun Solaris Client. The Client software. • Digital DEC/EDI V4.0 Sun Solaris Client Man Pages. Reference manual pages for Client's command line interface. Determining Disk Space Requirements The tables below list the disk space requirements for loading Digital DEC/EDI Application Client software subsets: you need this space available on the disks where you choose to load the software subsets. The figures shown in these tables are peak requirements. After installation, slightly less disk space is required. The tables list the disk space requirements per directory. This is relevant if you are doing installations on systems where these directories are mount points for different disk partitions. Preparing to Install on Sun Solaris 7-7 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Table 7-2 Space Required for Client and Client Man Pages Using these disk space requirements, total the values for the subsets you will load in each directory. Compare the space required for subsets with the free space currently on the disks where Digital DEC/EDI Application Client files will reside. To determine the amount of disk space available on your system, enter the df command. Backing Up Your System Disk Digital recommends that you back up your file systems before installing any software. For information about backing up your file systems, see the Sun Solaris system documentation. Directory Client (Kb) Client Man Pages (Kb) /usr 500 100 /var 110 - /etc 50 - Total 660 100 7-8 Installing the Digital DEC/EDI Client OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Installing the Digital DEC/EDI Client This section describes how to install the Digital DEC/EDI Application Client. Before you start the installation, read Chapter 5 UNIX - Installation of Compaq DEC/EDI Server and Application Client, The first part of this chapter describes how to enter (setld) to start the installation procedure. The way you do this depends on whether you are installing: • Locally, using CD-ROM media • From a server area Installing From CD-ROM Consolidated Distribution Media This procedure is for Sun Solaris only. It loads Digital DEC/EDI Application Client files on to a disk belonging to the system where you perform the installation. When Digital DEC/EDI Application Client is run, its executable images are mapped into memory on your system. Follow these steps to install Digital DEC/EDI Application Client from CDROM media: 1. Mount the media on the appropriate disk drive. 2. Log in as superuser (login name root) to the system where you will install the Digital DEC/EDI Application Client. 3. Move to an area on disk (for example, /kits) where you have some space to unpack the tar file. # cd /kits You need approximately 800 Kb. 4. Copy the files from the CD-ROM onto disk by using the tar command: # tar - xvf/cdrom/sun_solaris/decedi0400_sun_client.tar This creates an output directory from which you can install the kit. The tar command also puts a copy of the setld command in the /etc area. Use it to install the client software, as follows: # /etc/setld -l output The installation procedure now displays the names of the Digital DEC/EDI Application Client subsets, and asks you to specify the subsets you want to load. See Chapter 4 to continue the installation. Installing the Digital DEC/EDI Client 7-9 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Installing From an RIS Distribution Area If you are installing Digital DEC/EDI Application Client 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 will install Digital DEC/EDI Application Client. 2. Make sure you are at the root directory (/) by entering the following command: #cd / 3. Enter a setld command that requests the load function -l option and identifies the system where the Digital DEC/EDI Application Client subsets are located. For example, if you are loading Digital DEC/EDI Application Client subsets from a 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 Running the Installation Procedure on page 7-9 to continue the installation. Running the Installation Procedure Once you have entered the setld) command to install the software, the system takes you through a dialogue in which you are prompted for details about how the installation is to take place. At each prompt during the dialogue, you can do any of the following: 1. Enter your reply and press (Return). 2. Abort the installation by pressing (Ctrl/C). There are some minor differences in the Sun Solaris and HP-UX dialogues. For a full listing of the dialogues, see Appendix G Sun Solaris Client or Appendix H HP-UX Client, depending on which platform you are installing on. If you encounter any failures during the installation dialogue, see (error_messages_app). 7-10 Installing the Digital DEC/EDI Client OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Specifying Subsets You are prompted to specify which Digital DEC/EDI Application Client subsets you want to load. For example, when installing the Digital DEC/EDI Client on Sun Solaris, the dialogue is as follows: Enter Subset Selections The subsets listed below are optional: 1 Digital DEC/EDI V4.0 Sun Solaris Client 2 Digital DEC/EDI V4.0 Sun Solaris Man Pages 3 All of the Above 4 None of the Above 5 Exit without installing subsets Enter your choice(s): If you specify more than one number at the prompt, separate each number with a space, not a comma. Note: Note that if you are installing from a RIS distribution area, the number of subsets can vary, depending on what products are available in the RIS area and how many subsets they have. Next, the dialogue lets you verify your choice. For example, if you enter 3 in response to the previous prompt, you will see the following display: You are installing the following optional subsets: Digital DEC/EDI V4.0 Sun Solaris Client Digital DEC/EDI V4.0 Sun Solaris Man PagesIs this correct? (y/n): If the displayed subsets are the ones you want to load, enter y. If the displayed subsets are not the ones you intended to choose, enter n. In this case, the subset selection menu is again displayed and you can correct your choice of optional subsets. Messages Displayed During the Loading Process The installation procedure loads and verifies the selected Digital DEC/EDI Application Client subsets. During this process, you see a sequence of messages on the screen. 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 Installation Verification Procedure (IVP) message. After Client Installation 7-11 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT After Client Installation This section explains what you need to do after the installation to make Digital DEC/EDI Application Client ready for use. After the Client Installation After installing the Digital DEC/EDI Client, you must: • Run the Digital DEC/EDI Installation Verification Procedure (IVP) • Delete any older Digital DEC/EDI client from your system Refer to Part 3 for advice on any database migration tasks that you may need to complete Running the Installation Verification Procedure After installing Digital DEC/EDI Application Client, 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 Digital DEC/EDI Application Client. The Digital DEC/EDI Application Client IVP verifies the installation as follows: · Checks that the client subset is installed. To run the IVP after an installation, enter the following command, where subsetname can be any Digital DEC/EDI Application Client subset: # setld -v subsetname For a sample Digital DEC/EDI Application Client IVP, see appropriate: • (sample_listing_ivp_osf) • (sample_listing_ivp_ux). If the verification process fails, look in the /var/adm/fverify.log file for information to help diagnose the problem. 7-12 DIGITAL DEC/EDI Application Client on Redhat Linux OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Deleting Digital DEC/EDI Application Client from Your System If you must remove a version of Digital DEC/EDI Application Client from your system, delete each subset that you previously installed. To delete subsets: 1. Log in as superuser (login name root)). 2. Make sure you are at the root directory (/) by entering the following command: # cd / 3. Enter the following setld) command (you may need to use the Bourne shell sh to run setld): # setld -i | grep DEDI For example: # setld -i | grep -i dediclt DEDICLT400 installed Compaq DEC/EDI Client DEDICLTMAN400 installed Compaq DEC/EDI Client Man Pages 4. Look for the word "installed" in the listing produced, and then delete the installed subsets. For example: # setld -d DEDICLT400 DEDICLTMAN400 Deleting "Compaq DEC/EDI Client Man Pages" (DEDICLTMAN400). Deleting "Compaq DEC/EDI Client" (DEDICLT400). DIGITAL DEC/EDI Application Client on Redhat Linux Preparing to Install on Redhat Linux This section describes the tasks that you should carry out before installing the DIGITAL DEC/EDI Client on a Redhat Linux system. It also describes the prerequisites for installing the DEC/EDI Client. Reading the Online Release Notes DEC/EDI Application Client provides online release notes. DIGITAL strongly recommends that you read the release notes before using the DIGITAL DEC/EDI Application Client on Redhat Linux 7-13 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT product. The release notes may contain information about the application. The release notes for DEC/EDI Application Client are in the following file: /usr/doc/decediv40.release_notes Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your DEC/EDI Application Client software distribution kit. If your software kit is damaged or incomplete, contact your DIGITAL representative. Checking the Installation Procedure Requirements Installing DEC/EDI Application Client approximately takes 1min, depending on your type of media and system configuration. Checking Login Privileges You must have superuser privileges to install the DEC/EDI Application Client software. Checking Hardware Requirements To install DEC/EDI Application Client, you need the following hardware: -Terminal You can use either a hardcopy or video terminal to communicate with the operating system. See the DEC/EDI Application Client Software product Description (SPD) for additional hardware requirements. Checking Software Requirements DEC/EDI Application Client V4.0 requires the Redhat Linux operating system 6.2. This operating system includes TCP/IP, which must be configured as described in the applicable Redhat Linux installation guidebook. Determining Disk Space Requirements The tables below list the disk space requirements for loading DEC/EDI Application Client software: you need this space available on the disks where you choose to load the software. The figures shown in these tables are peak requirements. After installation, slightly less disk space is required. The tables list the disk space 7-14 DIGITAL DEC/EDI Application Client on Redhat Linux OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT requirements per directory. This is relevant if you are doing installations on systems where these directories are mount points for different disk partitions. To determine the amount of disk space available on your system, enter the following command. # df Backing up your System Disk: DIGITAL recommends that you back up your file systems before installing any software. For information about backing up your fily systems, see the Redhat Linux system documentation. Installing from the Distribution Media This procedure is for Redhat Linux only. It loads DEC/EDI Application Client files on to a disk belonging to the system where you perform the installation. When DEC/EDI Application Client is run, its executable images are mapped into memory on your system. Follow these steps to install DEC/EDI Application Client: 1. Mount the media on the appropriate disk drive 2. Log in as superuser (login name: root) to the system where you will install the software 3. Move on to the area where you have sufficient disk space to untar the file, and issue the following command: # tar -xvf /cdrom/decedi0400_linux_client.tar This untars the files into the new directory output 4. Change directory # cd output Table 7-3 Space required for Client and Client Man pages. Directory Client (Kb) Client Man Pages (Kb) /usr 500 100 /var 110 - Total 610 100 DIGITAL DEC/EDI Application Client on Redhat Linux 7-15 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT 5. Use Redhat Package Manager (rpm) tool to install the software by issuing the following command # rpm -i DEDI-4-0.i386.rpm This will install both the Client software and the man pages. After Client Installation Running the Installation verification procedure 1. After completion of the installation, verify for the # rpm -V DEDI This command verifies the DEDI-4-0 installed on your system. The log shows any failures in the installation. Configuring the Applicatin Client You must configure the Application Client before you can user. The following command configures the application. #/usr/bin/decedi_config.sh Deleting DEC/EDI Application Client from your System If you must remove a version of DEC/EDI Application Client from your system, you need to perform the following: 1. Log into the system as superuser 2. Query the RPM to view the installed DEC/EDI products # rpm -q DEDI 3. Issue the following command to uninstall the product you selected (e.g. DEDI-4-0) # rpm -e DEDI-4-0 4. This removes the client software from your system. For more details about files, installation and configuration see the APPENDIX I. 7-16 DIGITAL DEC/EDI Application Client on Windows NT/ 2000 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT DIGITAL DEC/EDI Application Client on Windows NT/ 2000 Preparing to Install on Windows NT/ 2000 This section describes the tasks that you should carry out before installing the DEC/EDI Client on a Windows NT/ 2000 system. It also describes the prerequisites for installing the DEC/EDI Client. Reading the Online Release Notes DEC/EDI Application Client provides online release notes. DIGITAL strongly recommends that you read the release notes before using the product. The release notes may contain information about changes to the application. The release notes for DEC/EDI Application Client are in the following file: decediv40.release_notes Checking the Software Distribution Kit Use the Bill of Materials (BOM) to check the contents of your DEC/EDI Application Client software distribution kit. If your software kit is damaged or incomplete, contact your DIGITAL representative. Checking the Installation Procedure Requirements This Chapter discusses requirements for installing DEC/EDI Application Client. Installing DEC/EDI Application Client approximately takes 1min, depending on your type of media and system configuration. Checking Login Privileges Any User who has enough privileges to install software, can install the DEC/EDI Application Client software. Checking Hardware Requirements To install DEC/EDI Application Client, you need the following hardware: Terminal See the DEC/EDI Application Client Software product Description (SPD) for additional hardware requirements. DIGITAL DEC/EDI Application Client on Windows NT/ 2000 7-17 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT Checking Software Requirements DEC/EDI Application Client V4.0 requires the Windows NT/ 2000 operating system. Determining Disk Space Requirements The tables below list the disk space requirements for installing DEC/EDI Application Client software: you need this space available on the disk where you choose to install the software. The figures shown in these tables are peak requirements. After installation, slightly less disk space is required. The tables list the disk space requirements of the directory in which the Client is going to be installed. Installing from the Distribution Media This procedure is for Windows NT/ 2000 only. It installs DEC/EDI Application Client software on to system where you perform the installation. Follow these steps to install DEC/EDI Application Client: 1. Log in to the system where you will install the software 2. Insert the Product CD into the CD drive 3. Go to the directory Platforms/Win32/Client 4. Double click on the Compaq DEC/EDI Application Client self- extracting executable. This starts the installation procedure, which itself guides you for the installation. Table 7-4 Space required for Client and Help Directory Client (Mb) Installation directory 1.8 Total 1.8 7-18 DIGITAL DEC/EDI Application Client on Windows NT/ 2000 OTHER PLATFORMS - INSTALLATION OF DIGITAL DEC/EDI APPLICATION CLIENT After Client Installation, you are required to perform the following configuration: 1. Copy decedi_servers.template file to decedi_servers.dat and place it in the Application Client installation directory itself. 2. The Application Client software uses this file to connect to the Compaq DEC/EDI Server. 3. Open decedi_servers.dat in a text editor and edit the contents as mentioned therein and save the modifications. Refer APPENDIX J for complete file listing. Deleting DEC/EDI Application Client from your System If you must remove DEC/EDI Application Client from your system, you need to perform the following: 1. Log in to the system. 2. Select Control Panel->Add/Remove Programs-> Compaq EDI Application Client 3. This uninstalls the DEC/EDI Application Client software from your machine. Chapter 8 Managing Message Updates This chapter describes the installation of Digital DEC/EDI Message Updates by the System Manager or Administrator, onto the following platforms: • Tru64 UNIX • OpenVMS Introduction Messaging standards are normally input during the installation process. This is covered in the following chapters: • Chapter 5 UNIX - Installation of Compaq DEC/EDI Server and Application Client • Chapter 6 OpenVMS - Installation of Server and Client The following features which are provided through the Message Update Services are covered in this chapter as shown below: • Installing new versions of an EDI Standard. See Installing New Versions of EDI Standards on page 8-3. • Creating a new version from an existing version. See Copying Existing Versions to New Ones on page 8-4. • Copying data labels for a version of a standard to a different versions. See Copying Data Labels Between Versions on page 8-4. • Deleting a version of an EDI standard. See Deleting a Version of an EDI Standard on page 8-4. 8-2 MANAGING MESSAGE UPDATES Using the Message Update Services Tru64 UNIX The Message Update Service Tool is installed in the directory /usr/sbin with the name decedi_must. To invoke the Message Update Service Tool: • The Digital DEC/EDI database must exist. • You must be logged into the root account # decedi_must When you run the tool, you are presented with a menu of options (See Tru64 UNIX and OpenVMS on page 8-3). OpenVMS To invoke the Message Update Service Tool: • The Digital DEC/EDI data server must be running. • You must be logged into an authorised account $ RUN DECEDI$TOOLS:DECEDI$MESSAGE_UPDATES.EXE When you run the tool, you are presented with a menu of options (See Tru64 UNIX and OpenVMS on page 8-3). 8-3 MANAGING MESSAGE UPDATES Tru64 UNIX and OpenVMS The following sections describe each of the options. Installing New Versions of EDI Standards If you elect to install new versions of EDI standards from the messages directory you are presented with a menu of all of the standard version files installed on your Server: You can choose to install one version of a standard at a time, or all versions of a standard. Installation of a version of standard involves translating the standard definition in the supplied IMPDEF message file into Digital DEC/EDI format. This may be time consuming. If multiple versions of a standard are required, it can be more efficient to select ALL versions of a standard, and leave the installation running. Versions of standards that are not required can be removed by using the delete version option. If a selected version already exists in the database, then you are asked if the installation should continue. Once a version of a standard has been installed, that version can not be used by Digital DEC/EDI until Data Labels have been defined for that version. This is done by using the Data Label Generator. When the exit option is selected from the install menu, a reminder about Data Labels is displayed on the screen. If a problem is detected during the installation of a version of a standard then the Message Update Service Tool ensures that the standards database is not left in a corrupt state. It does this by removing any parts of the standard definition that had been installed by the installation process. 8-4 MANAGING MESSAGE UPDATES Copying Existing Versions to New Ones If you elect to copy an existing version of a standard to a new version of the same standard then a menu listing all of the versions currently installed on Digital DEC/EDI is displayed. On selecting a version of a standard to copy you are prompted for the name of the new version to be created. The Digital DEC/EDI Message Update Service Tool then copies the existing version of the standard to the new version. Copying Data Labels Between Versions If you elect to copy the Data Labels associated with one version of a standard to a different version of the same standard, a menu is displayed, listing all of the versions currently installed. On selecting a version to copy from, you are prompted for a version to copy to. Deleting a Version of an EDI Standard If you elect to delete a version of a standard, then a menu is displayed, listing all of the versions that are currently installed. On selecting a version to delete, the specified version is deleted, and a menu of remaining standards and versions is displayed. Enter the menu number of the standard and version to remove.Before deleting the a version of a standard, the Message Update Service Tool searches all of the trading partner profiles on the Server for any that use the specified standard and version. If any profiles are found then the tool displays a warning message, and prompts you to indicate whether the delete processing should continue. Dealing with Recovery The Digital DEC/EDI Message Update Service Tool has built-in recovery processing to prevent standards definitions in the database from becoming corrupt. If, for any reason, execution of the Message Update Service Tool is halted while it is updating the database, then it is likely that the database will have been corrupted. 8-5 MANAGING MESSAGE UPDATES When it is next run, the tool detects that the database is corrupt. You are offered the choice of continuing with the action that the tool was performing at the time of interruption, or removing the corrupt version from the database. 8-6 MANAGING MESSAGE UPDATES Where to Look If Things Go Wrong If problems occur while you are using the Message Update Service Tool, error messages are recorded in the Message Update Services Log File. This file is named DECEDI_MUS.LOG and it is created in your default directory. If the Message Update Service Tool detects an error, and a log file does not already exist in your directory, a new log file is created, and the error message appended to the new file. If a log file does exist in your default directory, then the error is appended to the existing file. The log file may contain the following classes of message: • %MUS-E- : Error Messages. • %MUS-W- : Warning Messages. • %MUS-I- : Informational Messages. The main use of the log file is to aid your Digital DEC/EDI Support centre in solving any problems that occur. If a log file is created during the execution of the Digital DEC/EDI Message Update Service Tool, and it contains messages other than informational messages, then it is recommended that you contact your Digital DEC/EDI Support centre. Chapter 9 Installing Digital DEC/EDI Cockpit and CommandCenter This chapter describes the installation of Digital DEC/EDI Cockpit and CommandCenter, by the System Manager or Administrator, onto PCs running the following: • Windows NT/2000 Pre-Installation Tasks In preparing to install a Cockpit or a CommandCenter kit, there are three groups of tasks to complete: • Check the contents of your Cockpit or CommandCenter kit • Make sure that you have at least the pre-requisite hardware to run Cockpit or CommandCenter • Make sure that pre-requisite software applications are installed correctly on your computer setup. Check your Cockpit or CommandCenter Kit There are two kits: • The CommandCenter kit • The Cockpit kit Note that Cockpit and Commandcenter kits are separately ordered items. CommandCenter Kit The CommandCenter kit contains the following component: 9-2 Pre-Installation Tasks INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER • CommandCenter (including Cockpit) Cockpit Kit The Cockpit kit contains the following component: • Cockpit Pre-Installation Tasks 9-3 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Check for Prerequisite Hardware The products have the following hardware requirements: • 80486sx processor or better. • VGA monitor or better (SVGA is recommended for CommandCenter). • 64 Mb or more of main memory (RAM). 64 Mb are recommended. 64 Mb of main memory for Windows NT. 128 Mb are recommended. • Sufficient hard disk space to 'unpack' the Digital DEC/EDI components before they are installed. The demand for disk space during installation is approximately double that occupied by each component when installation is complete. The disk space requirements are: - Cockpit requires 4 Mb. Therefore, during installation, you need 8 Mb. - CommandCenter requires 10 Mb. Therefore, you may require up to 20 Mb. In total, you may require up to 28 Mb of hard disk space during installation. • A CD-ROM reader (for CommandCenter only) • A LAN connection. • A mouse or compatible pointing device. 9-4 Pre-Installation Tasks INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Check for Prerequisite Software The following software must be installed and running on the personal computer before you install Cockpit or CommandCenter. You should install these products in the order in which they are listed: • Microsoft Windows NT or Windows 2000. Rdb • Oracle ODBC driver for Rdb, Version 2.0.20, 2.10.11 (32-bit driver). Oracle8 Supported Oracle8 and SQL*NET combinations are outlined in the following short sections: On Windows NT: • Oracle8 ODBC driver (32-bit driver), Version 8.00.03.00 or higher • Oracle SQL*NET Client Version 2.3.4 or higher • Oracle8 Required Support Files 7.2.2.3.1 or higher On Windows 2000: • Oracle 8 ODBC driver, Version 1.13.5.0.0A or higher • Oracle SQL*NET Client, Version 2.2.2.1.0 or higher • Oracle TCP/IP Protocol Adapter (V2), Version 2.2.2.1.0 or higher Backup your Hard Disk Before installing Cockpit or CommandCenter on your PC, it is recommended that you backup the disk or disks on to which you will do the installation. In addition to the above, you need to ensure that your Digital DEC/EDI Server node already has the Digital DEC/EDI V4.0 software correctly installed. The following section provides some additional notes on installing the database access components. Pre-Installation Tasks 9-5 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Additional Notes on Installing Pre-requisite Software Pre-Installation Tasks for Oracle 8i on the PC If you want to use Oracle 8i as your preferred database, you will need to carry out the following pre-installation tasks: 1. Run the SQL*Net Easy Configuration utility, which is part of the Oracle for Windows program group, to add an alias for the Digital DEC/EDI database as follows: 2. Select the "Add Database Alias" option, and click OK 3. Enter the following details, substituting the actual host name of the Digital DEC/EDI server node in place of Database Alias: _decedidb The node name should be the short form. For example, for edipc.domain.com, use edipc. 4. Enter the full address of the TCP/IP Host name, and the database instance. TCP/IP Host Name: .domain.com Database Instance: decedidb 5. Click OK to add the alias 6. Select Exit SQL*Net Easy configuration, and click OK. 9-6 Pre-Installation Tasks INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Checking for the Prerequisite Software Before proceeding with the installation of Cockpit or CommandCenter, you are recommended to perform the checks listed in this section. These help you to verify that the software on your PC, and the network link to your Digital DEC/EDI Server are correctly set up. You should be able to complete each of these tests before installing and using Cockpit or CommandCenter. You should be able to do the following: • If you are using TCP/IP networking services, test the TCP/IP network connection between your PC and the Digital DEC/EDI Server by using ping. Time to Install The amount of time to install Cockpit or CommandCenter depends on the speed of your PC and hard disks that you are using. However the installation of Cockpit and Command Center should take no longer than 5 minutes. Installing the Software 9-7 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Installing the Software This section describes how to install Cockpit and CommandCenter, and lists some of the more common problems that may be encountered during the installation. 9-8 Installation Procedure INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Installation Procedure Copy the contents of the CDROM to the PC. Locate the executable (\ProgramFiles\Digital) and click on the icon. The software gets installed. Server Configuration As the installation continues, you are prompted to configure the server. If you wish, you may postpone this task until after the installation.You may also terminate the installation at this point. If you decide to configure the server, select one of two options: Add.. to configure a new server Edit.. to configure a listed server that you need to select The Edit Server Setup dialog is displayed. Use the following information to help you enter the correct information in each field on your setup screen: Installation directory. This is the directory where files are installed. You can change the default value offered if you wish. The Setup program creates the specified directory if it does not already exist. Computer Name. This is the name of your PC, for example, edipc. Server Name. This is the name of the Digital DEC/EDI Server you want to use. Note that this name is not the nodename (although it can be). It is any name you wish to use to refer to a particular Server. If you expect to use more than one Server, enter the name of one of them here. You may add more definitions when you first run Cockpit or CommandCenter. Server Nodename. This is the nodename of the Server you want to use. It must be a name that your network understands. You should enter the full name of the Server, unless your PC and the Server are operating on a common network segment. Server Type. Select from either Tru64 UNIX or OpenVMS. Server Version Supported Servers for Tru64 UNIX are V3.2, V3.2B and V4.0. Supported Servers for Open VMS are V3.2, V3.2B and V4.0. Network. For Tru64 UNIX and OpenVMS, the supported network is TCP/IP . Installation Procedure 9-9 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Database Driver. This field defines the database product that you are using on the PC and on the Server, as well as the ODBC driver used on the PC. Microsoft Access Do not select this. It is reserved by Digital for demonstration versions of the Cockpit and CommandCenter. User Defined Select this if the database you are using does not match one of the options above. Unlike the other options, the ODBC datasource isn't automatically configured by the installation. The installation will tell you the name of the datasource, which should be noted, and you must configure it yourself. See the section in Post Installation Tasks for a description of how to do this. Oracle73 Select this if you are using an Oracle73 database. Account. This is the name of an account on the Server that you intend to use to access the Digital DEC/EDI Server data. If you know the name of this account, enter the value now. If you don't know the name, enter any value: you will be able to change it, or use other accounts when you use CommandCenter or Cockpit. Note that this value is case-sensitive. That is, values like JONES and jones are regarded as different accounts. Database Name. This is only relevant with Oracle 7 database. OnLine This is the name of the Digital DEC/EDI database on the Digital DEC/EDI Server system. With Oracle 7, leave this value set to its default value of decedi_db. Class Options are: GENERIC, V51, V60, V61. Specify GENERIC if you have standard SQL Services installed on your OpenVMS Server. Specify one of the other options if you have multi-version SQL installed, to tell it which version to use. OnLine Service. This is the name of the network service to use to connect to the named database on the Digital DEC/EDI Server. This should be set to decedi_pc. Readme Files As the installation nears completion, you are prompted to decide whether to read the Readme file. Reboot Options When the installation is complete you may be prompted to reboot your PC. 9-10 Installation Procedure INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER You do not have to reboot at this time, but note that you must do this eventually to register any new server configuration. Release Notes By default, the installation creates a Program Manager group called Digital DEC/EDI Cockpit or Digital DEC/EDI CommandCenter, depending on which kit you are installing. One of the icons within that group displays release notes about the software. You should review these notes before proceeding with the post-installation tasks described in the next chapter. TCP/IP Tracing • If you are using the TCP/IP network interface, use this button to 'trace' the requests and traffic across the network between the PC and Server into a file on the PC. Further information on using the tool is provided in the Digital DEC/EDI: User's Guides (Tru64 UNIX and OpenVMS). Post-Installation 9-11 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Post-Installation This chapter assumes that you have now completed the installation of Cockpit or CommandCenter, as described in the previous chapter. Before you can use the software, you need to perform a number of post-installation tasks. Some of these tasks involve configuration work on the Digital DEC/EDI Server node or nodes that you are using. The tasks are summarized here. Post-Installation Tasks After you install CommandCenter or Cockpit, your post-installation tasks include the following: • Server Configuration • Running the Digital DEC/EDI Network Tester These tasks are described in the following sections. Server Configuration Activities On each Digital DEC/EDI Server, you need to complete the following before you can use Cockpit or CommandCenter to connect to the Server. These activities are described in more detail in the Digital DEC/EDI: User's Guide, unless indicated otherwise: • Install the CommandCenter LMF license PAK on a Digital DEC/EDI Server. The CommandCenter needs to find a valid license on at least one Server node. The license does not need to be installed on each Server. If you are using CommandCenter to connect to more than one Server, install the license on the Server you use most often. • Create a user account that your PC uses to access the Digital DEC/EDI database. When you use Cockpit or CommandCenter to connect to the Server, you are asked to enter the name of this account and its password. • Grant access to the Digital DEC/EDI database for this user account. Unless stated otherwise, you need to repeat these Server configuration activities on each Digital DEC/EDI Server that you are using. The next section describes how you can test the resulting configuration. 9-12 Post-Installation INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Post-Installation Tasks This section explains how to do the post-installation configuration tasks to link Digital DEC/EDI CommandCenter and Cockpit on your personal computer to your Digital DEC/EDI Server. The tasks include: • Configure your Server to accept a link from your personal computer. • Setup your Server account. If you have already installed the Digital DEC/EDI CommandCenter or Cockpit before, and you have configured your Server to accept a link from your personal computer, there is no need to repeat the last two steps mentioned above. Problem Solving 9-13 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Problem Solving There are two main sections in this section: • General Problems Information on general problems • Getting More Information This section outlines the range of error logs and diagnostic tools that you can use to obtain more detailed information about problems you may encounter. Some of these tools are specific to a particular version of the CommandCenter or Cockpit, and they are marked as such. The section also contains advice on how to report problems to Digital. General Problems • You are not licensed for Digital DEC/EDI on server nodename: . This message may be displayed when running any of the CommandCenter editors or when using the version of Cockpit from the CommandCenter kit. The license allowing you to use the CommandCenter with this Server has expired or has not been installed. See the Digital DEC/EDI: Installation book for information on installing the CommandCenter license. • Using to abort Cockpit or CommandCenter. There are situations where the Cockpit or CommandCenter can hang the Digital DEC/EDI Server. These occur when either Cockpit or one of the CommandCenter editors has been aborted abnormally, either by a fault in the code, by you having pressed , or by some other abnormal exit. It is recommended that you avoid using to abort the applications whilst they are reading the Digital DEC/EDI Server database. In this situation, if the application was in the middle of an operation, links to the Server will still be active, waiting for the application to terminate the transaction explicitly. Starting the application again does not clear this. The result may be a protected read lock on the Digital DEC/EDI Server database which may affect the components of the Digital DEC/EDI Server eventually. 9-14 Problem Solving INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER • Problems running several CommandCenter editors. The CommandCenter does not place any explicit limitations on the number of separate editors you can run concurrently. However, in practice, there are limitations that you may reach. As you run any Windows application, you consume various Windows resources. Windows places a fixed limit on certain resources that the Cockpit and CommandCenter editors use in common with other applications. It is possible for you to attempt to exceed the available resources by running many applications. However, there is no simple method of predicting the point at which resources will run out. To help avoid Windows resource problems, it is recommended that you try not to run more than two CommandCenter editors at the same time. Also, avoid running too many other applications at the same time as running the Cockpit or CommandCenter. Error When Connecting to Server Normally seen when attempting to log on when the Port Server has not been started. Startup the Port Server and try again. Problem Solving 9-15 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Tru64 UNIX Server - Problem Solving In general, these sections of problems are reported by the Digital DEC/EDI Network Tester. TCP/IP Network Interface related Problems • 'Error when connecting to Server' 'The specified address is not available from the local machine' You will receive this error message when attempting to connect to the Server, if you have not manually added the decedi_csg service to the services file on your PC. You must add this entry to the services file prior to connecting to the Digital DEC/EDI Server, as described in Network Tester on page 9-20. 9-16 Problem Solving INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER OpenVMS Server - Problem Solving In general, these sections of problems are reported by the Digital DEC/EDI Network Tester. ODBC-related problems Driver not capable This means you have installed other software on your PC since ODBC installation, and it has disturbed the Digital DEC/EDI settings. A more likely cause is that your ODBC kit is too old, in which case you should obtain the latest kit, and reinstall. Unsupported version of SQL/Services Client DLL Trying to attach to a database or table fails with the message: [MICROSOFT][ODBC DLL]Driver's SQLAllocConnect failed. [DEC][ODBC]Unsupported version of SQL/Services Client DLL. Multiple version or the wrong version of SQSAPIW.DLL are present on the PC. Ensure that only one version of SQSAPIW.DLL is present on the PC and resides in the \WINDOWS\SYSTEM directory. If necessary, copy SQSAPIW.DLL directly from the installation diskette to the \WINDOWS\SYSTEM directory. Trying to attach to a database or table fails with native error code -2035 This is a SQL/Services error which usually results when the Server on the VMS system has died. This usually means that SQL/Services was never installed correctly on the VMS machine. On the VMS machine, examine SYS$STARTUP:SQLSRV$.LOG and any logs in the default SQL /Services account for the cause of the problems. Invalid Class Name [DEC][ODBC][Rdb]%SQLSRV-F-NO_CLS, Invalid Class Name An undefined SQL/Services class name was specified when the data source was configured on the PC via the ODBC Administrator. Problem Solving 9-17 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Another potential reason is that you are running SQL /Services standard version which expects GENERIC as the class, or SQL/Services multi version, which expects V61 etc. as the class name. Suberror code is n [DEC][ODBC] [Rdb]Network Error: Suberror code is nn This is usually a Pathworks error where nn = the Pathworks error code. The error codes can be found in the Pathworks files errno.h (for DECNET) or sock_err.h (for TCP/IP). Some of the more common errors are: • [DEC][ODBC][Rdb]Network Error: Suberror code is 3 This occurs when SQL/Services is not running. • [DEC][ODBC][Rdb]Network Error: Suberror code is 49 This occurs when the target DECNET node is not defined on the PC. • [DEC][ODBC][Rdb]Network Error: Suberror code is 60 This occurs when pathworks times out, usually as a result of the SQL/Services Server crashing. Client not authorized to access database The username supplied via ODBC is not authorized to access the database. Ensure the user has an account on the Server and has enough privileges to access the Digital DEC/EDI database. 9-18 Getting More Information INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Getting More Information The following sections provide suggestions on getting more information about problems that you may be experiencing. These assist more experienced users to diagnose less common problems. The Digital DEC/EDI Error Log Each of the different components of the Digital DEC/EDI Server is capable of reporting informational and error messages in the Digital DEC/EDI Error Log file. The information in this file is stored in a coded format, and you need to use special tools to look at its content. The normal means of viewing the Error Log is to use the Cockpit. However, until you have a correctly operating Cockpit installation, this is not possible. If you are unable to get Cockpit to work, perhaps because you have not completed some element of its configuration, it is possible that the Error Log contains important information that can assist you in diagnosing any problems. If you suspect the Error Log may contain such information, the Server contains a simple utility to allow you to look at the Error Log. Tru64 UNIX On the Tru64 UNIX Server this utility is called decedi_look. For more information on using this utility, refer to its man page entry on the Server: # man decedi_look Getting More Information 9-19 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER ODBC Tracing Use the Microsoft ODBC administrator. This resides in the Control Panel. Run the ODBC administrator and do the following: • Select Options. • Select the Trace ODBC Calls option. • Choose a file to be used to store the trace information - click on the Select File... button. This creates a trace file detailing ODBC activity for each function call or request that uses ODBC. Remember to turn tracing off when you no longer need it. SQL/Services Tracing Rdb... SQL/Services tracing provides a detailed log of all individual SQL database functions executed. To enable SQL/Services tracing, use an editor, such as Notepad, to open the following file: \WINDOWS\SQSAPIW.INI Enable client logging by removing the semi-colon (;) comment mark before the line: ClientLogging=7 You should restart Windows for this change to take effect. This generates a file called CLIENT.LOG which details all the SQL/Services calls made. ...Rdb Reverse the change to SQSAPIW.INI when you no longer need tracing. You should restart Windows for this to be effective. 9-20 Network Tester INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Network Tester The Cockpit has a network testing option which is used by clicking-on the Network Tester icon to enable the facility. A menu-driven series of simple prompts take you through the test process. Note that you will need to know the identity of the server that you will be addressing. Error Messages The following error message may occur if decedi_csg is not defined in the "services" file, or if the port number for decedi_csg is not compatible with the port number defined on the server. Error when connecting to Server' The specified address is not available from the local machine If this occurs, you will need to modify the SERVICE file to add the correct Port number. The line to be added is as follows: decedi_csg /tcp # Digital DEC/EDI GUI for example: decedi_csg 5152/tcp # Digital DEC/EDI GUI Where the Port Number is as you recorded during the configuration described in Compaq DEC/EDI Services TCP/IP Port Numbers on page 3-4. Tip Use the Find File facility to locate the SERVICES file, and use Notepad to add the line with the Port Number. TCP/IP Tracing If you are using the TCP/IP network interface, you may trace the requests and traffic between the PC and your Server into log files on both the PC and Server. After defining the server uing the simple menu options provided, select the TCP/IP Test button from the next menu. The test is carried out automatically and a successful test result is reported. In the event of a failure, use the error message and the log file to establish the cause of the problem. Reporting Problems 9-21 INSTALLING DIGITAL DEC/EDI COCKPIT AND COMMANDCENTER Reporting Problems If an error occurs while Digital DEC/EDI Cockpit or CommandCenter is being used, and you believe the error is caused by a problem with one of these Digital DEC/EDI components, take one of the following actions: • If you have a BASIC or DECsupport Software Agreement, you should call your Customer Support Center. (With these services, you receive telephone support that provides high-level advisory and remedial assistance.) • If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). • If you have purchased Digital DEC/EDI CommandCenter or Cockpit within the past 90 days and you think the problem is caused by a software error, you can submit a Software Performance Report (SPR). Part IV System Verification This part describes the verification procedure after the installation of Digital DEC/EDI. Introduction It assumes that the following components have been installed: • Network Components • Database Components • Digital DEC/EDI Server • Digital DEC/EDI Client(s) • Digital DEC/EDI Cockpit or CommandCenter as required Intended Audience It provides a set of simple tests and verification checks that may be used by the Network Administrator to verify a successful installation. Chapter 10 UNIX System Verification Introduction This chapter describes how to verify that the installed system configuration is functioning correctly, and how to identify and correct common problems. Scope and Purpose This chapter takes the form of a self-paced tutorial that is designed to introduce you directly to setting up and using Digital DEC/EDI after your system has been installed. The examples are designed to minimise the amount of data entry that you have to perform, and provide an overview of Digital DEC/EDI. The tutorial takes you quickly through the significant stages from starting with a newly installed and unconfigured Digital DEC/EDI system, to exchanging and tracking documents between two hypothetical trading partners. As such, the activities it involves mirror many that will become familiar in live trading with partners either inside or outside your organization. Note: The example in this section installs the EDIFACT 90.1 standard, along with data labels of a specific format, which are used to identify EDI elements within the mapping process. If your Digital DEC/EDI system already has EDIFACT 90.1 installed, check with your Digital DEC/EDI administrator to make sure that you are not going to affect the existing system. 10-2 Introduction UNIX SYSTEM VERIFICATION The tutorial introduces you to the following activities: • Verification that the Digital DEC/EDI Server software and its prerequisites have been successfully installed, and may be successfully started up and shut down. • The use of both local and remote Application Client systems to communicate with the Digital DEC/EDI Server. • The use of PC-based Cockpit and CommandCenter installations to communicate with the Digital DEC/EDI Server. • Configuration of the Digital DEC/EDI Server with EDI Standards and Trading Partner profile details, and the use of the Import/Export communications gateway. • The compilation of a Mapping Table and its installation on the Server. • Monitoring the Digital DEC/EDI Server to ensure it is able to correctly send, receive and process application files and EDI transmissions. • Basic housekeeping of the Digital DEC/EDI Server, by archiving data that has been successfully processed. The files described and used in this tutorial are provided as part of the Digital DEC/EDI software installation. Beyond the Scope and Purpose The tutorial is not a detailed exercise in the more advanced aspects of system configuration, Mapping Table development, and application integration with Digital DEC/EDI. When you want to know more about any topic addressed by this tutorial, or any other queries, refer to the appropriate sections of the related books Digital DEC/EDI: Application Development and the Digital DEC/EDI: User's Guides (Tru64 UNIX and OpenVMS). Overview 10-3 UNIX SYSTEM VERIFICATION Overview The example in this tutorial covers the hypothetical case where your company, DEC Direct UK Ltd, is sending invoices to another company called Shiny New Systems. In the outgoing case, you pretend to be DEC Direct UK Ltd which is sending the invoice. You have agreed with your Trading Partner, Shiny New Systems, that you will use a subset of the EDIFACT 90.1 INVOIC message which you have defined. To distinguish it from the message on which it is based, you have named the message subset MINVOX. In the incoming case, you pretend to be Shiny New Systems which is receiving the invoice. You have agreed to receive and process the MINVOX subset of the EDIFACT 90.1 INVOIC message from your Trading Partner, DEC Direct UK Ltd. 10-4 Overview UNIX SYSTEM VERIFICATION An Example Application File There is an example application file that has come from your business application, which is provided as part of the Digital DEC/EDI software installation. The file is provided with the Digital DEC/EDI Application Client subset, in the Digital DEC/EDI examples directory: /usr/examples/decedi/client/minvox_o.dat The file is also provided with the CommandCenter, in the directory specified during the installation process. You may use this to examine the structure of the file whilst developing the Mapping Table, or to create a copy of the file on the Application Client system. The Application File contains some of the data to be sent in the MINVOX message. Before sending the message to your Trading Partner, the file needs to be processed to produce an EDI format message that can be sent to your Trading Partner. The following steps are involved in this process and are performed by separate components of the Digital DEC/EDI server system: • Mapping - An intermediate file known as the Internal Format File is generated using data from the Application File. Some of the values in the Internal Format file are automatically generated, or calculated from other values or variables. This step is performed by the Mapper. • Conversion - The Internal Format File is converted into an EDI format message. This step is performed by the EDIFACT Converter. • Transmission File Building - One or more EDI format messages are placed in an EDI Transmission File, which is then ready to be sent to your Trading Partner. This step is performed by the EDIFACT Transmission File Builder. Overview 10-5 UNIX SYSTEM VERIFICATION Preparation Task Summary The following list broadly summarizes the tasks you need to complete before attempting the client examples: • Install the prerequisite software and EDI definitions • Configure the client • Set up the server • Compile the example mapping tables • Create trading partner profiles • Start Digital DEC/EDI • Build and replace the profile cache The following sections tell you what to do in detail. 10-6 A: Installing the Software and EDI Definitions UNIX SYSTEM VERIFICATION A: Installing the Software and EDI Definitions 1. Install the prerequisite software in accordance with the Digital DEC/EDI: Software Product Description (SPD). 2. Install the Digital DEC/EDI Client and Server. (These may be on different systems). For example, if you are installing from CD-ROM: # /usr/sbin/setld -l /cdrom Where /cdrom is the mount point of the CD-ROM device. The following subsets are required for use in this tutorial: Note: It is recommended that you also install the Man page subsets for future reference, though these are not required for this example. Table 10-1 Remote Client Installation Subset Description DEDIBASE400 Digital DEC/EDI Base DEDICLT400 Digital DEC/EDI Client Table 10-2 Server and Local Client Installation Subset Description DEDIBASE400 Digital DEC/EDI Base DEDICLT400 Digital DEC/EDI Client DEDISERV400 Digital DEC/EDI Server DEDIAMSGBASE400 Digital DEC/EDI Message Updates Base DEDIAMSGEDIF400 Digital DEC/EDI Message Updates EDIFACT IMPDEF files A: Installing the Software and EDI Definitions 10-7 UNIX SYSTEM VERIFICATION 3. Install the Digital DEC/EDI Message Update Service kit. This is achieved by installing the Message Updates base subset, and the IMPDEF subsets for the standards required. This example uses the EDIFACT IMPDEF files. Ensure that the subset is installed by enetering the following command: # /usr/sbin/setld -i | grep DEDIAMSGEDIF320 Enter the following command: # decedi_must From the menu, select EDIFACT 901, to install the definitions that are used in this example. Note: If there are any other EDI standards that you wish to install, it is recommended that you do so at this stage, while the Digital DEC/EDI Server is not in use. 4. Create the MINVOX Definition Install data labels for the EDIFACT 90.1 standard and create the private MINVOX document definition. Run the Digital DEC/EDI Data Label Generator: # /usr/sbin/decedi_dlg -s=EDIFACT -v=901 -f=ID 10-8 A: Installing the Software and EDI Definitions UNIX SYSTEM VERIFICATION 5. Create the private MINVOX definition by using the Digital DEC/EDI CommandCenter EDI Tables Editor on a PC connected to the Server. a From the "Getting Started" menu, select the "Manage Documents" option b From the "Getting Started - Documents" menu, select the option to edit an existing document saved in a file on the PC. c From within the Open dialog, select minvox.tab, and press Open. d You will be prompted to log on to the Server. Enter the defined server name, your user name and password to log on to the server. e Click on the Save to Server icon, or select the menu option Server..Save to save the document to the current server. f You will be informed that the document is not currently associated with any server, and will be asked to confirm that it should be saved to the specified server. Click Yes to confirm, and then exit from the EDI tables editor. g You will be asked about the tables cache, you do not need to rebuild it at this stage. Click Continue to exit from the EDI tables editor. B: Configuring the Client 10-9 UNIX SYSTEM VERIFICATION B: Configuring the Client The Digital DEC/EDI Client may be run either locally, that is, on the same node as the Digital DEC/EDI Server, or remotely on a different node. Configure Network Interface Configure the Digital DEC/EDI Client and Server for a TCP/IP only connection. 1. On the Digital DEC/EDI Server, run the Digital DEC/EDI configuration utility: # /usr/sbin/decedi_config 2. Configure network interface: 3. If using a remote client, repeat steps 1 and 2 on the remote client node, ensuring that you select the same network interface as you configured on the Digital DEC/EDI Server. Oracle 7 The account is registered with the Oracle 7 server. It does not have to be the same as any existing user accounts. 10-10 B: Configuring the Client UNIX SYSTEM VERIFICATION Register the Client Applications To configure the Digital DEC/EDI Server for Tru64 UNIX, you must use the Digital DEC/EDI CommandCenter on a remote PC. Use the CommandCenter Management Services Editor to register the client applications. If the client and server are on the same node, then simply enter the server node name. 1. Select the Getting Started option, Configure Applications. 2. Select Create a new application. 3. Enter DEC-DIRECT-UK-LTD as the Application Name. You will be asked to log in to the server that you should have already configured in the CommandCenter. If you have not already defined a server for the CommandCenter, do so now. Enter your server password. 4. Select the tabbed dialog, Node. 5. Click on the Add button. You will be prompted for the name of the node on which this client application is located. Enter the node name and select Ok. 6. Select the Details tabbed dialog, and click on the Add button. 7. Repeat steps 3 to 5, but this time, use the application name, SHINYNEW- SYSTEMS. You use this application when you pretend to be SHINY-NEWSYSTEMS, and fetch the files that were sent by the partner, DECDIRECT- UK-LTD. 8. Save these application details by clicking on the Save button. You will be prompted to build and replace the cache. You should wait until all of the server data has been configured. B: Configuring the Client 10-11 UNIX SYSTEM VERIFICATION Define Services You need to define and start the services that you need to use. To do this: 1. From the CommandCenter, select the Management Services Editor, and define the following services: - EDIFACT/ODETTE Services - Import/Export Gateway 2. You will be prompted to log into the server, so enter the server name and your password details. 10-12 C: Compiling the Mapping Tables UNIX SYSTEM VERIFICATION C: Compiling the Mapping Tables Load and compile the Mapping Tables using the CommandCenter Mapping Table Editor. These tables are supplied with the CommandCenter. Alternatively, you may like a more detailed look at how these are created, so that you can create a mapping table for your own future needs. For detailed steps in creating the incoming and outgoing Mapping tables used by this example, refer to the next two chapters in this part of the book, Creating an Incoming Mapping Table and Creating an Outgoing Mapping Table. If you choose to use the supplied mapping tables, complete the following: 1. Select the Getting Started option, Load Sample Incoming Mapping Table and select MINVOX_I. 2. Compile this table by selecting Compile option from the Mapping menu. 3. When the table has compiled successfully, copy it to the server by clicking on Ok in the Copy to Server window that pops up. 4. Repeat the above procedure for the MINVOX_O table. Note that this sample table can also be loaded from the File menu. D: Defining Gateway and Connection 10-13 UNIX SYSTEM VERIFICATION D: Defining Gateway and Connection Use the CommandCenter Communications Editor to define: • The gateway: Import/Export • The connection: CVP_E Defining the Gateways: 1. From the "Getting Started" dialog, select the Edit Gateway Parameters option. ? You will be prompted to log on to the Server. Enter the defined server name, your user name and password to log on to the server. 2. Within the Select Connections dialog, specify the connection ID CVP_E and click on OK. 3. From the Edit Gateways dialog, select Import/Export Gateway 4. Within the Import/Export Gateway details dialog, leave the connection error limit as 20, and specify the following locations: Import /var/adm/decedi/impexp Export /var/adm/decedi/impexp 5. Click on Save, and then Close the Edit Gateways dialog Creating the Connections 1. You will be presented with a list of gateways and connections, with the caption "Filtered by: CVP_E" 2. Click on the line "IMPEXP Disabled Stopped", and from the Edit menu, select Add->Connection. Enter the Connection ID: CVP_E and click on OK 3. Set the syntax to EDIFACT by selecting it from the drop-down menu 4. Select the "Delete" option within the "Action on Import" box. 5. Within the Operating system commands, select the Post-Export option, and enter the following text: /usr/examples/decedi/server/decedi_loopback.sh #EXPFIL #EXPLOC #IMPLOC #CONN This enables the "loopback" example script, which is run automatically each time a transmission file is exported through the CVP_E connection. 10-14 D: Defining Gateway and Connection UNIX SYSTEM VERIFICATION This script renames the transmission file and re-imports it back through the CVP_E connection. This is useful for testing bidirectional agreements, as used in this example. Enabling the Gateway and Connection 1. Select the CVP_E connection, and cick on the Enable/Disable button, or select the Enable option from the Operations menu. 2. Select the IMPEXP Gateway, and click on the Enable/Disable button, or select the Enable option from the Operations menu. Ignore the message from the GUI Server about a gateway of this type not running, as the Digital DEC/EDI Server has not yet been restarted. 3. Exit from the Communications Editor. E: Adding Trading Partner Profiles 10-15 UNIX SYSTEM VERIFICATION E: Adding Trading Partner Profiles Use the CommandCenter Trading Partner Editor to add profiles for SHINY-NEW-SYSTEMS and DEC-DIRECT-UK-LTD. When you post a file to a trading partner using this example, you pretend to be the company, DEC-DIRECT-UK-LTD, and your trading partner is SHINY-NEW-SYSTEMS. When you want to fetch files, you pretend be SHINY-NEW-SYSTEMS, collecting files sent from your partner, DEC-DIRECT-UK-LTD. Thus you need to create two trading partner profiles, each detailing the document, MINVOICE, that you will exchange with the partner. 1. Enter the Trading Partner Editor and select the Trading Partner Wizard to create or edit Trading Partners. The Trading Partner Wizard is a quick way to create up to two trading partners and their agreements by entering the minimum amount of information. You will be asked to log in to the server, so enter the server name and your password details. 2. On the Trading Partner Wizard window, check the box marked, Create two Trading Partners and their Agreements, and enter the following information: After entering the above information, select OK. Trading Partner SHINY-NEW-SYSTEMS Application DEC-DIRECT-UK-LTD Template Use the default supplied, DEFAULT.INI and select the option to create two trading partners and their agreements Application Interchange ID DDUK Partner Interchange ID SNS Connection CVP_E Direction Take the default, Bidirectional Outgoing Document Browse and select, MINVOICE Incoming Document Browse and select, MINVOICE 10-16 E: Adding Trading Partner Profiles UNIX SYSTEM VERIFICATION You will then see your two new trading partners in a list. 3. Expand the list by clicking on the boxes checked with the letter X in them to see the agreement, document and connection defined for each trading partner. 4. Select any of these to verify that the details you entered are correct and to have a look at the other information that can be entered for Trading Partner agreements. 5. Finally, select the Cache option to Build and Replace the cache. F: Restart the Digital DEC/EDI Server 10-17 UNIX SYSTEM VERIFICATION F: Restart the Digital DEC/EDI Server Shut down and restart the Digital DEC/EDI Server, to ensure that the EDIFACT and Import/Export components are restarted, and that the new profile cache becomes effective. The commands are as follow: # decedi_stop # decedi_start 10-18 G: Running the Examples UNIX SYSTEM VERIFICATION G: Running the Examples Sending the Document Application Client Node 1. 1.Select a local user account from which to run the examples, and ensure that account is authorized for Digital DEC/EDI database access. # decedi_config 2. Select the option - Modify Database Users. Check that the user is in the list. Oracle Rdb You may need to set the database path or version from within the .login, .cshrc or .profile of the account. Log into the user account, and change directory to a scratch directory which has its protection set, so it can be written to by the decedi account. Copy the following files from the Digital DEC/EDI examples directory, located at /usr/examples/decedi/client to your local Client directory: minvox_in.dat minvox_out.dat 3. Rename minvox_in.dat to original_minvox_in.dat mv minvox_in.dat original_minvox_in.dat 4. Use the Cockpit to monitor the progress of the MINVOX invoice document you will be sending. Before sending the document, start the Cockpit so you can monitor its progress.From the "Getting Started" dialog, select the option to obtain a summary of Documents and Transmission Files on your Digital DEC/EDI Server. In the Summary View dialog, check that the default server name is the one you have defined, and select the Date Range tab, click on Today and press OK. You will be prompted to log on to the Server. Enter the defined server name, your user name and password to log on to the server. Select Summary..Options and in the Summary Options dialog, select the display of both Inbound and Outbound documents and transmissions, and select Auto-updates every 1 minute. This will show a number of status bars within the Cockpit summary view. Resize the Cockpit window do you can see all the totals, if G: Running the Examples 10-19 UNIX SYSTEM VERIFICATION possible. In the summary view, a green LED icon indicates no failures, a yellow LED icon indicates no further failures since the last update, and a red LED icon indicates one or more documents or transmission files have failed since the last update. A black vertical bar on the status bar indicates the value prior to the last update, so you can monitor any changes. Keep the Cockpit window active, and in a separate terminal window send the example document to Digital DEC/EDI 5. Send the document to Digital DEC/EDI: trade post DEC-DIRECT-UK-LTD -priority=high spec_of_minvox_out.dat \table_name=minvox_o This will send the transmission file immediately it has been built, and automatically reimport it, using the "loopback" example script. Cockpit, CommandCente r 6. Use the Cockpit to monitor the progress of the documents and transmission files on the system. When they reach a status of Purgeable/Cancelled, the archive process will periodically remove them from the Current audit trail, and place them in the Archive audit trail. This is normal behaviour. Eventually a document should appear with a status of Available. Double- Click on the Available status bar, and in the Coose Summary Category dialog, click OK to view the Application ID. The Application ID should be SHINY-NEW-SYSTEMS.This means that the document is now available for fetching by the SHINY-NEWSYSTEMS application. Server Node Once the document is available, you may fetch the application file by issuing a TRADE FETCH command: trade fetch SHINY-NEW-SYSTEMS minvox_in.dat - /table_name=minvox_i 7. Compare the fetched document with expected output using the following: diff minvox_in.dat original_minvox_in.dat 10-20 Network Tester UNIX SYSTEM VERIFICATION Network Tester The Cockpit has a network testing option which is used by clicking-on the Network Tester icon to enable the facility. A menu-driven series of simple prompts take you through the test process. Note that you will need to know the identity of the server that you will be addressing. Error Messages The following error message may occur if decedi_csg is not defined in the "services" file, or if the port number for decedi_csg is not compatible with the port number defined on the server. Error when connecting to Server' The specified address is not available from the local machine If this occurs, you will need to modify the SERVICE file to add the correct Port number. The line to be added is as follows: DECEDI_CSG /TCP Where the Port Number is as you recorded during the configuration described in Compaq DEC/EDI Services TCP/IP Port Numbers on page 3-4. Tip Use the Find File facility to locate the SERVICES file, and use Notepad to add the line with the Port Number. Troubleshooting Common Problems 10-21 UNIX SYSTEM VERIFICATION Troubleshooting Common Problems Tracing in the TCP/IP Client/Server Interface The aim of the tracing is to aid users and field service personel in tracing what is going on during a TCP/IP exchange so that errors due to misconfiguration can be easily detected. Environment Tracing will be controlled by the environment variable DECEDI_TCP_TRACE, which is assigned a string. The string is composed of a series of letters, each letter identifying a particular component of the exchange that needs to be traced. The letters currectly supported are: 'A' : Switch on all trace options available 'C' : Trace children: Specific to the port server. This lists when children are created or reused, and to which child a request is rerouted. 'P' : Trace protocol: List the protocol messages sent and received. 'S' : Trace services: ? On the client side this reports which server nodes and services are attempted to be contacted. ? On the server side this reports which clients made contact to which services. 'T' : Trace traffic: List the size of messages being sent or received. This would normally be used in conjunction with 'P'. The reason for two is that 'P' is traced as soon as we send or receive the message header, whilst the 'T' cant be done until be have completed sending or receiving the data. To trace everything you could set DECEDI_TCP_TRACE to "A" or to "CPST". Each process involved in the TCP/IP linkage does its own tracing to its own trace log. The log file being: /var/adm/decedi/logs/tcp_trace_.log ODBC-related Problems ...Rdb The username supplied via ODBC is not authorized to access the database. Ensure that the user has an account on the server and has enough privileges to access the Digital DEC/EDI database. 10-22 Troubleshooting Common Problems UNIX SYSTEM VERIFICATION Chapter 11 OpenVMS System Verification Introduction This chapter describes how to verify that the installed system configuration is functioning correctly, and how to identify and correct common problems. Scope and Purpose This chapter takes the form of a self-paced tutorial that is designed to introduce you directly to setting up and using Digital DEC/EDI after your system has been installed. The examples are designed to minimise the amount of data entry that you have to perform, and provide an overview of Digital DEC/EDI. The tutorial takes you quickly through the significant stages from starting with a newly installed and unconfigured Digital DEC/EDI system, to exchanging and tracking documents between two hypothetical trading partners. As such, the activities it involves mirror many that will become familiar in live trading with partners either inside or outside your organization. Note: The example in this section installs the EDIFACT 90.1 standard, along with data labels of a specific format, which are used to identify EDI elements within the mapping process. If your Digital DEC/EDI system already has EDIFACT 90.1 installed, check with your Digital DEC/EDI administrator to make sure that you are not going to affect the existing system. 11-2 Introduction OPENVMS SYSTEM VERIFICATION About the Tutorial The tutorial introduces you to the following activities: • Verification that the Digital DEC/EDI Server software and its prerequisites have been successfully installed, and may be successfully started up and shut down. • The use of both local and remote Application Client systems to communicate with the Digital DEC/EDI Server. • The use of PC-based Cockpit and CommandCenter installations to communicate with the Digital DEC/EDI Server. • Configuration of the Digital DEC/EDI Server with EDI Standards and Trading Partner profile details, and the use of the Import/Export communications gateway. • The compilation of a Mapping Table and its installation on the Server. • Monitoring the Digital DEC/EDI Server to ensure it is able to correctly send, receive and process application files and EDI transmissions. • Basic housekeeping of the Digital DEC/EDI Server, by archiving data that has been successfully processed. The files described and used in this tutorial are provided as part of the Digital DEC/EDI software installation. Beyond the Scope and Purpose The tutorial is not a detailed exercise in the more advanced aspects of system configuration, Mapping Table development, and application integration with Digital DEC/EDI. When you want to know more about any topic addressed by this tutorial, refer to the appropriate sections of the related books Digital DEC/EDI: Application Development and the Digital DEC/EDI: User's Guide. Overview 11-3 OPENVMS SYSTEM VERIFICATION Overview The example in this tutorial covers the hypothetical case where your company, DEC Direct UK Ltd, is sending invoices to another company called Shiny New Systems. In the outgoing case, you pretend to be DEC Direct UK Ltd which is sending the invoice. You have agreed with your Trading Partner, Shiny New Systems, that you will use a subset of the EDIFACT 90.1 INVOIC message which you have defined. To distinguish it from the message on which it is based, you have named the message subset MINVOX. In the incoming case, you pretend to be Shiny New Systems which is receiving the invoice. You have agreed to receive and process the MINVOX subset of the EDIFACT 90.1 INVOIC message from your Trading Partner, DEC Direct UK Ltd 11-4 Overview OPENVMS SYSTEM VERIFICATION An Example Application File There is an example application file that has come from your business application, which is provided as part of the Digital DEC/EDI software installation. The file is provided with the OpenVMS Application Client or Server, in the Digital DEC/EDI examples directory: DECEDI$EXAMPLES:MINVOX_OUT.DAT About the Application File The Application File contains some of the data to be sent in the MINVOX message. Before sending the message to your Trading Partner, the file needs to be processed to produce an EDI format message that can be sent to your Trading Partner. The following steps are involved in this process and are performed by separate components of the Digital DEC/EDI server system: • Mapping - An intermediate file known as the Internal Format File is generated using data from the Application File. Some of the values in the Internal Format file are automatically generated, or calculated from other values or variables. This step is performed by the Mapper. • Conversion - The Internal Format File is converted into an EDI format message. This step is performed by the EDIFACT Converter. • Transmission File Building - One or more EDI format messages are placed in an EDI Transmission File, which is then ready to be sent to your Trading Partner. This step is performed by the EDIFACT Transmission File Builder. Overview 11-5 OPENVMS SYSTEM VERIFICATION Preparation Task Summary The following list broadly summarizes the tasks you need to complete before attempting the client examples: • Install the prerequisite software and EDI definitions • Configure the client • Set up the server • Compile the example mapping tables • Create trading partner profiles • Start Digital DEC/EDI • Build and replace the profile cache The following sections tell you what to do in detail. 11-6 A: Installing the Software and EDI Definitions OPENVMS SYSTEM VERIFICATION A: Installing the Software and EDI Definitions 1. Install the prerequisite software in accordance with the Digital DEC/EDI: Software Product Description (SPD). 2. Install the Digital DEC/EDI Client and Server. (These may be on different systems). For example, if you are installing from a device named CDROM: $@SYS$UPDATE:VMSINSTAL DECEDIA040 CDROM: OPTIONS NInstall the Digital DEC/EDI Message Update Service kit. On OpenVMS, this is achieved by re-running the installation procedure on the Digital DEC/EDI Server node, and selecting the option to install EDI standards definition. Select the menu option to install the EDIFACT 90.1 IMPDEF files. 3. Install the Digital DEC/EDI CommandCenter on a remote PC, and configure the CommandCenter to communicate with the Digital DEC/EDI Server. Note: The use of the CommandCenter is optional for OpenVMS servers. Install the EDIFACT 90.1 standard by using the Message Update Service. Peform a Digital DEC/EDI startup, using the following command: $ @SYS$STARTUP:DECEDI$STARTUP Enter the following command: $ RUN DECEDI$TOOLS:DECEDI$MESSAGE_UPDATES.EXE You are presented with a list of available standards to install. Select EDIFACT 90.1 from the menu. This may take a few minutes to install. Note: If there are any other EDI standards that you wish to install, it is recommended that you do so at this stage, while the Digital DEC/EDI Server is not in use. A: Installing the Software and EDI Definitions 11-7 OPENVMS SYSTEM VERIFICATION 4. Install data labels for the EDIFACT 90.1 standard and create the private MINVOX document definition. Run the Digital DEC/EDI Table Extractor and Loader tool: $ RUN DECEDI$TOOLS:DECEDI$TEL.EXE Select option 2, Load Definitions, and give the location of the EDIFACT 90.1 definition file: DECEDI$EXAMPLES:EDIFACT_901_DIRECTORY.DAT Enter the version number as 901, and confirm that you want to load the associated data labels as well. Select option 2, Load Definitions, and give the location of the MINVOX definition file: DECEDI$EXAMPLES:EDIFACT_901_MINVOX_DOCUMENT.DAT Enter the version number as 901, and specify MINVOICE as the internal document id. Select option 3, Exit. 11-8 B: Configuring the Client OPENVMS SYSTEM VERIFICATION B: Configuring the Client The Digital DEC/EDI Client may be run either locally, that is, on the same node as the Digital DEC/EDI Server, or remotely on a different node. Granting User Access Rights Before registering a user with Digital DEC/EDI, that user must first be registered with the OpenVMS system. The user must already have an OpenVMS Authorization Entry in SYS$SYSTEM:SYSUAF.DAT, granting one of the following OpenVMS rights identifiers: • DECEDI$ADMINISTRATOR You can then register the user with Digital DEC/EDI, giving administrator access rights. • DECEDI$SUPERVISOR You can then register the user with Digital DEC/EDI, giving supervisor access rights. You register a user with Digital DEC/EDI by using the Digital DEC/EDI command ADD USER, assigning Digital DEC/EDI access rights. In Interchange there are two levels of Digital DEC/EDI access rights: • Administrator access rights: TRANS_ADMIN or COMMS_ADMIN • Supervisor access rights: SUPERVISOR B: Configuring the Client 11-9 OPENVMS SYSTEM VERIFICATION Configure Network Interface Configure the Digital DEC/EDI Client and Server for a TCP/IP only connection. 1. On the Digital DEC/EDI Server, run the Digital DEC/EDI configuration utility: Ensure that the Digital DEC/EDI logical names have been defined by entering the following command: $ @SYS$STARTUP:DECEDI$LOGICALS Run the configuration utility: $ @DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER 2. Configure the network interface: 3. If using a remote client, repeat steps 1 and 2 on the remote client node, ensuring that you select the same network interface as you configured on the Digital DEC/EDI Server. If using the TCP/IP network interface, add the server node name to the Server configuration file. 11-10 C: Compiling the Mapping Tables OPENVMS SYSTEM VERIFICATION C: Compiling the Mapping Tables You may use the CommandCenter Mapping Table Editor on a remote PC. CommandCente r Load and compile the Mapping Tables using the CommandCenter Mapping Table Editor. These tables are supplied with the CommandCenter. Alternatively, you may like a more detailed look at how these are created, so that you can create a mapping table for your own future needs. For detailed steps in creating the incoming and outgoing Mapping tables used by this example, refer to the next two chapters in this part of the book, Creating an Incoming Mapping Table and Creating an Outgoing Mapping Table. If you choose to use the supplied mapping tables, complete the following: 1. Select the Getting Started option, Load Sample Incoming Mapping Table and select MINVOX_I. 2. Compile this table by selecting Compile option from the Mapping menu. 3. When the table has compiled successfully, copy it to the server by clicking on Ok in the Copy to Server window that pops up. 4. Repeat the above procedure for the MINVOX_O table. Note that this sample table can also be loaded from the File menu. D: Configuring the Server 11-11 OPENVMS SYSTEM VERIFICATION D: Configuring the Server Registering the Services 1. Start Interchange with the command: $ INTERCHANGE 2. Use the $ EDIT CONFIGURATION facility to select MAINTAIN SERVICES, press INSERT then add the following component: EDIFACT_TRANSLATOR 3. Move the cursor to Save and press Select Repeat Step 2 for component IMPORT_EXPORT_GATEWAY with ID: CVP_E 4. Finish by using the EXIT key. Registering the Business Applications 1. Start Interchange with the command: $ INTERCHANGE 2. Use the EDIT CONFIGURATION facility to select REGISTER APPLICATIONS, press INSERT then add the following Invoice Application: DEC-DIRECT-UK-LTD 3. Add the following details: ID: DEC-DIRECT-UK-LTD Name: DECdirect (UK) Ltd 4. Press Do to save the details 5. Repeat Step 3 and 4 to add the following entries: ID: SHINY-NEW-SYSTEMS Name: Shiny New Systems 6. Finish by using the EXIT key. 11-12 D: Configuring the Server OPENVMS SYSTEM VERIFICATION Registering a Node 1. Start the Digital DEC/EDI User Interface with the command: $ INTERCHANGE 2. Use the EDIT CONFIGURATION facility to select REGISTER NODE, press INSERT then add the node and transport details appropriate to your installation, by selecting from the menu 3. Finish by using the EXIT key. E: Adding Trading Partner Profiles 11-13 OPENVMS SYSTEM VERIFICATION E: Adding Trading Partner Profiles 1. Start the Digital DEC/EDI User Interface with the command: $ INTERCHANGE 2. Load the profiles: EDI> LOAD PROFILE DECEDI$EXAMPLES:PROFILE_DEC-DIRECTUK- LTD.DAT EDI> LOAD PROFILE DECEDI$EXAMPLES:PROFILE_SHINY-NEWSYSTEMS. DAT 3. Use the following command to examine a profile: EDI> LIST PROFILE /FULL DEC-DIRECT-UK-LTD 4. Finish by using the EXIT key. 5. Build the cache on completion with the following command: EDI> BUILD CACHE /ALL EDI> REPLACE CACHE /ALL 11-14 F: Start the Digital DEC/EDI Server OPENVMS SYSTEM VERIFICATION F: Start the Digital DEC/EDI Server Start the Digital DEC/EDI Server by entering the following command: $ @SYS$STARTUP:DECEDI$STARTUP G: Running the Examples 11-15 OPENVMS SYSTEM VERIFICATION G: Running the Examples Sending the Document Application Client Node 1. Copy the following files from the DECEDI$EXAMPLES directory to your local Client directory: MINVOX_IN.DAT MINVOX_OUT.DAT 2. Rename MINVOX_IN.DAT to ORIGINAL_MINVOX_IN.DAT 3. Send the document to Digital DEC/EDI: $ TRADE POST DEC-DIRECT-UK-LTD spec_of_MINVOX_OUT.DAT - /TABLE=MINVOX_O /PRIORITY=HIGH Server Node 4. Enter the Digital DEC/EDI user interface: $ INTERCHANGE then monitor the progress of the invoice you have sent using: $ INTERCHANGE EDI> LIST DOCUMENT EDI> LIST TRANSMISSION Or use Cockpit to follow the progress of the invoice you have sent. The transmission file should eventually appear with the following status: AWAITING_TRANSMISSION 5. Once the documents are successfully built and awaiting transmission, start CVP_E connection using the following command: $ INTERCHANGE START CONN CVP_E IMPEXP 6. The resulting transmission file is exported to the Import/Export gateway directory DECEDI$TOP:[CVP.IMPEXP] with a file type of .EXPORT. Rename the exported transmission file, to a new unique transmission file name, with a file type of .IMPORT. Ensure that the last part of the file name is CVP_E. For example, $ RENAME - DECEDI$TOP:[CVP.IMPEXP]19JUN199711593183_CVP_E.EXPOR T - DECEDI$TOP:[CVP.IMPEXP]I01_19JUN199711593183_CVP_E.I MPORT 11-16 G: Running the Examples OPENVMS SYSTEM VERIFICATION 7. Reimport the transmission file by starting the CVP_E connection: $ INTERCHANGE START CONN CVP_E IMPEXP 8. Enter the Digital DEC/EDI user interface: $ INTERCHANGE then monitor the progress of the invoice you have sent using: $ INTERCHANGE EDI> LIST TRANSMISSION EDI> LIST DOCUMENT Or use Cockpit to follow the progress of the invoice you are importing. The document should eventually be created with the following status: AVAILABLE 9. Once the document is available, you may fetch the application file by issuing the TRADE FETCH command: $ TRADE FETCH DEC-DIRECT-UK-LTD SYS$SCRATCH:MINVOX_IN.DAT - /TABLE=MINVOX_I 10.Compare the fetched document with expected output using the following: $ DIFFERENCES MINVOX_IN.DAT ORIGINAL_MINVOX_IN.DAT Network Tester 11-17 OPENVMS SYSTEM VERIFICATION Network Tester The Cockpit has a network testing option which is used by clicking-on the Network Tester icon to enable the facility. A menu-driven series of simple prompts take you through the test process. Note that you will need to know the identity of the server that you will be addressing. Error Messages The following error message may occur if decedi_csg is not defined in the "services" file, or if the port number for decedi_csg is not compatible with the port number defined on the server. Error when connecting to Server' The specified address is not available from the local machine If this occurs, you will need to modify the SERVICE file to add the correct Port number. The line to be added is as follows: DECEDI_CSG /TCP # port number Where the Port Number is as you recorded during the configuration described in Compaq DEC/EDI Services TCP/IP Port Numbers on page 3-4. Tip Use the Find File facility to locate the SERVICES file, and use Notepad to add the line with the Port Number. 11-18 Troubleshooting Common Problems OPENVMS SYSTEM VERIFICATION Troubleshooting Common Problems ODBC Tracing Use the Microsoft ODBC administrator. This resides in the Control Panel. Run the ODBC administrator and do the following: • Select Options. • Select the Trace ODBC Calls option. • Choose a file to be used to store the trace information - click on the Select File... button. This creates a trace file detailing ODBC activity for each function call or request that uses ODBC. Remember to turn tracing off when you no longer need it. Troubleshooting Common Problems 11-19 OPENVMS SYSTEM VERIFICATION SQL/Services Tracing Rdb... SQL/Services tracing provides a detailed log of all individual SQL database functions executed. To enable SQL/Services tracing, use an editor, such as Notepad, to open the following file: \WINDOWS\SQSAPIW.INI Enable client logging by removing the semi-colon (;) comment mark before the line: ClientLogging=7 You should restart Windows for this change to take effect. This generates a file called CLIENT.LOG which details all the SQL/Services calls made. ...Rdb Reverse the change to SQSAPIW.INI when you no longer need tracing. You should restart Windows for this to be effective. Tracing in the TCP/IP Client/Server Interface The aim of the tracing is to aid users and field service personel in tracing what is going on during a TCP/IP exchange so that errors due to misconfiguration can be easily detected. Environment Tracing will be controlled by the environment variable logical DECEDI$TCP_TRACE, which is assigned a string. The string is composed of a series of letters, each letter identifying a particular component of the exchange that needs to be traced. The letters currectly supported are: 'A' : Switch on all trace options available 'C' : Trace children: Specific to the port server. This lists when children are created or reused, and to which child a request is rerouted. 'P' : Trace protocol: List the protocol messages sent and received. 'S' : Trace services: ? On the client side this reports which server nodes and services are attempted to be contacted. ? On the server side this reports which clients made contact to which services. 'T' : Trace traffic: List the size of messages being sent or received. This would normally be used in conjunction with 'P'. The reason for two is that 11-20 Troubleshooting Common Problems OPENVMS SYSTEM VERIFICATION 'P' is traced as soon as we send or receive the message header, whilst the 'T' cant be done until be have completed sending or receiving the data. To trace everything you could set DECEDI_TCP_TRACE to "A" or to "CPST". Each process involved in the TCP/IP linkage does its own tracing to its own trace log. The log file being: DECEDI$ERROR:tcp_trace_.log Troubleshooting Common Problems 11-21 OPENVMS SYSTEM VERIFICATION ODBC-Related Problems Driver not capable This means you have installed other software on your PC since ODBC installation, and it has disturbed the Digital DEC/EDI settings. A more likely cause is that your ODBC kit is too old, in which case you should obtain the latest kit, and reinstall. Unsupported version of SQL/Services Client DLL Trying to attach to a database or table fails with the message: [MICROSOFT][ODBC DLL]Driver's SQLAllocConnect failed. [DEC][ODBC]Unsupported version of SQL/Services Client DLL. Multiple version or the wrong version of SQSAPIW.DLL are present on the PC. Ensure that only one version of SQSAPIW.DLL is present on the PC and resides in the \WINDOWS\SYSTEM directory. If necessary, copy SQSAPIW.DLL directly from the installation diskette to the \WINDOWS\SYSTEM directory. Trying to attach to a database or table fails with native error code -2035 This is a SQL/Services error which usually results when the Server on the VMS system has died. This usually means that SQL/Services was never installed correctly on the VMS machine. On the VMS machine, examine SYS$STARTUP:SQLSRV$.LOG and any logs in the default SQL /Services account for the cause of the problems. Invalid Class Name [DEC][ODBC][Rdb]%SQLSRV-F-NO_CLS, Invalid Class Name An undefined SQL/Services class name was specified when the data source was configured on the PC via the ODBC Administrator. Another potential reason is that you are running SQL /Services standard version which expects GENERIC as the class, or SQL/Services multi version, which expects V61 etc. as the class name. Suberror code is n [DEC][ODBC] [Rdb]Network Error: Suberror code is nn This is usually a Pathworks error where nn = the Pathworks error code. The error codes can be found in the Pathworks files errno.h (for DECNET) or sock_err.h (for TCP/IP). Some of the more common errors are: • [DEC][ODBC][Rdb]Network Error: Suberror code is 3 This occurs when SQL/Services is not running. 11-22 Troubleshooting Common Problems OPENVMS SYSTEM VERIFICATION • [DEC][ODBC][Rdb]Network Error: Suberror code is 49 This occurs when the target DECNET node is not defined on the PC. • [DEC][ODBC][Rdb]Network Error: Suberror code is 60 This occurs when pathworks times out, usually as a result of the SQL/Services Server crashing. Client not authorized to access database The username supplied via ODBC is not authorized to access the database. Ensure the user has an account on the Server and has enough privileges to access the Digital DEC/EDI database. Appendix A OpenVMS Server and Client Log of New Server and Client Installation on OPEN VMS AXP $ @SYS$UPDATE:VMSINSTAL DECEDIA040 DKA400:[V4_KIT] OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.2-1 It is 12-OCT-2001 at 02:17. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: DECEDIA V4.0 Beginning installation of DECEDIA V4.0 at 02:17 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes -2 Log of New Server and Client Installation on OPEN VMS AXP 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Compaq Computer Corporation 1989,2000. 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 Compaq Computer Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? YES * Do you want to run the IVP after the installation [YES]? YES ======================================================= ==== Compaq DEC/EDI can be installed on a node as both a Client and a Server or just a Client to a remote Server. ======================================================= ==== * Do you want to install the Server [YES]? YES ======================================================= ==== In order to use the TCP/IP client interfaces you need to configure them for Compaq DEC/EDI after the installation by running the command file DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER.COM ======================================================= ===== The following versions of Rdb/VMS are available: Log of New Server and Client Installation on OPEN VMS AXP -3 *V7.0-3 * Please enter the Rdb/VMS version to be used by Compaq DEC/EDI [*V7.0-3]: Current PROCESS Oracle Rdb environment is version V7.0-3 (MULTIVERSION) Current PROCESS SQL environment is version V7.0-3 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V7.0-3 (MULTIVERSION) * On what device should the DECEDI directories reside: DKA0 * What is the UIC to be used for the Compaq DEC/EDI account: [500,1] No further questions will be asked during the installation. Installation of Compaq DEC/EDI V4.0 will take approximately 7-15 minutes %DECEDIA-I-INFO, defining DECEDI Account with autogenerated password %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named DECEDI. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier DECEDI value [000500,000001] added to rights database %VMSINSTAL-IACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %DECEDIA-I-INFO, Defining Compaq DEC/EDI Directories %DECEDIA-I-CREATEDIR, Creating directory DKA0:[DECEDI] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DKA0:[DECEDI]. %DECEDIA-I-CREATEDIR, Creating directory DKA0:[DECEDI.AUDIT_DB] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DKA0:[DECEDI.AUDIT_DB]. %DECEDIA-I-CREATEDIR, Creating directory DKA0:[DECEDI.ARCHIVE_DB] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DKA0:[DECEDI.ARCHIVE_DB]. -4 Log of New Server and Client Installation on OPEN VMS AXP %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[DATA] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[DATA]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ERROR] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[ERROR]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[VANREPORTS] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[VANREPORTS]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHREPORTS] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[ARCHREPORTS]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[TOOLS] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[TOOLS]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[DS_SCRATCH] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[DS_SCRATCH]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[BACKUP] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[BACKUP]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[CVP]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP.WORK] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[CVP.WORK]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP.IMPEXP] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[CVP.IMPEXP]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[3780PLUS] Log of New Server and Client Installation on OPEN VMS AXP -5 %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[3780PLUS]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[MESSAGE_UPDATES] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[MESSAGE_UPDATES]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CACHE] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[CACHE]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[MAP_TABLES] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[MAP_TABLES]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[TEMP] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[TEMP]. %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECEDI]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_1] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_1]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_2] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_2]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_3] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_3]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_4] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_4]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_5] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_5]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_6] -6 Log of New Server and Client Installation on OPEN VMS AXP %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_6]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_7] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_7]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_8] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_8]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_9] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_9]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_10] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_10]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_11] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_11]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_12] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_12]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_13] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_13]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_14] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_14]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_15] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_15]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_16] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_16]. Log of New Server and Client Installation on OPEN VMS AXP -7 %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_17] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_17]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_18] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_18]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_19] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_19]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_20] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[STORE_20]. %DECEDIA-I-SECURDIR, Securing all Compaq DEC/EDI directories... %DECEDIA-I-INFO, Restoring Compaq DEC/EDI Files... %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %DECEDIA-I-CREATEDB, Creating default database... %DECEDIA-I-CREATEDB, Creating default Archive database... %DECEDIA-I-INFO, Loading Compaq DEC/EDI Files... %DECEDIA-I-INFO, Loading tools and examples... %DECEDIA-I-INFO, Loading DCL command tables... %DECEDIA-I-INFO, Loading help files... %DECEDIA-I-INFO, Loading TPU section files... %TPU-S-CREATED, File WARP91$DKA0:[SYS0.SYSUPD.DECEDIA040]DECEDI$SECTION.TPU$ SECTION;1 created %TPU-S-SECTSAVED, 76 procedures, 90 variables, 29 keys saved %DECEDIA-I-INFO, Loading System images... %DECEDIA-I-INFO, Loading Application service files... -8 Log of New Server and Client Installation on OPEN VMS AXP %DECEDIA-I-INFO, Loading Translation service images... %DECEDIA-I-INFO, Loading Communication service images... %DECEDIA-I-INFO, Loading Communication service files... %DECEDIA-I-INFO, Loading FDL Files... %DECEDIA-I-INFO, Loading Data Files... %DECEDIA-I-INFO, Loading Command Files... %DECEDIA-I-INFO, Loading Mapper Files... %DECEDIA-I-INFO, Restoring The Message Updates Service Tool for Compaq DEC/EDI V4.0. %VMSINSTAL-I-RESTORE, Restoring product save set L ... %DECEDIA-I-INFO, Converting Data Files... %DECEDIA-I-INFO, Loading CVP data... Installation of Compaq DEC/EDI V4.0 succeeded ============================================= ======================================================= ======= DECEDI$PRVSHR.EXE Image should be loaded into the Memory using a privileged account. Following Command should be run in order to make use of the Compaq DEC/EDI Client. INSTALL ADD SYS$LIBRARY:DECEDI$PRVSHR.EXE /OPEN/SHARE/HEADER/PROT It can also be added in the SYSTARTUP_VMS.COM. ======================================================= ======= %DECEDIA-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Executing IVP for Compaq DEC/EDI V4.0 =============================== Copyright (c) Compaq Computer Corporation 1990-2000. All rights reserved. Please wait - Checking all Compaq DEC/EDI files ================================ Log of Migration of Server and Client on OPEN VMS AXP -9 ====================================== IVP was successful. Total number of files expected : 225 Number of files missing : 0 Number of checksum errors : 0 Number of file protection errors : 0 Number of file ownership errors : 0 Number of locked files : 0 ====================================== IVP for Compaq DEC/EDI V4.0 has Executed to Completion ====================================================== Installation of DECEDIA V4.0 completed at 02:29 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA040.VMI_DATA VMSINSTAL procedure done at 02:30 Log of Migration of Server and Client on OPEN VMS AXP $ @SYS$UPDATE:VMSINSTAL DECEDIA040 DKA400:[EDI_V4] OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.2-1 It is 12-OCT-2001 at 01:00. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES -10 Log of Migration of Server and Client on OPEN VMS AXP The following products will be processed: DECEDIA V4.0 Beginning installation of DECEDIA V4.0 at 01:00 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? YES%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Compaq Computer Corporation 1989,2000. 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 Compaq Computer Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. The Compaq DEC/EDI V3.2B server is installed on this node. This Compaq DEC/EDI V4.0 kit installation procedure gives you the option of upgrading from Compaq DEC/EDI Log of Migration of Server and Client on OPEN VMS AXP -11 V3.2B to Compaq DEC/EDI V4.0 or loading definitions of EDI standards for use with the Compaq DEC/EDI Message Updates Service. Please select: 1 - To install EDI standards definitions. 2 - To upgrade from Compaq DEC/EDI V3.2B to Compaq DEC/EDI V4.0. 3 - To abort this installation. * Option [1]: 2 ======================================================= WARNING You have instructed this installation procedure to migrate your Compaq DEC/EDI server from V3.2B to V4.0. ======================================================= ======================================================= When Migrating to a V4 database please backup your data from Mapper and Audit Databases. When Migrating ensure FBR$LIBRARY logical is Defined. ======================================================= * Do you wish to continue with this upgrade [NO]? YES * Do you want to purge files replaced by this installation [YES]? YES * Do you want to run the IVP after the installation [YES]? YES ======================================================= === -12 Log of Migration of Server and Client on OPEN VMS AXP Compaq DEC/EDI can be installed on a node as both a Client and a Server or just a Client to a remote Server. ======================================================= === * Do you want to install the Server [YES]? YES ======================================================= ===== In order to use the TCP/IP client interfaces you need to configure them for Compaq DEC/EDI after the installation by running the command file DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER.COM ======================================================= ===== ======================================================= ======= Compaq DEC/EDI Server already exists on this node. Installation of Compaq DEC/EDI will retain data integrity. Upgrading Compaq DEC/EDI Server V3.2B to Compaq DEC/EDI Server V4.0 ======================================================= ======= * Do you still want to proceed with this installation [YES]? YES * Specify the directory to store the UNL File for migration [DECEDI$TEMP:]: The following versions of Rdb/VMS are available: *V7.0-3 * Please enter the Rdb/VMS version to be used by Compaq DEC/EDI [*V7.0-3]: Log of Migration of Server and Client on OPEN VMS AXP -13 Current PROCESS Oracle Rdb environment is version V7.0-3 (MULTIVERSION) Current PROCESS SQL environment is version V7.0-3 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V7.0-3 (MULTIVERSION) No further questions will be asked during the installation. Installation of Compaq DEC/EDI V4.0 will take approximately 7-15 minutes %DECEDIA-I-INFO, defining DECEDI Account with autogenerated password %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %DECEDIA-I-INFO, Defining Compaq DEC/EDI Directories %DECEDIA-I-DIREXISTS, Amending ownership of directory DKA0:[DECEDI] %DECEDIA-I-DIREXISTS, Amending ownership of directory DKA0:[DECEDI.AUDIT_DB] %DECEDIA-I-DIREXISTS, Amending ownership of directory DKA0:[DECEDI.ARCHIVE_DB] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[DATA] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[ERROR] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[VANREPORTS] -14 Log of Migration of Server and Client on OPEN VMS AXP %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[ARCHREPORTS] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[TOOLS] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[DS_SCRATCH] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[BACKUP] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[CVP] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[CVP.WORK] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[CVP.IMPEXP] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[3780PLUS] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[MESSAGE_UPDATES] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[CACHE] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[MAP_TABLES] %DECEDIA-I-DIREXISTS, Amending existing directory DECEDI$TOP:[TEMP] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_1] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_2] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_3] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_4] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_5] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_6] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_7] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_8] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_9] Log of Migration of Server and Client on OPEN VMS AXP -15 %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_10] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_11] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_12] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_13] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_14] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_15] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_16] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_17] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_18] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_19] %DECEDIA-I-DIREXISTS, Amending ownership of directory DECEDI$TOP:[STORE_20] %DECEDIA-I-SECURDIR, Securing all Compaq DEC/EDI directories... %DECEDIA-I-INFO, Restoring Compaq DEC/EDI Files... %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %DECEDIA-I-INFO, Loading Compaq DEC/EDI Files... %DECEDIA-I-INFO, Loading tools and examples... %DECEDIA-I-INFO, Loading DCL command tables... %DECEDIA-I-INFO, Loading help files... %DECEDIA-I-INFO, Loading TPU section files... %TPU-S-CREATED, File WARP91$DKA0:[SYS0.SYSUPD.DECEDIA040]DECEDI$SECTION.TPU$ SECTION;1 created -16 Log of Migration of Server and Client on OPEN VMS AXP %TPU-S-SECTSAVED, 76 procedures, 90 variables, 29 keys saved %DECEDIA-I-INFO, Loading System images... %DECEDIA-I-INFO, Loading Application service files... %DECEDIA-I-INFO, Loading Translation service images... %DECEDIA-I-INFO, Loading Communication service images... %DECEDIA-I-INFO, Loading Communication service files... %DECEDIA-I-INFO, Loading FDL Files... %DECEDIA-I-INFO, Loading Data Files... %DECEDIA-I-INFO, Loading Command Files... %DECEDIA-I-INFO, Loading Mapper Files... %DECEDIA-I-INFO, Restoring The Message Updates Service Tool for Compaq DEC/EDI V4.0. %VMSINSTAL-I-RESTORE, Restoring product save set L ... %DECEDIA-I-INFO, Converting Data Files... %DECEDIA-I-INFO, Loading CVP data... Installation of Compaq DEC/EDI V4.0 succeeded ==================================== ======================================================= ======= DECEDI$PRVSHR.EXE Image should be loaded into the Memory using a privileged account. Following Command should be run in order to make use of the Compaq DEC/EDI Client. INSTALL ADD SYS$LIBRARY:DECEDI$PRVSHR.EXE /OPEN/SHARE/HEADER/PROT It can also be added in the SYSTARTUP_VMS.COM. ======================================================= ======= %DECEDIA-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Log of Migration of Server and Client on OPEN VMS AXP -17 =================== Migration Starts... =================== ======================== Migrating EVENT table... ======================== %RDMS-W-DOFULLBCK, full database backup should be done to ensure future recovery %SQL-I-DEPR_FEATURE, Deprecated Feature: Default evaluation for constraints: DEFERRABLE %SQL-I-DEPR_FEATURE, Deprecated Feature: Default evaluation for constraints: DEFERRABLE %RMU-I-DATRECUNL, 39 data records unloaded. Successfully completed unloading EVENT TABLE data %RMU-I-DATRECREAD, 39 data records read from input file. %RMU-I-DATRECSTO, 39 data records stored. Successfully completed loading EVENT TABLE data ======================= Creating AVAIL table... ======================= %RDMS-W-DOFULLBCK, full database backup should be done to ensure future recovery 0 rows inserted ============================================ Migrating THF & TLF tables in ARCHIVE DB ... ============================================ -18 Log of Migration of Server and Client on OPEN VMS AXP %RMU-I-DATRECUNL, 222 data records unloaded. Successfully completed unloading THF_TABLE data 37 rows updated 222 rows deleted 0 rows updated %RMU-I-DATRECREAD, 222 data records read from input file. %RMU-I-DATRECSTO, 222 data records stored. Successfully Completed loading THF_TABLE data 222 rows updated Migration from V3.2B to V4.0 succeeded Executing IVP for Compaq DEC/EDI V4.0 ===================================== Copyright (c) Compaq Computer Corporation 1990-2000. All rights reserved. Please wait - Checking all Compaq DEC/EDI files =============================================== ====================================== IVP was successful. Total number of files expected : 236 Number of files missing : 0 Number of checksum errors : 0 Number of file protection errors : 0 Number of file ownership errors : 0 Number of locked files : 0 ====================================== IVP for Compaq DEC/EDI V4.0 has Executed to Completion Log of Migration of Server and Client on OPEN VMS AXP -19 ============================================ Installation of DECEDIA V4.0 completed at 01:15 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA040.VMI_DATA VMSINSTAL procedure done at 01:15 Appendix BOpenVMS Client only Log of New Client Installation of OPEN VMS AXP $ @SYS$UPDATE:VMSINSTAL DECEDIA040 DKA400:[EDI_V4] OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.2-1 It is 12-OCT-2001 at 01:57. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: DECEDIA V4.0 Beginning installation of DECEDIA V4.0 at 01:57 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Compaq Computer Corporation 1989,2000. All rights reserved. B-2 OpenVMS Client only OpenVMS Client only 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 Compaq Computer Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? YES * Do you want to run the IVP after the installation [YES]? YES ========================================================== Compaq DEC/EDI can be installed on a node as both a Client and a Server or just a Client to a remote Server. ========================================================== * Do you want to install the Server [YES]? NO ============================================================ In order to use the TCP/IP client interfaces you need to configure them for Compaq DEC/EDI after the installation by running the command file DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER.COM ============================================================ * On what device should the DECEDI directories reside: DKA0 * What is the UIC to be used for the Compaq DEC/EDI account: [500,1] * What is the name of the node on which the Compaq DEC/EDI Server will run: JMEKON.ERI.XKO.DEC.COM No further questions will be asked during the installation. Installation of Compaq DEC/EDI V4.0 will take approximately 2- 5 minutes %DECEDIA-I-INFO, defining DECEDI Account with autogenerated password %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named DECEDI. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier DECEDI value [000500,000001] added to rights database %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. OpenVMS Client only B- 3 OPENVMS CLIENT ONLY %UAF-I-MDFYMSG, user record(s) updated %DECEDIA-I-INFO, Defining Compaq DEC/EDI Directories %DECEDIA-I-CREATEDIR, Creating directory DKA0:[DECEDI] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DKA0:[DECEDI]. %DECEDIA-I-CREATEDIR, Creating directory DKA0:[DECEDI.TOOLS] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DKA0:[DECEDI.TOOLS]. %DECEDIA-I-CREATEDIR, Creating directory DKA0:[DECEDI.DATA] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DKA0:[DECEDI.DATA]. %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECEDI]. %DECEDIA-I-SECURDIR, Securing all Compaq DEC/EDI directories... %DECEDIA-I-INFO, Restoring Compaq DEC/EDI Files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %DECEDIA-I-INFO, Loading Compaq DEC/EDI Files... %DECEDIA-I-INFO, Loading tools... %DECEDIA-I-INFO, Loading DCL command tables... %DECEDIA-I-INFO, Loading System images... %DECEDIA-I-INFO, Loading Application service images... %DECEDIA-I-INFO, Loading Application service files... Installation of Compaq DEC/EDI V4.0 succeeded ============================================= ========================================================== DECEDI$PRVSHR.EXE Image should be loaded into the Memory using a privileged account. Following Command should be run in order to make use of the Compaq DEC/EDI Client. INSTALL ADD SYS$LIBRARY:DECEDI$PRVSHR.EXE /OPEN/SHARE/HEADER/PROT It can also be added in the SYSTARTUP_VMS.COM. ========================================================== %DECEDIA-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Executing IVP for Compaq DEC/EDI V4.0 ===================================== Copyright (c) Compaq Computer Corporation 1990-2000. All rights reserved. B-4 OpenVMS Client only OpenVMS Client only Please wait - Checking all Compaq DEC/EDI files =============================================== ====================================== IVP was successful. Total number of files expected : 16 Number of files missing : 0 Number of checksum errors : 0 Number of file protection errors : 0 Number of file ownership errors : 0 Number of locked files : 0 ====================================== IVP for Compaq DEC/EDI V4.0 has Executed to Completion ====================================================== Installation of DECEDIA V4.0 completed at 01:59 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA040.VMI_DATA VMSINSTAL procedure done at 01:59 Log of Migration of Client on OPEN VMS AXP $ @SYS$UPDATE:VMSINSTAL DECEDIA040 DKA400:[EDI_V4] OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.2-1 It is 12-OCT-2001 at 02:12. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: DECEDIA V4.0 Beginning installation of DECEDIA V4.0 at 02:12 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. OpenVMS Client only B- 5 OPENVMS CLIENT ONLY Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Compaq Computer Corporation 1989,2000. 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 Compaq Computer Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? YES * Do you want to run the IVP after the installation [YES]? YES ========================================================== Compaq DEC/EDI can be installed on a node as both a Client and a Server or just a Client to a remote Server. ========================================================== * Do you want to install the Server [YES]? NO ========================================================== In order to use the TCP/IP client interfaces you need to configure them for Compaq DEC/EDI after the installation by running the command file DECEDI$TOOLS:DECEDI$CONFIGURE_CLIENT_SERVER.COM =========================================================== ============================================================== Compaq DEC/EDI Client already exists on this node. Upgrading Compaq DEC/EDI Client V3.2B to Compaq DEC/EDI Client V4.0 ============================================================== * Do you still want to proceed with this installation [YES]? YES B-6 OpenVMS Client only OpenVMS Client only * What is the name of the node on which the Compaq DEC/EDI Server will run: JMEKON No further questions will be asked during the installation. Installation of Compaq DEC/EDI V4.0 will take approximately 2- 5 minutes %DECEDIA-I-INFO, defining DECEDI Account with autogenerated password %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %DECEDIA-I-INFO, Defining Compaq DEC/EDI Directories %DECEDIA-I-DIREXISTS, Amending ownership of directory DKA0:[DECEDI] %DECEDIA-I-DIREXISTS, Amending ownership of directory DKA0:[DECEDI.TOOLS] %DECEDIA-I-DIREXISTS, Amending ownership of directory DKA0:[DECEDI.DATA] %DECEDIA-I-SECURDIR, Securing all Compaq DEC/EDI directories... %DECEDIA-I-INFO, Restoring Compaq DEC/EDI Files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %DECEDIA-I-INFO, Loading Compaq DEC/EDI Files... %DECEDIA-I-INFO, Loading tools... %DECEDIA-I-INFO, Loading DCL command tables... %DECEDIA-I-INFO, Loading System images... %DECEDIA-I-INFO, Loading Application service images... %DECEDIA-I-INFO, Loading Application service files... Installation of Compaq DEC/EDI V4.0 succeeded ==================================== ============================================================== DECEDI$PRVSHR.EXE Image should be loaded into the Memory using a privileged account. Following Command should be run in order to make use of the Compaq DEC/EDI Client. OpenVMS Client only B- 7 OPENVMS CLIENT ONLY INSTALL ADD SYS$LIBRARY:DECEDI$PRVSHR.EXE /OPEN/SHARE/HEADER/PROT It can also be added in the SYSTARTUP_VMS.COM. ============================================================== %DECEDIA-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Executing IVP for Compaq DEC/EDI V4.0 =============================== Copyright (c) Compaq Computer Corporation 1990-2000. All rights reserved. Please wait - Checking all Compaq DEC/EDI files ==================================== ====================================== IVP was successful. Total number of files expected : 18 Number of files missing : 0 Number of checksum errors : 0 Number of file protection errors : 0 Number of file ownership errors : 0 Number of locked files : 0 ======================================= IVP for Compaq DEC/EDI V4.0 has Executed to Completion ============================================ Installation of DECEDIA V4.0 completed at 02:14 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA040.VMI_DATA VMSINSTAL procedure done at 02:14 Appendix C OpenVMS Message Updates Kit @SYS$UPDATE:VMSINSTAL DECEDIA040 DKA400:[V4_KIT] OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.2-1 It is 12-OCT-2001 at 19:00. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: DECEDI$DS DECEDI$AS_1 $ @SYS$UPDATE:VMSINSTAL DECEDIA040 DKA400:[USERS.PRAKASH.03OCTKIT] OPTIONS N OpenVMS AXP Software Product Installation Procedure V7.2-1 It is 12-OCT-2001 at 19:01. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: DECEDIA V4.0 Beginning installation of DECEDIA V4.0 at 19:01 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Compaq Computer Corporation 1989,2000. 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. B-10 OpenVMS Message Updates Kit OpenVMS Message Updates Kit This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. The Compaq DEC/EDI V4.0 server is already installed on this node. This Compaq DEC/EDI V4.0 kit installation procedure gives you the option of re installing Compaq DEC/EDI V4.0 or loading definitions of EDI standards for use with the Compaq DEC/EDI Message Updates Service. Please select: 1 - To install EDI standards definitions. 2 - To re install Compaq DEC/EDI V4.0. 3 - To abort this installation. * Option [1]: 1 This Compaq DEC/EDI V4.0 kit contains support for version 2 of the Compaq DEC/EDI Message Updates Service, which superceeds the version 1 Compaq DEC/EDI Message Updates Service. Compaq DEC/EDI Message Updates Service V2 consists of two parts: The Message Updates Service tool. This installation procedure will ensure that the correct version of this tool for Compaq DEC/EDI V4.0 is installed. A set of IMPDEF files containing standards definitions. In order to use Message Updates with Compaq DEC/EDI V4.0 you must now indicate which standards you wish to use with your Compaq DEC/EDI system. For more information about Compaq DEC/EDI Message Updates Service V2 see the Message Updates Release notes that are installed by this Compaq DEC/EDI kit. Version 1 Compaq DEC/EDI Message Updates Services are not supported by Compaq DEC/EDI V4.0 * Do you wish to install Compaq DEC/EDI MUS IMPDEF files [YES]? The Message Updates Service stores Standard/Version IMPDEF files in a directory referred to by the logical name DECEDI$IMPDEF. The DECEDI$IMPDEF directory does not exist. It is normally created in the DECEDI$TOP directory structure. * Do you wish to suggest an alternative path for DECEDI$IMPDEF [N]? %VMSINSTAL-I-SYSDIR, This product creates system disk directory DECEDI$TOP:[IMPDEF]/OWNER_UIC=[DECE DI]/PROTECTION=(S:RWED,O:RWED,G:R,W:R). * Do you wish to restore any EDIFACT IMPDEF files [Y]? %VMSINSTAL-I-RESTORE, Restoring product save set G ... The IMPDEF files for the following versions of EDIFACT are available : 1 901 902 911 OpenVMS Message Updates Kit B- 11 OPENVMS MESSAGE UPDATES KIT 912 921 CTRL D00A D93A D94B D95A D95B D96A D96B D97A D97B D98A D98B D99A D99B S93A Enter a comma separated list of EDIFACT IMPDEF files to restore. e.g. 1,S93A Or type ALL to select all EDIFACT IMPDEF files. * Select EDIFACT IMPDEF files to restore [ALL]: Restoring the chosen EDIFACT IMPDEF files requires 21137 storage blocks. This will leave you with 479428 free blocks. * Do you wish to continue restoring the chosen EDIFACT IMPDEF files. [Y]? * Do you wish to restore any ODETTE IMPDEF files [Y]? %VMSINSTAL-I-RESTORE, Restoring product save set H ... The IMPDEF files for the following versions of ODETTE are available : 1 3 Enter a comma separated list of ODETTE IMPDEF files to restore. e.g. 1,3 Or type ALL to select all ODETTE IMPDEF files. * Select ODETTE IMPDEF files to restore [ALL]: Restoring the chosen ODETTE IMPDEF files requires 232 storage blocks. This will leave you with 479196 free blocks. * Do you wish to continue restoring the chosen ODETTE IMPDEF files. [Y]? * Do you wish to restore any X12 IMPDEF files [Y]? %VMSINSTAL-I-RESTORE, Restoring product save set I ... The IMPDEF files for the following versions of X12 are available : 002001 002002 002003 B-12 OpenVMS Message Updates Kit OpenVMS Message Updates Kit 002040 003010 003020 003021 003022 003030 003031 003032 003040 003041 003050 003051 003052 003060 003061 003062 003070 003071 003072 004010 004011 004012 004020 004021 004030 Enter a comma separated list of X12 IMPDEF files to restore. e.g. 002001,004030 Or type ALL to select all X12 IMPDEF files. * Select X12 IMPDEF files to restore [ALL]: Restoring the chosen X12 IMPDEF files requires 87829 storage blocks. This will leave you with 391367 free blocks. * Do you wish to continue restoring the chosen X12 IMPDEF files. [Y]? * Do you wish to restore any TDCC IMPDEF files [Y]? %VMSINSTAL-I-RESTORE, Restoring product save set J ... The IMPDEF files for the following versions of TDCC are available : 002006 002007 002008 002009 003000 003001 003020 003030 003040 003050 OpenVMS Message Updates Kit B- 13 OPENVMS MESSAGE UPDATES KIT 003060 003070 004010 Enter a comma separated list of TDCC IMPDEF files to restore. e.g. 002006,004010 Or type ALL to select all TDCC IMPDEF files. * Select TDCC IMPDEF files to restore [ALL]: Restoring the chosen TDCC IMPDEF files requires 19570 storage blocks. This will leave you with 371797 free blocks. * Do you wish to continue restoring the chosen TDCC IMPDEF files. [Y]? * Do you wish to restore any TRADACOMS IMPDEF files [Y]? %VMSINSTAL-I-RESTORE, Restoring product save set K ... The IMPDEF files for the following versions of TRADACOMS are available : 89 93 Enter a comma separated list of TRADACOMS IMPDEF files to restore. e.g. 89,93 Or type ALL to select all TRADACOMS IMPDEF files. * Select TRADACOMS IMPDEF files to restore [ALL]: Restoring the chosen TRADACOMS IMPDEF files requires 389 storage blocks. This will leave you with 371408 free blocks. * Do you wish to continue restoring the chosen TRADACOMS IMPDEF files. [Y]? %DECEDIA-I-INFO, Restoring The Message Updates Service Tool for Compaq DEC/EDI V4.0. %VMSINSTAL-I-RESTORE, Restoring product save set L ... Installation of MUS for Compaq DEC/EDI V4.0 succeeded ===================================================== %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of DECEDIA V4.0 completed at 19:11 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA040.VMI_DATA VMSINSTAL procedure done at 19:11 Appendix D Digital UNIX Server and Client Installtion Log Use the setld command to install the DEC/EDI software # setld -l /dedi040/kit 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) Compaq DEC/EDI 3780 Gateway 2) Compaq DEC/EDI Base 3) Compaq DEC/EDI Client Man Pages 4) Compaq DEC/EDI Client 5) Compaq DEC/EDI Internet SMTP/MIME Gateway 6) Compaq DEC/EDI Mailbus 400 Gateway 7) Compaq DEC/EDI Message Updates Base --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Estimated free diskspace(MB) in root:29.3 usr:1106.7 var:475.8 Choices (for example, 1 2 4-6): 8) Compaq DEC/EDI Message Updates EDIFACT IMPDEF files 9) Compaq DEC/EDI Message Updates Man Pages 10) Compaq DEC/EDI Message Updates ODETTE IMPDEF files 11) Compaq DEC/EDI Message Updates TDCC IMPDEF files 12) Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files 13) Compaq DEC/EDI Message Updates X12 IMPDEF files 14) Compaq DEC/EDI OFTP Gateway 15) Compaq DEC/EDI Server Man Pages 16) Compaq DEC/EDI Server 17) Compaq DEC/EDI Translation Services --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. D-16 Digital UNIX Server and Client Digital UNIX Server and Client Estimated free diskspace(MB) in root:29.3 usr:1106.7 var:475.8 Choices (for example, 1 2 4-6): Or you may choose one of the following options: 18) ALL of the above 19) CANCEL selections and redisplay menus 20) EXIT without installing any subsets Estimated free diskspace(MB) in root:29.3 usr:1106.7 var:475.8 Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 18 You are installing the following optional subsets: Compaq DEC/EDI 3780 Gateway Compaq DEC/EDI Base Compaq DEC/EDI Client Man Pages Compaq DEC/EDI Client Compaq DEC/EDI Internet SMTP/MIME Gateway Compaq DEC/EDI Mailbus 400 Gateway Compaq DEC/EDI Message Updates Base Compaq DEC/EDI Message Updates EDIFACT IMPDEF files Compaq DEC/EDI Message Updates Man Pages Compaq DEC/EDI Message Updates ODETTE IMPDEF files Compaq DEC/EDI Message Updates TDCC IMPDEF files Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files Compaq DEC/EDI Message Updates X12 IMPDEF files Compaq DEC/EDI OFTP Gateway Press RETURN to display the next screen. Compaq DEC/EDI Server Man Pages Compaq DEC/EDI Server Compaq DEC/EDI Translation Services Estimated free diskspace(MB) in root:29.3 usr:1017.8 var:475.8 Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 17 subsets will be installed. Loading subset 1 of 17 ... DEC/EDI Base (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Base (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Base Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 2 of 17 ... DEC/EDI Server (Compaq Tru64 UNIX) version 4.0 Digital UNIX Server and Client D-17 DIGITAL UNIX SERVER AND CLIENT Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Server (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Server Copying from /usr/users/sriram/kit/dedi400/kit (disk) Working....Tue Nov 6 19:11:55 IST 2001 Verifying Loading subset 3 of 17 ... DEC/EDI Server Man Pages (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Server Man Pages (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Server Man Pages Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 4 of 17 ... DEC/EDI Client (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Client (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Client Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 5 of 17 ... DEC/EDI Client Man Pages (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Client Man Pages (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Client Man Pages Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 6 of 17 ... DEC/EDI Translation Services (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Translation Services (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Translation Services Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 7 of 17 ... D-18 Digital UNIX Server and Client Digital UNIX Server and Client DEC/EDI Mailbus 400 Gateway (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Mailbus 400 Gateway (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Loading subset 8 of 17 ... DEC/EDI OFTP Gateway (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI OFTP Gateway (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Loading subset 9 of 17 ... DEC/EDI Internet SMTP/MIME Gateway (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Internet SMTP/MIME Gateway (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Internet SMTP/MIME Gateway Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 10 of 17 ... DEC/EDI 3780 Communications Gateway (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI 3780 Communications Gateway (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI 3780 Gateway Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 11 of 17 ... DEC/EDI Message Updates Base version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates Base subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates Base Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 12 of 17 ... DEC/EDI Message Updates Man Pages version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. Digital UNIX Server and Client D-19 DIGITAL UNIX SERVER AND CLIENT DEC/EDI Message Updates Man Pages subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates Man Pages Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 13 of 17 ... DEC/EDI Message Updates EDIFACT IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates EDIFACT IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates EDIFACT IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 14 of 17 ... DEC/EDI Message Updates ODETTE IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates ODETTE IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates ODETTE IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 15 of 17 ... DEC/EDI Message Updates X12 IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates X12 IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates X12 IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Working....Tue Nov 6 19:13:37 IST 2001 Verifying Loading subset 16 of 17 ... DEC/EDI Message Updates TDCC IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates TDCC IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates TDCC IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 17 of 17 ... DEC/EDI Message Updates TRADACOMS IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. D-20 Digital UNIX Server and Client Digital UNIX Server and Client All rights reserved. DEC/EDI Message Updates TRADACOMS IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying 15 of 17 subsets installed successfully. Configuring "Compaq DEC/EDI Base" (DEDIBASE400) Configuring "Compaq DEC/EDI Server" (DEDISERV400) Configuring "Compaq DEC/EDI Server Man Pages" (DEDISERVMAN400) Configuring "Compaq DEC/EDI Client" (DEDICLT400) Configuring "Compaq DEC/EDI Client Man Pages" (DEDICLTMAN400) Configuring "Compaq DEC/EDI Translation Services" (DEDITRAN400) Configuring "Compaq DEC/EDI Internet SMTP/MIME Gateway" (DEDISMTP400) Configuring "Compaq DEC/EDI 3780 Gateway" (DEDI3780400) Configuring "Compaq DEC/EDI Message Updates Base" (DEDIAMSGBASE400) Configuring "Compaq DEC/EDI Message Updates Man Pages" (DEDIAMSGMAN400) Configuring "Compaq DEC/EDI Message Updates EDIFACT IMPDEF files" (DEDIAMSGEDIF400) Configuring "Compaq DEC/EDI Message Updates ODETTE IMPDEF files" (DEDIAMSGODET400) Configuring "Compaq DEC/EDI Message Updates X12 IMPDEF files" (DEDIAMSGX12400) Configuring "Compaq DEC/EDI Message Updates TDCC IMPDEF files" (DEDIAMSGTDCC400) Configuring "Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files" (DEDIAMSGTRAD400) Deinstalltion Log The following subsets need "Compaq DEC/EDI Message Updates Base" (DEDIAMSGBASE400) to operate correctly: Compaq DEC/EDI Message Updates EDIFACT IMPDEF files (DEDIAMSGEDIF400) Compaq DEC/EDI Message Updates Man Pages (DEDIAMSGMAN400) Compaq DEC/EDI Message Updates ODETTE IMPDEF files (DEDIAMSGODET400) Compaq DEC/EDI Message Updates TDCC IMPDEF files (DEDIAMSGTDCC400) Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files (DEDIAMSGTRAD400) Compaq DEC/EDI Message Updates X12 IMPDEF files (DEDIAMSGX12400) Are you sure you wish to delete "Compaq DEC/EDI Message Updates Base" (DEDIAMSGBASE400)? (y/n): y Digital UNIX Server and Client D-21 DIGITAL UNIX SERVER AND CLIENT Deleting "Compaq DEC/EDI Message Updates Base" (DEDIAMSGBASE400). Deleting "Compaq DEC/EDI 3780 Gateway" (DEDI3780400). Deleting "Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files" (DEDIAMSGTRAD400). Deleting "Compaq DEC/EDI Message Updates TDCC IMPDEF files" (DEDIAMSGTDCC400). Deleting "Compaq DEC/EDI Message Updates EDIFACT IMPDEF files" (DEDIAMSGEDIF400). Deleting "Compaq DEC/EDI Message Updates Man Pages" (DEDIAMSGMAN400). The following subsets need "Compaq DEC/EDI Base" (DEDIBASE400) to operate correctly: Compaq DEC/EDI Server (DEDISERV400) Are you sure you wish to delete "Compaq DEC/EDI Base" (DEDIBASE400)? (y/n): y Deleting "Compaq DEC/EDI Message Updates X12 IMPDEF files" (DEDIAMSGX12400). Deleting "Compaq DEC/EDI Message Updates ODETTE IMPDEF files" (DEDIAMSGODET400). Deleting "Compaq DEC/EDI Client Man Pages" (DEDICLTMAN400). Deleting "Compaq DEC/EDI Client" (DEDICLT400). Deleting "Compaq DEC/EDI Base" (DEDIBASE400). Deleting "Compaq DEC/EDI Internet SMTP/MIME Gateway" (DEDISMTP400). Deleting "Compaq DEC/EDI OFTP Gateway" (DEDIOFTP400). Deleting "Compaq DEC/EDI Translation Services" (DEDITRAN400). Deleting "Compaq DEC/EDI Server Man Pages" (DEDISERVMAN400). Deleting "Compaq DEC/EDI Server" (DEDISERV400). Appendix E DIGITAL UNIX Client only # setld -l /usr/users/sriram/kit/dedi400/kit 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) Compaq DEC/EDI 3780 Gateway 2) Compaq DEC/EDI Client Man Pages 3) Compaq DEC/EDI Client 4) Compaq DEC/EDI Internet SMTP/MIME Gateway 5) Compaq DEC/EDI Mailbus 400 Gateway 6) Compaq DEC/EDI OFTP Gateway --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Estimated free diskspace(MB) in root:28.7 usr:1018.1 var:438.3 Choices (for example, 1 2 4-6): 2-3 Or you may choose one of the following options: 7) ALL of the above 8) CANCEL selections and redisplay menus 9) EXIT without installing any subsets Estimated free diskspace(MB) in root:28.7 usr:1017.6 var:438.3 Add to your choices, choose an overriding action or press RETURN to confirm previous selections. Choices (for example, 1 2 4-6): 2-3 You are installing the following optional subsets: Compaq DEC/EDI Client Man Pages Compaq DEC/EDI Client Estimated free diskspace(MB) in root:28.7 usr:1017.6 var:438.3 Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 2 subsets will be installed. E-24 DIGITAL UNIX Client only DIGITAL UNIX Client only Loading subset 1 of 2 ... DEC/EDI Client (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Client (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Client Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 2 of 2 ... DEC/EDI Client Man Pages (Compaq Tru64 UNIX) version 4.0 Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Client Man Pages (Compaq Tru64 UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Client Man Pages Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying 2 of 2 subsets installed successfully. Configuring "Compaq DEC/EDI Client" (DEDICLT400) Configuring "Compaq DEC/EDI Client Man Pages" (DEDICLTMAN400) Appendix F DIGITAL UNIX Message Updates # setld -l /usr/users/sriram/kit/dedi400/kit 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) Compaq DEC/EDI 3780 Gateway 2) Compaq DEC/EDI Internet SMTP/MIME Gateway 3) Compaq DEC/EDI Mailbus 400 Gateway 4) Compaq DEC/EDI Message Updates Base 5) Compaq DEC/EDI Message Updates Man Pages 6) Compaq DEC/EDI Message Updates ODETTE IMPDEF files 7) Compaq DEC/EDI Message Updates TDCC IMPDEF files 8) Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files 9) Compaq DEC/EDI Message Updates X12 IMPDEF files 10) Compaq DEC/EDI OFTP Gateway --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Estimated free diskspace(MB) in root:28.7 usr:1071.0 var:438.4 Choices (for example, 1 2 4-6):4-9 Or you may choose one of the following options: 11) ALL of the above 12) CANCEL selections and redisplay menus 13) EXIT without installing any subsets Estimated free diskspace(MB) in root:28.7 usr:1018.1 var:438.4 Add to your choices, choose an overriding action or press RETURN to confirm previous selections. Choices (for example, 1 2 4-6): 4-9 You are installing the following optional subsets: Compaq DEC/EDI Message Updates Base Compaq DEC/EDI Message Updates Man Pages Compaq DEC/EDI Message Updates ODETTE IMPDEF files Compaq DEC/EDI Message Updates TDCC IMPDEF files F-26 DIGITAL UNIX Message Updates DIGITAL UNIX Message Updates Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files Compaq DEC/EDI Message Updates X12 IMPDEF files Estimated free diskspace(MB) in root:28.7 usr:1018.1 var:438.4 Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 6 subsets will be installed. Loading subset 1 of 6 ... DEC/EDI Message Updates Base version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates Base subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates Base Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 2 of 6 ... DEC/EDI Message Updates Man Pages version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates Man Pages subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates Man Pages Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 3 of 6 ... DEC/EDI Message Updates ODETTE IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates ODETTE IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates ODETTE IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 4 of 6 ... DEC/EDI Message Updates X12 IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates X12 IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates X12 IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Working....Sat Nov 17 14:08:26 IST 2001 Verifying DIGITAL UNIX Message Updates F-27 DIGITAL UNIX MESSAGE UPDATES Loading subset 5 of 6 ... DEC/EDI Message Updates TDCC IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates TDCC IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates TDCC IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying Loading subset 6 of 6 ... DEC/EDI Message Updates TRADACOMS IMPDEF files version Copyright Compaq Computer Corporation 1990,2001. All rights reserved. DEC/EDI Message Updates TRADACOMS IMPDEF files subset will take approximately 2 minutes to install, depending on your system and configuration. Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files Copying from /usr/users/sriram/kit/dedi400/kit (disk) Verifying 6 of 6 subsets installed successfully. Configuring "Compaq DEC/EDI Message Updates Base" (DEDIAMSGBASE400) Configuring "Compaq DEC/EDI Message Updates Man Pages" (DEDIAMSGMAN400) Configuring "Compaq DEC/EDI Message Updates ODETTE IMPDEF files" (DEDIAMSGODET400) Configuring "Compaq DEC/EDI Message Updates X12 IMPDEF files" (DEDIAMSGX12400) Configuring "Compaq DEC/EDI Message Updates TDCC IMPDEF files" (DEDIAMSGTDCC400) Configuring "Compaq DEC/EDI Message Updates TRADACOMS IMPDEF files" (DEDIAMSGTRAD400) Appendix G Sun Solaris Client Kit Contents #tar -xvf decedi0400_sun_client.tar x /etc/setld, 50428 bytes, 99 tape blocks x /usr/doc/decedi_spd_ss_040.txt, 11646 bytes, 23 tape blocks x output, 0 bytes, 0 tape blocks x output/space, 0 bytes, 0 tape blocks x output/instctrl, 0 bytes, 0 tape blocks x output/instctrl/DEDICLT400.inv, 2691 bytes, 6 tape blocks x output/instctrl/DEDICLT400.ctrl, 150 bytes, 1 tape blocks x output/instctrl/DED400.comp, 0 bytes, 0 tape blocks x output/instctrl/DEDICLT400.scp, 13046 bytes, 26 tape blocks x output/instctrl/DEDIMAN400.inv, 751 bytes, 2 tape blocks x output/instctrl/DEDIMAN400.ctrl, 153 bytes, 1 tape blocks x output/instctrl/DEDIMAN400.scp, 12864 bytes, 26 tape blocks x output/instctrl/DEDI.image, 48 bytes, 1 tape blocks x output/DEDICLT400, 174080 bytes, 340 tape blocks x output/DEDIMAN400, 40960 bytes, 80 tape blocks x output/INSTCTRL, 40960 bytes, 80 tape blocks x output/DEDI.image, 48 bytes, 1 tape blocks Installation Log #/etc/setld -l output *** Enter Subset Selections *** The subsets listed below are optional: 1) Compaq DEC/EDI V4.0 SUN Solaris Client 2) Compaq DEC/EDI V4.0 SUN Solaris Man Pages 3) All of the Above 4) None of the Above 5) Exit without installing subsets Enter your choice(s): 3 You are installing the following subsets: G-30 Sun Solaris Client Sun Solaris Client Compaq DEC/EDI V4.0 SUN Solaris Client Compaq DEC/EDI V4.0 SUN Solaris Man Pages Is this correct? (y/n): y ************************************************************** DEC/EDI Client (Sun Solaris) Copyright Compaq Computer Corporation 1990,2001. 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. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. ************************************************************** ************************************************************** This DEC/EDI Client (Sun Solaris) subset will take approximately 2 minutes to install, depending on your system and configuration. ************************************************************** Compaq DEC/EDI V4.0 SUN Solaris Client (DEDICLT400) Copying from output (disk) Verifying ************************************************************** DEC/EDI Client Man Pages (Sun Solaris) Copyright Compaq Computer Corporation 1990,2001. 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. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. ************************************************************** ************************************************************** This DEC/EDI Client Man Pages (Sun Solaris) subset will take approximately 2 minutes to install, depending on your system and configuration. Sun Solaris Client G-31 SUN SOLARIS CLIENT ************************************************************** Compaq DEC/EDI V4.0 SUN Solaris Man Pages (DEDIMAN400) Copying from output (disk) Verifying :- creating softlinks ... done. ************************************************************** DEC/EDI Client (Sun Solaris) successfully installed ************************************************************** :- creating softlinks ... done. ************************************************************** DEC/EDI Client Man Pages (Sun Solaris) successfully installed ************************************************************** Configuration Log #/usr/bin/decedi_config.sh Configuring the TCP/IP Client-Server link Assigned port 5150 /etc/services for Compaq DEC/EDI Post-Fetch service. Assigned port 5151 /etc/services for Compaq DEC/EDI Track service. These port numbers must match those used on the remote Compaq DEC/EDI Server. If these numbers are different on the Compaq DEC/EDI Server then please modify /etc/services and update the port nunbers associated with decedi_csf and decedi_cst. ************************************************************** * To supply the server node information, create a file: * * /var/adm/decedi/decedi_servers.dat * * Use the template, /var/adm/decedi/decedi_servers.template. * * * * TCP/IP Configuration Complete * ************************************************************** Press to continue. Deinstallation Log #/etc/setld -d DEDICLT400 DEDIMAN400 DEC/EDI Client (Sun Solaris):- Removing softlinks ... done. Deleting Compaq DEC/EDI V4.0 SUN Solaris Client (DEDICLT400). ************************************************************** DEC/EDI Client (Sun Solaris) has been deleted ************************************************************** DEC/EDI Client Man Pages (Sun Solaris):- Removing softlinks ... done. Deleting Compaq DEC/EDI V4.0 SUN Solaris Man Pages (DEDIMAN400). ************************************************************** DEC/EDI Client Man Pages (Sun Solaris) has been deleted ************************************************************** Directory and File listing for SUN Solaris Client Table 11-1 Files in Client Subset Directory File Description /etc setld Utility to install DEC/EDI Client software /usr/opt/DEDICLT400 Subdirectories where physicalfiles reside. The files which precede this entry are mainly softlinks to files under this directory. /var/adm/decedi decedi_servers.template This file is the template file which contains the template for defining the server listing. Copy this file to decedi_servers.dat and enter all your server entries in it. /usr/bin trade Command Line Interface /usr/bin decedi_config.sh Shell script for TCP/IP configuration /usr/doc decediv40.release_notes DEC/EDI Client Release Notes /usr/include decedi_api_common.h API common values and structures decedi_api_def.h decedi_api_msgs.h decedi_platforms.h API entry points API return values API platform specific Sun Solaris Client G-33 SUN SOLARIS CLIENT /usr/lib/nls/msg/ en_US.88591 decedi_api.cat Message Catalogue /usr/lib libdecediapi.so Shareable link library /usr/examples/decedi api_exam.sh Client example compilation shell script api_exam.c Client programming example cli_exam.sh Client sample shell script init_fetch.sh Start import example crehdr_o.dat TRADACOMS example application file invoic_o.dat X12 eample application file minvox_o.dat EDIFACT example application file minvox_o.ihf EDIFACT DEC/EDI Inhouse file minvox_i.tx Example transmission file minvox_i.tx_smtp Example SMTP transmission systest.csh System tests shell script o3desado.dat ODETTE example application file e911inv1.dat EDIFACT example application file e911inv2.dat EDIFCAT example application file Table 11-1 Files in Client Subset Directory File Description G-34 Sun Solaris Client Sun Solaris Client Table 11-2 Files in Man subset /usr/opt/DEDI MAN400 Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this directory. /usr/man/man1 trade.1 Reference page for Command Line Interface /usr/man/man3 decedi_add_item_list.3 Reference page for Application Programming Interface decedi_free_item_list.3 Reference page for Application Programming Interface decedi_fetch.3 Reference page for Application Programming Interface decedi_post.3 Reference page for Application Programming Interface decedi_track.3 Reference page for Application Programming Interface decedi_free_track_list.3 Reference page for Application Programming Interface Appendix H HP-UX Client Kit Contents #tar -xvf decedi0400_hp_client.tar x /etc/setld, 50428 bytes, 99 tape blocks x output/space, 0 bytes, 0 tape blocks x output/instctrl/DEDICLT400.inv, 2665 bytes, 6 tape blocks x output/instctrl/DEDICLT400.ctrl, 144 bytes, 1 tape blocks x output/instctrl/DED400.comp, 0 bytes, 0 tape blocks x output/instctrl/DEDICLT400.scp, 13050 bytes, 26 tape blocks x output/instctrl/DEDIMAN400.inv, 744 bytes, 2 tape blocks x output/instctrl/DEDIMAN400.ctrl, 147 bytes, 1 tape blocks x output/instctrl/DEDIMAN400.scp, 12876 bytes, 26 tape blocks x output/instctrl/DEDI.image, 48 bytes, 1 tape blocks x output/DEDICLT400, 235520 bytes, 460 tape blocks x output/DEDIMAN400, 40960 bytes, 80 tape blocks x output/INSTCTRL, 40960 bytes, 80 tape blocks x output/DEDI.image, 48 bytes, 1 tape blocks Installtion Log #/etc/setld -l output *** Enter Subset Selections *** The subsets listed below are optional: 1) Compaq DEC/EDI V4.0 HP-UX Client 2) Compaq DEC/EDI V4.0 HP-UX Man Page 3) All of the Above 4) None of the Above 5) Exit without installing subsets Enter your choice(s):3 You are installing the following subsets: Compaq DEC/EDI V4.0 HP-UX Client Compaq DEC/EDI V4.0 HP-UX Man Pages Is this correct? (y/n):y H-36 HP-UX Client HP-UX Client ************************************************************** Compaq DEC/EDI Client (HP UNIX) Copyright Compaq Computer Corporation 1990,2001. 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. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. ************************************************************** ************************************************************** This Compaq DEC/EDI Client (HP UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. ************************************************************** Compaq DEC/EDI V4.0 HP-UX Client (DEDICLT400) Copying from output (disk) Verifying ************************************************************** Compaq DEC/EDI Client Man Pages (HP UNIX) Copyright Compaq Computer Corporation 1990,2001. 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. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. ************************************************************** ************************************************************** This Compaq DEC/EDI Client Man Pages (HP UNIX) subset will take approximately 2 minutes to install, depending on your system and configuration. ************************************************************** Compaq DEC/EDI V4.0 HP-UX Man Pages (DEDIMAN400) Copying from output (disk) Verifying :- creating softlinks ... done. ************************************************************** Compaq DEC/EDI Client (HP UNIX) successfully installed ************************************************************** HP-UX Client H-37 HP-UX CLIENT :- creating softlinks ... done. ************************************************************** Compaq DEC/EDI Client Man Pages (HP UNIX) successfully installed ************************************************************** Configuration Log #/usr/bin/decedi_config.sh Configuring the TCP/IP Client-Server link Assigned port 5150 /etc/services for Compaq DEC/EDI Post-Fetch service. Assigned port 5151 /etc/services for Compaq DEC/EDI Track service. These port numbers must match those used on the remote Compaq DEC/EDI Server. If these numbers are different on the Compaq DEC/EDI Server then please modify /etc/services and update the port nunbers associated with decedi_csf and decedi_cst. ************************************************************** * To supply the server node information, create a file: * * /var/adm/decedi/decedi_servers.dat * * Use the template, /var/adm/decedi/decedi_servers.template. * * * * TCP/IP Configuration Complete * ************************************************************** Press to continue. Deinstallation Log #/etc/setld -d DEDICLT400 DEDIMAN400 Compaq DEC/EDI Client (HP UNIX):- Removing softlinks ... done. Deleting Compaq DEC/EDI V4.0 HP-UX Client (DEDICLT400). ************************************************************** Compaq DEC/EDI Client (HP UNIX) has been deleted ************************************************************** Compaq DEC/EDI Client Man Pages (HP UNIX):- Removing softlinks ... done. Deleting Compaq DEC/EDI V4.0 HP-UX Man Pages (DEDIMAN400). ************************************************************** Compaq DEC/EDI Client Man Pages (HP UNIX) has been deleted ************************************************************** Directory and File listing for HP-UX Client Table 11-3 Files in Client Subset Directory File Description /etc setld Utility to install DEC/EDI Client software /usr/opt/DEDICLT400 Subdirectories where physicalfiles reside. The files which precede this entry are mainly softlinks to files under this directory. /var/adm/decedi decedi_servers.template This file is the template file which contains the template for defining the server listing. Copy this file to decedi_servers.dat and enter all your server entries in it. /usr/bin trade Command Line Interface /usr/bin decedi_config.sh Shell script for TCP/IP configuration /usr/doc decediv40.release_notes DEC/EDI Client Release Notes /usr/include decedi_api_common.h API common values and structures decedi_api_def.h decedi_api_msgs.h decedi_platforms.h API entry points API return values API platform specific /usr/lib/nls/msg/ en_US.88591 decedi_api.cat Message Catalogue /usr/lib libdecediapi.sl Shareable link library /usr/examples/decedi api_exam.sh Client example compilation shell script HP-UX Client H-39 HP-UX CLIENT api_exam.c Client programming example cli_exam.sh Client sample shell script init_fetch.sh Start import example crehdr_o.dat TRADACOMS example application file invoic_o.dat X12 eample application file minvox_o.dat EDIFACT example application file minvox_o.ihf EDIFACT DEC/EDI Inhouse file minvox_i.tx Example transmission file minvox_i.tx_smtp Example SMTP transmission systest.csh System tests shell script o3desado.dat ODETTE example application file e911inv1.dat EDIFACT example application file e911inv2.dat EDIFCAT example application file Table 11-3 Files in Client Subset Directory File Description H-40 HP-UX Client HP-UX Client Table 11-4 Files in Man subset /usr/opt/DEDI MAN400 Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this directory. /usr/man/man1 trade.1 Reference page for Command Line Interface /usr/man/man3 decedi_add_item_list.3 Reference page for Application Programming Interface decedi_free_item_list.3 Reference page for Application Programming Interface decedi_fetch.3 Reference page for Application Programming Interface decedi_post.3 Reference page for Application Programming Interface decedi_track.3 Reference page for Application Programming Interface decedi_free_track_list.3 Reference page for Application Programming Interface Appendix I RedHat Linux Client Kit Contents #tar -xvf decedi0400_linux_client.tar DEDI-4-0.i386.rpm Installation Log #rpm -i DEDI-4-0.i386.rpm ************************************************************** Compaq DEC/EDI Client Copyright Compaq Computer Corporation 1990, 2001. 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. Unpublished rights reserved under applicable copyright laws. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. ******************************************************* * * * Installing Compaq DEC/EDI Client and Manpages ... * * * ******************************************************* ******************************************************* * * * This Compaq DEC/EDI Client and Manpages installation* * will take approximately 1 minute to install, * * depending on your system and configuration * * * ******************************************************* I-42 RedHat Linux Client RedHat Linux Client *************************************************** * Compaq DEC/EDI Application Client and Man pages * * installed successfully * * * *************************************************** Configuration Log #/usr/bin/decedi_config.sh Configuring the TCP/IP Client-Server link Assigned port 5150 /etc/services for Compaq DEC/EDI Post-Fetch service. Assigned port 5151 /etc/services for Compaq DEC/EDI Track service. These port numbers must match those used on the remote Compaq DEC/EDI Server. If these numbers are different on the Compaq DEC/EDI Server then please modify /etc/services and update the port nunbers associated with decedi_csf and decedi_cst. ************************************************************** * To supply the server node information, create a file: * * /var/adm/decedi/decedi_servers.dat * * Use the template, /var/adm/decedi/decedi_servers.template. * * * * TCP/IP Configuration Complete * ************************************************************** Press to continue. Deinstallation Log #rpm -e DEDI-4-0 ************************************************** * * * Uninstalling Compaq DEC/EDI Application Client * * and Man pages........ * ************************************************** ********************************************* * * * Compaq DEC/EDI Application Client and Man * * pages uninstalled successfully * * * ********************************************* RedHat Linux Client I-43 REDHAT LINUX CLIENT Directory and File listing for Redhat Linux Client Directory File Description /usr/opt/DEDICLT400 Subdirectories where physicalfiles reside. The files which precede this entry are mainly softlinks to files under this directory. /var/adm/decedi decedi_servers.template This file is the template file which contains the template for defining the server listing. Copy this file to decedi_servers.dat and enter all your server entries in it. /usr/bin trade Command Line Interface /usr/bin decedi_config.sh Shell script for TCP/IP configuration /usr/doc decediv40.release_notes DEC/EDI Client Release Notes /usr/include decedi_api_common.h API common values and structures decedi_api_def.h decedi_api_msgs.h decedi_platforms.h API entry points API return values API platform specific /usr/lib/nls/msg/ en_US.ISO8859-1 decedi_api.cat Message Catalogue /usr/shlib libdecediapi.so Shareable link library /usr/examples/decedi api_exam.sh Client example compilation shell script api_exam.c Client programming example cli_exam.sh Client sample shell script init_fetch.sh Start import example I-44 RedHat Linux Client RedHat Linux Client crehdr_o.dat TRADACOMS example application file invoic_o.dat X12 eample application file minvox_o.dat EDIFACT example application file minvox_o.ihf EDIFACT DEC/EDI Inhouse file minvox_i.tx Example transmission file minvox_i.tx_smtp Example SMTP transmission systest.csh System tests shell script o3desado.dat ODETTE example application file e911inv1.dat EDIFACT example application file e911inv2.dat EDIFCAT example application file Directory File Description /usr/opt/DEDI MAN400 Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this directory. /usr/man/man1 trade.1 Reference page for Command Line Interface /usr/man/man3 decedi_add_item_list.3 Reference page for Application Programming Interface decedi_free_item_list.3 Reference page for Application Programming Interface decedi_fetch.3 Reference page for Application Programming Interface RedHat Linux Client I-45 REDHAT LINUX CLIENT decedi_post.3 Reference page for Application Programming Interface decedi_track.3 Reference page for Application Programming Interface decedi_free_track_list.3 Reference page for Application Programming Interface I-46 RedHat Linux Client RedHat Linux Client Appendix J Directory and File listing for Windows NT/2000 Client Directory File Description Compaq EDI Client Installation directory AtlEdiServer.dll decedi_servers.template COM component This file is the template file which contains the template for defining the server listing. Copy this file to decedi_servers.dat and enter all your server entries in it. crehdr_o.dat TRADACOMS example application file invoic_o.dat X12 eample application file minvox_o.dat EDIFACT example application file minvox_o.ihf EDIFACT DEC/EDI Inhouse file minvox_i.tx Example transmission file minvox_i.tx_smtp Example SMTP transmission o3desado.dat ODETTE example application file I-48 Directory and File listing for Windows NT/2000 Client Directory and File listing for Windows NT/2000 Client e911inv1.dat EDIFACT example application file e911inv2.dat EDIFCAT example application file Readme.txt Readme file Trade.exe Executable to launch GUI Trade.HLP Help file .\VB Samples Directory where the VB sample source files are available EdiClient.vbp VB project file PostFetch.frm VB form .\VC Samples Directory where the VC sample source files are available ediclientformfc.cpp VC source file ediclientformfc.dsw VC Project Work space ediclientformfc.dsp VC Project file Directory File Description Appendix K UNIX Installation -Directory and File Listing The tables in this section list the contents of DEC/EDI directories when the installation process is complete. 1. Client Subset-DIGITAL UNIX Directory File Description /usr/bin trade Command Line Interface /usr/doc DECEDI400.RELEASE DEC/EDI Release Notes- _NOTES ASCII and PostScript, DECEDI400_RELEASE respectively NOTES.PS /usr/include decedi_api API common values and common.h structures /usr/include decedi_api API entry points def.h /usr/include decedi_api API return values msgs.h /usr/include decedi API platform specific platforms.h /usr/lib/nls/msg/en decedi_api.cat Message Catalogue US.88591 /usr/shlib libdecediapi_ Shareable link tcp.so libraries libdecediapi.so I-50 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing /usr/opt/DEDICLT400/ Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this directory. /var/adm/decedi decedi_db_ora_ sql script file users.sql /var/adm/decedi decedi_servers.dat 2. Client Subset-HP-UX Directory File Description /etc setld Utility to install DEC/EDI Client software /usr/bin trade Command Line Interface /usr/bin decedi_cisd Client Information Server daemon (ACAS) /usr/bin decedi_imcd Client Information Server daemon (CORBA) /usr/bin decedi_imrd Client Registration daemon (CORBA) /usr/bin decedi_make Client Registration imc_obj executable (CORBA) /usr/doc decedi DEC/EDI Client Release client.release Notes notes.txt /usr/include decedi.crl ACAS DEC/EDI Class Definition /usr/include decedi_api API common values and common.h structures /usr/include decedi_api API entry points def.h /usr/include decedi_api API return values UNIX Installation - Directory and File Listing I-51 UNIX INSTALLATION - DIRECTORY AND FILE LISTING msgs.h /usr/include decedi API platform specific platforms.h /usr/lib/nls/msg/en decedi_api.cat Message Catalogue US.88591 /usr/lib libdecediapi.sl Shareable link library (currently installed) /usr/lib libdecediapi Shareable link libraries acas.sl or, for ACAS and CORBA libdecediapi corba.sl /usr/opt/DEDICLT310/ Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this directory. /var/adm/decedi decedi.co ACAS DEC/EDI User Context Object /var/adm/decedi decedi.cr ACAS DEC/EDI Class repository /var/adm/decedi decedisys.col ACAS DEC/EDI System Context Definition /var/adm/decedi decediusr.col ACAS DEC/EDI User Context Definition /var/adm/decedi decedi.idl CORBA DEC/EDI Interface Definition /var/adm/decedi decedi.iml_hpux CORBA DEC/EDI Interface Definition /var/adm/decedi decedi.mml CORBA DEC/EDI Interface Definition /var/adm/decedi decedi_imc CORBA DEC/EDI Interface obj.dat Definition /var/adm/decedi decedi_imc CORBA DEC/EDI Interface I-52 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing reg.dat Definition /var/adm/decedi decedi_imr CORBA DEC/EDI Interface reg.dat Definition /var/adm/decedi decedi_obb.co CORBA DEC/EDI Interface Definition /var/adm/decedi decedi_obb CORBA DEC/EDI Interface context.col Definition /var/adm/decedi decedi CORBA DEC/EDI Interface repository.ir Definition 3. Client Subset-Sun Solaris Directory File Description /etc setld Utility to install DEC/EDI Client software /usr/bin trade Command Line Interface /usr/bin decedi_imcd Client Information Server daemon (CORBA) /usr/bin decedi_imrd Client Registration daemon (CORBA) /usr/bin decedi_make Client Registration imc_obj executable (CORBA) /usr/doc decedi DEC/EDI Client Release client.release Notes notes.txt /usr/include decedi.crl ACAS DEC/EDI Class Definition /usr/include decedi_api API common values and common.h structures /usr/include decedi_api API entry points def.h /usr/include decedi_api API return values msgs.h UNIX Installation - Directory and File Listing I-53 UNIX INSTALLATION - DIRECTORY AND FILE LISTING /usr/include decedi API platform specific platforms.h /usr/lib/nls/msg/en decedi_api.cat Message Catalogue US.88591 /usr/lib libdecediapi.so Shareable link library /usr/opt/DEDICLT310/ Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this directory. /var/adm/decedi decedi.idl CORBA DEC/EDI Interface Definition /var/adm/decedi decedi.iml CORBA DEC/EDI Interface sunsol Definition /var/adm/decedi decedi.mml CORBA DEC/EDI Interface Definition /var/adm/decedi decedi_imc CORBA DEC/EDI Interface obj.dat Definition /var/adm/decedi decedi_imc CORBA DEC/EDI Interface reg.dat Definition /var/adm/decedi decedi_imr CORBA DEC/EDI Interface reg.dat Definition /var/adm/decedi decedi_obb.co CORBA DEC/EDI Interface Definition /var/adm/decedi decedi_obb CORBA DEC/EDI Interface context.col Definition /var/adm/decedi decedi CORBA DEC/EDI Interface repository.ir Definition 4. Reference Pages Subset DIGITAL UNIX Directory File Description I-54 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing /usr/share/man/man3 decedi_add Reference page for item_list.3 application programming interface /usr/share/man/man3 decedi_fetch.3 Reference page for application programming interface /usr/share/man/man3 decedi_free Reference page for item_list.3 application programming interface /usr/share/man/man3 decedi_free Reference page for track_list.3 application programming interface /usr/share/man/man3 decedi_post.3 Reference page for application programming interface /usr/share/man/man3 decedi_track.3 Reference page for application programming interface /usr/opt/DEDICLTMAN400/ Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this_directory. 5. Reference Pages_Subset-HP-UX Directory File Description /etc setld Utility to install DEC/EDI Client software /usr/man/man1 decedi.1 Reference page for Command Line Interface /usr/man/man3 decedi_add Reference page for item_list.3 application programming interface /usr/man/man3 decedi_fetch.3 Reference page for application programming UNIX Installation - Directory and File Listing I-55 UNIX INSTALLATION - DIRECTORY AND FILE LISTING interface /usr/man/man3 decedi_free Reference page for item_list.3 application programming interface /usr/man/man3 decedi_free Reference page for track_list.3 application programming interface /usr/man/man3 decedi_post.3 Reference page for application programming interface /usr/man/man3 decedi_track.3 Reference page for application programming interface /usr/opt/DEDIMAN310/ Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this_directory. 6. Reference Pages Subset Sun Solaris Directory File Description /etc setld Utility to install DEC/EDI Client software /usr/man/man1 decedi.1 Reference page for Command Line Interface /usr/man/man3 decedi_add Reference page for item_list.3 application programming interface /usr/man/man3 decedi_fetch.3 Reference page for application programming interface /usr/man/man3 decedi_free Reference page for item_list.3 application programming interface I-56 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing /usr/man/man3 decedi_free Reference page for track_list.3 application programming interface /usr/man/man3 decedi_post.3 Reference page for application programming interface /usr/man/man3 decedi_track.3 Reference page for application programming interface /usr/opt/DEDIMAN310/ Subdirectories where physical files reside. The files which precede this entry are mainly softlinks to files under this_directory. 7. User Documentation Files Directory File Description /usr/doc decedimsg210. Message Updates Release releas_notes Notes (Text) /usr/doc decedimsg210 Message Updates Release release_notes.ps Notes (PostScript) /usr/doc DECEDI400.release DEC/EDI Release Notes notes (Text) /usr/doc DECEDI400 DEC/EDI Release Notes release_notes.ps (PostScript) 8. Examples and Script Files Directory File Description /usr/examples api_exam.c Client programming example /decedi/client /usr/examples api_exam.sh Client example compilation /decedi/client shell script UNIX Installation - Directory and File Listing I-57 UNIX INSTALLATION - DIRECTORY AND FILE LISTING /usr/examples cli_exam.sh Client example shell /decedi/client script /usr/examples crehdr_o.dat TRADACOMS example /decedi/client application file /usr/examples e911inv1.dat EDIFACT example applica- /decedi/client tion file /usr/examples e911inv2.dat EDIFACT example applica- /decedi/client tion file /usr/examples init_fetch.sh Start import example /decedi/client /usr/examples invoic_o.dat X12 example application /decedi/client file /usr/examples minvox_i.tx Example transmission file /decedi/client /usr/examples minvox_i.tx_smtp Example SMTP transmission /decedi/client /usr/examples minvox_o.dat EDIFACT example applica- /decedi/client tion file /usr/examples minvox_o.ihf Example DEC/EDI Inhouse /decedi/client file /usr/examples o3desado.dat ODETTE example application /decedi/client file /usr/examples systest.csh System tests shell script /decedi/client /usr/examples decedi_msl Shared Lookups Example /decedi/mapper insert_inf.sql (Informix) /usr/examples decedi_msl Shared Lookups Example /decedi/mapper insert_ora.sql (Oracle 7) /usr/examples decedi_msl Shared Lookups Example /decedi/mapper insert_rdb.sql (Oralce Rdb) /usr/examples decedi Import/Export Loopback /decedi/server loopback.sh Script I-58 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing /usr/examples sqs_create.sqs SQL/Services creation /decedi/sqs example /usr/examples sqs_startup.sqs SQL/Services startup /decedi/sqs example /usr/examples sqs_shutdown.sqs SQL/Services shutdown /decedi/sqs example /var/adm/decedi decedi_geis 3780 Gateway GEIS TCL /data sndrcv.tcl script /var/adm/decedi decedi_tymnet 3780 Gateway BT-Tymnet TCL /data sndrcv.tcl script 9. Header Files Directory File Description /usr/include decedi_api API common values and common.h structures /usr/include decedi_api_def.h API entry points /usr/include decedi_api_msgs.h API return values /usr/include decedi API platform specific platforms.h 10.Message Catalog Directory File Description /usr/lib/nls/msg decedi_api.cat API Message Catalog /en_US.ISO8859-1 /usr/lib/nls/msg decedi Server Message Catalog /en_US.ISO8859-1 general.cat 11.System Images Directory File Description /usr/sbin decedi__delete Delete Shared Lookups lookups /usr/sbin decedi_alarm Alarm script UNIX Installation - Directory and File Listing I-59 UNIX INSTALLATION - DIRECTORY AND FILE LISTING /usr/sbin decedi_arch Secondary archive command /usr/sbin decedi_arch Archive script script /usr/sbin decedi_asd Archive server daemon /usr/sbin decedi_ccid Comms controller (incoming) /usr/sbin decedi_ccod Comms controller (outgoing) /usr/sbin decedi_checkdir Directory ownership checker /usr/sbin decedi_config Configration Utility /usr/sbin decedi_dlg Data label generator /usr/sbin decedi_dump_db Database dump utility /usr/sbin decedi_ecnvd EDIFACT converter (outgoing) /usr/sbin decedi_etfbd EDIFACT Transmission File Builder /usr/sbin decedi_etfsd EDIFACT Transmission File Splitter /usr/sbin decedi_etrnd EDIFACT translator (incoming) /usr/sbin decedi_impexpd Import/Export gateway daemon /usr/sbin decedi_look Error log viewer /usr/sbin decedi_manage Comms management utility /usr/sbin decedi_must Message Updates tool /usr/sbin decedi_orapwd Oracle 7 connection server daemon I-60 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing /usr/sbin decedi_pcc Profile cache constructor /usr/sbin decedi_pcv Profile cache viewer /usr/sbin decedi_recache Shared lookups recache lookups command /usr/sbin decedi_repair Repair utility /usr/sbin decedi_retr Retrieve command /usr/sbin decedi_retr Retrieve script script /usr/sbin decedi_setup Setup command /usr/sbin decedi_ssr_server Startup/shutdown server /usr/sbin decedi_start Startup command /usr/sbin decedi_start Component start agent component /usr/sbin decedi_stop Shutdown command /usr/sbin decedi_sysetup System setup /usr/sbin decedi_systart System startup /usr/sbin decedi_systop System shutdown /usr/sbin decedi_tcnvd TRADACOMS converter /usr/sbin decedi_ttrnd TRADACOMS translator /usr/sbin decedi_view Share lookups viewer lookups /usr/sbin decedi_xcnvd X12 converter /usr/sbin decedi_xtfbd X12 Transmission File Builder /usr/sbin decedi_xtrnd X12 translator /usr/sbin trade DEC/EDI_trade_command UNIX Installation - Directory and File Listing I-61 UNIX INSTALLATION - DIRECTORY AND FILE LISTING 12.Online Help Directory File Description /usr/share/man decedi_arch.8 man pages for secondary /man8 archive /usr/share/man decedi_dlg.8 man pages for data label /man8 generator /usr/share/man decedi_look.8 man pages for error log /man8 viewer /usr/share/man decedi_manage.8 man pages for comms /man8 management /usr/share/man decedi_must.8 man pages for message /man8 updates tool /usr/share/man decedi_pcv.8 man pages for profile /man8 cache viewer /usr/share/man decedi_repair.8 man pages for repair /man8 utilty /usr/share/man decedi_retr.8 man pages for retrieve /man8 /usr/share/man trade.1 man pages for trade /man1 command 13.Shared Libraries Directory File Description /usr/shlib libdecedi_db.so Database shareable object library /usr/shlib libdecedi_db_c.so Database common shareable object library /usr/shlib libdecedi_db Database Informix inf.so shareable object library /usr/shlib libdecedi_db Database Oracle 7 ora.so shareable object library /usr/shlib libdecedi Numbering schemes I-62 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing numshr.so shareable object library /usr/shlib libdecediapi.so API shareable object library /usr/shlib libdecediapi API shareable object _tcp.so library 14.DEC/EDI Configuration Files Directory File Description /var/adm/decedi/db decedi_db_inf Database creation script create_db.sql (Informix) /var/adm/decedi/db decedi_db_inf Schema SQL create_schema.sql script(Informix) /var/adm/decedi/db decedi_db_inf User management script users.sql /var/adm/decedi/db decedi_db_ora Database creation script create_db.sql (Oracle 7) /var/adm/decedi/db decedi_db_ora Schema SQL script(Oracle create_schema.sql 7) /var/adm/decedi decedi_migrate Database migration script db_from_ database type from an old .sql latest version. Database type can be: o ora-Oracle7 /var/adm/decedi/db decedi_migrate Database migration script ora_v32_db.sql 15.EDI and Message Definitions Directory File Description /var/adm/decedi decedi_edif EDI Message and Directory /impdef 1.impdef definition /var/adm/decedi decedi EDI Message and Directory UNIX Installation - Directory and File Listing I-63 UNIX INSTALLATION - DIRECTORY AND FILE LISTING /impdef definition for the .impdef specfied EDI standard and its versions. Standard can be one of: o edif-EDIFACT o odet-ODETTE o trad-TRADACOMS o x12 -X12 o tdcc-TDCC /var/adm/decedi decedi_edif EDI Message and Directory /impdef 902.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef 911.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef 912.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef 921.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef d93a.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef d94b.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef d95a.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef d95b.impdef definition /var/adm/decedi decedi_edif EDI Message and Directory /impdef s93a.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 002001.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 002002.impdef definition I-64 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 002003.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 002040.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003010.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003020.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003021.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003022.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003030.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003031.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003032.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003040.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003041.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003050.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003051.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003052.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003060.impdef definition /var/adm/decedi decedi_x12 EDI Message and Directory /impdef 003061.impdef definition UNIX Installation - Directory and File Listing I-65 UNIX INSTALLATION - DIRECTORY AND FILE LISTING /var/adm/decedi decedi_x12_ EDI Message and Directory /impdef 004010.impdef definition /var/adm/decedi decedi_x12_ EDI Message and Directory /impdef 004011.impdef definition /var/adm/decedi decedi_x12_ EDI Message and Directory /impdef 004012.impdef definition /var/adm/decedi decedi_x12_ EDI Message and Directory /impdef 004020.impdef definition /var/adm/decedi decedi_x12_ EDI Message and Directory /impdef 004021.impdef definition /var/adm/decedi decedi_x12_ EDI Message and Directory /impdef 004030.impdef definition 16.New Server Files in an Oracle7 Setup Directory File Description $ORACLE_HOME/dbs initdecedidb.ora /var/adm/decedi decedi_db_ora create_db.sql /var/adm/decedi decedi_db_ora create_schema.sql /var/adm/decedi decedi_db_ora users.sql /var/adm/decedi decedi_migrate db_v314_v31ssb ora.sql decedidb decedi_ctrl1.dbf decedidb decedi_ctrl2.dbf decedidb decedi_ctrl3.dbf decedidb decedi_log1.dbf decedidb decedi_log2.dbf decedidb decedi_log3.dbf I-66 UNIX Installation - Directory and File Listing UNIX Installation - Directory and File Listing decedidb decedi_mdata.dbf decedidb decedi_mindex.dbf decedidb decedi_mtemp.dbf decedidb decedi_rbs.dbf decedidb decedi_system.dbf /etc listener.ora Default Oracle network template /etc tnsnames.ora Default Oracle network template /etc tnsnav.ora Default Oracle network template Appendix L OpenVMS Installation -Directory and File Listing The tables in this section list the contents of DEC/EDI directories when the installation process is complete. 1. DECEDI$TOP:[000000] IDENTIFIER=[DECEDI],OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+ DELETE+CONTROL IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,OPTIONS=DEFAULT,ACCESS=READ+WRITE +EXECUTE IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,OPTIONS=DEFAULT,ACCESS=READ+WR ITE+EXECUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELE TE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE 3780PLUS.DIR;1 1 [DECEDI] (RWED,RWED,,) ARCHIVE_DB.DIR;1 2 [DECEDI] (RWED,RWED,,) ARCHREPORTS.DIR;1 2 [DECEDI] (RWED,RWED,,) AUDIT_DB.DIR;1 4 [DECEDI] (RWED,RWED,,) BACKUP.DIR;1 1 [DECEDI] (RWED,RWED,,) CACHE.DIR;1 1 [DECEDI] (RWED,RWED,,) CVP.DIR;1 1 [DECEDI] (RWED,RWED,,) DATA.DIR;1 27 [DECEDI] (RWED,RWED,,) DS_SCRATCH.DIR;1 1 [DECEDI] (RWED,RWED,,) ERROR.DIR;1 1 [DECEDI] (RWED,RWED,,) IMPDEF.DIR;1 1 [DECEDI] (RWED,RWED,R,R) MAP_TABLES.DIR;1 1 [DECEDI] (RWED,RWED,,) MESSAGE_UPDATES.DIR;1 1 [DECEDI] (RWED,RWED,,) STORE_1.DIR;1 6 [DECEDI] (RWED,RWED,,) STORE_10.DIR;1 5 [DECEDI] (RWED,RWED,,) STORE_11.DIR;1 8 [DECEDI] (RWED,RWED,,) STORE_12.DIR;1 5 [DECEDI] (RWED,RWED,,) STORE_13.DIR;1 9 [DECEDI] (RWED,RWED,,) STORE_14.DIR;1 5 [DECEDI] (RWED,RWED,,) J-68 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing STORE_15.DIR;1 8 [DECEDI] (RWED,RWED,,) STORE_16.DIR;1 5 [DECEDI] (RWED,RWED,,) STORE_17.DIR;1 8 [DECEDI] (RWED,RWED,,) STORE_18.DIR;1 4 [DECEDI] (RWED,RWED,,) STORE_19.DIR;1 8 [DECEDI] (RWED,RWED,,) STORE_2.DIR;1 9 [DECEDI] (RWED,RWED,,) STORE_20.DIR;1 5 [DECEDI] (RWED,RWED,,) STORE_3.DIR;1 9 [DECEDI] (RWED,RWED,,) STORE_4.DIR;1 8 [DECEDI] (RWED,RWED,,) STORE_5.DIR;1 8 [DECEDI] (RWED,RWED,,) STORE_6.DIR;1 9 [DECEDI] (RWED,RWED,,) STORE_7.DIR;1 8 [DECEDI] (RWED,RWED,,) STORE_8.DIR;1 5 [DECEDI] (RWED,RWED,,) STORE_9.DIR;1 7 [DECEDI] (RWED,RWED,,) TEMP.DIR;1 1 [DECEDI] (RWED,RWED,,) TOOLS.DIR;1 6 [DECEDI] (RWED,RWED,,) VANREPORTS.DIR;1 1 [DECEDI] (RWED,RWED,,) 2. DECEDI$TOP:[ARCHIVE_DB] DECEDI$ARCHIVE_DB.RDA;2 1724 [DECEDI] (RWED,RW,,) DECEDI$ARCHIVE_DB.RDB;2 124 [DECEDI] (RWED,RW,,) DECEDI$ARCHIVE_DB.SNP;2 202 [DECEDI] (RWED,RW,,) DECEDI$ARCHIVE_DB_CHF.RDA;2 2414 [DECEDI] (RWED,RW,,) DECEDI$ARCHIVE_DB_CHF.SNP;2 202 [DECEDI] (RWED,RW,,) DECEDI$ARCHIVE_DB_CLF.RDA;2 3224 [DECEDI] (RWED,RW,,) DECEDI$ARCHIVE_DB_CLF.SNP;2 808 [DECEDI] (RWED,RW,,) DECEDI$ARCHIVE_DB_MISC_ 404 [DECEDI] (RWED,RW,,) COMS_1.RDA;2 DECEDI$ARCHIVE_DB_MISC_ 202 [DECEDI] (RWED,RW,,) COMS_1.SNP;2 DECEDI$ARCHIVE_DB_MISC_ 404 [DECEDI] (RWED,RW,,) TRANS_1.RDA;2 DECEDI$ARCHIVE_DB_MISC_ 202 [DECEDI] (RWED,RW,,) TRANS_1.SNP;2 DECEDI$ARCHIVE_DB_ 2012 [DECEDI] (RWED,RW,,) THF.RDA;2 DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,RW,,) THF.SNP;2 DECEDI$ARCHIVE_DB_ 2416 [DECEDI] (RWED,RW,,) TLF.RDA;2 DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,RW,,) TLF.SNP;2 3. DECEDI$TOP:[AUDIT_DB] IDENTIFIER=[DECEDI], ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE OpenVMS Installation - Directory and File Listing J-69 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELE TE IDENTIFIER=[*,*],ACCESS=NONE DECEDI$AUDIT_DB.RDB;2 336 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_CHF.RDA;2 2414 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_CHF.SNP;2 202 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_CLF.RDA;2 3224 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_CLF.SNP;2 808 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,RW,,) AVAIL.RDA;2 DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,RW,,) AVAIL.SNP;2 DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,RW,,) COMS_1.RDA;2 DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,RW,,) COMS_1.SNP;2 DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,RW,,) COMS_2.RDA;2 DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,RW,,) COMS_2.SNP;2 DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,RW,,) TRANS_1.RDA;2 DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,RW,,) TRANS_1.SNP;2 DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,RW,,) TRANS_2.RDA;2 DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,RW,,) TRANS_2.SNP;2 DECEDI$AUDIT_DB_SYS.RDA;2 3206 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_SYS.SNP;2 202 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_THF.RDA;2 2012 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_THF.SNP;2 202 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_TLF.RDA;2 2416 [DECEDI] (RWED,RW,,) DECEDI$AUDIT_DB_TLF.SNP;2 404 [DECEDI] (RWED,RW,,) DECEDI.ERR;1 1 [DECEDI] (RWED,RE,,) FBR$AUDIT_AREA.RDA;2 8444 [DECEDI] (RWED,RW,,) FBR$AUDIT_AREA.SNP;2 404 [DECEDI] (RWED,RW,,) FBR$RUN_ID.DAT;1 1 [DECEDI] (RWED,RWED,RWED,RE) 4. DECEDI$TOP:[CVP] IDENTIFIER=[DECEDI],OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+ DELETE+CONTROL IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,OPTIONS=DEFAULT,ACCESS=READ+WRITE +EXECUTE IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE J-70 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing IDENTIFIER=DECEDI$ADMINISTRATOR,OPTIONS=DEFAULT,ACCESS=READ+WR ITE+EXE CUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELE TE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE DECEDI$CVP.COM;4 55 [DECEDI] (RWED,RWED,RE,RE) DECEDI$CVP_COMPARE.COM;4 22 [DECEDI] (RWED,RWED,RE,RE) DECEDI$CVP_FETCH.EXE;4 1860 [DECEDI] (RWED,RWED,RE,RE) DECEDI$CVP_LOOPBACK.COM;4 11 [DECEDI] (RWED,RWED,RE,RE) DECEDI$CVP_RUN_FETCH.COM;4 5 [DECEDI] (RWED,RWED,RE,RE) DECEDI$CVP_SEND.DAT;4 1 [DECEDI] (RWED,RWED,RE,RE) DECEDI$CVP_SEND.EXE;4 1930 [DECEDI] (RWED,RWED,RE,RE) IMPEXP.DIR;1 50 [DECEDI] (RWED,RWED,,) WORK.DIR;1 1 [DECEDI] (RWED,RWED,,) 5. DECEDI$TOP:[DATA] IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELE TE IDENTIFIER=[*,*],ACCESS=NONE A0901.DAT;1 30 [DECEDI] (RWED,RWED,RE,) A0CTRL.DAT;1 15 [DECEDI] (RWED,RWED,RE,) B0901.DAT;1 42 [DECEDI] (RWED,RWED,RE,) B0CTRL.DAT;1 42 [DECEDI] (RWED,RWED,RE,) D0901.DAT;3 15 [DECEDI] (RWED,RE,,) DECEDI$3780_ 1 [DECEDI] (RWED,RWED,RE,) JMEKON.COM;77 DECEDI$ACCESS.DAT;1 15 [DECEDI] (RWED,RWED,RE,) DECEDI$ACCESS.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$ACCESS_GROUP_ 2 [DECEDI] (RWED,RWED,RE,RE) DESC.FDL;4 DECEDI$ACCESS_GROUP_ 3 [DECEDI] (RWED,RWED,RE,RE) MEMBERS.FDL;4 DECEDI$AGREEMENTS_ 132 [DECEDI] (RWED,RWED,RE,) DETAIL_TABLE.DAT;1 DECEDI$AGREEMENTS_ 3 [DECEDI] (RWED,RWED,RE,RE) DETAIL_TABLE.FDL;4 DECEDI$AGREEMENTS_ 384 [DECEDI] (RWED,RWED,RE,) TABLE.DAT;1 DECEDI$AGREEMENTS_ 4 [DECEDI] (RWED,RWED,RE,RE) TABLE.FDL;4 DECEDI$ARCH_SRV_PAR.DAT;1 9 [DECEDI] (RWED,RWED,RE,) DECEDI$AS_2_JMEKON.OUT;1 2 [DECEDI] (RWED,RE,,) DECEDI$AS_3_JMEKON.COM;2 1 [DECEDI] (RWED,RWED,RE,) OpenVMS Installation - Directory and File Listing J-71 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING DECEDI$CC_1_JMEKON.OUT;67 2 [DECEDI] (RWED,RWED,RE,) DECEDI$CLIENT_ 51 [DECEDI] (RWED,RWED,RE,) APPLICATIONS.DAT;1 DECEDI$CLIENT_ 3 [DECEDI] (RWED,RWED,RE,RE) APPLICATIONS.FDL;4 DECEDI$CNV_E_1_ 2 [DECEDI] (RWED,RWED,RE,) JMEKON.OUT;71 DECEDI$CNV_E_2_ 1 [DECEDI] (RWED,RWED,RE,) JMEKON.COM;1 DECEDI$CNV_E_3_ 1 [DECEDI] (RWED,RWED,RE,) JMEKON.COM;1 DECEDI$CONFIG_ 0 [DECEDI] (RWED,RWED,RE,RE) LOGICALS.DAT;1 DECEDI$CONTROL_NUM.DAT;1 9 [DECEDI] (RWED,RWED,,) DECEDI$CONTROL_NUM.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$CSF_1_ 1 [DECEDI] (RWED,RWED,RE,) JMEKON.COM;193 DECEDI$CSF_1_ 2 [DECEDI] (RWED,RWED,RE,) JMEKON.OUT;88 DECEDI$CSF_2_JMEKON. 1 [DECEDI] (RWED,RWED,RE,) COM;10 DECEDI$CSF_2_JMEKON.OUT;8 2 [DECEDI] (RWED,RE,,) DECEDI$CSF_3_JMEKON.COM;4 1 [DECEDI] (RE,RE,,) DECEDI$CSF_3_JMEKON.OUT;4 2 [DECEDI] (RWED,RE,,) DECEDI$CSG_1_JMEKON. 1 [DECEDI] (RWED,RWED,RE,) COM;163 DECEDI$CSG_1_JMEKON.OUT;71 2 [DECEDI] (RWED,RWED,RE,) DECEDI$CSG_2_JMEKON.COM;1 1 [DECEDI] (RWED,RE,,) DECEDI$CSG_2_JMEKON.OUT;1 2 [DECEDI] (RWED,RE,,) DECEDI$CST_1_JMEKON. 1 [DECEDI] (RWED,RWED,RE,) COM;159 DECEDI$CST_1_JMEKON.OUT;67 2 [DECEDI] (RWED,RWED,RE,) DECEDI$DATA_DESC.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DATA_LABEL.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DATA_LABEL_ 327 [DECEDI] (RWED,RWED,RE,RE) EDIF_901.DAT;2 DECEDI$DATA_LABEL_ 219 [DECEDI] (RWED,RWED,RE,RE) EDIF_CTRL.DAT;3 DECEDI$DATA_SET_ID.DAT;5 4 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DOCUMENT_TABLE 2 [DECEDI] (RWED,RWED,RE,RE) .FDL;4 DECEDI$DOC_AREA_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$DOC_DESC_TABLE. 48 [DECEDI] (RWED,RWED,RE,) DAT;1 DECEDI$DOC_DESC_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DS_JMEKON.COM;190 1 [DECEDI] (RWED,RWED,RE,) J-72 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing DECEDI$DS_JMEKON.OUT;72 2 [DECEDI] (RWED,RWED,RE,) DECEDI$ELEMENT_CODES. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$ELEMENT_CODES_ 324 [DECEDI] (RWED,RWED,RE,) EDIF_901.DAT;1 DECEDI$ELEMENT_CODES_ 168 [DECEDI] (RWED,RWED,RE,) EDIF_CTRL.DAT;1 DECEDI$ELEMENT_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$FA_MAPPING_ 3 [DECEDI] (RWED,RWED,RE,RE) TABLE.FDL;4 DECEDI$FORMAT_TABLE. 33 [DECEDI] (RWED,RWED,RE,) DAT;1 DECEDI$FORMAT_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$IMPEXP_JMEKON. 1 [DECEDI] (RWED,RWED,RE,) COM;165 DECEDI$IMPEXP_JMEKON. 2 [DECEDI] (RWED,RWED,RE,) OUT;67 DECEDI$INTERCHANGE_ 9 [DECEDI] (RWED,RWED,RE,) ARCHIVE.JNL;1 DECEDI$IVP_CHECKSUMS. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$JOB_DESC.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$MAPPER_SHARED_ 3 [DECEDI] (RWED,RWED,RE,RE) LOOKUPS.FDL;4 DECEDI$MGT_CONFIG.DAT;1 114 [DECEDI] (RWED,RWED,RE,) DECEDI$MGT_CONFIG.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$NODE_ 324 [DECEDI] (RWED,RWED,RE,) CONFIGURATION.DAT;1 DECEDI$NODE_ 2 [DECEDI] (RWED,RWED,RE,RE) CONFIGURATION.FDL;25 DECEDI$NODE_ 24 [DECEDI] (RWED,RWED,RE,) CONFIGURATION_DETAILS.DAT;1 DECEDI$NODE_ 2 [DECEDI] (RWED,RWED,RE,RE) CONFIGURATION_DETAILS.FDL;4 DECEDI$PARAMETERS_FILE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$PARTNER_TABLE. 144 [DECEDI] (RWED,RWED,RE,) DAT;1 DECEDI$PARTNER_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$PS_JMEKON.COM;166 1 [DECEDI] (RWED,RWED,RE,) DECEDI$PS_JMEKON.OUT;67 2 [DECEDI] (RWED,RWED,RE,) DECEDI$P_DOCUMENT_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$P_DOC_AREA_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) OpenVMS Installation - Directory and File Listing J-73 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING FDL;4 DECEDI$P_DOC_AREA_TABLE_ 3 [DECEDI] (RWED,RE,,) EDIF_901.DAT;3 DECEDI$P_DOC_DESC_TABLE. 105 [DECEDI] (RWED,RWED,RE,) DAT;1 DECEDI$P_DOC_DESC_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$P_ELEMENT_CODES. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$P_ELEMENT_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$P_SEGMENT_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$P_SEG_DESC.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$P_SUB_ELE_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$QUALIFIER_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$RESERVED_DATA_ 3 [DECEDI] (RWED,RWED,RE,RE) LABELS.FDL;4 DECEDI$RESERVED_SEG_ 2 [DECEDI] (RWED,RWED,RE,RE) TABLE.FDL;4 DECEDI$RES_DATA_LABELS_ 234 [DECEDI] (RWED,RWED,RE,RE) EDIF.DAT;4 DECEDI$RES_DATA_LABELS_ 234 [DECEDI] (RWED,RWED,RE,RE) ODET.DAT;4 DECEDI$RES_DATA_LABELS_ 234 [DECEDI] (RWED,RWED,RE,RE) TDCC.DAT;4 DECEDI$RES_DATA_LABELS_ 234 [DECEDI] (RWED,RWED,RE,RE) TRAD.DAT;4 DECEDI$RES_DATA_LABELS_ 11 [DECEDI] (RWED,RWED,RE,RE) X12.DAT;4 DECEDI$RES_SEG_TABLE_ 36 [DECEDI] (RWED,RWED,RE,RE) EDIF.DAT;4 DECEDI$RES_SEG_TABLE_ 36 [DECEDI] (RWED,RWED,RE,RE) ODET.DAT;4 DECEDI$RES_SEG_TABLE_ 36 [DECEDI] (RWED,RWED,RE,RE) TDCC.DAT;4 DECEDI$RES_SEG_TABLE_ 36 [DECEDI] (RWED,RWED,RE,RE) TRAD.DAT;4 DECEDI$RES_SEG_TABLE_ 36 [DECEDI] (RWED,RWED,RE,RE) X12.DAT;4 DECEDI$SCHEDULE.DAT;4 135 [DECEDI] (RWED,RWED,RE,RE) DECEDI$SCHEDULE.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$SCR_P_GEIS_01_ 4 [DECEDI] (RWED,RWED,RE,RE) LOGIN.DAT;4 DECEDI$SCR_P_GEIS_02_ 5 [DECEDI] (RWED,RWED,RE,RE) PRODUCTION.DAT;4 J-74 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing DECEDI$SCR_P_GEIS_03_ 2 [DECEDI] (RWED,RWED,RE,RE) SENDER_STATUS.DAT;4 DECEDI$SCR_P_GEIS_04_ 2 [DECEDI] (RWED,RWED,RE,RE) RECEIVER_STATUS.DAT;4 DECEDI$SCR_P_GEIS_05_ 2 [DECEDI] (RWED,RWED,RE,RE) UNRETRIEVED_DOC.DAT;4 DECEDI$SCR_P_GEIS_06_ 2 [DECEDI] (RWED,RWED,RE,RE) SENDER_ERROR.DAT;4 DECEDI$SCR_P_GEIS_07_ 2 [DECEDI] (RWED,RWED,RE,RE) SENDER_SUMMARY.DAT;4 DECEDI$SCR_P_GEIS_08_ 2 [DECEDI] (RWED,RWED,RE,RE) ERROR_RECOVERY.DAT;4 DECEDI$SCR_P_GEIS_09_ 2 [DECEDI] (RWED,RWED,RE,RE) SENDER_DOC.DAT;4 DECEDI$SCR_P_GEIS_10_ 23 [DECEDI] (RWED,RWED,RE,RE) LOGOUT.DAT;4 DECEDI$SCR_P_MCDD_01_ 3 [DECEDI] (RWED,RWED,RE,RE) LOGIN.DAT;4 DECEDI$SCR_P_MCDD_02_ 3 [DECEDI] (RWED,RWED,RE,RE) PRODUCTION.DAT;4 DECEDI$SCR_P_MCDD_03_ 22 [DECEDI] (RWED,RWED,RE,RE) LOGOUT.DAT;4 DECEDI$SEGMENT_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$SEGMENT_TABLE_ 96 [DECEDI] (RWED,RWED,RE,) EDIF_901.DAT;1 DECEDI$SEGMENT_TABLE_ 96 [DECEDI] (RWED,RWED,RE,) EDIF_CTRL.DAT;1 DECEDI$SEG_DESC.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$SEG_DESC_EDIF_ 12 [DECEDI] (RWED,RWED,RE,) 901.DAT;1 DECEDI$SEG_DESC_EDIF_ 9 [DECEDI] (RWED,RWED,RE,) CTRL.DAT;1 DECEDI$SEQ_HISTORY.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$SITE_ROUTING.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$SITE_TABLE.DAT;1 24 [DECEDI] (RWED,RWED,RE,) DECEDI$SITE_TABLE.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$SRV_ 582 [DECEDI] (RWED,RWED,RE,RE) CONFIGURATION.DAT;4 DECEDI$SRV_CONFIGURATION. 13 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$SRV_CONFIG_DEFS. 612 [DECEDI] (RWED,RWED,RE,RE) DAT;4 DECEDI$SRV_PARAMETER. 27 [DECEDI] (RWED,RWED,RE,RE) DAT;4 DECEDI$SRV_PARAMETER. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$SUB_ELE_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) OpenVMS Installation - Directory and File Listing J-75 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING FDL;4 DECEDI$SUB_ELE_TABLE_ 33 [DECEDI] (RWED,RWED,RE,) EDIF_901.DAT;1 DECEDI$SUB_ELE_TABLE_ 33 [DECEDI] (RWED,RWED,RE,) EDIF_CTRL.DAT;1 DECEDI$SYSTEM_PARAMETERS. 9 [DECEDI] (RWED,RWED,RE,) DAT;1 DECEDI$SYSTEM_PARAMETERS. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$SYSTEM_VERSIONS. 15 [DECEDI] (RWED,RWED,RE,RE) DAT;4 DECEDI$SYSTEM_VERSIONS. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$TEL_TRANSFER.FDL;4 2 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TFB_1_JMEKON. 1 [DECEDI] (RWED,RWED,RE,) COM;112 DECEDI$TFB_1_JMEKON. 5 [DECEDI] (RWED,RWED,RE,) OUT;14 DECEDI$TFS_2_JMEKON.COM;1 1 [DECEDI] (RWED,RWED,RE,) DECEDI$TFS_3_JMEKON.COM;1 1 [DECEDI] (RWED,RWED,RE,) DECEDI$TP_CODE_TRANS.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TP_DATA_LABEL.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TP_DOCUMENT_TABLE 2 [DECEDI] (RWED,RWED,RE,RE) .FDL;4 DECEDI$TP_DOC_AREA_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$TP_ELEMENT_TABLE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$TP_QUAL_TABLE.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TP_SEGMENT_TABLE. 3 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$TP_STD_VERS.FDL;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TRANSMISSION_FILE_ 15 [DECEDI] (RWED,RWED,RE,) DETAILS.DAT;1 DECEDI$TRANSMISSION_FILE_ 2 [DECEDI] (RWED,RWED,RE,RE) DETAILS.FDL;4 DECEDI$USER_ACCESS_FILE. 2 [DECEDI] (RWED,RWED,RE,RE) FDL;4 DECEDI$VAN_APPEND_ 4 [DECEDI] (RWED,RWED,RE,RE) SENDFILES.COM;4 DECEDI_CSF.GS;165 49 [DECEDI] (RWED,RWED,RE,) DECEDI_CSG.GS;166 49 [DECEDI] (RWED,RWED,RE,) DECEDI_CST.GS;166 49 [DECEDI] (RWED,RWED,RE,) DECEDI_CS_TRACE.GS;165 1 [DECEDI] (RWED,RWED,RE,) DECEDI_SERVERS.DAT;7 4 [DECEDI] (RWED,RWED,RE,) DECEDI_SERVERS.TEMPLATE;4 4 [DECEDI] (RWED,RWED,RE,RE) FBR$RUN_ID.DAT;2 1 [DECEDI] (RWED,RE,,) I0901.DAT;2 168 [DECEDI] (RWED,RWED,RE,) J-76 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing I0CTRL.DAT;3 168 [DECEDI] (RWED,RE,,) 6. DECEDI$TOP:[TOOLS] AUDIT.EXTRACT;1 93 [DECEDI] (RWED,RE,,) BALKI.OUT;1 168 [DECEDI] (RWED,RWED,RE,RE) DECEDI$17OCT200122473285. 93 [DECEDI] (RWED,RE,,) EXTRACT;1 DECEDI$ARCHIVE_DATABASE. 36 [DECEDI] (RWED,RWED,RE,RE) SQL;4 DECEDI$ARCHIVE_DB_CREATE. 925 [DECEDI] (RWED,RWED,RE,RE) EXE;4 DECEDI$AUDIT_DATABASE. 50 [DECEDI] (RWED,RWED,RE,RE) SQL;4 DECEDI$AUDIT_EXTRACT. 265 [DECEDI] (RWED,RWED,RE,RE) COM;4 DECEDI$AUDIT_EXTRACT. 2305 [DECEDI] (RWED,RWED,RE,RE) EXE;4 DECEDI$AUDIT_EXTRACT_ 3 [DECEDI] (RWED,RWED,RE,RE) TABLES.DAT;4 DECEDI$AUDIT_USER_REF_ 1 [DECEDI] (RWED,RWED,RE,RE) TABLES.DAT;4 DECEDI$CONFIGURE_CLIENT_ 7 [DECEDI] (RWED,RWED,RE,RE) SERVER.COM;4 DECEDI$CONVERT_DOC.EXE;4 13 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DB_CREATE.EXE;4 959 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG.COM;4 5 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG.EXE;4 131 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_COPY.COM;4 11 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_DOC.PS;4 175 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_DOC.TXT;4 72 [DECEDI] (RWED,RWED,RE,RE) DECEDI$EDIFACT_CONTRL.PS;4 77 [DECEDI] (RWED,RWED,RE,RE) DECEDI$EDIFACT_CONTRL.TXT;4 19 [DECEDI] (RWED,RWED,RE,RE) DECEDI$FBRMSG.EXE;1 6 [DECEDI] (RWED,RWED,RE,RE) DECEDI$FIXUP_IVP.COM;4 78 [DECEDI] (RWED,RWED,RE,RE) DECEDI$LINK_TUNE_DB.COM;4 3 [DECEDI] (RWED,RWED,RE,RE) DECEDI$LINK_TUNE_SYINFO. 3 [DECEDI] (RWED,RWED,RE,RE) COM;4 DECEDI$MESSAGE_UPDATES. 439 [DECEDI] (RWED,RWED,RE,RE) EXE;5 DECEDI$PCV.EXE;4 84 [DECEDI] (RWED,RWED,RE,RE) DECEDI$PCV.PS;4 77 [DECEDI] (RWED,RWED,RE,RE) DECEDI$PCV.TXT;4 21 [DECEDI] (RWED,RWED,RE,RE) DECEDI$PS_CONTROL.COM;4 5 [DECEDI] (RWED,RWED,RE,RE) DECEDI$PS_CONTROL.PS;4 60 [DECEDI] (RWED,RWED,RE,RE) DECEDI$PS_CONTROL.TXT;4 10 [DECEDI] (RWED,RWED,RE,RE) DECEDI$RECOVER.COM;4 7 [DECEDI] (RWED,RWED,RE,RE) DECEDI$RECOVER.EXE;4 2005 [DECEDI] (RWED,RWED,RE,RE) OpenVMS Installation - Directory and File Listing J-77 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING DECEDI$TAILOR.COM;4 138 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL.EXE;4 278 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL_DOC.PS;4 270 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL_DOC.TXT;4 127 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.EXE;7 378 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.OBJ;4 241 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.PS;4 335 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.TXT;4 165 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_SYINFO.EXE;5 11 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_SYINFO.OBJ;4 19 [DECEDI] (RWED,RWED,RE,RE) DECEDI$VIEW_LOOKUPS.EXE;4 161 [DECEDI] (RWED,RWED,RE,RE) DECEDI$X25_FORCE_PWD.EXE;4 60 [DECEDI] (RWED,RWED,RE,RE) DECEDI$X25_MIGRATE.EXE;4 1678 [DECEDI] (RWED,RWED,RE,RE) DECEDI.ERR;1 1 [DECEDI] (RWED,RWED,RE,) DECEDI_MUS.LOG;1 1 [DECEDI] (RWED,RWED,RE,) DECEDI__RECOVER_AVAIL_ 1 [DECEDI] (RWED,RWED,RE,RE) TABLE.COM;1 DECEDI__RECOVER_AVAIL_ 1 [DECEDI] (RWED,RWED,RE,RE) TABLE.SQL;1 DOC_DEF_V32.DAT;1 168 [DECEDI] (RWED,RE,,) FBEXPORT.EXE;4 178 [DECEDI] (RWED,RWED,RE,RE) FBEXPORT_USER_GUIDE.PS;4 160 [DECEDI] (RWED,RWED,RE,RE) FBEXPORT_USER_GUIDE.TXT;4 69 [DECEDI] (RWED,RWED,RE,RE) MESSAGE.EXE;1 8 [DECEDI] (RWED,RE,,) MINVOX_OUT.FBI;1 1 [DECEDI] (RWED,RE,,) MINVOX_OUT.FBO;1 2 [DECEDI] (RWED,RWED,RE,) MINVOX_OUT.TMP;1 2 [DECEDI] (RWED,RE,,) 7. SYS$COMMON:[SYS$STARTUP] DECEDI$CLEO_SHUTDOWN.COM;2 4 [SYSTEM] (RWED,RWED,RWED,) DECEDI$CLEO_STARTUP.COM;2 4 [SYSTEM] (RWED,RWED,RWED,) DECEDI$SHUTDOWN.COM;18 44 [SYSTEM] (RWED,RWED,RWED,) DECEDI$STARTUP.COM;13 63 [SYSTEM] (RWED,RWED,RWED,) DECEDI$SYSHUTDOWN.COM;2 3 [SYSTEM] (RWED,RWED,RWED,) DECEDI$SYSTARTUP.COM;2 3 [SYSTEM] (RWED,RWED,RWED,) 8. SYS$COMMON:[SYSEXE] DECEDI$3780.EXE;4 2207 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$ARCHIVE_SERVER. 1987 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI$CHECK_FILES.COM;4 7 [SYSTEM] (RWED,RWED,RWED,) DECEDI$CLI.EXE;4 70 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CNV_EDIFACT.EXE;4 2092 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CNV_TRADACOMS. 2209 [SYSTEM] (RWED,RWED,RE,RE) EXE;3 DECEDI$CNV_X12.EXE;4 2996 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$COMMS_CONTROL. 1982 [SYSTEM] (RWED,RWED,RE,RE) J-78 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing EXE;4 DECEDI$CONTROL_NUM_USER_ 44 [SYSTEM] (RWED,RWED,RE,RE) DEFINED.EXE;4 DECEDI$CSF.EXE;6 2992 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CSG.EXE;4 3564 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CST.EXE;4 2069 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$DATA_SERVER. 404 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI$DELETE_LOOKUPS. 121 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI$IMPEXP.EXE;5 1933 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$INTERCHANGE. 23511 [SYSTEM] (RWED,RWED,RE,RE) EXE;12 DECEDI$INTERCHANGE. 23314 [SYSTEM] (RWED,RWED,RE,RE) EXE_NITRO2;1 DECEDI$LOGIN.COM;4 5 [SYSTEM] (RWED,RWED,E,E) DECEDI$LOOK.COM;4 5 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$LOOK.EVE;4 1 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$OFTP.EXE;4 2123 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$PEDI.EXE;4 2330 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$PS.EXE;4 170 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$PS_CONTROL. 100 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI$RECACHE_ 161 [SYSTEM] (RWED,RWED,RE,RE) LOOKUPS.EXE;4 DECEDI$SERVICES.EXE;4 88 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SHUTDOWN.EXE;4 160 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$STARTUP.EXE;4 3197 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TFB.EXE;4 2073 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TFB_X12.EXE;4 2765 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TFS.EXE;4 2123 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TRNS_EDIFACT. 2222 [SYSTEM] (RWED,RWED,RE,RE) EXE;6 DECEDI$TRNS_ 2156 [SYSTEM] (RWED,RWED,RE,RE) TRADACOMS.EXE;3 DECEDI$TRNS_X12. 3592 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI$VAN_TRAX. 1897 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI$X25.EXE;4 2024 [SYSTEM] (RWED,RWED,RE,RE) FBR$DECEDI_ 5 [SYSTEM] (RWED,RWED,RE,RE) EXTRACT.COM;4 FBR$EXTRACT_INSTALL. 9 [SYSTEM] (RWED,RWED,RE,RE) COM;4 FBR$RECOVER.EXE;4 2776 [SYSTEM] (RWED,RWED,RE,RE) FBR$RUNTIME.EXE;4 2754 [SYSTEM] (RWED,RWED,RE,RE) FBR$TRACKING.EXE;4 806 [SYSTEM] (RWED,RWED,RE,RE) FBR$UI.EXE;4 3114 [SYSTEM] (RWED,RWED,RE,RE) OpenVMS Installation - Directory and File Listing J-79 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING 9. SYS$COMMON:[SYSHLP] DECEDI$COMMAND_HELP. 700 [SYSTEM] (RWED,RWED,RWED,RE) HLB;4 DECEDI$REVIEW_HELP. 49 [SYSTEM] (RWED,RWED,RWED,RE) HLB;4 DECEDI$UI_FIELD_HELP. 581 [SYSTEM] (RWED,RWED,RWED,RE) HLB;4 DECEDI$UI_HELP_KEYS_ 9 [SYSTEM] (RWED,RWED,RWED,RE) ENGLISH.TXT;4 DECEDIMSG021.RELEASE_ 181 [SYSTEM] (RWED,RWED,RWED,RE) NOTES;14 DECEDIV40.RELEASE_ 37 [SYSTEM] (RWED,RWED,RWED,RE) NOTES;14 10. SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] DECEDI$COMM_APPSHR. 4 [SYSTEM] (RWED,RWED,RWED,RE) OPT;4 DECEDI$CONTRL_SHR. 3 [SYSTEM] (RWED,RWED,RWED,RE) OPT;4 DECEDI_POST_FETCH.C;4 17 [SYSTEM] (RWED,RWED,RWED,RE) EDIFACT_901_DIRECTORY. 180 [SYSTEM] (RWED,RWED,RWED,RE) DAT;4 EDIFACT_901_MINVOX_ 180 [SYSTEM] (RWED,RWED,RWED,RE) DOCUMENT.DAT;5 HELLO.C;4 3 [SYSTEM] (RWED,RWED,RWED,RE) INVOICE_IN.DAT;4 1 [SYSTEM] (RWED,RWED,RWED,RE) INVOICE_IN.FBO;4 76 [SYSTEM] (RWED,RWED,RWED,RE) INVOICE_OUT.DAT;4 1 [SYSTEM] (RWED,RWED,RWED,RE) INVOICE_OUT.FBO;4 165 [SYSTEM] (RWED,RWED,RWED,RE) MINVOX_HOOK_OUT.FBO;4 189 [SYSTEM] (RWED,RWED,RWED,RE) MINVOX_IN.DAT;4 3 [SYSTEM] (RWED,RWED,RWED,RE) MINVOX_IN.FBO;4 63 [SYSTEM] (RWED,RWED,RWED,RE) MINVOX_OUT.DAT;4 2 [SYSTEM] (RWED,RWED,RWED,RE) MINVOX_OUT.FBI;1 19 [SYSTEM] (RWED,RWED,RE,) MINVOX_OUT.FBO;5 80 [SYSTEM] (RWED,RWED,RE,) PROFILE-DEC-DIRECT-UK- 3 [SYSTEM] (RWED,RWED,RWED,RE) LTD.DAT;4 PROFILE-HAPPY-JACK- 3 [SYSTEM] (RWED,RWED,RWED,RE) SOFTWARE.DAT;4 PROFILE-INVOICE- 3 [SYSTEM] (RWED,RWED,RWED,RE) APPLICATION.DAT;4 PROFILE-SHINY-NEW- 3 [SYSTEM] (RWED,RWED,RWED,RE) SYSTEMS.DAT;4 X12_002002_DIRECTORY. 342 [SYSTEM] (RWED,RWED,RWED,RE) DAT;4 J-80 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing 11. .SYS$COMMON:[SYSLIB] DECEDI$API_DEF.BAS;4 15 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$API_DEF.COB;4 15 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$API_DEF.FOR;4 10 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$API_DEF.H;4 11 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$API_DEF.LIB;4 15 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$API_DEF.PAS;4 14 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$API_DEF.PLI;4 12 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$APPSHR_V2.EXE;4 145 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$COMM_APPSHR. 1102 [SYSTEM] (RWED,RWE,RWE,RE) EXE;4 DECEDI$CONTRLSHR. 1024 [SYSTEM] (RWED,RWE,RWE,RE) EXE;4 DECEDI$DATACHECKSHR. 8 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI$EXTSHR.EXE;4 852 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$GDI_DEFS.BAS;4 16 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$GDI_DEFS.FOR;4 11 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$GDI_DEFS.H;4 9 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$GDI_DEFS.LIB;4 14 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$GDI_DEFS.PAS;4 12 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$GDI_DEFS.PLI;4 10 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$LIBSHR.EXE;4 812 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$NUMSHR.EXE;4 433 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$PRVSHR.EXE;5 8 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI$SECTION.TPU$ 122 [SYSTEM] (RWED,RWED,RE,RE) SECTION;4 DECEDI$SEQCHECKSHR. 29 [SYSTEM] (RWED,RWED,RE,RE) EXE;4 DECEDI_API_COMMON.H;4 48 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI_API_DEF.H;4 9 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI_API_MSGS.H;4 24 [SYSTEM] (RWED,RWE,RWE,RE) DECEDI_PLATFORMS.H;4 14 [SYSTEM] (RWED,RWE,RWE,RE) 12. SYS$COMMON:[SYSTEST] DECEDI$IVP.COM;4 55 [SYSTEM] (RWED,RWED,RWED,) DECEDI$IVP_CHECKSUMS. 414 [SYSTEM] (RWED,RWED,RWED,) DAT;7 DECEDI$IVP_CHECKSUMS_ 414 [SYSTEM] (RWED,RWED,RE,) NEW.DAT;2 13. Logical Names All DEC/EDI logical names are entered into logical name tables when DEC/EDI is started. These names are defined by the following startup files: SYS$MANAGER:DECEDI$LOGICALS.COM OpenVMS Installation - Directory and File Listing J-81 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING SYS$MANAGER:DECEDI$SYLOGICALS.COM SYS$MANAGER:DECEDI$SYLOGICALS_.COM. The logical names are automatically entered into the DECEDI logical name table whenever you run DEC/EDI's startup procedure. The list is in alphabetical order. To see the logical names grouped by the DEC/EDI components that use them, look at the command procedure that define them. The following logicals are defined in the logical name table DECEDI$LOGICAL_NAMES: "DECEDI$3780" = "DECEDI$TOP:[3780PLUS]" "DECEDI$ACF" = "DECEDI$DATA:DECEDI$ACCESS.DAT" "DECEDI$ARCHIVE_DB" = "BITTER$DKB200:[DECEDI.ARCHIVEDB]DECEDI$ARCHIVE_DB.RDB" "DECEDI$ARCHREPORTS" = "DECEDI$TOP:[ARCHREPORTS]" "DECEDI$AST" = "DECEDI$DATA:DECEDI$SITE_TABLE.DAT" "DECEDI$AUDIT_DB" = "BITTER$DKB200:[DECEDI.AUDITDB]DECEDI$AUDIT_DB.RDB" "DECEDI$AUDIT_DB_REFRESH" = "0 06:00:00" "DECEDI$AUDIT_DB_VERSION" = "5.1" "DECEDI$BACKUP" = "DECEDI$TOP:[BACKUP]" "DECEDI$CACHE" = "DECEDI$TOP:[CACHE]" "DECEDI$CAF" = "DECEDI$DATA:DECEDI$CLIENTAPPLICATIONS.DAT" "DECEDI$CNT" = "DECEDI$DATA:DECEDI$CONTROL_NUM.DAT" "DECEDI$COM" = "SYS$MANAGER" "DECEDI$CVP" = "DECEDI$TOP:[CVP]" "DECEDI$CVP_IMPEXP" = "DECEDI$TOP:[CVP.IMPEXP]" "DECEDI$CVP_WORK" = "DECEDI$TOP:[CVP.WORK]" "DECEDI$DAT" = "DECEDI$NON_UNIQUE_DECEDI$DOC_AREA_TABLE.DAT" "DECEDI$DATA" = "DECEDI$TOP:[DATA]" "DECEDI$DDF" = "DECEDI$DATA:DECEDI$DOC_DESC_TABLE.DAT" "DECEDI$DLF" = "DECEDI$DATA:DECEDI$DATA_DESC.DAT" "DECEDI$DLM" = "DECEDI$NON_UNIQUE_DECEDI$DATA_LABEL.DAT" "DECEDI$DS_CLEANUP" = "1" "DECEDI$DS_CLEANUP_COUNT" = "120" "DECEDI$DS_N_TIMEOUT_MAX" = "5" "DECEDI$DS_TIMEOUT" = "60" "DECEDI$DTF" = "DECEDI$NON_UNIQUE_DECEDI$DOCUMENT_TABLE.DAT" "DECEDI$ECF" = "DECEDI$NON_UNIQUE_DECEDI$ELEMENT_CODES.DAT" "DECEDI$ELF"="DECEDI$NON_UNIQUE_DECEDI$ELEMENT_CEDI$ERROR"="DE CEDI$TOP:[ERROR]" "DECEDI$EXAMPLES" ="SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI]" "DECEDI$EXE" = "SYS$SYSTEM" "DECEDI$FMT" = "DECEDI$DATA:DECEDI$FA_MAPPING_TABLE.DAT" "DECEDI$FTF" = "DECEDI$DATA:DECEDI$FORMAT_TABLE.DAT" "DECEDI$HK_LOCK_THRESHOLD" = "100" "DECEDI$JDF" = "DECEDI$DATA:DECEDI$JOB_DESC.DAT" "DECEDI$LOOK" = "DECEDI$EXE:DECEDI$LOOK.COM" "DECEDI$MAPS" = "DECEDI$TOP:[MAP_TABLES]" J-82 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing "DECEDI$MAX_DICTIONARIES" = "2" "DECEDI$MAX_DOCUMENTS" = "10" "DECEDI$MAX_SEGMENT_TABLES" = "2" "DECEDI$MCF" = "DECEDI$DATA:DECEDI$MGT_CONFIG.DAT" "DECEDI$MESSAGES" = "SYS$MESSAGE:DECEDI$MESSAGE.EXE" "DECEDI$MESSAGE_UPDATES" = "DECEDI$TOP:[MESSAGE_UPDATES]" "DECEDI$MSG" = "SYS$MESSAGE" "DECEDI$NCD" = "DECEDI$DATA:DECEDI$NODE_CONFIGURATION_DETAILS.DAT" "DECEDI$PAT" = "DECEDI$NON_UNIQUE_DECEDI$P_DOC__ABLE.DAT" "DECEDI$PCF" = "DECEDI$NON_UNIQUE_DECEDI$P_ELEMENT_CODES.DAT" "DECEDI$PDF" = "DECEDI$DATA:DECEDI$P_DOC_DESC_TABLE.DAT" "DECEDI$PDT" = "DECEDI$NON_UNIQUE_DECEDI$P_DOCUMENT_TABLE.DAT" "DECEDI$PET" = "DECEDI$NON_UNIQUE_DECEDI$P_ELEMENT_TABLE.DAT" "DECEDI$PSD" = "DECEDI$NON_UNIQUE_DECEDI$P_SEG_DESC.DAT" "DECEDI$PSE" = "DECEDI$NON_UNIQUE_DECEDI$P_SUB_ELE_TABLE.DAT" "DECEDI$PST" = "DECEDI$NON_UNIQUE_DECEDI$P_SEGMENT_TABLE.DAT" "DECEDI$QTF" = "DECEDI$NON_UNIQUE_DECEDI$QUALIFIER_TABLE.DAT" "DECEDI$SAFE_DIRECTORY" = "DECEDI$TOP:[DS_SCRATCH]" "DECEDI$SCF" = "DECEDI$DATA:DECEDI$SRV_CONFIGURATION.DAT" "DECEDI$SDF" = "DECEDI$NON_UNIQUE_DECEDI$SEG_DESC.DAT" "DECEDI$SEF" = "DECEDI$NON_UNIQUE_DECEDI$SUB_ELE_TABLE.DAT" "DECEDI$SHUTDOWN" = "SYS$STARTUP:DECEDI$SHUTDOWN" "DECEDI$SPA" = "DECEDI$DATA:DECEDI$SRV_PARAMETER.DAT" "DECEDI$SPF" = "DECEDI$DATA:DECEDI$SYSTEM_PARAMETERS.DAT" "DECEDI$SRF" = "DECEDI$DATA:DECEDI$SITE_ROUTING.DAT" "DECEDI$STARTUP" = "SYS$STARTUP:DECEDI$STARTUP" "DECEDI$STARTUP_DS_TIMEOUT_LENGTH" = "0 00:01:00.00" "DECEDI$STARTUP_FS_TIMEOUT_LENGTH" = "0 00:30:00.00" "DECEDI$STARTUP_TIMEOUT_LENGTH" = "0 00:10:00.00" "DECEDI$STF" = "DECEDI$NON_UNIQUE_DECEDI$SEGMENT_TABLE.DAT" "DECEDI$STORE_1" = "DECEDI$TOP:[STORE_1]" "DECEDI$STORE_10" = "DECEDI$TOP:[STORE_10]" "DECEDI$STORE_11" = "DECEDI$TOP:[STORE_11]" "DECEDI$STORE_12" = "DECEDI$TOP:[STORE_12]" "DECEDI$STORE_13" = "DECEDI$TOP:[STORE_13]" "DECEDI$STORE_14" = "DECEDI$TOP:[STORE_14]" "DECEDI$STORE_15" = "DECEDI$TOP:[STORE_15]" "DECEDI$STORE_16" = "DECEDI$TOP:[STORE_16]" "DECEDI$STORE_17" = "DECEDI$TOP:[STORE_17]" "DECEDI$STORE_18" = "DECEDI$TOP:[STORE_18]" "DECEDI$STORE_19" = "DECEDI$TOP:[STORE_19]" "DECEDI$STORE_2" = "DECEDI$TOP:[STORE_2]" "DECEDI$STORE_20" = "DECEDI$TOP:[STORE_20]" "DECEDI$STORE_3" = "DECEDI$TOP:[STORE_3]" "DECEDI$STORE_4" = "DECEDI$TOP:[STORE_4]" "DECEDI$STORE_5" = "DECEDI$TOP:[STORE_5]" "DECEDI$STORE_6" = "DECEDI$TOP:[STORE_6]" OpenVMS Installation - Directory and File Listing J-83 OPENVMS INSTALLATION - DIRECTORY AND FILE LISTING "DECEDI$STORE_7" = "DECEDI$TOP:[STORE_7]" "DECEDI$STORE_8" = "DECEDI$TOP:[STORE_8]" "DECEDI$STORE_9" = "DECEDI$TOP:[STORE_9]" "DECEDI$STORE_CURRENT" = "1" "DECEDI$STORE_HIGH" = "20" "DECEDI$STORE_LOW" = "1" "DECEDI$SVF" = "DECEDI$DATA:DECEDI$SYSTEM_VERSIONS.DAT" "DECEDI$SWA" = "DECEDI$DATA:DECEDI$SWIFT_AUDIT.DAT" "DECEDI$SWH" = "DECEDI$DATA:DECEDI$SWIFT_HISTORY.DAT" "DECEDI$TAT" = "DECEDI$NON_UNIQUE_DECEDI$TP_DOC_AREA TABLE.DAT" "DECEDI$TCT" = "DECEDI$NON_UNIQUE_DECEDI$TP_CODE TRANS.DAT" "DECEDI$TDL" = "DECEDI$NON_UNIQUE_DECEDI$TP_DATA LABEL.DAT" "DECEDI$TDT" = "DECEDI$NON_UNIQUE_DECEDI$TP_DOCUMENT TABLE.DAT" "DECEDI$TEMP" = "DECEDI$TOP:[TEMP]" "DECEDI$TET" = "DECEDI$NON_UNIQUE_DECEDI$TP_ELEMENT TABLE.DAT" "DECEDI$TFD" = "DECEDI$DATA:DECEDI$TRANSMISSION_FILE DETAILS.DAT" "DECEDI$TOOLS" = "DECEDI$TOP:[TOOLS]" "DECEDI$TOP" = "BITTER$DKB200:[DECEDI.]" "DECEDI$TPA" = "DECEDI$DATA:DECEDI$AGREEMENTS_TABLE.DAT" "DECEDI$TPD" = "DECEDI$DATA:DECEDI$AGREEMENTS_DETAIL TABLE.DAT" "DECEDI$TPF" = "DECEDI$DATA:DECEDI$PARTNER_TABLE.DAT" "DECEDI$TPQ" = "DECEDI$NON_UNIQUE_DECEDI$TP_QUAL TABLE.DAT" "DECEDI$TSF" = "DECEDI$DATA:DECEDI$SCHEDULE.DAT" "DECEDI$TST" = "DECEDI$NON_UNIQUE_DECEDI$TP_SEGMENT TABLE.DAT" "DECEDI$TSV" = "DECEDI$DATA:DECEDI$TP_STD_VERS.DAT" "DECEDI$UI_HELP_KEYS" = "SYS$HELP:DECEDI$UI_HELP_KEYS_ENGLISH.TXT" "DECEDI$VANREPORTS" = "DECEDI$TOP:[VANREPORTS]" The following DEC/EDI logicals are defined in the system table LNM$SYSTEM_TABLE: "DECEDI$CLUSTER_MEMBER_LETTER" = "A" "DECEDI$COMMS_PSI" = "MBA521:" "DECEDI$DATA_SERVER" = "MBA1410:" "DECEDI$DS_MBX_3BC" = "MBA1427:" "DECEDI$DS_MBX_3BD" = "MBA1424:" "DECEDI$DS_MBX_3BE" = "MBA1425:" "DECEDI$DS_MBX_3BF" = "MBA1423:" "DECEDI$DS_MBX_3C0" = "MBA1428:" "DECEDI$DS_MBX_3C1" = "MBA1426:" "DECEDI$MAX_MAPPING_TABLES" = "10" "DECEDI$MSL_KEY" = "DECEDI$MSL_1" "DECEDI$NODE" = "ABACUS " "DECEDI$N_AS_MAX" = "1" "DECEDI$N_AS_PRESTART" = "1" J-84 OpenVMS Installation - Directory and File Listing OpenVMS Installation - Directory and File Listing "DECEDI$N_EDIF_CNV_MAX" = "1" "DECEDI$N_EDIF_CNV_PRESTART" = "1" "DECEDI$N_EDIF_TFB" = "2" "DECEDI$N_EDIF_TFB_MAX" = "1" "DECEDI$N_EDIF_TFB_PRESTART" = "1" "DECEDI$N_EDIF_TFS_MAX" = "1" "DECEDI$N_EDIF_TFS_PRESTART" = "1" "DECEDI$N_EDIF_TRNS_MAX" = "1" "DECEDI$N_EDIF_TRNS_PRESTART" = "1" "DECEDI$N_IMPEXP_GWAY_MAX" = "1" "DECEDI$N_SCHED" = "1" "DECEDI$N_SCHED_MAX" = "1" "DECEDI$N_SCHED_PRESTART" = "1" "DECEDI$N_TRAD_CNV_MAX" = "1" "DECEDI$N_TRAD_CNV_PRESTART" = "1" "DECEDI$N_TRAD_TRNS_MAX" = "1" "DECEDI$N_TRAD_TRNS_PRESTART" = "1" "DECEDI$N_X12_CNV" = "1" "DECEDI$N_X12_CNV_MAX" = "5" "DECEDI$N_X12_CNV_PRESTART" = "3" "DECEDI$N_X12_TFB" = "2" "DECEDI$N_X12_TFB_MAX" = "5" "DECEDI$N_X12_TFB_MAX=" = "5" "DECEDI$N_X12_TFB_PRESTART" = "3" "DECEDI$N_X12_TFB_PRESTART=" = "3" "DECEDI$N_X12_TRNS" = "1" "DECEDI$N_X12_TRNS_MAX" = "1" "DECEDI$N_X12_TRNS_PRESTART" = "1" "DECEDI$STARTUP_SHUTDOWN" = "MBA49:" "DECEDI_CSF_MAX" = "5" "DECEDI_CSF_PRESTART" = "3" "DECEDI_CSG_MAX" = "1" "DECEDI_CSG_PRESTART" = "1" "DECEDI_CST_MAX" = "1" "DECEDI_CST_PRESTART" = "1" "DECEDI_PS_MBX" = "MBA527:" Index A Aborting the Installation 6-17 Access Control Editor 4-11 Access From a Local Client 6-36 Accessing the Online Release Notes 6-16 Account Quotas For The Installing Account 6-14 Adding a DEC/EDI Account 5-18 Adding Symbols to User's LOGIN.COM 6-36 After installing DEC/EDI and the document standards 6-30 All Services on a Single Node 6-20 Application Client 1-2 Application Development xvii Audience xv Autogen 6-13 B Backing up 6-1 BIL 6-1 Bill of Materials 5-8 Bisynchronous Communication 1-12 BOM 6-1 C Calculating Values for GBLPAGES and GBLSECTIONS 6-12 Changing Account Quotas 6-15 Changing System Parameter Values 6-13 Check the contents of your DEC/EDI software distribution kit 5-8 Check the Installation Kit is correct 6-1 Check your Cockpit or CommandCenter Kit 9-1 Checking DEC X.25 is Installed 5-18 Checking for Installed Licenses 6-7 Checking for TCP/IP Services 5-17 Checking Mailbus 400 is Installed 5-18 Checking Oracle Rdb is Installed 5-18 Checking Oracle SQL Services is Running 5-18 Checking System Parameter Values 6-11 Checking the DEC/EDI account 5-18 Clean system - installation 6-20 CLEO 3780Plus 1-12 Client Man Pages 5-6 Cockpit 1-2 Cockpit and CommandCenter 1-5 CommandCenter 1-2 Communication Options 1-8 Completing the Installation Procedure 6-28 Configuring server overview of 2-5 Configuring the DEC/EDI Server 3-1 Conversion 10-4 Copying data labels between versions 8-4 EDI standards 8-4 Creating user accounts 4-11 CSC 5-32 ctivities xv D Data labels copying between versions 8-4 Database calculating required the size of 4-3 deciding where to locate 4-3 Database Administrator 4-1 DEC Direct UK Ltd 10-3 Index-86 DEC/EDI 3780 (BISYNC) 5-6 DEC/EDI Account Details (UIC) 6-18 DEC/EDI Error Log 6-35 DEC/EDI Security 6-33 DEC/EDI User Interfaces 1-2 DEC/EDI Version 3.2 onto a VMS system 6-1 DECEDI Account 6-38 DECEDI$ADMINISTRATOR 11-8 DECEDI$STARTUP FULL 11-14 DECEDI$SUPERVISOR 11-8 DECEDI_MUS.LOG 8-6 Deciding Where to Locate the Database 4-3 Defining DEC/EDI Logical Names 6-32 Deleting an EDI standard 8-4 Determining and Reporting Problems 6-37 Determining Disk Space 5-20 Determining Diskspace 6-9 Digital UNIX 4-13 Digital UNIX Server - Problem Solving 9-15 Digital UNIX SQL Services 4-13 Digital UNIX, Sun Solaris, HP-UX 1-9 Disk Quota 6-39 Disk Space Requirement 6-9 Disk Space Requirements 5-19 Displayed Files with Errors 6-28 Documentation xvii DSNlink 5-32 E EDI format message 10-4 EDI standards copying 8-4 deleting 8-4 installing 8-3 EDI-COMCEN license 5-9 EDIFACT 1-8 EDIFACT 90.1 standard 11-1 EDIFACT IMPDEF files 5-6 Editing the System Files 6-31 Enabling the Protection 6-33 Error When Connecting to Server 9-14 Establishing the Configuration 1-3 Example Application File 10-4 F FileBridge UI 1-3 Files DECEDI_MUS.LOG 8-6 Files and Logical Names Added to Your System 6-16 G Gateway 6-3 GBLPAGE 6-12 GBLSECTIONS 6-12 Getting More Information 9-18 H hypothetical trading partners 10-1 I Import/Export Communication 1-12 Increasing Disk Quota 6-39 Installation xvii, 6-21 Client On Top Of Server 6-19 Server On Client-Only System 6-19 Installation Failure 6-27 installation onto a 'clean' system 6-1 Installing EDI standards 8-3 Installing on a Cluster 6-20 Installing the Message Update Kit 6-29 INTERCHANGE 1-3, 4-1 Internal Format File 10-4 Index-87 Internet SMTP/MIME Communication 1-12 Introduction xvii IVP 6-16 L License Management Facility (LMF) 5-8 License PAK 6-7 License Product Authorization Key 5-8 Locating the database 4-3 lsnrctl 5-15 M Mailbus 400 Gateway 5-6 Management Services Editor 10-10 Mandatory 6-6 Mapping 10-4 Message Updates 1-8 Message Updates TDCC files 5-7 Message Updates TRADACOMS files 5-7 Message Updates X12 files 5-7 Migrating the Database 4-10 Migration from V1.3A 6-21 Migration Sequence 6-20 MINVOX 10-3 More about Backup 6-17 More about License Management Facility 6-7 Multi-node Client/Server System 1-4 Multinode System with Translation and Communications all on One Node 6-20 MUS copying data labels 8-4 copying EDI standards 8-4 deleting an EDI standard 8-4 installing EDI standards 8-3 log file 8-6 problems 8-6 recovery 8-4 N Network and Rdb Monitor Startup 6-32 Network Interface 1-9 NFS mounted disks 4-4 Number of Processes 6-40 O ODBC 1-10 ODBC administrator 11-18 ODETTE IMPDEF files 5-6 OFTP Communication 1-12 OFTP Gateway 5-6 OpenVMS 6-1 OpenVMS Server - Problem Solving 9-16 ORACLE 7 1-7 Oracle CD-ROM disk 5-16 ORACLE ODBC Driver for Rdb 1-11 ORACLE Rdb 1-7 ORACLE SQL/Services for Rdb 1-7 ORACLE_HOME 5-16 ORACLE_SID 5-16 ORACLE_TERM 5-16 P PAK(s) 5-8 Pascal Run-Time Library 6-32 ping 5-14 PL/SQL 5-17 Post-Configuration Tasks 3-6 Pre-Configuration tasks 3-2 pre-installation information 2-1 Pre-Installation Tasks for Oracle 7 on the PC 9-5 Product Installation Documentation 1-2 Q Questions, Getting Help 4-6 Index-88 R Registering a License 6-7 Registering Licenses on Digital UNIX 5-10 Release Notes xviii Reporting Problems 9-21 S sendmail function 1-12 Server 1-1 setld command 1-8 Setting Up Cockpit an overview 2-5 CommandCenter an overview 2-4 remote Application Clients an overview 2-4 Server and Local Application Clients an overview 2-3 Setting up any Cockpit installations 2-1 Setting up any CommandCenter installations 2-1 Setting up any remote Application Clients 2-1 Setting up the Server 2-1 Shiny New Systems 10-3 Single Node System 1-3 SMTP/MIME 1-12 SMTP/MIME Communications Gateway 5-6 Software Licenses 5-8 Software Licensing 6-7 Start the DEC/EDI Server 11-14 Supported Configurations 1-3 Supported Software Versions 6-3 svrmgrl 5-17 SYNCcable+ 1-12 SYS$STARTUP 11-9 System Parameters 6-10 system reboot 6-35 System Startup 6-31 T TCP/IP Link Checking 5-14 TCP/IP Network Interface 3-1 TCP/IP only 1-7 TCP/IP Port Server Monitoring Tools 3-7 Time to Install 6-18 tracing behaviour 3-7 TRADACOMS 1-8 TRADANET VAN 1-12 Translation Services 5-6 Transmission File Builder 10-4 Transmission File Building 10-4 Troubleshooting Common Problems 11-18 Typical Protection 6-33 Typographical Conventions xix U U.S. customers 5-32 Upgrading to V3.2 6-20 upgrading' an earlier version 6-1 User accounts creating 4-11 User's Guides xvii, 10-2 Using the CommandCenter 2-1 Using the Correct Pascal Run-Time Library 6-32 V VMS System Generation Utility 6-10 VMSINSTAL Requirements 6-17 W Windows 3.1x, Windows 95, Windows NT 1-10 Windows 95/NT 9-1 Index-89 X X.25 VAN Communication 1-12 X.400 Communication 1-12 X12 1-8 Z Zero additional licensing or software needed for use of Import/Export gateway 1-13