DEC/EDI_____________________________________________ Installing the OpenVMS Server and Application Client Order Number: AA-PA9TG-TE Revision/Update Information: Revised for DEC/EDI Version 2.1A Operating System: OpenVMS VAX Version 6.1 OpenVMS AXP Version 6.1 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ November 1995 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1990, 1995. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: AXP, DEC, DEC/EDI, DECforms, DECnet, DECwindows, MAILbus, OpenVMS, VAX, VAX 9000, VAXcluster, VAXstation, VMS, VMSmail, and the DIGITAL logo. AT&T is a trademark of American Telephone & Telegraph Company. TYMNET is a registered trademark of TYMNET, Inc. UNIX is a registered trademark licensed exclusively by X/Open Company Ltd. OSF/1 is a registered trademark of Open Software Foundation, Inc. IBM, AIX and RS/6000 are registered trademarks of International Business Machines Corporation. HP and HP-UX are registered trademarks of Hewlett-Packard Company. Microsoft is a registered trademark, and Windows is a trademark, of Microsoft Corporation. CLEO, 3780Plus and SYNCcable+ are registered trademarks of CLEO Communications. Oracle is a registered trademark of the Oracle Corporation. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... xi 1 Preparing to Install DEC/EDI 1.1 Required Operating System Components.......... 1-1 1.2 Prerequisite Software Products................ 1-2 1.2.1 OpenVMS/VAX Server Requirements........... 1-2 1.2.1.1 General Requirements.................... 1-2 1.2.1.2 Gateway Requirements.................... 1-2 1.2.1.3 Application Interface Requirements...... 1-3 1.2.1.4 Supported Software Versions............. 1-4 1.2.2 OpenVMS/AXP Server Requirements........... 1-6 1.2.2.1 General Requirements.................... 1-6 1.2.2.2 Gateway Requirements.................... 1-6 1.2.2.3 Application Interface Requirements...... 1-7 1.2.2.4 Supported Software Versions............. 1-8 1.2.3 Requirements for DEC/EDI V2 Application Clients on OpenVMS ....................... 1-9 1.3 Registering Your Software License ............ 1-9 1.4 Installation Procedure Requirements........... 1-10 1.4.1 Time...................................... 1-10 1.4.2 Privileges For The Installing Account..... 1-11 1.4.3 Disk Space................................ 1-11 1.4.4 System Parameters......................... 1-13 1.4.4.1 Checking System Parameter Values........ 1-15 1.4.4.2 Setting the WSMAX System Parameter ..... 1-15 1.4.4.3 Calculating Values for GBLPAGES and GBLSECTIONS............................. 1-16 1.4.5 Account Quotas For The Installing Account................................... 1-17 1.4.6 VMSINSTAL Requirements.................... 1-19 1.4.7 Backing Up Your System Disk............... 1-20 1.5 Reinstalling ................................. 1-20 iii 1.5.1 Reinstallation: Client On Top Of Server... 1-20 1.5.2 Reinstallation: Server On Client-Only System ................................... 1-21 1.6 Running ACAS with DECNET/OSI for use with DEC/EDI....................................... 1-21 1.7 ObjectBroker.................................. 1-22 1.8 Installing on a Cluster....................... 1-22 1.9 Information Needed During Installation........ 1-22 1.10 Migration Sequence............................ 1-23 1.10.1 All Services on a Single Node............. 1-23 1.10.2 Multinode System with Translation and Communications all on One Node............ 1-23 1.10.3 Multinode System with Distributed Translation and Communications............ 1-23 1.11 Migration from V1.3A.......................... 1-24 2 Installing DEC/EDI 2.1 Accessing the Online Release Notes............ 2-1 2.2 Files and Logical Names Added to Your System........................................ 2-1 2.3 Running the Installation Verification Procedure (IVP)............................... 2-1 2.4 Aborting the Installation..................... 2-2 2.5 Installing DEC/EDI Version 2.1................ 2-2 2.5.1 Shutting Down DEC/EDI..................... 2-2 2.5.2 Invoking VMSINSTAL........................ 2-2 2.5.3 Questions for Server With Client Installation ............................. 2-4 2.5.4 Questions For Client-Only Installation ... 2-11 2.5.5 Informational Messages.................... 2-15 2.5.6 Running the Installation Verification Procedure................................. 2-15 2.5.7 Completing the Installation Procedure..... 2-16 2.6 Error Recovery................................ 2-16 iv 3 After Installing 3.1 Configuring ACA Services for DEC/EDI.......... 3-1 3.2 Editing the System Files...................... 3-1 3.3 Defining DEC/EDI Logical Names................ 3-3 3.4 Modifying DECforms Logical Names.............. 3-3 3.5 Using the Correct Pascal Run-Time Library..... 3-4 3.6 Enhancing DEC/EDI Security.................... 3-4 3.7 Modifying the System Page File Size........... 3-5 3.8 Rebooting the System.......................... 3-6 3.9 Renaming the DEC/EDI Error Log................ 3-6 3.10 Modifying User Accounts....................... 3-7 3.10.1 Adding Symbols to User's LOGIN.COM........ 3-7 3.11 Determining and Reporting Problems............ 3-8 3.12 The DECEDI Account............................ 3-8 3.12.1 Increasing Disk Quota..................... 3-9 3.12.2 Calculating the Required Number of Processes................................. 3-10 3.12.3 Modifying Quota for the DECEDI Account.... 3-12 3.12.3.1 Calculating the WSEXTENT Value.......... 3-12 3.12.3.2 Calculating the ENQLM Value............. 3-13 3.12.4 Ownership of the DECEDI Account........... 3-13 3.12.5 Account privileges on the DECEDI Account................................... 3-13 3.13 Defining FileBridge Rights.................... 3-14 3.13.1 The Rights Database....................... 3-14 3.13.1.1 FBR$SUPERVISOR.......................... 3-15 3.13.1.2 FBR$DEVELOPMENT......................... 3-16 3.13.1.3 FBR$OPERATIONS.......................... 3-16 3.14 Data Migration................................ 3-16 3.14.1 Using the AUDIT_DB Option................. 3-17 3.14.1.1 Migrating from a Distributed V1.3 System.................................. 3-18 3.14.2 Using the ARCHIVE_DB Option............... 3-18 3.14.3 Using the MAPPER_DB Option................ 3-19 3.14.4 Using the TRAX Option..................... 3-19 3.15 Additional Post Installation Tasks for Migration from V1.3A.......................... 3-20 3.15.1 Node Configuration........................ 3-20 3.15.2 EDIFACT UNS Segment Handling Changes...... 3-21 v 4 Installation Verification Procedure A Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX................................... A-1 A.2 Log of New Client Installation on OpenVMS VAX........................................... A-9 A.3 Log of New Server and Client Installation On OpenVMS AXP................................... A-13 A.4 Log of New Client Installation on OpenVMS AXP........................................... A-19 A.5 Log of Reinstallation On OpenVMS AXP ......... A-22 B Installing DEC/EDI Translation Standards B.1 Preparation for the Message Update ........... B-1 B.2 Running the Message Update Procedure ......... B-1 B.3 Aborting the Message Update Installation ..... B-2 C Files in the Installation Kit C.1 Save Set A.................................... C-1 C.2 Save Set B.................................... C-1 C.3 Save Set C.................................... C-3 C.4 Save Set D.................................... C-4 C.5 Save Set E.................................... C-6 C.6 Save Set F.................................... C-8 D File Protection on the Installed Files D.1 OpenVMS AXP Server Files...................... D-1 D.1.1 Files in DECEDI$TOP:[000000].............. D-1 D.1.2 Files in DECEDI$TOP:[ARCHIVE_DB].......... D-3 D.1.3 Files in DECEDI$TOP:[AUDIT_DB]............ D-4 D.1.4 Files in DECEDI$TOP:[CVP]................. D-6 D.1.5 Files in DECEDI$TOP:[DATA]................ D-7 D.1.6 Files in DECEDI$TOP:[TOOLS]............... D-13 D.2 OpenVMS AXP Server FileBridge Directory Structure..................................... D-16 D.2.1 Files in [FILEBRIDGE] .................... D-16 D.2.2 Files in [FILEBRIDGE.] ........ D-17 D.2.3 Files in [FILEBRIDGE.TEST_DB] ............ D-18 vi D.3 OpenVMS AXP Server System Directory Structure..................................... D-19 D.3.1 Files in SYS$COMMON:[SYS$STARTUP] ........ D-19 D.3.2 Files in SYS$COMMON:[SYSEXE] ............. D-19 D.3.3 Files in SYS$COMMON:[SYSHLP] ............. D-21 D.3.4 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] ...... D-22 D.3.5 Files in SYS$COMMON:[SYSLIB] ............. D-23 D.3.6 Files in SYS$COMMON:[SYSMGR] ............. D-23 D.3.7 Files in SYS$COMMON:[SYSMSG] ............. D-24 D.3.8 Files in SYS$COMMON:[SYSTEST] ............ D-24 D.3.9 Files in SYS$COMMON:[SYSTEST.FBR] ........ D-25 D.4 OpenVMS VAX Server Files...................... D-25 D.4.1 Files in DECEDI$TOP:[000000].............. D-25 D.4.2 Files in DECEDI$TOP:[AUDIT_DB]............ D-27 D.4.3 Files in DECEDI$TOP:[ARCHIVE_DB].......... D-28 D.4.4 Files in DECEDI$TOP:[CVP]................. D-30 D.4.5 Files in DECEDI$TOP:[DATA]................ D-31 D.4.6 Files in DECEDI$TOP:[TOOLS]............... D-39 D.5 OpenVMS VAX Server FileBridge Directory Structure..................................... D-41 D.5.1 Files in [FILEBRIDGE] .................... D-41 D.5.2 Files in [FILEBRIDGE.] ........ D-42 D.5.3 Files in [FILEBRIDGE..FBR$DB] .......................................... D-43 D.5.4 Files in [FILEBRIDGE.TEST_DB] ............ D-43 D.5.5 Files in [FILEBRIDGE.TEST_DB.FBR$DB] ..... D-44 D.6 OpenVMS VAX Server System Directory Structure..................................... D-44 D.6.1 Files in SYS$COMMON:[SYS$STARTUP] ........ D-44 D.6.2 Files in SYS$COMMON:[SYSEXE] ............. D-44 D.6.3 Files in SYS$COMMON:[SYSHLP] ............. D-47 D.6.4 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] ...... D-47 D.6.5 Files in SYS$COMMON:[SYSLIB] ............. D-48 D.6.6 Files in SYS$COMMON:[SYSMGR] ............. D-49 D.6.7 Files in SYS$COMMON:[SYSMSG] ............. D-49 D.6.8 Files in SYS$COMMON:[SYSTEST] ............ D-50 D.6.9 Files in SYS$COMMON:[SYSTEST.FBR] ........ D-50 D.7 OpenVMS AXP Client Directory Structure ....... D-50 D.7.1 Files in DECEDI$TOP:[000000].............. D-50 D.7.2 Files in DECEDI$TOP:[DATA]................ D-51 vii D.8 OpenVMS AXP Client System Directory Structure..................................... D-51 D.8.1 Files in SYS$COMMON:[SYSEXE] ............. D-51 D.8.2 Files in SYS$COMMON:[SYSHLP] ............. D-52 D.8.3 Files in SYS$COMMON:[SYSLIB] ............. D-52 D.8.4 Files in SYS$COMMON:[SYSMSG] ............. D-53 D.8.5 Files in SYS$COMMON:[SYSTEST] ............ D-53 D.9 OpenVMS VAX Client DEC/EDI Directory Structure .............................................. D-53 D.9.1 Files in DECEDI$TOP:[000000].............. D-53 D.9.2 Files in DECEDI$TOP:[TOOLS]............... D-54 D.10 OpenVMS VAX Client System Directory Structure..................................... D-54 D.10.1 Files in SYS$COMMON:[SYSEXE].............. D-54 D.10.2 Files in SYS$COMMON:[SYSHLP] ............. D-55 D.10.3 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] ...... D-55 D.10.4 Files in SYS$COMMON:[SYSLIB] ............. D-55 D.10.5 Files in SYS$COMMON:[SYSMSG] ............. D-56 D.10.6 Files in SYS$COMMON:[SYSTEST] ............ D-56 E DEC/EDI Logical Names E.1 Logical Names................................. E-1 Tables 1-1 OpenVMS/VAX Software Product Versions Supported On DEC/EDI V2.1................. 1-5 1-2 OpenVMS/AXP Software Product Versions Supported On DEC/EDI V2.1................. 1-8 1-3 Time Taken to Install .................... 1-10 1-4 OpenVMS VAX Server: Disk Space Requirements.............................. 1-12 1-5 OpenVMS VAX Client: Disk Space Requirements ............................. 1-12 1-6 OpenVMS AXP Server: Disk Space Requirements.............................. 1-12 1-7 OpenVMS AXP Client: Disk Space Requirements.............................. 1-13 1-8 Server and Client Installations: Required System Parameter Values................... 1-14 viii 1-9 Client-Only Installations: Required System Parameter Values.......................... 1-14 1-10 Server Installation: Process Account Quotas for the Installing Account......... 1-18 1-11 Client Installation: Process Account Quotas for the Installing Account......... 1-18 3-1 Quotas for the DECEDI Account............. 3-9 3-2 DEC/EDI Processes......................... 3-11 D-1 Files in DECEDI$TOP:[000000].............. D-1 D-2 Files in DECEDI$TOP:[ARCHIVE_DB].......... D-3 D-3 Files in DECEDI$TOP:[AUDIT_DB]............ D-4 D-4 Directory Files in DECEDI$TOP:[CVP]....... D-6 D-5 Non-Directory Files in DECEDI$TOP:[CVP]... D-6 D-6 Files in DECEDI$TOP:[DATA]................ D-7 D-7 Files in DECEDI$TOP:[TOOLS]............... D-13 D-8 Files in [FILEBRIDGE] .................... D-17 D-9 Files in [FILEBRIDGE.] ........ D-17 D-10 Files in [FILEBRIDGE.TEST_DB] ............ D-18 D-11 Files in SYS$COMMON:[SYS$STARTUP] ........ D-19 D-12 Files in SYS$COMMON:[SYSEXE] ............. D-19 D-13 Files in SYS$COMMON:[SYSHLP] ............. D-21 D-14 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] ...... D-22 D-15 Files in SYS$COMMON:[SYSLIB] ............. D-23 D-16 Files in SYS$COMMON:[SYSMGR] ............. D-24 D-17 Files in SYS$COMMON:[SYSMSG] ............. D-24 D-18 Files in SYS$COMMON:[SYSTEST] ............ D-24 D-19 Files in SYS$COMMON:[SYSTEST.FBR] ........ D-25 D-20 Files in DECEDI$TOP:[000000].............. D-25 D-21 Files in DECEDI$TOP:[AUDIT_DB]............ D-27 D-22 Files in DECEDI$TOP:[ARCHIVE_DB].......... D-29 D-23 Directory Files in DECEDI$TOP:[CVP]....... D-30 D-24 Files in DECEDI$TOP:[DATA]................ D-31 D-25 Files in DECEDI$TOP:[TOOLS]............... D-39 D-26 Files in [FILEBRIDGE] .................... D-42 D-27 Files in [FILEBRIDGE.] ........ D-42 D-28 Files in [FILEBRIDGE..FBR$DB] .......................................... D-43 ix D-29 Files in [FILEBRIDGE.TEST_DB] ............ D-43 D-30 Files in [FILEBRIDGE.TEST_DB.FBR$DB] ..... D-44 D-31 Files in SYS$COMMON:[SYS$STARTUP] ........ D-44 D-32 Files in SYS$COMMON:[SYSEXE] ............. D-45 D-33 Files in SYS$COMMON:[SYSHLP] ............. D-47 D-34 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] ...... D-47 D-35 Files in SYS$COMMON:[SYSLIB] ............. D-48 D-36 Files in SYS$COMMON:[SYSMGR] ............. D-49 D-37 Files in SYS$COMMON:[SYSMSG] ............. D-49 D-38 Files in SYS$COMMON:[SYSTEST] ............ D-50 D-39 Files in SYS$COMMON:[SYSTEST.FBR] ........ D-50 D-40 Files in DECEDI$TOP:[000000].............. D-51 D-41 Files in DECEDI$TOP:[DATA]................ D-51 D-42 Files in SYS$COMMON:[SYSEXE] ............. D-52 D-43 Files in SYS$COMMON:[SYSHLP] ............. D-52 D-44 Files in SYS$COMMON:[SYSLIB] ............. D-52 D-45 Files in SYS$COMMON:[SYSMSG] ............. D-53 D-46 Files in SYS$COMMON:[SYSTEST] ............ D-53 D-47 Files in DECEDI$TOP:[000000].............. D-54 D-48 Files in DECEDI$TOP:[TOOLS]............... D-54 D-49 Files in SYS$COMMON:[SYSEXE] ............. D-55 D-50 Files in SYS$COMMON:[SYSHLP] ............. D-55 D-51 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] ...... D-55 D-52 Files in SYS$COMMON:[SYSLIB] ............. D-56 D-53 Files in SYS$COMMON:[SYSMSG] ............. D-56 D-54 Files in SYS$COMMON:[SYSTEST] ............ D-56 x _________________________________________________________________ Preface Product Name: DEC/EDI Version 2.1A Readership This manual is for installers of DEC/EDI. It describes how to install DEC/EDI Version 2.1A. The manual assumes that you are an OpenVMS system manager and have some experience of installing software on OpenVMS systems. Related Books This is one of a set of DEC/EDI books. The complete list is as follows: o DEC/EDI: Installing the OpenVMS Server and Application Client DEC/EDI: Installing the UNIX Application Client DEC/EDI: Cockpit Installing These books describe how to install the DEC/EDI software into the particular environment you are using. They also describe how to run the Installation Verification Procedure. If you are installing DEC/EDI into a mixed environment, for example a Server on OpenVMS and a Client on OSF/1 (UNIX), then you will need to refer to more than one of these books. o DEC/EDI: Introduction This book is an introduction to EDI, and to Digital's EDI system, DEC/EDI. It describes the main components of the system, and how business documents are processed and communicated to trading partners. It introduces the ideas of industry-standard documents and industry- standard communications protocols. xi o DEC/EDI: Getting Started This book gives you an introduction to configuring DEC/EDI. As you work through the book, you configure your DEC/EDI system, following a worked example. o DEC/EDI: Configuring This book describes in detail how to configure the DEC/EDI system for use; in particular the Translation and Communication Services. The book includes many examples of the commands and screens that you use for this task. Refer to DEC/EDI: Command Reference for a full specification of the commands and screens. Refer also to DEC/EDI: Mapping Reference for how to set up the Mapping Service. o DEC/EDI: Mapping Reference This book describes how to configure the Mapping Service. This task involves setting up tables which map the data file formats used by applications onto the data label formats used by DEC/EDI. o DEC/EDI: Command Reference This book provides a full specification of all the management commands for configuring and running the DEC/EDI system. It also explains the screens invoked by these commands. o DEC/EDI: Maintaining This book describes how to run and maintain the DEC/EDI system on a day-to-day basis. You may also want to refer to DEC/EDI: Problem Solving. o DEC/EDI: Problem Solving Refer to this book if you encounter problems when running DEC/EDI. This book helps you to identify each problem, and suggests ways of correcting them. o DEC/EDI: Error Messages This book lists DEC/EDI error and warning messages, and suggests solutions to the problems that caused them. o DEC/EDI: Using the Application Client xii This book describes how to implement application programs that will interface with a DEC/EDI Client. An application can interface to the Client directly, by using C callable routines; or you can use DCL or UNIX commands to pass files of application data to and from the Client. This book gives a full specification of the callable interface routines, and of the command line interface. There is also extensive on-line documentation supplied as part of the DEC/EDI software. Documentation on Tools Supplied with DEC/EDI There are a number of tools provided with the DEC/EDI Server, in the directory DECEDI$TOOLS. Some of the tools have their documentation with them in DECEDI$TOOLS (placed there by the DEC/EDI installation procedure); other tools are documented in the DEC/EDI books. The tools and their documentation are listed below. o DEC/EDI V2.1 Migrate This utility enables you to migrate the contents of an old V1.3 database into a new V2.1 database, and old Filebridge/Mapper databases to the new format. If you are installing DEC/EDI Version 2.1 over a previous version of DEC/EDI there are some important operations you need to do before installation. These are described in DEC/EDI: Installing the OpenVMS Server and Application Client. If you do not follow the recomended procedure you may lose data and configuration information from your system. For more information on this tool see DEC/EDI: Installing the OpenVMS Server and Application Client. o Audit Data Extraction Tool (ADET) This tool gathers information from DEC/EDI audit trails and writes that information to a single output file. You can then use the information in the output file as input to your own reporting programs, to produce reports of archived and live data. xiii The Audit Data Extraction Tool collects information from DEC/EDI's archived and live database. You can specify the type of information it collects, and the format of the records in the output file. For documentation of how to use this tool, see DEC/EDI: Maintaining. o Data Label Generator This tool generates data label definitions for DEC/EDI. It can create data labels for an entire version of a standard, or data labels that are restricted to a trading partner-specific definition of a document within the standard and version. This tool reduces the amount of setup you need to do when installing versions of a standard into DEC/EDI. For documentation on how to use this tool, see either of the following files: DECEDI$TOOLS:DECEDI$DLG_DOC.TXT (ASCII format) DECEDI$TOOLS:DECEDI$DLG_DOC.PS (PostScript format) o Table Extractor and Loader The DEC/EDI Table Extractor and Loader is a tool that enables you to extract or load the table definitions used by the Translation Service. Using this tool, you can extract an existing definition and load it back into the same system, for example, to use with a different version of the document standard, or with a different trading partner. Alternatively you can load the definition into an entirely different DEC/EDI system, for example when upgrading to a later release of the DEC/EDI software. You can also use the Table Extractor and Loader to extract table definitions from a DEC/EDI system installed on OpenVMS VAX and load them into one installed on OpenVMS AXP, and vice versa. The Table Extractor and Loader can extract and load any of the following definitions: - User defined or modified document definitions. - User defined or modified segment, element, sub- element, and code definitions, including data labels. xiv - Trading partner specific document, segment, and element definitions, including data labels. - Value validation definitions. - Code translation definitions. For documentation on using this tool, see either of the following files: DECEDI$TOOLS:DECEDI$TEL_DOC.TXT (ASCII format) DECEDI$TOOLS:DECEDI$TEL_DOC.PS (PostScript format) o DEC/EDI Tailoring Tool This tool enables you to do any of the following: - Move on-line or archive storage directories to a different disk or directory. - Add new on-line or archive storage directories. - Move all or part of the DEC/EDI Archive or Audit Database to a different disk or directory. - Change the size of the DEC/EDI Archive or Audit Database. See DEC/EDI: Maintaining for more information about this tool. o DEC/EDI Database Tuning Tool This tool automatically tunes your Rdb database. The Database Tuning Utility (TEDI) permits users to modify and tune key Rdb database parameters relevant to the performance of DEC/EDI. TEDI is the main tuning tool for the DEC/EDI Rdb database. It is provided as an image called DECEDI$TUNE_ DB.EXE in the directory DECEDI$TOOLS. TEDI allows you to modify the following Rdb audit database parameters: - the number of Rdb users for the database - whether or not to use snapshots. - the number of local & global buffers - whether or not to use global buffers, if so : o the number of global buffers xv o the user limit on global buffers TEDI has two modes of operation: SET and TUNE. The SET option modifies the Rdb database with the parameters you specify. No automatic calculations are performed with this option. The TUNE option calculates the parameters and optionally modifies the Rdb database to the new calculated parameters. The current machine environment is examined to determine the optimum parameter settings. For documentation on how to use this tool, see either of the following files: o DECEDI$TOOLS:DECEDI$TUNE_DB.TXT (ASCII format) o DECEDI$TOOLS:DECEDI$TUNE_DB.PS (PostScript format) xvi 1 _________________________________________________________________ Preparing to Install DEC/EDI This chapter discusses the preparations and requirements necessary for installing DEC/EDI. If you are installing DEC/EDI Version 2.1 over a previous version of DEC/EDI, there are some important facts you need to be aware of and actions you need may need to take before starting. These are described in this chapter. If you do not follow the advice and procedures described here you may lose data or configuration information from your system. Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. If you are upgrading to DEC/EDI Version 2.1 from DEC/EDI Version 1.3A, you are recommended to read DEC/EDI: Introduction to learn the main system level differences you are likely to notice in using DEC/EDI Version 2.1. 1.1 Required Operating System Components One of the following versions of OpenVMS: o OpenVMS VAX Version 6.1 o OpenVMS AXP Version 6.1 Preparing to Install DEC/EDI 1-1 Preparing to Install DEC/EDI 1.2 Prerequisite Software Products 1.2 Prerequisite Software Products The information contained in the following sections define which software products you will need in addition to DEC /EDI for your selected configuration of the DEC/EDI V2.1 products. Where specific versions of software products are listed in the attached, they are believed to be correct at the time this document was created. As newer versions of these software products are released they too may be supported for use in conjunction with DEC/EDI V2.1. For more information, contact your Digital Support representative. 1.2.1 OpenVMS/VAX Server Requirements This section describes the layered products which are needed to run a DEC/EDI server on an OpenVMS/VAX platform. Some products are mandatory, others are optional and depend on which configuration options (for example which DEC/EDI gateways) you select. 1.2.1.1 General Requirements The following products are required for all OpenVMS/VAX server installations: o OpenVMS/VAX o DECforms runtime o Oracle Rdb runtime o DECnet or DECnet/OSI In addition the DEC/EDI FileBridge mapper may extract record layouts from Oracle CDD/Repository, although this is optional. 1.2.1.2 Gateway Requirements You will need to run DECnet/OSI if you are expecting to run any of the following DEC/EDI gateways: o X.25 o OFTP o X.400 1-2 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.2 Prerequisite Software Products o Pedi (X.435) If you are using the X.400 Gateway, you will need to have VAX Message Router and VAX Message Router X.400 Gateway products installed. If you are using the Pedi Gateway, you would normally require the MAILbus 400 Message Transfer Agent. However there is no version of this currently available which supports the version of OpenVMS/VAX required by DEC/EDI V2.1, although this situation may change. To work around this, the DEC/EDI Server contains an X.API component within the kit which needs to be separately installed. This X.API component allows DEC/EDI to connect to a MAILbus 400 Message Transfer Agent (MTA) on another CPU. If you are using the Bisync gateway, you will need the VAX 2780/3780 Protocol Emulator product. If you are using the 3780Plus Gateway, you will need the CLEO 3780Plus product. 1.2.1.3 Application Interface Requirements Your applications may interface to the DEC/EDI V2.1 server on OpenVMS/VAX using one or more of the following interfaces: o Using a DEC/EDI V2 Application Client, either on the same node as the server or on a separate node. o Using the DEC/EDI V1 'data label' API interface on the same node as the DEC/EDI V2 server o Using the DEC/EDI FileBridge CLI or API interfaces on the same node as the DEC/EDI V2 server o Using DEC/EDI V1.3A Application Services on a separate node to the OpenVMS/VAX server. This option requires DECnet (or DECnet/OSI) to link the OpenVMS/VAX server node to the node running DEC/EDI V1.3A Application Services. DEC ACA/ObjectBroker will be required to link the DEC/EDI V2 Application Clients to the server (even if the clients and server are on the same node. DEC ACA/ObjectBroker requires a network layer over which it can connect clients and the server. Preparing to Install DEC/EDI 1-3 Preparing to Install DEC/EDI 1.2 Prerequisite Software Products This network layer may, in general, be provided by DEC TCP/IP Services, DECnet or DECnet/OSI, however other constraints will often influence your choice. If you wish to connect any of the DEC/EDI V2 Application Clients on the following platforms to the OpenVMS/VAX server, then DEC ACA/ObjectBroker requires that all Application Clients use TCP/IP as the network layer to connect to the server: o OSF/1 AXP o HP-UX o IBM AIX If you are not expecting to use any of the above listed DEC/EDI Application Clients, the choice of network layer to use will be influenced by which DEC/EDI gateways you expect to run (or more specifically whether or not those gateways require DECnet/OSI). However all DEC/EDI Application Clients must be connected using the same network layer. 1.2.1.4 Supported Software Versions Given the information in the previous section, Table 1-1 shows the versions of software products that are supported for use with DEC/EDI V2.1 on OpenVMS/VAX. 1-4 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.2 Prerequisite Software Products Table 1-1 OpenVMS/VAX Software Product Versions Supported __________On_DEC/EDI_V2.1__________________________________ SPD Product_Name__________Nos._____Supported_Versions__________ OpenVMS/VAX 25.01 V6.1 DECforms runtime 29.90 V1.4, V2.0 DEC ACA/ObjectBroker 36.06 V2.1, V2.5, V2.5A + /44.12 Oracle Rdb runtime (25.59) V5.1, V6.0 DEC TCP/IP Services 25.A4 V3.1, V3.2 Oracle (25.53) V5.3, V5.3A0 CDD/Repository DECnet/VAX 48.48 V6.1 DECnet/OSI 25.03 V5.7, V5.8 VAX 2780/3780 25.07 V1.8 Protocol Emulator CLEO 3780Plus - V04204 Message Router 26.33 V3.3, V3.3A Message Router, 27.50 V2.3 X.400 Gateway +The_name_DEC_ACA_Services_is_given_to_the_V2.1_product.___ From V2.5 onwards the product is known as ObjectBroker. Usage of ObjectBroker V2.5 or V2.5A refers to the deployment of the 'V2.1 compatibility mode kit' within those products. This installs as ACA V2.1-40. DEC/EDI V2.1 does not make use of the CORBA compliant interfaces of ObjectBroker V2.5. ___________________________________________________________ The name DEC ACA Services is given to the V2.1 product. From V2.5 onwards the product is known as ObjectBroker. Usage of ObjectBroker V2.5 or V2.5A refers to the deployment of the 'V2.1 compatibility mode kit' within those products. This installs as ACA V2.1-40. DEC/EDI V2.1 does not make use of the CORBA compliant interfaces of ObjectBroker V2.5. Preparing to Install DEC/EDI 1-5 Preparing to Install DEC/EDI 1.2 Prerequisite Software Products 1.2.2 OpenVMS/AXP Server Requirements This section describes the layered products which may be needed to run a DEC/ EDI server on an OpenVMS/AXP platform. Some products are mandatory, others are optional and depend on which configuration options (for example which DEC/EDI gateways) you select. 1.2.2.1 General Requirements The following products are required for all OpenVMS/AXP server installations: o OpenVMS/AXP o DECforms runtime o Oracle Rdb runtime o DEC ACA/ObjectBroker o Either DECnet or DECnet/OSI In addition the DEC/EDI FileBridge mapper may extract record layouts from Oracle CDD/Repository, although this is optional. 1.2.2.2 Gateway Requirements If you are using either of the OFTP or X.25 gateways, you need to have installed either: o DECnet/OSI and X.25, or, o DECnet and DEC X.25 Client If you are using the Pedi Gateway, you would normally require the MAILbus 400 Message Transfer Agent. However there is no version of this currently available for OpenVMS /AXP,although this may change. To work around this, the DEC/EDI Server contains an X.API component within the kit which needs to be separately installed. This X.API component allows DEC/EDI to connect to a MAILbus 400 Message Transfer Agent (MTA) on another CPU. DECnet/OSI is required for this. If you are using the 3780Plus Gateway, you will need the CLEO 3780Plus product. 1-6 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.2 Prerequisite Software Products 1.2.2.3 Application Interface Requirements Your applications may interface to the DEC/EDI V2.1 server on OpenVMS/AXP using one or more of the following interfaces: o Using a DEC/EDI V2 Application Client, either on the same node as the server or on a separate node. o Using DEC/EDI V1.3A Application Services on a separate node to the OpenVMS/AXP server. This option requires DECnet (or DECnet/OSI) to link the OpenVMS/AXP server node to the node running DEC/EDI V1.3A Application Services. DEC ACA/ObjectBroker will be required to link the DEC/EDI V2 Application Clients to the server. DEC ACA/ObjectBroker requires a network layer over which it can connect clients and the server. This is required even if clients are on the same node as the server This network layer may, in general, be provided by DEC TCP/IP Services, DECnet or DECnet/OSI. If you wish to connect any of the DEC/EDI V2 Application Clients on the following platforms to the OpenVMS/AXP server, then DEC ACA/ObjectBroker requires that all Application Clients use TCP/IP as the network layer to connect to the server: o OSF/1 AXP o HP-UX o IBM AIX If you are not expecting to use any of the above listed DEC/EDI Application Clients, the choice of network layer to use will be influenced by which DEC/EDI gateways you expect to run (or more specifically whether or not those gateways require DECnet/OSI). However all DEC/EDI Application Clients must be connected using the same network layer. Preparing to Install DEC/EDI 1-7 Preparing to Install DEC/EDI 1.2 Prerequisite Software Products 1.2.2.4 Supported Software Versions Given the information in the previous section, Table 1-2 shows versions of software products that are supported for use with DEC/EDI V2.1 on OpenVMS/AXP. Table 1-2 OpenVMS/AXP Software Product Versions Supported __________On_DEC/EDI_V2.1__________________________________ SPD Product_Name__________Nos._____Supported_Versions__________ OpenVMS/AXP 41.87 V6.1 DECforms runtime 29.90 V1.4D[2] DEC ACA 44.12 V2.1, V2.5, V2.5A /ObjectBroker[1] Oracle Rdb runtime (45.47) V5.1, V6.0 DEC TCP/IP Services 46.46 V3.1, V3.2 Oracle (25.53) V5.3 CDD/Repository DECnet/AXP 42.25 V6.1 DECnet/OSI 50.45 V5.7, V5.8 DEC X.25 Client 46.37 V1.1 X.25 47.37 V1.0a CLEO 3780Plus - V05034 [1]The_name_DEC_ACA_Services_is_given_to_the_V2.1_product._ From V2.5 onwards the product is known as ObjectBroker. Usage of ObjectBroker V2.5 or V2.5A refers to the deployment of the 'V2.1 compatibility mode kit' within those products. This installs as ACA V2.1-40. DEC/EDI V2.1 does not make use of the CORBA compliant interfaces of ObjectBroker V2.5. [2]DECforms V1.4D is a Mandatory Update to V1.4C. Some systems refer to this as the DECforms V1.4C MUP, others as V1.4D. (Saveset names are FORMSMUPD014). V1.4D is a standalone kit that does not require a previous version of DECforms be installed. ___________________________________________________________ 1-8 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.2 Prerequisite Software Products 1.2.3 Requirements for DEC/EDI V2 Application Clients on OpenVMS If you are installing just the Application Client part of either of the OpenVMS/VAX or OpenVMS/AXP kits, the pre- requisite products are: o OpenVMS (for VAX or AXP respectively) o DEC ACA/ObjectBroker o A network transport: provided by DEC TCP/IP Services or DECnet or DECnet/OSI ________________________ Note ________________________ Note that DEC ACA/ObjectBroker requires all Application Clients connected to a single server use the same network transport. ______________________________________________________ 1.3 Registering Your Software License Before you install and run FileBridge V2.1 on a newly licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). 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 FileBridge, review the PAK status and install the PAKs for any prerequisite or optional software before you install FileBridge. You should register your 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 DEC/EDI software. Once you perform the license registration and have loaded an authorization key, you can use DEC/EDI. Preparing to Install DEC/EDI 1-9 Preparing to Install DEC/EDI 1.3 Registering Your Software License To check to see what licenses you already have loaded, use the following command: $LICENSE LIST To register a license under VMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o 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". o 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. For complete information on using LMF, see the manual on the License Management Utility in the OpenVMS documentation set. 1.4 Installation Procedure Requirements The following sections discuss various requirements for installing DEC/EDI. 1.4.1 Time Table 1-3 shows the approximate time it takes to carry out the installation. The times can vary depending on your type of media and your system configuration. Table_1-3_Time_Taken_to_Install____________________________ Type_of_Installation__Time_to_Install_(minutes)____________ OpenVMS VAX Server 30 to 90 and Client OpenVMS VAX Client 5 to 15 only OpenVMS AXP Server 7 to 15 and client (continued on next page) 1-10 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements Table_1-3_(Cont.)_Time_Taken_to_Install____________________ Type_of_Installation__Time_to_Install_(minutes)____________ OpenVMS AXP Client 2 to 5 only_______________________________________________________ 1.4.2 Privileges For The Installing Account To install DEC/EDI, you must be logged in to a suitably privileged account, normally SYSTEM. The account you use must have SETPRV. 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. The installing account must have the process rights identifier ACAS$MANAGER. This is because the installation procedure has to shut down and restart ObjectBroker. If you do not use the SYSTEM account to do the installation, make sure that you use an account with ACAS$MANAGER. 1.4.3 Disk Space Installing DEC/EDI requires a certain amount of free storage disk space during the installation. Once DEC/EDI is installed, less storage space is required. The following tables give the the storage requirements for DEC/EDI: o OpenVMS VAX Server: Table 1-4. o OpenVMS VAX Client: Table 1-5. o OpenVMS AXP Server: Table 1-6. o OpenVMS AXP Client: Table 1-7. Preparing to Install DEC/EDI 1-11 Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements Table_1-4_OpenVMS_VAX_Server:_Disk_Space_Requirements______ Blocks During Disk_____________Installation__Blocks_After_Installation___ System 65,000 50,000 Selected for None 25,000 DEC/EDI data Selected for None 22,000 the_Mapper_________________________________________________ Table_1-5_OpenVMS_VAX_Client:_Disk_Space_Requirements______ Blocks During Disk_____________Installation__Blocks_After_Installation___ System 6,000 1,600 Selected for None 100 DEC/EDI_data_______________________________________________ Table_1-6_OpenVMS_AXP_Server:_Disk_Space_Requirements______ Blocks During Disk_____________Installation__Blocks_After_Installation___ System 90,000 75,000 Selected for None 25,000 DEC/EDI data Selected for None 22,000 the_Mapper_________________________________________________ 1-12 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements Table_1-7_OpenVMS_AXP_Client:_Disk_Space_Requirements______ Blocks During Disk_____________Installation__Blocks_After_Installation___ System 9,000 1,800 Selected for None 100 DEC/EDI_data_______________________________________________ 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 1.4.4 System Parameters For details of the minimum required system parameter values for the installation, see the following tables: o Server and Client installations: Table 1-8. o Client-only installations: Table 1-9. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. Preparing to Install DEC/EDI 1-13 Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements Table 1-8 Server and Client Installations: Required System __________Parameter_Values_________________________________ System_Parameter___________Minimum_Value___________________ CHANNELCNT 255 CLISYMTBL[1] 500 DEFMBXMXMSG 256 DEFMBXBUFQUO 2,048 GBLPAGES 3,350 free global pages GBLPAGFIL 9,216 GBLSECTIONS 84 free global sections WSMAX 8,192 MAXBUF 2,048 MAXPROCESSCNT 64 VIRTUALPAGECNT 60,000 [1]You_must_log_out_and_log_in_again_in_order_to_pick_up___ the new value of CLISYMTBL ___________________________________________________________ Table 1-9 Client-Only Installations: Required System __________Parameter_Values_________________________________ System_Parameter___________Minimum_Value___________________ CHANNELCNT 100 CLISYMTBL[1] 250 DEFMBXMXMSG 256 DEFMBXBUFQUO 1,024 GBLPAGES 1,500 free global pages GBLPAGFIL 8,192 GBLSECTIONS 60 free global sections WSMAX 2,048 MAXBUF 1,024 MAXPROCESSCNT 20 VIRTUALPAGECNT 30,000 [1]You_must_log_out_and_log_in_again_in_order_to_pick_up___ the new value of CLISYMTBL ___________________________________________________________ 1-14 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements The following sections show you how to: o Check system parameter values o Set the DEFMBXBUFQUO dynamic system parameter with the VMS System Generation Utility (SYSGEN) o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the VMS AUTOGEN command procedure 1.4.4.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the SYSGEN utility: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of each system parameter. The values displayed should equal or exceed the value of each parameter listed in Table 1-9 and Table 1-8. The following command displays the value for the DEFMBXBUFQUO system parameter: SYSGEN> SHOW DEFMBXBUFQUO After you finish checking the parameters with the SHOW command, enter EXIT to return to DCL level. 1.4.4.2 Setting the WSMAX System Parameter To increase WSMAX to the minimum value: 1. Edit the file SYS$SYSTEM:MODPARAMS.DAT and add the following line: 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: Preparing to Install DEC/EDI 1-15 Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK For more information about using AUTOGEN, see Guide to Setting Up a VMS System in the VMS documentation on system management. 1.4.4.3 Calculating Values for GBLPAGES and GBLSECTIONS To install and run DEC/EDI, you must set the correct values for the GBLPAGES and GBLSECTIONS system parameters. The values for GBLPAGES and GBLSECTIONS in Table 1-8 and Table 1-9 indicate that you must have at least that many unused pages or sections available on your system for the installation to process successfully. To calculate how many unused global pages and global sections your system has, perform the following steps: 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") To display a summary unused global pages and global sections, enter the following: $WRITE sys$output unused_pages $WRITE sys$output unused_sections 2. Determine if the number of unused pages is equal to or greater than the number specified in Table 1-8 and Table 1-9. If the number of unused pages is less than the number listed in the table, you need to increase the value for GBLPAGES. 3. Note the amount shown for "Global Sections Used". 4. Run the SYSGEN utility and use the SHOW command to determine the number of global sections that have been allocated: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLSECTIONS 1-16 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements 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 1-8 and Table 1-9. The difference between the two is the amount by which you need to increase the current value obtained in Step 4. Note, it is advisable to add a further 10% as contingency in case you expand your system in the future. If you need to change the value of GBLPAGES or GBLSECTIONS: 1. Edit the file SYS$SYSTEM:MODPARAMS.DAT and add a line indicating how many extra GBLPAGES or GBLSECTIONS you need. For example, to add 1000 more GBLPAGES and 300 more GBLSECTIONS, you would add the following lines: ADD_GBLPAGES = 1000 ADD_GBLSECTIONS = 300 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 For more information about using AUTOGEN, see Guide to Setting Up a VMS System in the VMS documentation on system management. 1.4.5 Account Quotas For The Installing Account The account you use to install DEC/EDI must have sufficient quotas to enable you to perform the installation. See the following tables for details of the necessary quotas: o For a server installation: Table 1-10 o For a client installation: Table 1-11 Preparing to Install DEC/EDI 1-17 Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements Table 1-10 Server Installation: Process Account Quotas for ___________the_Installing_Account__________________________ Account_Quota____Value_____________________________________ ASTLM 2,000 BIOLM 300 BYTLM 140,000 DIOLM 300 ENQLM 3,000 FILLM 1,000 JTQUOTA 2,048 PGFLQ 60,000 PRCLM 20 TQELM 1,000 WSDEF 2,048 WSEXTENT 8,192 WSQUO______________4,096___________________________________ Table 1-11 Client Installation: Process Account Quotas for ___________the_Installing_Account__________________________ Account_Quota____Value_____________________________________ ASTLM 25 BIOLM 20 BYTLM 20,000 DIOLM 20 ENQLM 200 FILLM 100 JTQUOTA 1,024 PGFLQ 10,240 PRCLM 5 TQELM 10 WSDEF 1,024 WSEXTENT 4,096 WSQUO______________2,048___________________________________ 1-18 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements User account quotas are stored in the file SYSUAF.DAT. You use the OpenVMS Authorize Utility to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the AUTHORIZE prompt (UAF>), use the SHOW command with the account you are going to use to install DEC/EDI in order to check the particular account. For example: UAF> SHOW SYSTEM To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: MODIFY account-name /quota-name=nnnn This example changes the FILLM quota for the SYSTEM account and then exits from the Authorize Utility: UAF> MODIFY SYSTEM /FILLM=1000 UAF> EXIT 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. For more information on modifying account quotas, see the description of the AUTHORIZE utility in the OpenVMS System Manager's Manual. 1.4.6 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o 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. To stop the installation process and correct the situation, enter NO or press RETURN. Then correct the problem and restart the installation. Preparing to Install DEC/EDI 1-19 Preparing to Install DEC/EDI 1.4 Installation Procedure Requirements 1.4.7 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. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Manager's Manual. 1.5 Reinstalling Note that you cannot install DEC/EDI Version 2.1 on to a system that has a version of DEC/EDI earlier than 1.3A. DEC/EDI stores logical names in two files: o SYS$MANAGER:DECEDI$LOGICALS.COM - this file will be overwritten by future installations of DEC/EDI. Do not change this file. o SYS$MANAGER:DECEDI$SYLOGICALS.COM - this file will not be touched by future installations of DEC/EDI. If you ever want to change any DEC/EDI logical names, define them in this file. 1.5.1 Reinstallation: Client On Top Of Server You can install the DEC/EDI Client on to a system that currently runs the DEC/EDI Server and Client. Then when you configure ObjectBroker as described in Section 3.1 it will be configured for a remote Server and you get a system that is configured to be a Client-only system. If you do install the Client on to a Server node, the installation procedure warns you and asks if you want to continue: ====================================================== WARNING DEC/EDI Server already exists on this node. You have requested a Client only installation. ACAS will be configured for a remote server. Upgrading DEC/EDI Server V2.1 to DEC/EDI Client V2.1 ======================================================= 1-20 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.5 Reinstalling * 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 Client-only system. 1.5.2 Reinstallation: Server On Client-Only System You can install the DEC/EDI Server on to a system that currently runs just the DEC/EDI Client. When you do this, the installation procedures warns you that the Client is already installed and asks you if you want to continue. =========================================================================== DEC/EDI Client already exists on this node. Upgrading DEC/EDI Client V2.1 to DEC/EDI Server V2.1 =========================================================================== * Do you still want to proceed with this installation [YES]? 1.6 Running ACAS with DECNET/OSI for use with DEC/EDI The ACAS V2.1 installation procedure assumes that the SYS$SYSTEM:NETACP.EXE will exist if DECNET exists. This is not the case with DECnet/OSI. To overcome this create a dummy SYS$SYSTEM:NETACP.EXE file to let the installation proceed. You can do this using the VMS command : $ CREATE SYS$SYSTEM:NETACP.EXE Pressing < CTRL Z > will signal the end of the file, create the dummy executable and return you to the DCL command level. ACAS V2.1 installation also assumes that the NETACP process is running if DECNET is running. Again this is not the case with DECnet/OSI. This will cause the installation to complain about an undefined symbol 'ACAS$NETWORK_ACTIVE' but the installation will still proceed successfully. After installation the ACAS IVP will run successfully but complain of the server processes output files being locked when it comes to delete them. These files will however be deleted when the VMS INSTAL procedure completes. Preparing to Install DEC/EDI 1-21 Preparing to Install DEC/EDI 1.6 Running ACAS with DECNET/OSI for use with DEC/EDI Once the installation of ACAS has sucessfully completed you must delete the dummy NETACP.EXE that you created. 1.7 ObjectBroker If you install the DEC/EDI Server on an OpenVMS VAX system without ObjectBroker you will not be able to use the V2 Client. If you wish to instal ACA Services at a later date you need to configure it for DEC/EDI as described in Section 3.1. 1.8 Installing on a Cluster You can install and run DEC/EDI on only a single node in a cluster. You can not run DEC/EDI on more than one node in a cluster. 1.9 Information Needed During Installation DEC/EDI Account Details The installation creates an account for use by DEC/EDI. You must specify a unique user identification code (UIC) for the account. If the account already exists, because you are reinstalling, then you are not asked to specify a UIC. For a first time installation, the rights identifier you assign to the DEC/EDI UIC must not already exist. That is, the identifier must not be the same as one assigned to something else on your system. Where To Put Files If you install the DEC/EDI Server, the installation procedure asks you where to put the DEC/EDI Server and the Mapper files. See Section 1.4.3 for details of how much space you need for these. Name of DEC/EDI Server Node If you are installing a Client-only system, the installation procedure asks you for the name of the DEC/EDI Server node and the name of the operating system the Server is running. 1-22 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.10 Migration Sequence 1.10 Migration Sequence If you have a DEC/EDI V2.0 environment, the order of ugrading to DEC/EDI V2.1 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. Refer to Section 3.14. If you have a DEC/EDI V1.3A environment the upgrade path depends on the configuration of your system. For any configuration there are certain tasks which must be performed after the installation in order to migrate your audit database and applications. Refer to Section 3.14. 1.10.1 All Services on a Single Node Upgrade to a V2.1 server. 1.10.2 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 V2.1 server. The new V2.1 server will support connections from the remote V1.3 Application Service nodes where the remote node is not part of the same OpenVMS cluster. These remote V1.3 Application Service nodes can then be upgraded to V2.1 client nodes as required. 1.10.3 Multinode System with Distributed Translation and Communications This configuration is not supported. You need to move the translation and communications services onto a single node before you can upgrade to a V2.1 server. Contact your support centre if you require more information. Preparing to Install DEC/EDI 1-23 Preparing to Install DEC/EDI 1.11 Migration from V1.3A 1.11 Migration from V1.3A Before installing DEC/EDI V2.1 a V1.3A system must be in an idle state with no failed documents or transmission files, and all File Server ripplebacks and copies completed. In addition, you are strongly recommended to empty the system of EDI data as far as is possible The first step is to deal with any failed documents or transmission files. They should be either reprocessed or cancelled. This is because certain failed statuses no longer exist on V2 and you may not be able to cancel them after the migration. The next step is to stop DEC/EDI processing any new documents. To achieve this do the following :- 1. Stop creating any new documents. 2. Stop fetching available documents. 3. Disable all gateways and connections. 4. Stop all TFB build intervals. Then let the system run until no documents are being processed. When this has happened the Interchange commands :- LIST DOC/STATUS=WORKING/SERVICE=TRANS, and LIST TRANS/STATUS=WORKING should show no records. To get all of the ripplebacks to complete, you need to do the following :- 1. Run DECEDI$TOOLS:DECEDI$CHECK_WF.EXE to force the population of the File Server work files with all history entries with 'Y' flags. 2. Run DECEDI$TOOLS:DECEDI$WHIP to force the File Server to process the work files. 1-24 Preparing to Install DEC/EDI Preparing to Install DEC/EDI 1.11 Migration from V1.3A 3. Wait until the system is quiet and issue the command :- $ SEARCH/NOOUT/STAT DECEDI$DATA:DECEDI$%FSWF.DAT EDI and, if all three files (SFSWF.DAT, TFSWF.DAT and CFSWF.DAT) are not empty then return to step 1 and repeat steps 1 and 2 until the files are empty. Shutdown your system and it is now ready for migration to V2.1. It is strongly recommended that you create a log file of the installation by logging in with: $set host 0 /log as the migration may output messages which you will want to refer to when examining your node configuration after the installation. Preparing to Install DEC/EDI 1-25 2 _________________________________________________________________ Installing DEC/EDI This chapter describes: o Where to find the Release Notes; see Section 2.1. o How to run the installation procedure; see Section 2.5. o How to abort the installation procedure; see Section 2.4. 2.1 Accessing the Online Release Notes 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 DEC/EDI has been installed, the Release Notes are in the following file: SYS$HELP:DECEDI021.RELEASE_NOTES 2.2 Files and Logical Names Added to Your System See Appendix C and Appendix E for lists of all the files and logical names the installation procedure adds to your system. 2.3 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for 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 DEC/EDI is installed correctly. Installing DEC/EDI 2-1 Installing DEC/EDI 2.3 Running the Installation Verification Procedure (IVP) After 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 DEC/EDI is still installed correctly. Use the following command to run the IVP independently: $ @SYS$TEST:DECEDI$IVP.COM See Chapter 4 for more information about the DEC/EDI IVP. 2.4 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. 2.5 Installing DEC/EDI Version 2.1 The following sections describe the first part of the installation procedure. 2.5.1 Shutting Down DEC/EDI If you already have DEC/EDI installed, you must shut down your DEC/EDI system. The command to shut down DEC/EDI is: $ @SYS$STARTUP:DECEDI$SHUTDOWN FULL 2.5.2 Invoking VMSINSTAL To start the installation, log in to a privileged account, such as the SYSTEM account. Next, use the following syntax to invoke VMSINSTAL: @SYS$UPDATE:VMSINSTAL product-name device-name OPTIONS N product-name The installation name for the product. For DEC/EDI Version 2.1, use the following installation names: o On OpenVMS VAX: DECEDI021 o On OpenVMS AXP: DECEDIA021 2-2 Installing DEC/EDI Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 device-name 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. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is completed. Note that device-name can also be a directory specification, if you have the save-sets on disk. OPTIONS N An optional parameter that indicates you want to be prompted to display or print the Release Notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not prompt you to display or print the Release Notes. VMSINSTAL has several other options; for information, see the OpenVMS documentation on software installation. The following example invokes VMSINSTAL to install DEC/EDI from tape drive MTA0:, and shows the system response. This example uses the OPTIONS N parameter for printing or displaying Release Notes. $ @SYS$UPDATE:VMSINSTAL DECEDIA021 MTA0: OPTIONS N OpenVMS ALPHA Software Product Installation Procedure V1.5 It is 6-MAY-1994 at 13:49. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later on in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the Release Notes during the installation. Installing DEC/EDI 2-3 Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 2.5.3 Questions for Server With Client Installation This section describes the questions that appear during the installation if you are installing both the DEC/EDI Server and the DEC/EDI Client. See Appendix A for a sample installation log. 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. 1. System backup * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. 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. Otherwise, enter NO to discontinue the installation. After you backup your system disk, you can restart the installation. 2. Mounting the media * Where will the distribution volumes be mounted: OpenVMS asks you where you want to mount the distribution volumes. Enter the device name. The DEC/EDI disk must be mounted system-wide (/SYSTEM). 3. Release Notes If you specified OPTIONS N when you invoked VMSINSTAL, you are now given options for reading the Release Notes. (The options may not be the same as those here, depending on your version of OpenVMS.) Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 2-4 Installing DEC/EDI Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 Enter 1 to display the Release Notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. Enter 2 to print the Release Notes. VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: Enter a queue name or press RETURN to send the file to the default output print device. Because Release Notes can be quite long, it is recommended that you use option 2 to print them. 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. 4. Continuing the installation The installation procedure now asks if you want to continue the installation. To continue, enter YES. Otherwise, press RETURN. In either case, the Release Notes are 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:DECEDI021.RELEASE_NOTES ________________________ Note ________________________ The name of the Release Notes file installed by VMSINSTAL consists of the current product name and version number. ______________________________________________________ 5. Choosing to purge files You have the option to purge files from previous installations of DEC/EDI that are superseded by this installation. Purging is recommended; however, if you need to keep files from previous installations, enter Installing DEC/EDI 2-5 Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 NO in response to the question. You may need to keep some of the files in the DECEDI$DATA directory: see Section 1.5 before proceeding. * Do you want to purge files replaced by this installation [YES]? 6. Running the IVP The installation procedure asks if you want to run the IVP once the installation is complete. * 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. 7. Opting to install the server The install procedure asks if you want to install the DEC/EDI server: * Do you want to install the server [YES]? You can install either of the following: o The DEC/EDI server and the DEC/EDI client. o Just the DEC/EDI client. Enter YES to install the server and the client. Enter NO to install just the client. 8. Optional Software and Licenses The installation procedure checks to see if all the optional software for your hardware platform is installed, as listed in Section 1.2. It also checks that the DEC/EDI licenses are installed. If any of the optional software is not installed, or if any of the licenses are not installed the procedure displays a message telling you so. For example: The following DEC/EDI component(s) are not licensed on this node ================================================================= DEC/EDI OFTP Services V2.1 DEC/EDI OFTP-Package Services V2.1 Note that the message does not necessarily mean that there is an error; the procedure checks for all optional software and all possible licenses. 2-6 Installing DEC/EDI Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 When it has completed the checks, the installation procedure asks if you want to continue with the installation: * Do you still want to proceed with this installation [YES]? The installation procedure also checks that mandatory prerequisite software has been installed and licensed. See Section 1.1 for details of the mandatory software. 9. RDB/VMS specification The following versions of Rdb/VMS are available: V4.2-0 *V5.1-0 * Please enter the Rdb/VMS version to be used by DEC/EDI [*V5.1-0]: *v5.1-0 Current PROCESS DEC Rdb environment is version V5.1-0 (MULTIVERSION) You must have RDB/VMS version 5.1 or later installed on your system to use DEC/EDI V2.1 10.Warning if you are reinstalling If you are reinstalling, you get a warning message, telling you that the new installation will overwrite data files that you may have changed. ================================================== DEC/EDI already exists on this node Installation of DEC/EDI will retain data integrity Upgrading DEC/EDI V2.1 to V2.1 ================================================== If you want to keep the data from these files, you should make safe copies of them before you continue with the installation. 11.Migrating mapper databases ================================================================== WARNING: The structure of all mapper databases needs to be modified. All previous FileBridge databases and DEC/EDI V2.1 mapper databases will need to be migrated before using the DEC/EDI V2.1 mapper. Installing DEC/EDI 2-7 Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 To migrate the live and test databases in FBR$HOME run the post-installation task DECEDI$V21_MIGRATE.COM. Migration of all local test databases should be done using FBR$ARCHIVE.COM. Read the release notes for details. ================================================================== 12.Specifying the directory for DEC/EDI data VMSINSTAL asks you where it should put the DEC/EDI directories. 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. * On what device should the DECEDI directories reside? See Section 1.4.3 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 DEC/EDI system is running. If the DECEDI account already exists, then the installation procedure uses the existing DECEDI directory specification. 13.New Installations: Specifying where to put the FileBridge directories The installation procedures asks where to to put the FileBridge directories: Enter the device and directory specification for FBR$HOME. * Directory name [SYS$SYSDEVICE:[FILEBRIDGE]]: The logical name FBR$HOME specifies the top-level directory under which the FileBridge (Mapper) audit databases and history directories reside. 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, or FBR$DEVELOPMENT. 2-8 Installing DEC/EDI Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 The first time you install FileBridge, you are must specify a location for FBR$HOME. VMSINSTAL then creates a LIVE database using a directory name created from a timestamp and a TEST database using the directory name TEST_DB. DEC/EDI FileBridge stores its audit database files and its history files in directories below that pointed to by FBR$HOME. The size of these files can grow significantly as you use the system. 14.Reinstallations: Specifying where to put the FileBridge directories If you are reinstalling FileBridge, the installation examines the values of the system logicals for FBR$HOME and FBR$LIBRARY. If these logicals are defined, you can choose whether to accept the current primary database or to create a new one. The current Mapper primary database has been determined from the state of the system. You can keep this database as your primary database, or create a new primary database. If you create a new primary database, then the current database will be switched to a history database. The current primary database is DISK$USER02:[FILEBRIDGE.940412132737.FBR$DB] If you want to change the value of FBR$HOME, the installation will proceed like an initial installation and request the location for FBR$HOME. If you accept the current value of FBR$HOME, you will be asked if you want to keep the existing primary database. The current primary database has been determined from the state of the system. You can keep this database or change it. If you change it, the current database will be switched to history. The current primary database is SYS$SYSDEVICE:[FILEBRIDGE.940129171341.FBR$DB] * Do you want to change the primary database [NO]? If you decide to change the primary database, a new database will be created and the current one switched to history. Installing DEC/EDI 2-9 Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 If the installation does not find system logicals for FBR$HOME and FBR$LIBRARY, it tries to determine these logicals from the DECEDI$STARTUP.COM file. In this case, it issues a warning: ****************WARNING**************************** The locations of FBR$HOME and the primary database have been determined from the current state of the system. You will be given an opportunity later in the installation change these. You must be certain that the values are currently valid if you decide to accept them. ***************************************************** If your system already has FileBridge audit database files, the installation procedure uses the current location, but gives you the option to create a new primary database: * Do you want to change the value of FBR$HOME [NO]? If you do create a new primary database, your the old one becomes a history database. Enter NO to keep using your current primary database. Enter YES to create a new primary database. 15.Specifying the account UIC * What is the UIC to be used for the DEC/EDI account: [400,1] VMSINSTAL asks you for the UIC that you want to allocate to the DECEDI account. You must enter the UIC in the form [x,y]. For example: [500,1] or [MYGROUP,EDI]. There are a number of restrictions, as follows: o The UIC chosen must not have a rights identifier already allocated to it. The UIC must not be used by anything else. o The UIC must be valid. o The group number (the first value) cannot be less than, or equal to, 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 DEC/EDI will reject it. 2-10 Installing DEC/EDI Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 2.5.4 Questions For Client-Only Installation This section describes the questions that appear during the installation if you are performing a Client-only installation. See Appendix A for a sample installation log. 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. 1. System backup * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press the key. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 2. Mounting the media * Where will the distribution volumes be mounted: OpenVMS asks you where you want to mount the distribution volumes. Enter the device name. The DEC/EDI disk must be mounted system-wide (/SYSTEM). 3. Release Notes If you specified OPTIONS N when you invoked VMSINSTAL, you are now given options for reading the Release Notes. (The options may not be the same as those here, depending on your version of OpenVMS.) Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: Installing DEC/EDI 2-11 Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 Enter 1 to display the Release Notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. Enter 2 to print the Release Notes. VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: Enter a queue name or press RETURN to send the file to the default output print device. Because Release Notes can be quite long, it is recommended that you use option 2 to print them. 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. 4. Continuing the installation The installation procedure now asks if you want to continue the installation. To continue, enter YES. Otherwise, press RETURN. In either case, the Release Notes are 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:DECEDI021.RELEASE_NOTES ________________________ Note ________________________ The name of the Release Notes file installed by VMSINSTAL consists of the current product name and version number. ______________________________________________________ 5. Choosing to purge files You have the option to purge files from previous installations of DEC/EDI that are superseded by this installation. Purging is recommended; however, if you need to keep files from previous installations, enter 2-12 Installing DEC/EDI Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 NO in response to the question. You may need to keep some of the files in the DECEDI$DATA directory: see Section 1.5 before proceeding. * Do you want to purge files replaced by this installation [YES]? 6. Running the IVP The installation procedure asks if you want to run the IVP once the installation is complete. * 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. 7. Opting to install the server The install procedure asks if you want to install the DEC/EDI server: * Do you want to install the server [YES]? You can install either of the following: o The DEC/EDI server and the DEC/EDI client. o Just the DEC/EDI client. Enter NO to install just the client. Enter YES to install the server and the client. 8. Specifying the directory for DEC/EDI data VMSINSTAL asks you where it should put the DEC/EDI directories. 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. * On what device should the DECEDI directories reside? See Section 1.4.3 to find out how much free space you need on this device. If the DECEDI account already exists, then the installation procedure uses the existing DECEDI directory specification as the default. Installing DEC/EDI 2-13 Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 9. Specifying the account UIC * What is the UIC to be used for the DEC/EDI account: VMSINSTAL asks you for the UIC that you want to allocate to the DECEDI account. You must enter the UIC in the form [x,y]. For example: [500,1] or [MYGROUP,EDI]. There are a number of restrictions, as follows: o The UIC chosen must not have a rights identifier already allocated to it. The UIC must not be used by anything else. o The UIC must be valid. o The group number (the first value) cannot be less than, or equal to, 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 DEC/EDI will reject it. 10.Specifying the name of the DEC/EDI Server Node The installation procedure asks you for the name of the node where the DEC/EDI Server will run: * What is the name of the node on which the DEC/EDI Server will run: Enter the name of the remote node where the DEC/EDI Server will run. 11.Identifying the type of DEC/EDI Server The installation procedure asks you whether the remote Server is running OpenVMS VAX or OpenVMS AXP: The following is a list of supported Server types : 1 - OpenVMS AXP 2 - OpenVMS VAX * Please select the Server type from the above list: Enter 1 if the remote server is running OpenVMS VAX. Enter 2 if the remote server is running OpenVMS AXP. 2-14 Installing DEC/EDI Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 2.5.5 Informational Messages At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If you are reinstalling, you get the following message: %FBR-F-EXISTS, Database already exists in target directory. You can ignore this message. 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. This procedure may take some time. At the end of the installation the installation procedure displays the following message: Installation of DEC/EDI succeeded. 2.5.6 Running the Installation Verification Procedure If you chose to run the IVP, VMSINSTAL runs it now. The IVP checks that all the specified files have been installed. When the IVP runs successfully, you see the following display: IVP was successful. When the IVP does not run successfully, you see the following display: IVP for DEC/EDI V2.1 has failed 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. To do this, enter the following command: $ @SYS$TEST:DECEDI$IVP.COM /OUTPUT="file.ext" Installing DEC/EDI 2-15 Installing DEC/EDI 2.5 Installing DEC/EDI Version 2.1 2.5.7 Completing the Installation Procedure The following messages indicate that the entire installation procedure is complete: Installation of DECEDIA V2.1 completed at 14:05 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA021.VMI_DATA VMSINSTAL procedure done at 14:06 You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 15-JUL-1991 10:09:17.22 Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2.6 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of DEC/EDI V2.1 has failed. If the IVP fails, the following messages are displayed: IVP for DEC/EDI V2.1 has failed to execute to completion. %VMSINSTAL-E-IVPFAIL, The IVP for DEC/EDI V2.1 has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o A prerequisite software version is incorrect o Quotas necessary for successful installation are insufficient o System parameter values for successful installation are insufficient o The OpenVMS help library is currently in use 2-16 Installing DEC/EDI Installing DEC/EDI 2.6 Error Recovery 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.) For information on installation requirements, see Chapter 1. Installing DEC/EDI 2-17 3 _________________________________________________________________ After Installing After installing DEC/EDI and the document standards (see Appendix B), you may need to perform the following tasks: o Configure the ACA Services o Edit the system startup and shutdown files o Reboot the system o Change account details for those people who are going to use the DEC/EDI INTERCHANGE command o Migrate data if upgrading from a previous version of DEC/EDI earlier than Version 2.1 This chapter also explains how to run the Installation Verification Procedure (IVP) after you have installed the software. 3.1 Configuring ACA Services for DEC/EDI If you want to use the client you need to configure ACA Services for DEC/EDI. This can be done after the installation if you have ACA Services installed, or at a later date when you have installed it. To configure ACA Services run the command file: $@DECEDI$TOOLS:CONFIGURE_ACAS.COM 3.2 Editing the System Files This section applies to: DEC/EDI Server systems You must edit the system startup and shutdown files to provide for automatic startup and shutdown of DEC/EDI when your system is rebooted. After Installing 3-1 After Installing 3.2 Editing the System Files There are three possible DEC/EDI modes of startup: ___________________________________________________________ Mode_____________Startup_Command___________________________ Full startup[1] @SYS$STARTUP:DECEDI$STARTUP FULL Partial startup @SYS$STARTUP:DECEDI$STARTUP Mapper only @SYS$STARTUP:DECEDI$STARTUP MAPPER startup [1]The_command_for_a_full_startup_must_come_after_the______ command_that_starts_Rdb_Monitor.___________________________ Add the command line that starts DEC/EDI to the system startup file. You must position this new command line after the line that invokes the network startup command procedure. The following table shows the name for the system startup command: ___________________________________________________________ Operating_System______Startup_File_________________________ OpenVMS VAX Version SYS$MANAGER:SYSTARTUP_VMS.COM 6.0 and later OpenVMS_AXP___________SYS$MANAGER:SYSTARTUP_VMS.COM________ The following example shows the network startup and Rdb Monitor startup command lines, followed by the startup command line for DEC/EDI: $ @SYS$MANAGER:STARTNET.COM . $ @SYS$STARTUP:RMONSTART.COM . $ @SYS$STARTUP:DECEDI$STARTUP.COM FULL You need to add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @SYS$STARTUP:DECEDI$SHUTDOWN.COM FULL ________________________ Note ________________________ When you shutdown your system you must ensure that DEC/EDI closes down before DECnet and/or P.S.I., and 3-2 After Installing After Installing 3.2 Editing the System Files before Rdb Monitor. ______________________________________________________ DEC/EDI uses the symbols DECEDI$DEFINE and DECEDI$DEASSIGN to define and deassign its logical names. The symbols, and all the logical names, are defined by the command procedure SYS$MANAGER:DECEDI$LOGICALS.COM. 3.3 Defining DEC/EDI Logical Names This section applies to: DEC/EDI Server systems DEC/EDI Client systems DEC/EDI stores logical names in two files: o SYS$MANAGER:DECEDI$LOGICALS.COM - this file will be overwritten by future installations of DEC/EDI. Do not change this file. o SYS$MANAGER:DECEDI$SYLOGICALS.COM - this file will not be touched by future installations of DEC/EDI. If you ever want to change any DEC/EDI logical names, define them in this file. 3.4 Modifying DECforms Logical Names This section applies to: DEC/EDI Server systems running on OpenVMS AXP with DECforms Version 1.4B If you are using the DEC/EDI Server, on an OpenVMS AXP system with DECforms Version 1.4B, you must uncomment some DECforms logical definitions in the following file: SYS$STARTUP:FORMS$STARTUP.COM The logical name definitions to uncomment are the following: $! $! DEFINE/SYSTEM/EXEC FORMS$MANAGER_TV SYS$LIBRARY:FORMS$MANAGER.EXE $! DEFINE/SYSTEM/EXEC FORMS$CIOSHR_TV SYS$LIBRARY:FORMS$CIOSHR.EXE $! DEFINE/SYSTEM/EXEC FORMS$PORTABLE_API_TV SYS$LIBRARY:FORMS$PORTABLE_API.EXE There is more information about these logical names in FORMS$STARTUP.COM. After Installing 3-3 After Installing 3.5 Using the Correct Pascal Run-Time Library 3.5 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. OpenVMS AXP Version 6.1 does not provide a Pascal run-time library. 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. 3.6 Enhancing DEC/EDI Security This section applies to: DEC/EDI Server systems DEC/EDI provides a high level of security, through the use of access rights, but you can provide a still greater level of security by using OpenVMS Access Control Lists (ACLs) on the Application Server mailbox, DECEDI$AFS_MBX. By restricting access to this mailbox, you ensure that an application cannot access DEC/EDI data unless the user running the application has access to the mailbox. To protect the mailbox, use an access control list (ACL). Create an access control entry (ACE) in the ACL for each user or group of user that require access to the mailbox. To avoid setting an ACL each time you start up your system, include the ACL definition in the system startup file. Typical protection to set up might be: o System: READ + WRITE + EXECUTE +DELETE + CONTROL o DECEDI: READ + WRITE + EXECUTE + DELETE o Specified user accounts: READ + WRITE o All other accounts: Deny all access A DEC/EDI Client that is on the same node as the DEC/EDI Server accesses the mailbox using the account that issued the Client calls. A DEC/EDI Client that is on a remote node from the DEC/EDI Server uses the DECEDI account to access the mailbox. 3-4 After Installing After Installing 3.6 Enhancing DEC/EDI Security To make sure that that the protection applies as soon as possible after the mailbox is created, put the commands to create the ACL immediately after the DEC/EDI startup command: $ @SYS$STARTUP:DECEDI$STARTUP FULL An example set of commands to do this follows: $ SET ACL /OBJECT=DEVICE DECEDI$AFS_MBX - /ACL=(IDENTIFIER=*, ACCESS=NONE)) $ SET ACL /OBJECT=DEVICE DECEDI$AFS_MBX - /ACL=(IDENTIFIER=SYSTEM, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) $ SET ACL /OBJECT=DEVICE DECEDI$AFS_MBX - /ACL=(IDENTIFIER=DECEDI, ACCESS=READ+WRITE+DELETE) $ SET ACL /OBJECT=DEVICE DECEDI$AFS_MBX - /ACL=(IDENTIFIER=TIMG, ACCESS=READ+WRITE) $ SET ACL /OBJECT=DEVICE DECEDI$AFS_MBX - /ACL=(IDENTIFIER=LSMITH, ACCESS=READ+WRITE) See the Introduction to VMS System Management and the OpenVMS VAX Guide to System Security for more information about ACLs and ACEs. 3.7 Modifying the System Page File Size This section applies to: DEC/EDI 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 DEC/EDI process that you run, up to a maximum of 20,000 blocks for 20 processes. You cannot do this until you have DEC/EDI running, because the number of DEC/EDI processes depends on your configuration. Once you have DEC/EDI configured, you can find out how many DEC/EDI processes there are on your system by using the DCL command SHOW SYSTEM. The name of every 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 After Installing 3-5 After Installing 3.7 Modifying the System Page File Size 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. See also Section 1.4.4 for more details on how to use SYSGEN and AUTOGEN, or refer to the OpenVMS documentation on system management and operations for more information. 3.8 Rebooting the System This section applies to: DEC/EDI Server systems DEC/EDI Client systems A system reboot: o Enables you to get DEC/EDI ready for use o (Server systems only) Ensures that the edits to the system startup command file are correct o Establishes any new parameter settings Note, however, that rebooting is optional. You can reboot your system after you have installed DEC/EDI, edited the system startup and shutdown files, and reset the system parameters if necessary. 3.9 Renaming the DEC/EDI Error Log This section applies to: DEC/EDI Server systems 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. 3-6 After Installing After Installing 3.9 Renaming the DEC/EDI Error Log You can reduce the speed with which the error log grows by defining the logical name DECEDI$LOG_SEVERITY to be "WARNING". This restricts 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 3.10 Modifying User Accounts This section applies to: DEC/EDI Server systems Page File Quota You must make sure that the account for each person who is going to use the 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 DEC/EDI Client to communicate with the DEC/EDI Server, then all user accounts that will use the Client interface must have the following: o The DEC/EDI FBR$OPERATIONS process rights identifier. o The same minimum account quotas as for the DECEDI account, as specified in Table 3-1. See Section 3.13 for a description of the following process rights identifiers: FBR$SUPERVISOR FBR$DEVELOPMENT FBR$OPERATIONS 3.10.1 Adding Symbols to User's LOGIN.COM For the 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 After Installing 3-7 After Installing 3.11 Determining and Reporting Problems 3.11 Determining and Reporting Problems If an error occurs while DEC/EDI is being used and you believe that the error is caused by a problem with DEC/EDI, take one of the following actions: o 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.) o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you purchased 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). If you find an error in the 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 number where the error was found. 3.12 The DECEDI Account This section applies to: DEC/EDI Server systems DEC/EDI Client systems The installation creates an account with a username of DECEDI. This account has only network access, and has the quotas listed in Table 3-1. These quotas are required to run DEC/EDI. Note, the DECEDI account is used only by DEC/EDI processes, not DEC/EDI users. 3-8 After Installing After Installing 3.12 The DECEDI Account Table_3-1_Quotas_for_the_DECEDI_Account____________________ 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___________________________________ If you are planning to use the V1.3 Support Services then, depending on the throughput of traffic, it may be necessary to increase the value of the DECEDI account quotas. 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. It may also be necessary to increasing some 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, then these are likely to be symptoms that the quotas are too low. 3.12.1 Increasing Disk Quota This section applies to: DEC/EDI Server systems After Installing 3-9 After Installing 3.12 The DECEDI Account If disk quotas are enabled on the system disk, or any disk that you use for 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 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 3.12.2 Calculating the Required Number of Processes This section applies to: DEC/EDI Server systems Once you have installed DEC/EDI you may need to modify the quota depending upon the number of processes you wish to run. In order to calculate the required number of processes you should do the following: o Determine the number of extra application file servers (XAFS) required. o Determine the number of extra EDIFACT converters (XEDIFC) required. o Determine the number of extra EDIFACT translators (XEDIFT) required. o Determine the number of extra X12 converters (XX12C) required. o Determine the number of extra X12 translators (XX12T) required. o Determine the number of extra TRADACOMS converters (XTCOMC) required. 3-10 After Installing After Installing 3.12 The DECEDI Account o Determine the number of extra TRADACOMS translators (XTCOMT) required. o Determine the number of gateways required. The total number of DEC/EDI processes is the sum of the processes in Table 3-2: Table_3-2_DEC/EDI_Processes________________________________ Process_______________Number_______________________________ Data Server 1 Communication 1 Control Import/Export 1 (optional) Gateway 3780Plus Gateway 1 (optional) X.400 Gateway 1 (optional) OFTP Gateway 1 (optional) X.25 Gateway 1 (optional) X.435 Gateway 1 (optional) Bisync Gateway 1 (optional) EDIFACT Service 4 + XEDIFC + XEDIFT (optional) (incl. ODETTE) X12 Services (incl. 3 + XX12C + XX12T (optional) TDCC) TRADACOMS 2 + XTCOMC + XTCOMT (optional) Application File 1 + XAFS (optional) Server_____________________________________________________ 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 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. After Installing 3-11 After Installing 3.12 The DECEDI Account ________________________ Note ________________________ We recommend that the minimum value for MAXPROCESSCNT is 64. ______________________________________________________ 3.12.3 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 DEC/EDI Server systems. 3.12.3.1 Calculating the WSEXTENT Value To calculate the value of WSEXTENT, do the following: To make sure the 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: o WSEXTENT sizes are in pages (512 bytes) o external_document_size is the size, in Kbytes, of the external format file created by the converter. For example, for 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 3-1, you should increase the DECEDI account value. If it is smaller, keep the default value because other 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. 3-12 After Installing After Installing 3.12 The DECEDI Account 3.12.3.2 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. EDIT PROFILE sets up various parameters which control the number of documents that can be placed in a transmission file. These are: o TPF_MDPG_L, Maximum documents per group o TPF_MGPI_L, Maximum groups per interchange o 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 3.12.4 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 DEC/EDI will fail. 3.12.5 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 DEC/EDI processes can communicate. You should not need to modify the privileges granted to the DECEDI account. After Installing 3-13 After Installing 3.13 Defining FileBridge Rights 3.13 Defining FileBridge Rights FileBridge security facilities prevent accidental insertion or loss of documents and reduce the risk of fraudulent use of FileBridge processing. FileBridge security facilities make use of OpenVMS rights identifiers. You will need to make sure that each person who is going to use FileBridge has been assigned at least one of the following FileBridge rights. The installation procedure has already added them to the OpenVMS rights database, but they must be assigned to each FileBridge user manually. o FBR$SUPERVISOR o FBR$DEVELOPMENT o FBR$OPERATIONS The OpenVMS documentation on the AUTHORIZE Utility explains how to assign an identifier to a user. 3.13.1 The Rights Database The OpenVMS rights database provides the security facilities for FileBridge. At most sites, the rights facility's system manager maintains this database. To use FileBridge, you must be assigned one or more of the three FileBridge 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 FileBridge 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. 3-14 After Installing After Installing 3.13 Defining FileBridge Rights 3.13.1.1 FBR$SUPERVISOR When assigned FBR$SUPERVISOR, you can edit the FileBridge 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 FileBridge 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: o FileBridge tables. The TEST INDICATOR option in the FileBridge table should not be set to LIVE until the table has been copied from the development environment into the production library. This should not be FBR$LIBRARY directory but could be a subdirectory under FBR$HOME. The supervisor must also set the options to enable the audit and history points as required by the installation, and then compile the FileBridge table. o 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 FileBridge rights, plus any access for FBR$SUPERVISOR. The database must be created with granted rights of INSERT and READ for the EVENT relation. o Hook Shared Images. Since part of FileBridge 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. After Installing 3-15 After Installing 3.13 Defining FileBridge Rights The supervisor must set the Shared Image filename in the FileBridge table to point to the appropriate directory before compiling the table. o 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. 3.13.1.2 FBR$DEVELOPMENT Assignment to the FBR$DEVELOPMENT category allows the user to create and modify FileBridge tables using the User Interface, but the TEST INDICATOR option cannot be set to LIVE. This user can also execute the FileBridge runtime program, but cannot use it with a FileBridge table that has the TEST INDICATOR option set to LIVE. If for any reason a fetch for 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. 3.13.1.3 FBR$OPERATIONS With this right, the user can execute the FileBridge runtime program using a FileBridge table that has the TEST INDICATOR set to LIVE. If the FileBridge runtime program gets a document with a TEST INDICATOR not set to LIVE while processing documents with a FileBridge 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. 3.14 Data Migration After the installation the following migration needs to be performed :- o Audit database o Archive database o Mapper database o TRAX gateway 3-16 After Installing After Installing 3.14 Data Migration A command file DECEDI$TOOLS:DECEDI$V21_MIGRATE.COM has been provided for this. It is strongly recommended that you create a log of any output produced by the migration by logging in using :- set host 0 /log before issuing the command. The command file takes a single parameter which can be one of the following :- o AUDIT_DB - Only the audit database migration will be performed. o ARCHIVE_DB - Only the archive database migration will be performed. o MAPPER_DB - Only the mapper database migration will be performed. o TRAX - Only the TRAX gateway will be migrated. If no parameter is specified all actions will be performed. 3.14.1 Using the AUDIT_DB Option The following logicals need to be defined in SYS$MANAGER:DECEDI$SYLOGICALS.COM :- o DECEDI$AUDIT_DB must point to the new V2.1 Rdb database. o DECEDI$AUDIT_DB_OLD must point to the old Rdb database. o DECEDI$PREVIOUS_VERSION must point to the previous EDI version, e.g. "1.3", "2.0", etc. These logicals should have been set up by the installation itself. The V2.1 database, by default is created in the directory DECEDI$TOP:[AUDIT_DB]. This is different from the default location of DECEDI$TOP:[AUDIT_DATABASE] for the V1.3 or V2.0 database. If the migration fails your old database will be unchanged so the procedure can be re-run after creating a new empty V2.1 database by running DECEDI$TOOLS:DECEDI$DB_CREATE.EXE. After Installing 3-17 After Installing 3.14 Data Migration 3.14.1.1 Migrating from a Distributed V1.3 System This configuration is not fully supported by the migration so there are some manual tasks that need to be done if you have been running with a distributed V1.3 system and haven't removed all documents and transmission files which have gone to, or originated from, remote translation or communication services. There are two possible outcomes from the migration :- 1. Documents and transmission files identified by the migration For those that can be identified from the audit trail you will see messages saying that these documents and transmission files have been rejected. If this is the case no entry will have been made for them in the V2.1 database. When you have completed the migration all files for these documents and transmission files will need to be manually removed from the store directories. 2. Transmission files not identified by the migration If you have transmission files which are migrated to the V2.1 database but already exist on another node you need to cancel them if possible or, if they are not PURGEABLE, manually remove then using SQL before starting up the gateway. Otherwise you could get duplicate files sent to a partner or duplicate documents processed by applications. Contact your support centre for more information. 3.14.2 Using the ARCHIVE_DB Option This parses the contents of the existing Archive Files in DECEDI$ARCH_DATA and moves any document and/or transmission file records to the new Rdb Archive Database whose root is indicated by the logical DECEDI$ARCHIVE_DB. The files themselves remain in the Archive Store Directories, although V2.1 does not add any further files to these directories. After performing an Interchange Archive these directories become empty and you should remove them from your system together with the archive store logicals. 3-18 After Installing After Installing 3.14 Data Migration Because the Archive Server now leaves archived files in the live store directories, you should consider increasing the number of store directories using the Tailoring Tool. 3.14.3 Using the MAPPER_DB Option This will migrate the live and test Mapper databases. All previous FileBridge databases and DEC/EDI V2.0 Mapper databases will need to be migrated before using the DEC/EDI V2.1 Mapper. The following logicals need to be defined: o FBR$LIBRARY must point to the live Mapper Rdb Database o FBR$TESTLIB must point to the test Mapper Rdb Database The above logicals are defined when a minimal startup of the EDI server is performed. They will remain defined after a full shutdown. Alternatively run the following command files: $ @SYS$STARTUP:DECEDI$DEFINE_MAPPER_LOGICALS.COM $ @SYS$STARTUP:DECEDI$SET_MAPPER_DATABASE.COM The installation procedure places the definition of FBR$LIBRARY in SYS$STARTUP:DECEDI$SET_MAPPER_DATABASE.COM. If you change the live database, the definition must be changed in this command file. FBR$TESTLIB is defined in SYS$STARTUP:DECEDI$DEFINE_MAPPER_LOGICALS.COM. If you change the test database, the definition must be changed in this command file. Before viewing using any Mapper databases, other than the two abve, they must be migrated using the following command: $ @FBR$EXE:FBR$ARCHIVE MIGRATE All new databases created with FBR$EXE:FBR$ARCHIVE.COM will be of the new structure. 3.14.4 Using the TRAX Option This option modifies existing TRAX transmission files to enable automatic tracking of transmission files versus TRADANET document references. To perform the migration you must have your TRADANET User Number (TUN). After Installing 3-19 After Installing 3.15 Additional Post Installation Tasks for Migration from V1.3A 3.15 Additional Post Installation Tasks for Migration from V1.3A 3.15.1 Node Configuration It is recommended that you check your node configuration using the Interchange command EDIT CONFIGURATION as follows :- o Select Maintain Services This should list the services you require on the V2.1 server. An entry for application services is no longer required for running applications so this will have been removed. If the installation detected remote V1.3 application service nodes it will have added an entry for V1.3 support services. Any remote application nodes will have been registered (see Register Nodes below). o Select Register Applications This will show the applications which supply documents to the translation services as on your V1.3 system. The node name no longer appears, instead the application will have been registered for the node (see Register Nodes below). o Select Register Site To Site Agreements This is a new option in EDIT CONFIGURATION which replaces the ROUTE commands used in V1.3. All entries on this display will be handled as site to site documents. Any entries in your V1.3 Site Routing Table which were identified as not being site to site will have been removed. As above, the node name no longer appears, instead the partner application will have been registered for the node (see Register Nodes below). o Select Register Nodes This is a new option in EDIT CONFIGURATION which is used to register remote nodes together with the applications which will run on those nodes. The current node also has an entry. Select each node and then select the Register Client Applications option. This list of applications should include all applications for that node and if the node is a remote V1.3 node they will be marked as V1.3. 3-20 After Installing After Installing 3.15 Additional Post Installation Tasks for Migration from V1.3A 3.15.2 EDIFACT UNS Segment Handling Changes DEC/EDI document definitions now cater for changes in document areas that are not denoted by a UNS segment. This has been done by including the UNS segments in the document definition itself. The EDIFACT Converter now uses the document definition to determine if the UNS segment needs to be inserted inbetween areas. The areas in the document definition can now exactly match those specified by the Edifact standard. When upgrading to DEC/EDI V2.1 the UNS segments are added to all EDIFACT document definition tables. All standard tables will have the UNS segment located as defined by the EDIFACT standard. For private and trading partner specific document definitions the UNS segment will be inserted between the areas in the document. The Table Extract and Load (TEL) Utility will add the UNS segments when loading a document from a V1.3 system. As a result of this the number of areas in the standard definition for certain documents will have changed. In order that existing applications do not fail, private copies of these documents are created during the installation unless one already exists. For Edifact 91.1, 91.2 and 92.1 the documents concerned are :- BANSTA CREEXT DOCINF PAYDUC REMADV CONEST DELJIT INVOIC PAYEXT REQOTE CONNIT DESADV INVRPT PAYMUL SLSRPT CONPVA DIRDEB ORDCHG PRICAT STATAC CONQVA DOCADV ORDERS QALITY SUPMAN CONTEN DOCAPP ORDRSP QUOTES You should change the applications to reflect the correct definition of the document. If you are using the data label API interface this means making sure that the $GROUP/$SEND_ GOUP levels match the areas as defined by the EDIFACT standard. The private definition can then be deleted. If you are using Filebridge, you need to re-import the document definitions. After Installing 3-21 4 _________________________________________________________________ Installation Verification Procedure The Installation Verification Procedure (IVP) for DEC/EDI checks that the installation is correct. After 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 it is still installed correctly. To run the IVP independently, use the following command: $ @SYS$TEST:DECEDI$IVP.COM The IVP checks that all the DEC/EDI files are in the correct locations. It also checks that files that are not supposed to change have indeed not changed. The IVP does not run DEC/EDI. Installation Verification Procedure 4-1 A _________________________________________________________________ Sample Installations This appendix contains logs of the following sample installations: o New Server and Client Installation On OpenVMS VAX; see Section A.1. o New Client Installation on OpenVMS VAX; see Section A.2. o New Server and Client Installation On OpenVMS AXP; see Section A.3. o New Client Installation on OpenVMS AXP; see Section A.4. o Reinstallation On OpenVMS AXP; see Section A.5. The sample installations assume that no users are logged on to your system and that you do not wish to print the Release Notes. The Installation Verification Procedure (IVP) is run in each case. A.1 Log of New Server and Client Installation On OpenVMS VAX Defining symbol CD ( Change directory ). Current PROCESS DEC Rdb environment is version V5.1- 1 (MULTIVERSION) Current PROCESS SQL environment is version V5.1-1 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V5.1- 2 (MULTIVERSION) USER:[TURNER] @inst OpenVMS VAX Software Product Installation Procedure V6.1 It is 23-NOV-1995 at 15:43. Sample Installations A-1 Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX Enter a question mark (?) at any time for help. %VMSINSTAL-W- NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: _RTA3: JOHNSON OBB$AGENT TURNER TURNER SQLSRV$SERVER * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: DECEDI V2.1 Beginning installation of DECEDI V2.1 at 15:43 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Digital Equipment Corporation 1989,1995. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227- 14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? ======================================================= 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]? A-2 Sample Installations Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX ======================================================= The DEC/EDI can be installed to use either the CORBA based ObjectBroker Interfaces or the ACAS based Interfaces. ======================================================= * Do you want to install the CORBA based Interface [YES]? =================================================== In order to use the client interfaces you need to configure ObjectBroker for DEC/EDI after the installation by running the command file DECEDI$TOOLS:DECEDI$CONFIGURE_ACAS.COM =================================================== ====================================================================== DEC/EDI Server already exists on this node. Installation of DEC/EDI will retain data integrity. Upgrading DEC/EDI Server V1.3A to DEC/EDI Server T2.1A DEC/EDI needs to be in an idle state with all ripple backs completed and empty work files. Refer to the Installation Guide for details. ====================================================================== * Do you still want to proceed with this installation [YES]? The following versions of Rdb/VMS are available: V6.0-0 *V5.1-1 * Please enter the Rdb/VMS version to be used by DEC/EDI [*V5.1- 1]: Current PROCESS DEC Rdb environment is version V5.1- 1 (MULTIVERSION) Current PROCESS SQL environment is version V5.1-1 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V5.1- 2 (MULTIVERSION) ================================================================== WARNING: The structure of all mapper databases needs to be modified. All previous FileBridge databases and DEC/EDI V2.0 mapper databases will need to be migrated before using the DEC/EDI V2.1 mapper. Sample Installations A-3 Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX To migrate the live and test databases in FBR$HOME run the post-installation task DECEDI$V21_MIGRATE.COM. Migration of all local test databases should be done using FBR$ARCHIVE.COM. Read the release notes for details. ================================================================== No further questions will be asked during the installation. Installation of DEC/EDI T2.1A will take approximately 30- 90 minutes %DECEDI-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 %DECEDI-I-INFO, Defining DEC/EDI Directories %DECEDI-I-DIREXISTS, Amending existing directory PROJ:[DECEDI] %DECEDI-I-CREATEDIR, Creating directory R4VACM$DIA3:[DECEDI.AUDIT_ DB] %DECEDI-I- CREATEDIR, Creating directory R4VACM$DIA3:[DECEDI.ARCHIVE_DB] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[DATA] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[ERROR] %DECEDI-I- DIREXISTS, Amending existing directory DECEDI$TOP:[VANREPORTS] %DECEDI-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHREPORTS] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[TOOLS] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[DS_ SCRATCH] %DECEDI-I- DIREXISTS, Amending existing directory DECEDI$TOP:[BACKUP] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[CVP] %DECEDI-I- DIREXISTS, Amending existing directory DECEDI$TOP:[CVP.WORK] %DECEDI-I- A-4 Sample Installations Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX DIREXISTS, Amending existing directory DECEDI$TOP:[CVP.IMPEXP] %DECEDI-I-CREATEDIR, Creating directory DECEDI$TOP:[3780PLUS] %DECEDI- I-DIREXISTS, Amending existing directory DECEDI$TOP:[MESSAGE_ UPDATES] %DECEDI-I-CREATEDIR, Creating directory DECEDI$TOP:[CACHE] %DECEDI-I-CREATEDIR, Creating directory DECEDI$TOP:[MAP_TABLES] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[TEMP] %DECEDI-I-DIREXISTS, Amending existing directory PROJ:[FILEBRIDGE] %DECEDI- I-DIREXISTS, Amending existing directory PROJ:[FILEBRIDGE.TEST_ DB] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 1] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 2] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 3] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 4] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 5] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 6] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 7] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 8] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 9] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 10] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 11] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 12] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 13] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 14] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 15] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ Sample Installations A-5 Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX 16] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 17] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 18] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 19] %DECEDI-I-DIREXISTS, Amending existing directory DECEDI$TOP:[STORE_ 20] %DECEDI-I-SECURDIR, Securing all DEC/EDI directories... %DECEDI-I-INFO, Restoring 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 ... %DECEDI-I-CONVDB, Updating DECEDI$AUDIT_ DB logicals in DECEDI$SYLOGICALS.COM... %DECEDI-I-CREATEDB, Creating new database in DECEDI$TOP:[AUDIT_ DB]... %DECEDI-I-CREATEDB, Creating new database in DECEDI$TOP:[ARCHIVE_ DB]... Copyright Digital Equipment Corporation 1990,1995. All rights reserved. FileBridge Database Archive Procedure - Version V2.1A ================================================================== WARNING: The structure of all mapper databases needs to be modified. All previous FileBridge databases and DEC/EDI V2.0 mapper databases will need to be migrated before using the DEC/EDI V2.1 mapper. To migrate the live and test databases in FBR$HOME run the post-installation task DECEDI$V21_MIGRATE.COM. Migration of all local test databases should be done using FBR$ARCHIVE.COM. Read the release notes for details. ================================================================== A-6 Sample Installations Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX %DECEDI-I-INFO, Loading DEC/EDI Files... %DECEDI-I-INFO, Loading tools and examples... %DECEDI-I-INFO, Loading DCL command tables... %DECEDI-I-INFO, Loading help files... %DECEDI-I-INFO, Loading TPU section files... %TPU-S-CREATED, File R4DDWE$DIA0:[SYS0.SYSUPD.DECEDI021]DECEDI$SECTION.TPU$SECTION;1 created %TPU-S-SECTSAVED, 76 procedures, 90 variables, 29 keys saved %DECEDI-I-INFO, Loading System images... %DECEDI-I-INFO, Loading Application service images... %DECEDI-I-INFO, Loading Application service files... %DECEDI-I-INFO, Loading Translation service images... %DECEDI-I-INFO, Loading Communication service images... %DECEDI-I-INFO, Loading Communication service files... %DECEDI-I-INFO, Loading FDL Files... %DECEDI-I-INFO, Loading Data Files... %DECEDI-I-INFO, Loading Command Files... %DECEDI-I-INFO, Loading Mapper Files... %DECEDI-I-INFO, Converting Data Files... This installation procedure is now migrating your DEC/EDI V1 EDIFACT document definitions to be compatible with DEC/EDI V2 EDIFACT components. DEC/EDI V1 EDIFACT document definitions have the following features: 1. The document definitions do not contain UNS segments. These are inserted automatically into outbound documents by the EDIFACT converter. 2. Some document definitions do not contain the correct number of areas. This is related to feature 1. The DEC/EDI V1 EDIFACT converter inserts a UNS segment each time it detects a change of areas within a document. While the combination of these two features means that DEC/EDI V1 produces EDIFACT documents with the correct number of UNS segments, it also means that the documents processed by DEC/EDI do not accurately reflect the EDIFACT definitions of those documents. This has been addressed in DEC/EDI V2, as a result of which DEC/EDI V2 document definition tables contain accurate EDIFACT document definitions. This migration of your DEC/EDI V1 EDIFACT document definitions inserts UNS segments between existing document areas. This will allow you to continue to use your existing applications. This migration does NOT replace your DEC/EDI V1 EDIFACT document definitions with DEC/EDI V2 EDIFACT document definitions. Please see the product release notes for more details. Sample Installations A-7 Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX %DECEDI-I-STDUNS1, Getting EDIFACT 1 files from DECEDI$DATA:... %DECEDI-I- STDUNS2, Adding UNS segments to EDIFACT 1 document definitions. %DECEDI-I-MIGTFD, Migrating the profile records to Transmission File Details records %DECEDI-I-INFO, Migrating node configuration... ==================================================================== WARNING: The function of the management configuration file has been modified. Please check the new configuration after the installation. Refer to the Installation Guide for details. ==================================================================== %DECEDI-I-INFO, Migrating Management Configuration File... %DECEDI-I-INFO, Migrating Application Site Table... %DECEDI-I-INFO, Migrating Site Routing Table... %DECEDI-I-INFO, Loading CVP data... Installation of DEC/EDI T2.1A succeeded ========================================= %DECEDI-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... %PURGE-W- FILNOTPUR, error deleting SYS$COMMON:[SYSLIB]DECEDI$PRVSHR.EXE;3 -RMS-E-FLK, file currently locked by another user Executing IVP for DEC/EDI T2.1A ================================= Copyright (c) Digital Equipment Corporation 1989,1995. All rights reserved. Please wait - Checking all DEC/EDI files ======================================== ====================================== IVP was successful. A-8 Sample Installations Sample Installations A.1 Log of New Server and Client Installation On OpenVMS VAX Total number of files expected : 313 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 DEC/EDI T2.1A has Executed to Completion ================================================= Installation of DECEDI V2.1 completed at 15:58 VMSINSTAL procedure done at 15:58 USER:[TURNER] dir sys$test:decedi* Directory SYS$COMMON:[SYSTEST] DECEDI$IVP.COM;2 DECEDI$IVP_CHECKSUMS.DAT;2 Total of 2 files. USER:[TURNER] sea SYS$COMMON:[SYSTEST]DECEDI$IVP_ CHECKSUMS.DAT decedi$mess DECEDI$TOOLS:[1mDECEDI$MESS[0mAGE_UPDATES.EXE EDI 1512558 SYSTEM=RWED, OWNER=RWED, GROUP=RE, WORLD=RE SYS$MESSAGE:[1mDECEDI$MESS[0mAGE.EXE EDI 2888968529 SYSTEM=RWED, OWNER=RWED, GROUP=RE, WORLD=RE USER:[TURNER] clr %DCL-W-IVVERB, unrecognized command verb - check validity and spelling \CLR\ USER:[TURNER] lo TURNER logged out at 23-NOV-1995 15:59:35.12 A.2 Log of New Client Installation on OpenVMS VAX $ @SYS$UPDATE:VMSINSTAL DECEDI020 USER1:[KITS] VAX/VMS Software Product Installation Procedure V5.5-2 It is 3-JUN-1994 at 09:08. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Sample Installations A-9 Sample Installations A.2 Log of New Client Installation on OpenVMS VAX The following products will be processed: DECEDI V2.1 Beginning installation of DECEDI V2.1 at 09:08 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Digital Equipment Corporation 1989,1994. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227- 14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital 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 =========================================================================== 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 * On what device should the DECEDI directories reside: USER1: * What is the UIC to be used for the DEC/EDI account: 333,1 * What is the name of the node on which the DEC/EDI Server will run: EDIVAX What is the type of machine the Server is on ? * Is it ALPHA/VMS or VAX/VMS: ALPHA/VMS No further questions will be asked during the installation. Installation of DEC/EDI V2.1 will take approximately 5- 15 minutes %DECEDI-I-INFO, defining DECEDI Account with autogenerated password A-10 Sample Installations Sample Installations A.2 Log of New Client Installation on OpenVMS VAX %VMSINSTAL-I- ACCOUNT, This installation creates an ACCOUNT named DECEDI. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier DECEDI value: [000333,000001] added to rights data base %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 adds an identifier named DECEDI$ADMINIST RATOR. %UAF-I-RDBADDMSG, identifier DECEDI$ADMINISTRATOR value: %X8001000E added to rig hts data base %VMSINSTAL-I- ACCOUNT, This installation adds an identifier named DECEDI$SUPERVIS OR. %UAF-I-RDBADDMSG, identifier DECEDI$SUPERVISOR value: %X8001000F added to rights data base %DECEDI-I-INFO, Defining DEC/EDI Directories %DECEDI-I-CREATEDIR, Creating directory USER1:[DECEDI] %DECEDI-I-CREATEDIR, Creating directory USER1:[DECEDI.TOOLS] %DECEDI-I-CREATEDIR, Creating directory USER1:[DECEDI.DATA] %VMSINSTAL-I- SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECE DI]. %DECEDI-I-SECURDIR, Securing all DEC/EDI directories... %DECEDI-I-INFO, Restoring DEC/EDI Files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Sample Installations A-11 Sample Installations A.2 Log of New Client Installation on OpenVMS VAX %DECEDI-I-INFO, Loading DEC/EDI Files... %DECEDI-I-INFO, Loading tools... Starting ACA Services Control Server %RUN-S-PROC_ID, identification of created process is 0000006F %DECEDI-I-INFO, Loading DCL command tables... %DECEDI-I-INFO, Loading System images... %DECEDI-I-INFO, Loading Application service images... %DECEDI-I-INFO, Loading Application service files... Installation of DEC/EDI V2.1 succeeded ========================================= %DECEDI-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... Executing IVP for DEC/EDI V2.1 ================================= Copyright (c) Digital Equipment Corporation 1989,1994. All rights reserved. Please wait - Checking all DEC/EDI files ======================================== ====================================== IVP was successful. Total number of files expected : 20 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 DEC/EDI V2.1 has Executed to Completion ================================================= Installation of DECEDI V2.1 completed at 09:27 VMSINSTAL procedure done at 09:27 A-12 Sample Installations Sample Installations A.3 Log of New Server and Client Installation On OpenVMS AXP A.3 Log of New Server and Client Installation On OpenVMS AXP $ @sys$update:vmsinstal OpenVMS AXP Software Product Installation Procedure V6.1 It is 23-NOV-1994 at 15:26. Enter a question mark (?) at any time for help. %VMSINSTAL-W- NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: _RTA3: USER1 SQLSRV$SERVER * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? YES * Where will the distribution volumes be mounted: ALE$DKA300:[000000.KITS] Enter the products to be processed from the first distribution volume set. * Products: DECEDIA021 * Enter installation options you wish to use (none): The following products will be processed: DECEDIA V2.1 Beginning installation of DECEDIA V2.1 at 15:26 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Digital Equipment Corporation 1989,1994. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227- 14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? YES Sample Installations A-13 Sample Installations A.3 Log of New Server and Client Installation On OpenVMS AXP * Do you want to run the IVP after the installation [YES]? YES ======================================================= 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 The following DEC/EDI component(s) are not licensed on this node ================================================================ DEC/EDI OFTP-Package Services V2.1 DEC/EDI OFTP Services V2.1 DEC/EDI X400-Package Services V2.1 DEC/EDI X400 Services V2.1 DEC/EDI Bisynchronous-Package Services V2.1 DEC/EDI Bisynchronous Services V2.1 Filebridge Runtime Services V2.1 * Do you still want to proceed with this installation [YES]? YES The following versions of Rdb/VMS are available: *V5.1-0 * Please enter the Rdb/VMS version to be used by DEC/EDI [*V5.1- 0]: *V5.1-0 Current PROCESS DEC Rdb environment is version V5.1- 0 (MULTIVERSION) * On what device should the DECEDI directories reside: ALE$DKA300 The logical name FBR$HOME specifies the directory under which the Mapper Audit Databases and History Files reside. FBR$HOME must have the minimum required disk space for the creation of the Audit Databases. Be aware that the Audit Databases can grow significantly as you use the Mapper. Enter the device and directory specification for FBR$HOME. * Directory name [SYS$SYSDEVICE:[FILEBRIDGE]]: * What is the UIC to be used for the DEC/EDI account: [50,60] No further questions will be asked during the installation. Installation of DEC/EDI V2.1 will take approximately 7- 15 minutes A-14 Sample Installations Sample Installations A.3 Log of New Server and Client Installation On OpenVMS AXP %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 [000050,000060] 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. %UAF-I-MDFYMSG, user record(s) updated %DECEDIA-I-INFO, Defining DEC/EDI Directories %DECEDIA-I- DIREXISTS, Amending existing directory ALE$DKA300:[DECEDI] %DECEDIA-I-CREATEDIR, Creating directory ALE$DKA300:[DECEDI.AUDIT_ DB] %DECEDIA-I- CREATEDIR, Creating directory ALE$DKA300:[DECEDI.ARCHIVE_DB] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[DATA] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ERROR] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[VANREPORTS] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHREPORTS] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[TOOLS] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[DS_SCRATCH] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[BACKUP] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP.WORK] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP.IMPEXP] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[3780PLUS] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[MESSAGE_ UPDATES] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CACHE] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[MAP_TABLES] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[TEMP] %DECEDIA-I- DIREXISTS, Amending existing directory SYS$SYSDEVICE:[FILEBRIDGE] %DECEDIA-I-DIREXISTS, Amending existing directory SYS$SYSDEVICE:[FILEBRIDGE.TEST_ Sample Installations A-15 Sample Installations A.3 Log of New Server and Client Installation On OpenVMS AXP DB] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_1] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_2] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_3] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_4] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_5] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_6] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_7] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_8] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_9] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_10] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_11] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_12] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_13] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_14] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_15] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_16] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_17] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_18] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_19] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_20] %DECEDIA-I-SECURDIR, Securing all DEC/EDI directories... %DECEDIA-I-INFO, Restoring 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... Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V2.1 Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V2.1 A new, empty FileBridge Archive Database is being placed in: SYS$SYSDEVICE:[FILEBRIDGE.941123152720.FBR$DB]FBR$AUDIT_ DATABASE.RDB The history records will be placed in: SYS$SYSDEVICE:[FILEBRIDGE.941123152720.FBR$HISTORY] The new database is being IMPORTed from: ALE$DKA200:[SYS0.SYSUPD.DECEDIA021]FBR$AUDIT_DATABASE.RBR A-16 Sample Installations Sample Installations A.3 Log of New Server and Client Installation On OpenVMS AXP This software is for Digital Internal Use Only Exported by DEC Rdb V5.1-0 Import/Export utility A component of DEC SQL V5.1-0 Previous name was DECEDI_OBJ:FBR$AUDIT_DATABASE It was logically exported on 20-NOV-1994 09:39 Multischema mode is DISABLED Database NUMBER OF USERS is 50 Database NUMBER OF CLUSTER NODES is 16 Database NUMBER OF DBR BUFFERS is 20 Database SNAPSHOT is ENABLED Database SNAPSHOT is IMMEDIATE Database JOURNAL EXTENSION is 512 Database BUFFER SIZE is 12 blocks Database NUMBER OF BUFFERS is 20 Adjustable lock granularity is ENABLED Database global buffering is DISABLED Journal fast commit is DISABLED Journal fast commit checkpoint interval is 0 blocks Journal fast commit checkpoint time is 0 seconds Commit to journal optimization is Disabled Journal fast commit TRANSACTION INTERVAL is 256 LOCK TIMEOUT is 0 seconds Definition of STORAGE AREA RDB$SYSTEM overridden Definition of STORAGE AREA EVENT_DATA_AREA overridden Definition of STORAGE AREA EVENT_INDEX_AREA overridden IMPORTing table EVENT This software is for Digital Internal Use Only Restore operation complete. Sample Installations A-17 Sample Installations A.3 Log of New Server and Client Installation On OpenVMS AXP %DECEDIA-I-INFO, Loading DEC/EDI Files... %DECEDIA-I-INFO, Loading tools and examples... %DECEDIA-I-INFO, Configuring DEC ACA Services... Starting ACA Services Control Server %RUN-S-PROC_ID, identification of created process is 0000079F %DECEDIA-I-INFO, Loading DCL command tables... %DECEDIA-I-INFO, Loading help files... %DECEDIA-I-INFO, Loading TPU section files... %TPU-S-CREATED, File ALE$DKA200:[SYS0.SYSUPD.DECEDIA021]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 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, Loading CVP data... Installation of DEC/EDI V2.1 succeeded ========================================= %DECEDIA-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... Executing IVP for DEC/EDI V2.1 ================================= Copyright (c) Digital Equipment Corporation 1989,1994. All rights reserved. Please wait - Checking all DEC/EDI files ======================================== ====================================== IVP was successful. A-18 Sample Installations Sample Installations A.3 Log of New Server and Client Installation On OpenVMS AXP Total number of files expected : 203 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 DEC/EDI V2.1 has Executed to Completion ================================================= Installation of DECEDIA V2.1 completed at 15:38 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA021.VMI_ DATA A.4 Log of New Client Installation on OpenVMS AXP $ @sys$update:vmsinstal DECEDIA020 DISK$USER01:[KITS] OpenVMS ALPHA Software Product Installation Procedure V1.5- 1H1 It is 22-MAY-1994 at 13:53. Enter a question mark (?) at any time for help. %VMSINSTAL-W- NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: SQLSRV$SERVER * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? Y The following products will be processed: DECEDIA V2.1 Beginning installation of DECEDIA V2.1 at 13:53 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Digital Equipment Corporation 1989,1994. All rights reserved. Sample Installations A-19 Sample Installations A.4 Log of New Client Installation on OpenVMS AXP Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227- 14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? Y * Do you want to run the IVP after the installation [YES]? Y =========================================================================== 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]? N * On what device should the DECEDI directories reside: CREST1$DKA100: * What is the UIC to be used for the DEC/EDI account: 500,500 * What is the name of the node on which the DEC/EDI Server will run: SYSTEM What is the type of machine the Server is on ? * Is it ALPHA/VMS or VAX/VMS: VAX/VMS No further questions will be asked during the installation. Installation of DEC/EDI V2.1 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,000500] added to rights data base %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- A-20 Sample Installations Sample Installations A.4 Log of New Client Installation on OpenVMS AXP ACCOUNT, This installation updates an ACCOUNT named DECEDI. %UAF-I-MDFYMSG, user record(s) updated %DECEDIA-I-INFO, Defining DEC/EDI Directories %DECEDIA-I-CREATEDIR, Creating directory CREST1$DKA100:[DECEDI] %DECEDIA-I- CREATEDIR, Creating directory CREST1$DKA100:[DECEDI.TOOLS] %DECEDIA-I- CREATEDIR, Creating directory CREST1$DKA100:[DECEDI.DATA] %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECEDI]. %DECEDIA-I-SECURDIR, Securing all DEC/EDI directories... %DECEDIA-I-INFO, Restoring DEC/EDI Files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %DECEDIA-I-INFO, Loading DEC/EDI Files... %DECEDIA-I-INFO, Loading tools... Starting ACA Services Control Server %RUN-S-PROC_ID, identification of created process is 000000AF %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 DEC/EDI V2.1 succeeded ========================================= %DECEDIA-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... Executing IVP for DEC/EDI V2.1 ================================= Copyright (c) Digital Equipment Corporation 1989,1994. All rights reserved. Please wait - Checking all DEC/EDI files ======================================== ====================================== IVP was successful. Sample Installations A-21 Sample Installations A.4 Log of New Client Installation on OpenVMS AXP Total number of files expected : 19 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 DEC/EDI V2.1 has Executed to Completion ================================================= Installation of DECEDIA V2.1 completed at 13:55 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA020.VMI_ DATA VMSINSTAL procedure done at 13:56 $ A.5 Log of Reinstallation On OpenVMS AXP $ @SYS$UPDATE:VMSINSTAL DECEDIA020 CREST1$DKA0:[KITS] OpenVMS ALPHA Software Product Installation Procedure V1.5- 1H1 It is 2-JUN-1994 at 18:33. Enter a question mark (?) at any time for help. %VMSINSTAL-W- NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: ACAS$CONTROL * Do you want to continue anyway [NO]? you * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: DECEDIA V2.1 Beginning installation of DECEDIA V2.1 at 18:34 A-22 Sample Installations Sample Installations A.5 Log of Reinstallation On OpenVMS AXP %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Digital Equipment Corporation 1989,1994. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227- 14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possesion, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital 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 =========================================================================== 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 The following DEC/EDI component(s) are not licensed on this node ================================================================ DEC/EDI OFTP Services V2.1 DEC/EDI OFTP-Package Services V2.1 DEC/EDI Bisynchronous Services V2.1 DEC/EDI Bisynchronous-Package Services V2.1 DEC/EDI X400 Services V2.1 DEC/EDI X400-Package Services V2.1 * Do you still want to proceed with this installation [YES]? YES Current PROCESS DEC Rdb environment is version V5.1- 0 (MULTIVERSION) * On what device should the DECEDI directories reside: CREST1$DKA100 The logical name FBR$HOME specifies the directory under which the Mapper Audit Databases and History Files reside. Enter the device and directory specification for FBR$HOME. Sample Installations A-23 Sample Installations A.5 Log of Reinstallation On OpenVMS AXP * Directory name [SYS$SYSDEVICE:[FILEBRIDGE]]: CREST1$DKA100:[FILEBRIDGE] WARNING: CREST1$DKA100: must have the minimum required disk space for the creation of the Audit Databases. Be aware that the Audit Databases can grow significantly as you use the Mapper. * What is the UIC to be used for the DEC/EDI account: 500,500 No further questions will be asked during the installation. Installation of DEC/EDI V2.1 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,000500] added to rights data base %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 DEC/EDI Directories %DECEDIA-I-CREATEDIR, Creating directory CREST1$DKA100:[DECEDI] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[DATA] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ERROR] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[VANREPORTS] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[TOOLS] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[DS_SCRATCH] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[BACKUP] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_DATA] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP.WORK] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CVP.IMPEXP] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[3780PLUS] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[MESSAGE_ UPDATES] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[AUDIT_ A-24 Sample Installations Sample Installations A.5 Log of Reinstallation On OpenVMS AXP DATABASE] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[CACHE] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[MAP_TABLES] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[TEMP] %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.DECEDI]. %VMSINSTAL-I- SYSDIR, This product creates system directory [SYSTEST.FBR]. %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_1] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_2] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_3] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_4] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_5] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_6] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_7] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_8] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_9] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_10] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_11] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_12] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_13] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_14] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_15] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_16] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_17] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_18] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_19] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[STORE_20] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 1] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 2] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 3] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 4] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 5] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 6] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 7] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ Sample Installations A-25 Sample Installations A.5 Log of Reinstallation On OpenVMS AXP 8] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 9] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 10] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 11] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 12] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 13] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 14] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 15] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 16] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 17] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 18] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 19] %DECEDIA-I-CREATEDIR, Creating directory DECEDI$TOP:[ARCHIVE_STORE_ 20] %DECEDIA-I-SECURDIR, Securing all DEC/EDI directories... %DECEDIA-I-INFO, Restoring 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 ... Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V2.1 A new, empty FileBridge Archive Database is being placed in: CREST1$DKA100:[FILEBRIDGE.TEST_DB.FBR$DB]FBR$AUDIT_ DATABASE.RDB The history records will be placed in: CREST1$DKA100:[FILEBRIDGE.TEST_DB.FBR$HISTORY] The new database is being IMPORTed from: CREST1$DKA0:[SYS0.SYSUPD.DECEDIA020]FBR$AUDIT_DATABASE.RBR A-26 Sample Installations Sample Installations A.5 Log of Reinstallation On OpenVMS AXP This software is for Digital Internal Use Only Exported by DEC Rdb V5.1-0 Import/Export utility A component of DEC SQL V5.1-0 Previous name was DECEDI_OBJ:FBR$AUDIT_DATABASE It was logically exported on 2-JUN-1994 02:37:36.25 Multischema mode is DISABLED Database NUMBER OF USERS is 50 Database NUMBER OF CLUSTER NODES is 16 Database NUMBER OF DBR BUFFERS is 20 Database SNAPSHOT is ENABLED Database SNAPSHOT is IMMEDIATE Database JOURNAL EXTENSION is 512 Database BUFFER SIZE is 12 blocks Database NUMBER OF BUFFERS is 20 Adjustable lock granularity is ENABLED Database global buffering is DISABLED Journal fast commit is DISABLED Journal fast commit checkpoint interval is 0 blocks Journal fast commit checkpoint time is 0 seconds Commit to journal optimization is Disabled Journal fast commit TRANSACTION INTERVAL is 256 LOCK TIMEOUT is 0 seconds Definition of STORAGE AREA RDB$SYSTEM overridden Definition of STORAGE AREA EVENT_DATA_AREA overridden Definition of STORAGE AREA EVENT_INDEX_AREA overridden IMPORTing relation EVENT This software is for Digital Internal Use Only Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V2.1 A new, empty FileBridge Archive Database is being placed in: CREST1$DKA100:[FILEBRIDGE.940602183508.FBR$DB]FBR$AUDIT_ DATABASE.RDB The history records will be placed in: CREST1$DKA100:[FILEBRIDGE.940602183508.FBR$HISTORY] The new database is being IMPORTed from: CREST1$DKA0:[SYS0.SYSUPD.DECEDIA020]FBR$AUDIT_DATABASE.RBR Sample Installations A-27 Sample Installations A.5 Log of Reinstallation On OpenVMS AXP This software is for Digital Internal Use Only Exported by DEC Rdb V5.1-0 Import/Export utility A component of DEC SQL V5.1-0 Previous name was DECEDI_OBJ:FBR$AUDIT_DATABASE It was logically exported on 2-JUN-1994 02:37:36.25 Multischema mode is DISABLED Database NUMBER OF USERS is 50 Database NUMBER OF CLUSTER NODES is 16 Database NUMBER OF DBR BUFFERS is 20 Database SNAPSHOT is ENABLED Database SNAPSHOT is IMMEDIATE Database JOURNAL EXTENSION is 512 Database BUFFER SIZE is 12 blocks Database NUMBER OF BUFFERS is 20 Adjustable lock granularity is ENABLED Database global buffering is DISABLED Journal fast commit is DISABLED Journal fast commit checkpoint interval is 0 blocks Journal fast commit checkpoint time is 0 seconds Commit to journal optimization is Disabled Journal fast commit TRANSACTION INTERVAL is 256 LOCK TIMEOUT is 0 seconds Definition of STORAGE AREA RDB$SYSTEM overridden Definition of STORAGE AREA EVENT_DATA_AREA overridden Definition of STORAGE AREA EVENT_INDEX_AREA overridden IMPORTing relation EVENT This software is for Digital Internal Use Only A-28 Sample Installations Sample Installations A.5 Log of Reinstallation On OpenVMS AXP %DECEDIA-I-INFO, Loading DEC/EDI Files... %DECEDIA-I-INFO, Loading tools... Starting ACA Services Control Server %RUN-S-PROC_ID, identification of created process is 0000032A %DECEDIA-I-INFO, Loading DCL command tables... %DECEDIA-I-INFO, Loading help files... %DECEDIA-I-INFO, Loading TPU section files... %TPU-S-CREATED, File CREST1$DKA0:[SYS0.SYSUPD.DECEDIA020]DECEDI$SECTION.TPU$SECTION;1 created %TPU-S-SECTSAVED, 76 procedures, 90 variables, 29 keys saved %TPU-S-CREATED, File CREST1$DKA0:[SYS0.SYSUPD.DECEDIA020]DECEDI$ELM.TPU$SECTION;1 created %TPU-S-SECTSAVED, 46 procedures, 56 variables, 0 keys saved %DECEDIA-I-INFO, Loading System images... %DECEDIA-I-INFO, Loading Application service 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, Loading CVP data... Installation of DEC/EDI V2.1 succeeded ========================================= %DECEDIA-I-CLEANUP, Performing post-installation cleanup %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... Executing IVP for DEC/EDI V2.1 ================================= Copyright (c) Digital Equipment Corporation 1989,1994. All rights reserved. Please wait - Checking all DEC/EDI files ======================================== ====================================== IVP was successful. Sample Installations A-29 Sample Installations A.5 Log of Reinstallation On OpenVMS AXP Total number of files expected : 201 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 DEC/EDI V2.1 has Executed to Completion ================================================= Installation of DECEDIA V2.1 completed at 18:46 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DECEDIA020.VMI_ DATA VMSINSTAL procedure done at 18:46 $ A-30 Sample Installations B _________________________________________________________________ Installing DEC/EDI Translation Standards This appendix describes how to install or remove DEC/EDI standards from the server. You can do any of the following: o Install a new standard and version from the DEC/EDI Message Update kit. o Copy an existing version of a standard to a new version of the same standard. o Copy the data labels associated with one version of a standard to a different version of the same standard. o Delete a version of a standard from DEC/EDI. B.1 Preparation for the Message Update You must do the following: o Find out the location of the DEC/EDI Message Update Kit. The file name for the kit has the following format: DECEDI2MSG014.% o Make sure that the account from which you will run the update procedure has at least one of the DEC/EDI administrator rights. o Make sure that DEC/EDI is running. B.2 Running the Message Update Procedure To run the message update procedure: 1. Give the following command: @DECEDI$TOOLS:DECEDI$MESSAGE_UPDATES.COM Installing DEC/EDI Translation Standards B-1 Installing DEC/EDI Translation Standards B.2 Running the Message Update Procedure This displays the following initial screen: DEC/EDI Message Updates Utility V2.1 Copyright (C) 1994 Digital Equipment Corporation. All rights reserved. Press F10 or CTRL/Z at any prompt to return to the previous prompt. Initializing environment.... 1) Install a new standard and version from the DEC/EDI Message Updates kit. 2) Copy an existing version of a standard to a new version of the same standard. 3) Copy the data labels associated with one version of a standard to a different version of the same standard. 4) Delete a version of a standard from DEC/EDI. 5) Exit. Enter an option (1-5) [5] : 2. Select the option you want. The procedure asks you for the location of the Message Update Kit. 3. Enter the name of the device where you have put the kit. If the kit is on a disk or CD-ROM, give the directory location as well. The installation procedure opens the first save set and then gives you a choice, based on what it found in the save set. 4. Answer any other questions the installation procedure may ask. B.3 Aborting the Message Update 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, if necessary. B-2 Installing DEC/EDI Translation Standards C _________________________________________________________________ Files in the Installation Kit This appendix lists the files that go into the different savesets. C.1 Save Set A DECEDI$SYLOGICALS.COM DECEDI021.RELEASE_NOTES IDENT.COM KITINSTAL.COM C.2 Save Set B DECEDI$ACCESS.FDL DECEDI$ADD_UNS.EXE (OpenVMS VAX only) DECEDI$AFS_MAIN.EXE DECEDI$ARCHIVE_DATABASE.SQL DECEDI$ARCHIVE_DB_CREATE.EXE DECEDI$ARCHIVE_SERVER.EXE DECEDI$AUDIT_DATABASE.SQL DECEDI$AUDIT_EXTRACT.COM DECEDI$AUDIT_EXTRACT.EXE DECEDI$AUDIT_EXTRACT_TABLES.DAT DECEDI$AUDIT_USER_REF_TABLES.DAT DECEDI$COMMAND_HELP.HLB DECEDI$CVP.COM DECEDI$CVP_COMPARE.COM DECEDI$CVP_FETCH.EXE DECEDI$CVP_LOOPBACK.COM DECEDI$CVP_RUN_FETCH.COM DECEDI$CVP_SEND.DAT DECEDI$CVP_SEND.EXE DECEDI$DATA_SERVER.EXE DECEDI$DATA_SET_ID.DAT DECEDI$DB_ALTER.EXE Files in the Installation Kit C-1 Files in the Installation Kit C.2 Save Set B DECEDI$DB_CONVERT.EXE DECEDI$DB_CREATE.EXE DECEDI$INTERCHANGE.CLD DECEDI$INTERCHANGE.EXE DECEDI$INTERCHANGE.HLP DECEDI$LINK_TUNE_DB.COM DECEDI$LINK_TUNE_SYINFO.COM DECEDI$LOGIN.COM DECEDI$MESSAGE.EXE DECEDI$MESSAGE_UPDATES.COM DECEDI$MGT_CONFIG.FDL DECEDI$MIGRATE_TFD.EXE (OpenVMS VAX only) DECEDI$REVIEW_HELP.HLB DECEDI$SECTION.TPU DECEDI$SERVICES.EXE DECEDI$SHUTDOWN.COM DECEDI$SHUTDOWN.EXE DECEDI$STARTUP.COM DECEDI$STARTUP.EXE DECEDI$SYSHUTDOWN.COM DECEDI$SYSTARTUP.COM DECEDI$SYSTEM_PARAMETERS.FDL DECEDI$TAILOR.COM DECEDI$TRADE.HLP DECEDI$TUNE_DB.EXE DECEDI$TUNE_DB.OBJ DECEDI$TUNE_DB.PS DECEDI$TUNE_DB.TXT DECEDI$TUNE_SYINFO.EXE DECEDI$TUNE_SYINFO.OBJ DECEDI$UI_FIELD_HELP.HLB DECEDI$UI_HELP_KEYS_ENGLISH.TXT DECEDI$V21_APPFILMIGR.EXE DECEDI$V21_ARCHIVE_MIGRATE.EXE DECEDI$V21_MIGRATE.COM DECEDI$V21_MIGRATE.EXE C-2 Files in the Installation Kit Files in the Installation Kit C.3 Save Set C C.3 Save Set C DECEDI$API_DEF.BAS DECEDI$API_DEF.COB DECEDI$API_DEF.FOR DECEDI$API_DEF.H DECEDI$API_DEF.LIB DECEDI$API_DEF.PAS DECEDI$API_DEF.PLI DECEDI$APPSHR.EXE DECEDI$APPSHR.OPT DECEDI$APPSHRG.EXE DECEDI$APPSHR_V2.EXE DECEDI$CHECKSUMS.DAT DECEDI$CIS.EXE DECEDI$CLI.CLD DECEDI$CLI.EXE DECEDI$CMSGS.EXE DECEDI$COMM_APPSHR.EXE DECEDI$COMM_APPSHR.OPT DECEDI$CREATE_SYS_VER_FILE.COM DECEDI$CREATE_SYS_VER_FILE.EXE DECEDI$IVP.COM DECEDI$IVP_CHECKSUMS.FDL DECEDI$MSF.EXE DECEDI$MST.EXE DECEDI$PRVSHR.EXE DECEDI$SITE_ROUTING.FDL DECEDI$SITE_TABLE.FDL DECEDI$SYSTEM_VERSIONS.FDL DECEDI.CRL DECEDI_API_COMMON.H DECEDI_API_DEF.H DECEDI_API_MSGS.H DECEDI_PLATFORMS.H Files in the Installation Kit C-3 Files in the Installation Kit C.4 Save Set D C.4 Save Set D A01.DAT (OpenVMS VAX only) A0901.DAT (OpenVMS VAX only) A0902.DAT (OpenVMS VAX only) A0911.DAT (OpenVMS VAX only) A0912.DAT (OpenVMS VAX only) A0921.DAT (OpenVMS VAX only) DECEDI$AGREEMENTS_DETAIL_TABLE.FDL DECEDI$AGREEMENTS_TABLE.FDL DECEDI$CLIENT_APPLICATIONS.FDL DECEDI$CNV_EDIFACT.EXE DECEDI$CNV_TRADACOMS.EXE DECEDI$CNV_X12.EXE DECEDI$CONTROL_NUM.FDL DECEDI$CONVERT_DOC.EXE DECEDI$CONVERT_DOCS.COM DECEDI$DATACHECKSHR.EXE DECEDI$DATA_DESC.FDL DECEDI$DATA_LABEL.FDL DECEDI$DLG.COM DECEDI$DLG.EXE DECEDI$DLG_COPY.COM DECEDI$DLG_DOC.PS DECEDI$DLG_DOC.TXT DECEDI$DOCUMENT_AUDIT.FDL DECEDI$DOCUMENT_TABLE.FDL DECEDI$DOC_AREA_TABLE.FDL DECEDI$DOC_DESC_TABLE.FDL DECEDI$ELEMENT_CODES.FDL DECEDI$ELEMENT_TABLE.FDL DECEDI$EXTSHR.EXE DECEDI$FA_MAPPING_TABLE.FDL DECEDI$FORMAT_TABLE.FDL DECEDI$NODE_CONFIGURATION_DETAILS.FDL DECEDI$NUMSHR.EXE DECEDI$PARAMETERS_FILE.FDL DECEDI$PARTNER_TABLE.FDL DECEDI$P_DOCUMENT_TABLE.FDL DECEDI$P_DOC_AREA_TABLE.FDL DECEDI$P_DOC_DESC_TABLE.FDL DECEDI$P_ELEMENT_CODES.FDL DECEDI$P_ELEMENT_TABLE.FDL C-4 Files in the Installation Kit Files in the Installation Kit C.4 Save Set D DECEDI$P_SEGMENT_TABLE.FDL DECEDI$P_SEG_DESC.FDL DECEDI$P_SUB_ELE_TABLE.FDL DECEDI$QUALIFIER_TABLE.FDL DECEDI$RESERVED_DATA_LABELS.FDL DECEDI$RESERVED_SEG_TABLE.FDL DECEDI$RES_DATA_LABELS_EDIF.DAT DECEDI$RES_DATA_LABELS_ODET.DAT DECEDI$RES_DATA_LABELS_TDCC.DAT DECEDI$RES_DATA_LABELS_TRAD.DAT DECEDI$RES_DATA_LABELS_X12.DAT DECEDI$RES_SEG_TABLE_EDIF.DAT DECEDI$RES_SEG_TABLE_ODET.DAT DECEDI$RES_SEG_TABLE_TDCC.DAT DECEDI$RES_SEG_TABLE_TRAD.DAT DECEDI$RES_SEG_TABLE_X12.DAT DECEDI$SEGMENT_TABLE.FDL DECEDI$SEG_DESC.FDL DECEDI$SEQCHECKSHR.EXE DECEDI$SEQ_HISTORY.FDL DECEDI$SUB_ELE_TABLE.FDL DECEDI$TEL.EXE DECEDI$TEL_DOC.PS DECEDI$TEL_DOC.TXT DECEDI$TEL_TRANSFER.FDL DECEDI$TFB.EXE DECEDI$TFB_X12.EXE DECEDI$TFS.EXE DECEDI$TP_CODE_TRANS.FDL DECEDI$TP_DATA_LABEL.FDL DECEDI$TP_DOCUMENT_TABLE.FDL DECEDI$TP_DOC_AREA_TABLE.FDL DECEDI$TP_ELEMENT_TABLE.FDL DECEDI$TP_QUAL_TABLE.FDL DECEDI$TP_SEGMENT_TABLE.FDL DECEDI$TP_STD_VERS.FDL DECEDI$TRANSLATION_HISTORY.FDL DECEDI$TRANSMISSION_FILE_DETAILS.FDL DECEDI$TRNS_EDIFACT.EXE DECEDI$TRNS_TRADACOMS.EXE DECEDI$TRNS_X12.EXE Files in the Installation Kit C-5 Files in the Installation Kit C.5 Save Set E C.5 Save Set E DECEDI$3780.EXE DECEDI$BISYNC.EXE (OpenVMS VAX only) DECEDI$BISYNC2.EXE (OpenVMS VAX only) DECEDI$CC_PSI_INTERFACE.EXE DECEDI$CC_TRAX_RESEND_TIMEOUT.EXE DECEDI$COMMS_CONTROL.EXE DECEDI$DIAL.COM (OpenVMS VAX only) DECEDI$DIAL.EXE (OpenVMS VAX only) DECEDI$FS_DECNET.EXE DECEDI$FS_MAIN.EXE DECEDI$IMPEXP.EXE DECEDI$JOB_DESC.FDL DECEDI$OFTP.EXE DECEDI$PEDI.EXE DECEDI$SCHEDULE.DAT DECEDI$SCHEDULE.FDL DECEDI$SCR_EDIC_01_LOGIN.DAT (OpenVMS VAX only) DECEDI$SCR_EDIC_02_PRODUCTION1.DAT (OpenVMS VAX only) DECEDI$SCR_EDIC_03_PRODUCTION2.DAT (OpenVMS VAX only) DECEDI$SCR_EDIC_04_PRODUCTION3.DAT (OpenVMS VAX only) DECEDI$SCR_EDIC_05_LOGOUT.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_01_LOGIN.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_02_PRODUCTION.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_03_SENDER_STATUS.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_04_RECEIVER_STATUS.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_05_UNRETRIEVED_DOCUMENT.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_06_SENDER_ERROR.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_07_SENDER_SUMMARY.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_08_ERROR_RECOVERY.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_09_SENDER_RETRIEVED_DOC.DAT (OpenVMS VAX only) DECEDI$SCR_GEIS_10_LOGOUT.DAT (OpenVMS VAX only) DECEDI$SCR_MCDD_01_LOGIN.DAT (OpenVMS VAX only) DECEDI$SCR_MCDD_02_PRODUCTION.DAT (OpenVMS VAX only) DECEDI$SCR_MCDD_03_LOGOUT.DAT (OpenVMS VAX only) DECEDI$SCR_P_GEIS_01_LOGIN.DAT DECEDI$SCR_P_GEIS_02_PRODUCTION.DAT DECEDI$SCR_P_GEIS_03_SENDER_STATUS.DAT DECEDI$SCR_P_GEIS_04_RECEIVER_STATUS.DAT C-6 Files in the Installation Kit Files in the Installation Kit C.5 Save Set E DECEDI$SCR_P_GEIS_05_UNRETRIEVED_DOC.DAT DECEDI$SCR_P_GEIS_06_SENDER_ERROR.DAT DECEDI$SCR_P_GEIS_07_SENDER_SUMMARY.DAT DECEDI$SCR_P_GEIS_08_ERROR_RECOVERY.DAT DECEDI$SCR_P_GEIS_09_SENDER_DOC.DAT DECEDI$SCR_P_GEIS_10_LOGOUT.DAT DECEDI$SCR_P_MCDD_01_LOGIN.DAT DECEDI$SCR_P_MCDD_02_PRODUCTION.DAT DECEDI$SCR_P_MCDD_03_LOGOUT.DAT DECEDI$SCR_TRAX_01_LOGIN.DAT DECEDI$SCR_TRAX_02_PASS.DAT DECEDI$SCR_TRAX_03_LISTR.DAT DECEDI$SCR_TRAX_04_XMIT.DAT DECEDI$SCR_TRAX_05_PARSE.DAT DECEDI$SCR_TRAX_06_LOGOUT.DAT DECEDI$SCR_TRAX_LOGOUT_ALT.DAT DECEDI$SRV_CONFIGURATION.DAT DECEDI$SRV_CONFIGURATION.FDL DECEDI$SRV_CONFIG_DEFS.DAT DECEDI$SRV_PARAMETER.DAT DECEDI$SRV_PARAMETER.FDL DECEDI$SUB_COPY_FS.EXE DECEDI$SUB_DN_FS.EXE DECEDI$SUB_RIP_FS.EXE DECEDI$TRANSMISSION_AUDIT.FDL DECEDI$TRANSMISSION_HISTORY.FDL DECEDI$TRAX_REFETCH_FILE.COM DECEDI$VAN_APPEND_SENDFILES.COM DECEDI$VAN_EDIC_APPEND_XFILES.COM (OpenVMS VAX only) DECEDI$VAN_EDIC_CLEANUP.COM (OpenVMS VAX only) DECEDI$VAN_EDIC_CONVERT.COM (OpenVMS VAX only) DECEDI$VAN_EDIC_CONVERT.FDL (OpenVMS VAX only) DECEDI$VAN_EDIC_CONVERT2.FDL (OpenVMS VAX only) DECEDI$VAN_EDIC_DELETE_OLD_XFILE.COM (OpenVMS VAX only) DECEDI$VAN_EDIC_PARSE_REPORTS.COM (OpenVMS VAX only) DECEDI$VAN_TRAX.EXE DECEDI$X25.EXE DECEDI$X252.EXE DECEDI$X25_FORCE_PWD.EXE DECEDI$X25_MIGRATE.EXE DECEDI$X400.EXE (OpenVMS VAX only) MTA$XAPI_SHR.EXE_PATCH (OpenVMS VAX only) Files in the Installation Kit C-7 Files in the Installation Kit C.6 Save Set F C.6 Save Set F DECEDI$GUI.EXE DECEDI_POST_FETCH.C EDIFACT_901_DIRECTORY.DAT EDIFACT_901_MINVOX_DOCUMENT.DAT FBR$ARCHIVE.COM FBR$AUDIT_DATABASE.RBR FBR$DCL.CLD FBR$DECEDI_EXTRACT.COM FBR$DECEDI_EXTRACT.EXE FBR$EXAMPLE.DAT FBR$EXAMPLE.FBO FBR$EXTRACT_INSTALL.COM FBR$HELP.HLP FBR$IVP.COM FBR$MESSAGES.H FBR$MESSAGES.OBJ FBR$RECOVER.EXE FBR$RTLIBRARY.OLB FBR$RUNTIME.EXE FBR$TRACKING.EXE FBR$UI.EXE MINVOX_IN.DAT MINVOX_IN.FBO MINVOX_OUT.DAT MINVOX_OUT.FBO PROFILE-DEC-DIRECT-UK-LTD.DAT PROFILE-SHINY-NEW-SYSTEMS.DAT C-8 Files in the Installation Kit D _________________________________________________________________ File Protection on the Installed Files D.1 OpenVMS AXP Server Files This section lists the files that are installed on an OpenVMS AXP Server. For lists of the files installed on an OpenVMS VAX Server, see Section D.4. D.1.1 Files in DECEDI$TOP:[000000] The files in this directory all have the following security: 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+WRITE+EXECUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE Table_D-1_Files_in_DECEDI$TOP:[000000]_____________________ Size File__________________(blocksOwner____Protection___________ 3780PLUS.DIR 1 [DECEDI] RWED,RWED,, DECEDI$ARCHIVE_ 3 [DECEDI] RWED,RWED,, DB.DIR (continued on next page) File Protection on the Installed Files D-1 File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-1_(Cont.)_Files_in_DECEDI$TOP:[000000]_____________ Size File__________________(blocksOwner____Protection___________ DECEDI$ARCHREPORTS.DIR1 [DECEDI] RWED,RWED,, DECEDI$AUDIT_DB.DIR 3 [DECEDI] RWED,RWED,, BACKUP.DIR 1 [DECEDI] RWED,RWED,, CACHE.DIR 1 [DECEDI] RWED,RWED,, CVP.DIR 1 [DECEDI] RWED,RWED,, DATA.DIR 13 [DECEDI] RWED,RWED,, DS_SCRATCH.DIR 1 [DECEDI] RWED,RWED,, ERROR.DIR 1 [DECEDI] RWED,RWED,, MAP_TABLES.DIR 1 [DECEDI] RWED,RWED,, MESSAGE_UPDATES.DIR 1 [DECEDI] RWED,RWED,, STORE_1.DIR 1 [DECEDI] RWED,RWED,, STORE_10.DIR 1 [DECEDI] RWED,RWED,, STORE_11.DIR 1 [DECEDI] RWED,RWED,, STORE_12.DIR 1 [DECEDI] RWED,RWED,, STORE_13.DIR 1 [DECEDI] RWED,RWED,, STORE_14.DIR 1 [DECEDI] RWED,RWED,, STORE_15.DIR 1 [DECEDI] RWED,RWED,, STORE_16.DIR 1 [DECEDI] RWED,RWED,, STORE_17.DIR 1 [DECEDI] RWED,RWED,, STORE_18.DIR 1 [DECEDI] RWED,RWED,, STORE_19.DIR 1 [DECEDI] RWED,RWED,, STORE_2.DIR 1 [DECEDI] RWED,RWED,, STORE_20.DIR 1 [DECEDI] RWED,RWED,, STORE_3.DIR 1 [DECEDI] RWED,RWED,, STORE_4.DIR 1 [DECEDI] RWED,RWED,, STORE_5.DIR 1 [DECEDI] RWED,RWED,, STORE_6.DIR 1 [DECEDI] RWED,RWED,, STORE_7.DIR 1 [DECEDI] RWED,RWED,, (continued on next page) D-2 File Protection on the Installed Files File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-1_(Cont.)_Files_in_DECEDI$TOP:[000000]_____________ Size File__________________(blocksOwner____Protection___________ STORE_8.DIR 1 [DECEDI] RWED,RWED,, STORE_9.DIR 1 [DECEDI] RWED,RWED,, TEMP.DIR 1 [DECEDI] RWED,RWED,, TOOLS.DIR 2 [DECEDI] RWED,RWED,, VANREPORTS.DIR________1______[DECEDI]_RWED,RWED,,__________ D.1.2 Files in DECEDI$TOP:[ARCHIVE_DB] The files in this directory all have the following security: IDENTIFIER=[DECEDI], ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-2_Files_in_DECEDI$TOP:[ARCHIVE_DB]_________________ DECEDI$ARCHIVE_DB.RDA 1196 [DECEDI] (RWED,R,,) DECEDI$ARCHIVE_DB.RDB 99 [DECEDI] (RWED,R,,) DECEDI$ARCHIVE_DB.SNP 202 [DECEDI] (RWED,R,,) DECEDI$ARCHIVE_DB_ 2414 [DECEDI] (RWED,R,,) CHF.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) CHF.SNP DECEDI$ARCHIVE_DB_ 3224 [DECEDI] (RWED,R,,) CLF.RDA DECEDI$ARCHIVE_DB_ 808 [DECEDI] (RWED,R,,) CLF.SNP DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) MISC_COMS_1.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) MISC_COMS_1.SNP (continued on next page) File Protection on the Installed Files D-3 File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-2_(Cont.)_Files_in_DECEDI$TOP:[ARCHIVE_DB]_________ DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) MISC_COMS_2.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) MISC_COMS_2.SNP DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) MISC_TRANS_1.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) MISC_TRANS_1.SNP DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) MISC_TRANS_2.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) MISC_TRANS_2.SNP DECEDI$ARCHIVE_DB_ 12500 [DECEDI] (RWED,R,,) THF.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) THF.SNP DECEDI$ARCHIVE_DB_ 7240 [DECEDI] (RWED,R,,) TLF.RDA DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) TLF.SNP____________________________________________________ D.1.3 Files in DECEDI$TOP:[AUDIT_DB] The files in this directory all have the following security: IDENTIFIER=[DECEDI], ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-3_Files_in_DECEDI$TOP:[AUDIT_DB]___________________ DECEDI$AUDIT_DB.RDA 1196 [DECEDI] (RWED,R,,) DECEDI$AUDIT_DB.RDB 99 [DECEDI] (RWED,R,,) DECEDI$AUDIT_DB.SNP 202 [DECEDI] (RWED,R,,) (continued on next page) D-4 File Protection on the Installed Files File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-3_(Cont.)_Files_in_DECEDI$TOP:[AUDIT_DB]___________ DECEDI$AUDIT_DB_ 2414 [DECEDI] (RWED,R,,) CHF.RDA DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) CHF.SNP DECEDI$AUDIT_DB_ 3224 [DECEDI] (RWED,R,,) CLF.RDA DECEDI$AUDIT_DB_ 808 [DECEDI] (RWED,R,,) CLF.SNP DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,R,,) COMS_1.RDA DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,R,,) COMS_1.SNP DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,R,,) COMS_2.RDA DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,R,,) COMS_2.SNP DECEDI$AUDIT_DB_MISC_ 404 [DECEDI] (RWED,R,,) TRANS_1.RDA DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,R,,) TRANS_1.SNP DECEDI$AUDIT_DB_MISC_ 804 [DECEDI] (RWED,R,,) TRANS_2.RDA DECEDI$AUDIT_DB_MISC_ 202 [DECEDI] (RWED,R,,) TRANS_2.SNP DECEDI$AUDIT_DB_ 17998 [DECEDI] (RWED,R,,) THF.RDA DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) THF.SNP DECEDI$AUDIT_DB_ 8684 [DECEDI] (RWED,R,,) TLF.RDA DECEDI$AUDIT_DB_ 404 [DECEDI] (RWED,R,,) TLF.SNP____________________________________________________ File Protection on the Installed Files D-5 File Protection on the Installed Files D.1 OpenVMS AXP Server Files D.1.4 Files in DECEDI$TOP:[CVP] Directory files within DECEDI$TOP:[CVP] have the following security: 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+WRITE+EXECUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE Table_D-4_Directory_Files_in_DECEDI$TOP:[CVP]______________ Size File_______________________(blocksOwner____Protection______ IMPEXP.DIR 1 [DECEDI] RWED, RWED, , WORK.DIR___________________1______[DECEDI]_RWED,_RWED,_,___ Non-directory files within DECEDI$TOP:[CVP] have the following security: IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-5_Non-Directory_Files_in_DECEDI$TOP:[CVP]__________ Size File__________________(blocksOwner____Protection___________ DECEDI$CVP.COM 55 [DECEDI] RWED,RWED,RE,RE DECEDI$CVP_ 22 [DECEDI] RWED,RWED,RE,RE COMPARE.COM (continued on next page) D-6 File Protection on the Installed Files File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-5_(Cont.)_Non-Directory_Files_in_DECEDI$TOP:[CVP]__ Size File__________________(blocksOwner____Protection___________ DECEDI$CVP_ 65 [DECEDI] RWED,RWED,RE,RE FETCH.EXE DECEDI$CVP_ 11 [DECEDI] RWED,RWED,RE,RE LOOPBACK.COM DECEDI$CVP_RUN_ 5 [DECEDI] RWED,RWED,RE,RE FETCH.COM DECEDI$CVP_SEND.DAT 1 [DECEDI] RWED,RWED,RE,RE DECEDI$CVP_SEND.EXE___65_____[DECEDI]_RWED,RWED,RE,RE______ D.1.5 Files in DECEDI$TOP:[DATA] The files in this directory all have the following security: IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-6_Files_in_DECEDI$TOP:[DATA]_______________________ Size File___________________(blocksOwner____Protection__________ DECEDI$ACCESS.DAT 15 [DECEDI] RWED,RWED,RE, DECEDI$ACCESS.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$AGREEMENTS_ 3 [DECEDI] RWED,RWED,RE,RE DETAIL_TABLE.FDL DECEDI$AGREEMENTS_ 4 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$CLIENT_ 2 [DECEDI] RWED,RWED,RE,RE APPLICATIONS.FDL (continued on next page) File Protection on the Installed Files D-7 File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-6_(Cont.)_Files_in_DECEDI$TOP:[DATA]_______________ Size File___________________(blocksOwner____Protection__________ DECEDI$CONTROL_ 2 [DECEDI] RWED,RWED,RE,RE NUM.FDL DECEDI$DATA_DESC.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$DATA_ 3 [DECEDI] RWED,RWED,RE,RE LABEL.FDL DECEDI$DATA_SET_ 3 [DECEDI] RWED,RWED,RE,RE ID.DAT DECEDI$DOCUMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$DOC_AREA_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$DOC_DESC_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE CODES.FDL DECEDI$ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$FA_MAPPING_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$FORMAT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$IVP_ 3 [DECEDI] RWED,RWED,RE,RE CHECKSUMS.FDL DECEDI$JOB_DESC.FDL 3 [DECEDI] RWED,RWED,RE,RE DECEDI$MGT_ 3 [DECEDI] RWED,RWED,RE,RE CONFIG.FDL DECEDI$NODE_ 2 [DECEDI] RWED,RWED,RE,RE CONFIGURATION_ DETAILS.FDL DECEDI$PARAMETERS_ 2 [DECEDI] RWED,RWED,RE,RE FILE.FDL (continued on next page) D-8 File Protection on the Installed Files File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-6_(Cont.)_Files_in_DECEDI$TOP:[DATA]_______________ Size File___________________(blocksOwner____Protection__________ DECEDI$PARTNER_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_DOCUMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_DOC_AREA_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_DOC_DESC_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE CODES.FDL DECEDI$P_ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_SEGMENT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_SEG_ 2 [DECEDI] RWED,RWED,RE,RE DESC.FDL DECEDI$P_SUB_ELE_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$QUALIFIER_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$RESERVED_DATA_ 3 [DECEDI] RWED,RWED,RE,RE LABELS.FDL DECEDI$RESERVED_SEG_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$RES_DATA_ 216 [DECEDI] RWED,RWED,RE,RE LABELS_EDIF.DAT DECEDI$RES_DATA_ 219 [DECEDI] RWED,RWED,RE,RE LABELS_ODET.DAT DECEDI$RES_DATA_ 219 [DECEDI] RWED,RWED,RE,RE LABELS_TDCC.DAT DECEDI$RES_DATA_ 222 [DECEDI] RWED,RWED,RE,RE LABELS_TRAD.DAT (continued on next page) File Protection on the Installed Files D-9 File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-6_(Cont.)_Files_in_DECEDI$TOP:[DATA]_______________ Size File___________________(blocksOwner____Protection__________ DECEDI$RES_DATA_ 222 [DECEDI] RWED,RWED,RE,RE LABELS_X12.DAT DECEDI$RES_SEG_TABLE_ 9 [DECEDI] RWED,RWED,RE,RE EDIF.DAT DECEDI$RES_SEG_TABLE_ 9 [DECEDI] RWED,RWED,RE,RE ODET.DAT DECEDI$RES_SEG_TABLE_ 9 [DECEDI] RWED,RWED,RE,RE TDCC.DAT DECEDI$RES_SEG_TABLE_ 9 [DECEDI] RWED,RWED,RE,RE TRAD.DAT DECEDI$RES_SEG_TABLE_ 9 [DECEDI] RWED,RWED,RE,RE X12.DAT DECEDI$SCHEDULE.DAT 135 [DECEDI] RWED,RWED,RE,RE DECEDI$SCHEDULE.FDL 3 [DECEDI] RWED,RWED,RE,RE DECEDI$SCR_P_GEIS_01_ 4 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT DECEDI$SCR_ 5 [DECEDI] RWED,RWED,RE,RE P_GEIS_02_ PRODUCTION.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_03_SENDER_ STATUS.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_04_RECEIVER_ STATUS.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_05_ UNRETRIEVED_DOC.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_06_SENDER_ ERROR.DAT (continued on next page) D-10 File Protection on the Installed Files File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-6_(Cont.)_Files_in_DECEDI$TOP:[DATA]_______________ Size File___________________(blocksOwner____Protection__________ DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_07_SENDER_ SUMMARY.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_08_ERROR_ RECOVERY.DAT DECEDI$SCR_P_GEIS_09_ 2 [DECEDI] RWED,RWED,RE,RE SENDER_DOC.DAT DECEDI$SCR_P_GEIS_10_ 22 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT DECEDI$SCR_P_MCDD_01_ 3 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT DECEDI$SCR_ 3 [DECEDI] RWED,RWED,RE,RE P_MCDD_02_ PRODUCTION.DAT DECEDI$SCR_P_MCDD_03_ 22 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT DECEDI$SCR_TRAX_01_ 14 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT DECEDI$SCR_TRAX_02_ 11 [DECEDI] RWED,RWED,RE,RE PASS.DAT DECEDI$SCR_TRAX_03_ 5 [DECEDI] RWED,RWED,RE,RE LISTR.DAT DECEDI$SCR_TRAX_04_ 14 [DECEDI] RWED,RWED,RE,RE XMIT.DAT DECEDI$SCR_TRAX_05_ 5 [DECEDI] RWED,RWED,RE,RE PARSE.DAT DECEDI$SCR_TRAX_06_ 9 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT DECEDI$SCR_TRAX_ 11 [DECEDI] RWED,RWED,RE,RE LOGOUT_ALT.DAT (continued on next page) File Protection on the Installed Files D-11 File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-6_(Cont.)_Files_in_DECEDI$TOP:[DATA]_______________ Size File___________________(blocksOwner____Protection__________ DECEDI$SEGMENT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$SEG_DESC.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$SEQ_ 3 [DECEDI] RWED,RWED,RE,RE HISTORY.FDL DECEDI$SITE_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$SRV_ 582 [DECEDI] RWED,RWED,RE,RE CONFIGURATION.DAT DECEDI$SRV_ 13 [DECEDI] RWED,RWED,RE,RE CONFIGURATION.FDL DECEDI$SRV_CONFIG_ 582 [DECEDI] RWED,RWED,RE,RE DEFS.DAT DECEDI$SRV_ 27 [DECEDI] RWED,RWED,RE,RE PARAMETER.DAT DECEDI$SRV_ 2 [DECEDI] RWED,RWED,RE,RE PARAMETER.FDL DECEDI$SUB_ELE_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$SYSTEM_ 2 [DECEDI] RWED,RWED,RE,RE PARAMETERS.FDL DECEDI$SYSTEM_ 15 [DECEDI] RWED,RWED,RE,RE VERSIONS.DAT DECEDI$SYSTEM_ 2 [DECEDI] RWED,RWED,RE,RE VERSIONS.FDL DECEDI$TEL_ 2 [DECEDI] RWED,RWED,RE,RE TRANSFER.FDL DECEDI$TP_CODE_ 3 [DECEDI] RWED,RWED,RE,RE TRANS.FDL DECEDI$TP_DATA_ 3 [DECEDI] RWED,RWED,RE,RE LABEL.FDL (continued on next page) D-12 File Protection on the Installed Files File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-6_(Cont.)_Files_in_DECEDI$TOP:[DATA]_______________ Size File___________________(blocksOwner____Protection__________ DECEDI$TP_DOCUMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_DOC_AREA_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_QUAL_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_SEGMENT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_STD_ 3 [DECEDI] RWED,RWED,RE,RE VERS.FDL DECEDI$TRANSMISSION_ 2 [DECEDI] RWED,RWED,RE,RE FILE_DETAILS.FDL DECEDI$VAN_APPEND_ 4 [DECEDI] RWED,RWED,RE,RE SENDFILES.COM______________________________________________ D.1.6 Files in DECEDI$TOP:[TOOLS] The files in this directory all have the following security: IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=[*,*],ACCESS=NONE Table_D-7_Files_in_DECEDI$TOP:[TOOLS]______________________ Size File__________________(blocksOwner____Protection___________ DECEDI$ARCHIVE_ 34 [DECEDI] (RWED,RWED,RE,RE) DATABASE.SQL (continued on next page) File Protection on the Installed Files D-13 File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-7_(Cont.)_Files_in_DECEDI$TOP:[TOOLS]______________ Size File__________________(blocksOwner____Protection___________ DECEDI$ARCHIVE_DB_ 825 [DECEDI] (RWED,RWED,RE,RE) CREATE.EXE DECEDI$AUDIT_ 37 [DECEDI] (RWED,RWED,RE,RE) DATABASE.SQL DECEDI$AUDIT_ 265 [DECEDI] (RWED,RWED,RE,RE) EXTRACT.COM DECEDI$AUDIT_ 2092 [DECEDI] (RWED,RWED,RE,RE) EXTRACT.EXE DECEDI$AUDIT_ 3 [DECEDI] (RWED,RWED,RE,RE) EXTRACT_TABLES.DAT DECEDI$AUDIT_USER_ 1 [DECEDI] (RWED,RWED,RE,RE) REF_TABLES.DAT DECEDI$DB_CREATE.EXE 831 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG.COM 5 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG.EXE 133 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_COPY.COM 11 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_DOC.PS 164 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_DOC.TXT 72 [DECEDI] (RWED,RWED,RE,RE) DECEDI$ELM.TPU 178 [DECEDI] (RWED,RWED,RE,RE) DECEDI$ELM.TPU$SECTION74 [DECEDI] (RWED,RWED,RE,RE) DECEDI$ELM_USER_ 90 [DECEDI] (RWED,RWED,RE,RE) GUIDE.PS DECEDI$ELM_USER_ 30 [DECEDI] (RWED,RWED,RE,RE) GUIDE.TXT DECEDI$LINK_TUNE_ 3 [DECEDI] (RWED,RWED,RE,RE) DB.COM DECEDI$LINK_TUNE_ 3 [DECEDI] (RWED,RWED,RE,RE) SYINFO.COM DECEDI$MESSAGE_ 168 [DECEDI] (RWED,RWED,RE,RE) UPDATES.COM DECEDI$TAILOR.COM 135 [DECEDI] (RWED,RWED,RE,RE) (continued on next page) D-14 File Protection on the Installed Files File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-7_(Cont.)_Files_in_DECEDI$TOP:[TOOLS]______________ Size File__________________(blocksOwner____Protection___________ DECEDI$TEL.EXE 288 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL_DOC.PS 259 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL_DOC.TXT 128 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TRAX_REFETCH_ 15 [DECEDI] (RWED,RWED,RE,RE) FILE.COM DECEDI$TUNE_DB.EXE 198 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.OBJ 243 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.PS 324 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.TXT 165 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_ 9 [DECEDI] (RWED,RWED,RE,RE) SYINFO.EXE DECEDI$TUNE_ 17 [DECEDI] (RWED,RWED,RE,RE) SYINFO.OBJ DECEDI$V21_ 786 [DECEDI] (RWED,RWED,RE,RE) APPFILMIGR.EXE DECEDI$V21_ARCHIVE_ 780 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.EXE DECEDI$V21_ 41 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.COM DECEDI$V21_ 1148 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.EXE DECEDI$X25_FORCE_ 63 [DECEDI] (RWED,RWED,RE,RE) PWD.EXE DECEDI$X25_ 1460 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.EXE DECEDI.CRL 19 [DECEDI] (RWED,RWED,RE,RE) DECEDI_CLIENT_ L 5 [DECEDI] (RWED,RWED,RE,) NODES.CO DECEDI_SYSTEM_ 2 [DECEDI] (RWED,RWED,RE,RE) CONTEXT.COL (continued on next page) File Protection on the Installed Files D-15 File Protection on the Installed Files D.1 OpenVMS AXP Server Files Table_D-7_(Cont.)_Files_in_DECEDI$TOP:[TOOLS]______________ Size File__________________(blocksOwner____Protection___________ DECEDI_USER_ 2 [DECEDI] (RWED,RWED,RE,RE) CONTEXT.COL________________________________________________ D.2 OpenVMS AXP Server FileBridge Directory Structure This section lists the files in the FileBridge directory structure on an OpenVMS AXP Server. For a list of the files in the FileBridge directory structure on an OpenVMS VAX Server, see Section D.5. D.2.1 Files in [FILEBRIDGE] Security for DIRECTORY files in this directory unless otherwise stated: DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RE,GROUP:,WORLD: IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=FBR$SUPERVISOR,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE IDENTIFIER=FBR$OPERATIONS,OPTIONS=DEFAULT,ACCESS=READ+EXECUTE IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE IDENTIFIER=FBR$DEVELOPMENT,OPTIONS=DEFAULT,ACCESS=READ+EXECUTE Security for non-directory files in this directory: D-16 File Protection on the Installed Files File Protection on the Installed Files D.2 OpenVMS AXP Server FileBridge Directory Structure IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) Table_D-8_Files_in_[FILEBRIDGE]____________________________ Size File__________________(blocksOwner____Protection___________ .DIR[1] 1 [DECEDI] RWE,RWE,RE,E FBR$AUDIT_ 11 [SYSTEM] RWED,RE,, DATABASE.RBR TEST_DB.DIR 1 [DECEDI] RWE,RWE,RE,E [1]This_name_is_the_date_and_time_that_the_directory_was___ created ___________________________________________________________ D.2.2 Files in [FILEBRIDGE.] Table D-9 Files in [FILEBRIDGE.] IDENTIFIER=[SYSTEM], ACCESS=READ + WRITE + CONTROL + BIT_5 + BIT_ 6 + BIT_7 + BIT_8 + BIT_9 + BIT_10 + BIT_11 + BIT_12 + BIT_13 + BIT_14_+_BIT_15_+_BIT_16_+_BIT_17_+_BIT_18_)_____________________ Size File__________________(blocksOwner____Protection___________ FBR$DB.DIR 1 [SYSTEM] RWE,RWE,RE,E FBR$HISTORY.DIR 1 [SYSTEM] RWE,RWE,RE,E FBR$AUDIT_DATA.RDA 8048 [SYSTEM] RWED,R,, FBR$AUDIT_DATA.SNP 404 [SYSTEM] RWED,R,, FBR$AUDIT_ 1612 [SYSTEM] RWED,R,, DATABASE.RDA FBR$AUDIT_ 88 [SYSTEM] RWED,R,, DATABASE.RDB[1] [1]IDENTIFIER=FBR$SUPERVISOR,_ACCESS=READ_+_WRITE_+_EXECUTE + DELETE + CONTROL IDENTIFIER=FBR$OPERATIONS, ACCESS=READ + EXECUTE IDENTIFIER=FBR$DEVELOPMENT, ACCESS=READ + EXECUTE (continued on next page) File Protection on the Installed Files D-17 File Protection on the Installed Files D.2 OpenVMS AXP Server FileBridge Directory Structure Table_D-9_(Cont.)_Files_in_[FILEBRIDGE.]________ Size File__________________(blocksOwner____Protection___________ FBR$AUDIT_ 202 [SYSTEM] RWED,R,, DATABASE.SNP FBR$AUDIT_INDEX.RDA 208 [SYSTEM] RWED,R,, FBR$AUDIT_INDEX.SNP 778 [SYSTEM] RWED,R,, FBR$RUN_ID.DAT[2] 1 [SYSTEM] RWED,RWED,RW, [2]DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RE,GROUP:,WORLD:___ IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ + WRITE + EXECUTE + DELETE + CONTROL IDENTIFIER=FBR$SUPERVISOR,OPTIONS=DEFAULT,ACCESS=READ + WRITE + EXECUTE + DELETE + CONTROL IDENTIFIER=FBR$OPERATIONS,ACCESS=READ + WRITE + EXECUTE IDENTIFIER=FBR$OPERATIONS,OPTIONS=DEFAULT,ACCESS=READ + WRITE + EXECUTE IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ + WRITE + EXECUTE IDENTIFIER=FBR$DEVELOPMENT,OPTIONS=DEFAULT,ACCESS=READ + WRITE + EXECUTE ___________________________________________________________ D.2.3 Files in [FILEBRIDGE.TEST_DB] Security for files in this directory unless otherwise stated: IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE Table_D-10_Files_in_[FILEBRIDGE.TEST_DB]___________________ Size File__________________(blocksOwner____Protection___________ FBR$DB.DIR 1 [SYSTEM] RWE,RWE,RE,E FBR$HISTORY.DIR_______1______[SYSTEM]_RWE,RWE,RE,E_________ D-18 File Protection on the Installed Files File Protection on the Installed Files D.3 OpenVMS AXP Server System Directory Structure D.3 OpenVMS AXP Server System Directory Structure D.3.1 Files in SYS$COMMON:[SYS$STARTUP] Table_D-11_Files_in_SYS$COMMON:[SYS$STARTUP]_______________ Size File__________________(blocksOwner____Protection___________ DECEDI$SHUTDOWN.COM 34 [SYSTEM] RWED,RWED,RWED, DECEDI$STARTUP.COM 59 [SYSTEM] RWED,RWED,RWED, DECEDI$SYSHUTDOWN.COM 5 [SYSTEM] RWED,RWED,RWED, DECEDI$SYSTARTUP.COM 5 [SYSTEM] RWED,RWED,RWED, ___________________________________________________________ D.3.2 Files in SYS$COMMON:[SYSEXE] Table_D-12_Files_in_SYS$COMMON:[SYSEXE]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$3780.EXE 1980 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$AFS_MAIN.EXE 1862 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$ARCHIVE_ 1723 [SYSTEM] (RWED,RWED,RE,RE) SERVER.EXE DECEDI$CC_PSI_ 1555 [SYSTEM] (RWED,RWED,RE,RE) INTERFACE.EXE DECEDI$CC_TRAX_ 1580 [SYSTEM] (RWED,RWED,RE,RE) RESEND_TIMEOUT.EXE DECEDI$CIS.EXE 24 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CLI.EXE 103 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CNV_ 1879 [SYSTEM] (RWED,RWED,RE,RE) EDIFACT.EXE DECEDI$CNV_ 1979 [SYSTEM] (RWED,RWED,RE,RE) TRADACOMS.EXE (continued on next page) File Protection on the Installed Files D-19 File Protection on the Installed Files D.3 OpenVMS AXP Server System Directory Structure Table_D-12_(Cont.)_Files_in_SYS$COMMON:[SYSEXE]____________ Size File__________________(blocksOwner____Protection___________ DECEDI$CNV_X12.EXE 2774 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$COMMS_ 1760 [SYSTEM] (RWED,RWED,RE,RE) CONTROL.EXE DECEDI$DATA_ 419 [SYSTEM] (RWED,RWED,RE,RE) SERVER.EXE DECEDI$FS_DECNET.EXE 1602 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$FS_MAIN.EXE 1702 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$GUI.EXE 3003 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$IMPEXP.EXE 1698 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$INTERCHANGE.EXE20695 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$LOGIN.COM 5 [SYSTEM] (RWED,RWED,E,E) DECEDI$LOOK.COM 5 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$LOOK.EVE 1 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$MSF.EXE 2332 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$MST.EXE 444 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$OFTP.EXE 1847 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$PCR.EXE 90 [SYSTEM] (RWED,RWED,RE,) DECEDI$PEDI.EXE 2094 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$REPOSITORY.CR 43 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SERVICES.EXE 91 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SHUTDOWN.EXE 126 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$STARTUP.EXE 271 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SUB_COPY_ 1716 [SYSTEM] (RWED,RWED,RE,RE) FS.EXE DECEDI$SUB_DN_FS.EXE 1752 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SUB_RIP_ 1705 [SYSTEM] (RWED,RWED,RE,RE) FS.EXE DECEDI$TFB.EXE 1833 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TFB_X12.EXE 2526 [SYSTEM] (RWED,RWED,RE,RE) (continued on next page) D-20 File Protection on the Installed Files File Protection on the Installed Files D.3 OpenVMS AXP Server System Directory Structure Table_D-12_(Cont.)_Files_in_SYS$COMMON:[SYSEXE]____________ Size File__________________(blocksOwner____Protection___________ DECEDI$TFS.EXE 1750 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TRNS_ 1783 [SYSTEM] (RWED,RWED,RE,RE) EDIFACT.EXE DECEDI$TRNS_ 1935 [SYSTEM] (RWED,RWED,RE,RE) TRADACOMS.EXE DECEDI$TRNS_X12.EXE 3388 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$VAN_TRAX.EXE 1687 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$X25.EXE 1774 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$X252.EXE 1970 [SYSTEM] (RWED,RWED,RE,RE) DECEDI_USER_ 11 [SYSTEM] (RWED,RWED,RE,RE) CONTEXT.CO FBR$ARCHIVE.COM 193 [SYSTEM] (RWED,RWED,RE,RE) FBR$DECEDI_ 7 [SYSTEM] (RWED,RWED,RE,RE) EXTRACT.COM FBR$EXTRACT_ 9 [SYSTEM] (RWED,RWED,RE,RE) INSTALL.COM FBR$RECOVER.EXE 842 [SYSTEM] (RWED,RWED,RE,RE) FBR$RUNTIME.EXE 835 [SYSTEM] (RWED,RWED,RE,RE) FBR$TRACKING.EXE 713 [SYSTEM] (RWED,RWED,RE,RE) FBR$UI.EXE____________3121___[SYSTEM]_(RWED,RWED,RE,RE)____ D.3.3 Files in SYS$COMMON:[SYSHLP] Table_D-13_Files_in_SYS$COMMON:[SYSHLP]____________________ Size File___________________(blocksOwner____Protection__________ DECEDI$COMMAND_ 400 [SYSTEM] RWED,RWED,RWED,RE HELP.HLB DECEDI$ELM.HLB 1125 [SYSTEM] RWED,RWED,RWED,RE (continued on next page) File Protection on the Installed Files D-21 File Protection on the Installed Files D.3 OpenVMS AXP Server System Directory Structure Table_D-13_(Cont.)_Files_in_SYS$COMMON:[SYSHLP]____________ Size File___________________(blocksOwner____Protection__________ DECEDI$REVIEW_ 42 [SYSTEM] RWED,RWED,RWED,RE HELP.HLB DECEDI$UI_FIELD_ 507 [SYSTEM] RWED,RWED,RWED,RE HELP.HLB DECEDI$UI_HELP_KEYS_ 9 [SYSTEM] RWED,RWED,RWED,RE ENGLISH.TXT DECEDI021.RELEASE_ 286 [SYSTEM] RWED,RWED,RWED,RE NOTES______________________________________________________ D.3.4 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] Table_D-14_Files_in_SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI]____ Size File___________________(blocksOwner____Protection__________ DECEDI_POST_FETCH.C 17 [SYSTEM] RWED,RWED,RWED,RE EDIFACT_901_ 172 [SYSTEM] RWED,RWED,RWED,RE DIRECTORY.DAT EDIFACT_901_MINVOX_ 172 [SYSTEM] RWED,RWED,RWED,RE DOCUMENT.DAT MINVOX_IN.DAT 3 [SYSTEM] RWED,RWED,RWED,RE MINVOX_IN.FBO 63 [SYSTEM] RWED,RWED,RWED,RE MINVOX_OUT.DAT 2 [SYSTEM] RWED,RWED,RWED,RE MINVOX_OUT.FBO 80 [SYSTEM] RWED,RWED,RWED,RE PROFILE-DEC-DIRECT- 3 [SYSTEM] RWED,RWED,RWED,RE UK-LTD.DAT PROFILE-SHINY-NEW- 3 [SYSTEM] RWED,RWED,RWED,RE SYSTEMS.DAT________________________________________________ D-22 File Protection on the Installed Files File Protection on the Installed Files D.3 OpenVMS AXP Server System Directory Structure D.3.5 Files in SYS$COMMON:[SYSLIB] Table_D-15_Files_in_SYS$COMMON:[SYSLIB]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$APPSHR.EXE 658 [SYSTEM] RWED,RWE,RWE,RE DECEDI$APPSHR_ 45 [SYSTEM] RWED,RWE,RWE,RE V2.EXE DECEDI$COMM_ 917 [SYSTEM] RWED,RWE,RWE,RE APPSHR.EXE DECEDI$DATACHECKSHR.EX7 [SYSTEM] RWED,RWED,RE,RE DECEDI$EXTSHR.EXE 830 [SYSTEM] RWED,RWE,RWE,RE DECEDI$NUMSHR.EXE 416 [SYSTEM] RWED,RWE,RWE,RE DECEDI$SECTION.TPU$SEC122N [SYSTEM] RWED,RWED,RE,RE DECEDI$SEQCHECKSHR.EXE30 [SYSTEM] RWED,RWED,RE,RE DECEDI_API_COMMON.H 42 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_DEF.H 10 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_MSGS.H 22 [SYSTEM] RWED,RWE,RWE,RE DECEDI_PLATFORMS.H 12 [SYSTEM] RWED,RWE,RWE,RE FBR$DECEDI_ 135 [SYSTEM] RWED,RWED,RWED,RE EXTRACT.EXE FBR$MESSAGES.H 40 [SYSTEM] RWED,RWED,RWED,RE FBR$MESSAGES.OBJ 119 [SYSTEM] RWED,RWED,RWED,RE FBR$RTLIBRARY.OLB_____1701___[SYSTEM]_RWED,RWED,RWED,RE____ D.3.6 Files in SYS$COMMON:[SYSMGR] File Protection on the Installed Files D-23 File Protection on the Installed Files D.3 OpenVMS AXP Server System Directory Structure Table_D-16_Files_in_SYS$COMMON:[SYSMGR]____________________ Size File___________________(blocksOwner____Protection__________ DECEDI$DEFINE_ 3 [SYSTEM] RWED,RWED,RWED, MAPPER_LOGICALS.COM DECEDI$LOGICALS.COM 18 [SYSTEM] RWED,RWED,RWED, DECEDI$SET_MAPPER_ 3 [SYSTEM] RWED,RWED,RWED, DATABASE.COM DECEDI$SYLOGICALS.COM 9 [SYSTEM] RWED,RWED,RWED, ___________________________________________________________ D.3.7 Files in SYS$COMMON:[SYSMSG] Table_D-17_Files_in_SYS$COMMON:[SYSMSG]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$CMSGS.EXE 31 [SYSTEM] RWED,RWED,RE,RE DECEDI$MESSAGE.EXE____544____[SYSTEM]_RWED,RWED,RE,RE______ D.3.8 Files in SYS$COMMON:[SYSTEST] Table_D-18_Files_in_SYS$COMMON:[SYSTEST]___________________ Size File__________________(blocksOwner____Protection___________ DECEDI$IVP.COM 55 [SYSTEM] RWED,RWED,RWED, DECEDI$IVP_ 416 [SYSTEM] RWED,RWED,RWED, CHECKSUMS.DAT FBR$IVP.COM 18 [SYSTEM] RWED,RWED,RWED, FBR.DIR_______________1______[SYSTEM]_RWED,RWE,RE,RE_______ D-24 File Protection on the Installed Files File Protection on the Installed Files D.3 OpenVMS AXP Server System Directory Structure D.3.9 Files in SYS$COMMON:[SYSTEST.FBR] Table_D-19_Files_in_SYS$COMMON:[SYSTEST.FBR]_______________ Size File__________________(blocksOwner____Protection___________ FBR$EXAMPLE.DAT 1 [SYSTEM] RWED,RWED,RWED,RE FBR$EXAMPLE.FBO_______376____[SYSTEM]_RWED,RWED,RWED,RE____ D.4 OpenVMS VAX Server Files This section lists the files that are installed on an OpenVMS VAX Server. For lists of the files installed on an OpenVMS AXP Server, see Section D.1. D.4.1 Files in DECEDI$TOP:[000000] The files in this directory all have the following security: 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+WRITE+EXECUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE Table_D-20_Files_in_DECEDI$TOP:[000000]____________________ Size File__________________(blocksOwner____Protection___________ 3780PLUS.DIR 1 [DECEDI] RWED,RWED,, ARCHIVE_DB.DIR 1 [DECEDI] RWED,RWED,, ARCHREPORTS.DIR 1 [DECEDI] RWED,RWED,, (continued on next page) File Protection on the Installed Files D-25 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-20_(Cont.)_Files_in_DECEDI$TOP:[000000]____________ Size File__________________(blocksOwner____Protection___________ AUDIT_DB.DIR 1 [DECEDI] RWED,RWED,, BACKUP.DIR 1 [DECEDI] RWED,RWED,, CACHE.DIR 1 [DECEDI] RWED,RWED,, CVP.DIR 1 [DECEDI] RWED,RWED,, DATA.DIR 16 [DECEDI] RWED,RWED,, DS_SCRATCH.DIR 1 [DECEDI] RWED,RWED,, ERROR.DIR 1 [DECEDI] RWED,RWED,, MAP_TABLES.DIR 1 [DECEDI] RWED,RWED,, MESSAGE_UPDATES.DIR 1 [DECEDI] RWED,RWED,, STORE_1.DIR 1 [DECEDI] RWED,RWED,, STORE_10.DIR 1 [DECEDI] RWED,RWED,, STORE_11.DIR 1 [DECEDI] RWED,RWED,, STORE_12.DIR 1 [DECEDI] RWED,RWED,, STORE_13.DIR 1 [DECEDI] RWED,RWED,, STORE_14.DIR 1 [DECEDI] RWED,RWED,, STORE_15.DIR 1 [DECEDI] RWED,RWED,, STORE_16.DIR 1 [DECEDI] RWED,RWED,, STORE_17.DIR 1 [DECEDI] RWED,RWED,, STORE_18.DIR 1 [DECEDI] RWED,RWED,, STORE_19.DIR 1 [DECEDI] RWED,RWED,, STORE_2.DIR 1 [DECEDI] RWED,RWED,, STORE_20.DIR 1 [DECEDI] RWED,RWED,, STORE_3.DIR 1 [DECEDI] RWED,RWED,, STORE_4.DIR 1 [DECEDI] RWED,RWED,, STORE_5.DIR 1 [DECEDI] RWED,RWED,, STORE_6.DIR 1 [DECEDI] RWED,RWED,, STORE_7.DIR 1 [DECEDI] RWED,RWED,, STORE_8.DIR 1 [DECEDI] RWED,RWED,, (continued on next page) D-26 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-20_(Cont.)_Files_in_DECEDI$TOP:[000000]____________ Size File__________________(blocksOwner____Protection___________ STORE_9.DIR 1 [DECEDI] RWED,RWED,, TEMP.DIR 1 [DECEDI] RWED,RWED,, TOOLS.DIR 2 [DECEDI] RWED,RWED,, VANREPORTS.DIR________1______[DECEDI]_RWED,RWED,,__________ D.4.2 Files in DECEDI$TOP:[AUDIT_DB] The files in this directory all have the following security, unless stated otherwise: IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-21_Files_in_DECEDI$TOP:[AUDIT_DB]__________________ Size File__________________(blocksOwner____Protection___________ DECEDI$AUDIT_DB.RDA 1196 [DECEDI] (RWED,R,,) DECEDI$AUDIT_DB.RDB 99 [DECEDI] (RWED,R,,) DECEDI$AUDIT_DB.SNP 202 [DECEDI] (RWED,R,,) DECEDI$AUDIT_DB_ 2414 [DECEDI] (RWED,R,,) CHF.RDA DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) CHF.SNP DECEDI$AUDIT_DB_ 3224 [DECEDI] (RWED,R,,) CLF.RDA DECEDI$AUDIT_DB_ 808 [DECEDI] (RWED,R,,) CLF.SNP DECEDI$AUDIT_DB_ 404 [DECEDI] (RWED,R,,) MISC_COMS_1.RDA (continued on next page) File Protection on the Installed Files D-27 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-21_(Cont.)_Files_in_DECEDI$TOP:[AUDIT_DB]__________ Size File__________________(blocksOwner____Protection___________ DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) MISC_COMS_1.SNP DECEDI$AUDIT_DB_ 404 [DECEDI] (RWED,R,,) MISC_COMS_2.RDA DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) MISC_COMS_2.SNP DECEDI$AUDIT_DB_ 404 [DECEDI] (RWED,R,,) MISC_TRANS_1.RDA DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) MISC_TRANS_1.SNP DECEDI$AUDIT_DB_ 404 [DECEDI] (RWED,R,,) MISC_TRANS_2.RDA DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) MISC_TRANS_2.SNP DECEDI$AUDIT_DB_ 2012 [DECEDI] (RWED,R,,) THF.RDA DECEDI$AUDIT_DB_ 202 [DECEDI] (RWED,R,,) THF.SNP DECEDI$AUDIT_DB_ 2416 [DECEDI] (RWED,R,,) TLF.RDA DECEDI$AUDIT_DB_ 404 [DECEDI] (RWED,R,,) TLF.SNP____________________________________________________ D.4.3 Files in DECEDI$TOP:[ARCHIVE_DB] The files in this directory all have the following security, unless stated otherwise: D-28 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-22_Files_in_DECEDI$TOP:[ARCHIVE_DB]________________ Size File__________________(blocksOwner____Protection___________ DECEDI$ARCHIVE_ 1196 [DECEDI] (RWED,R,,) DB.RDA DECEDI$ARCHIVE_ 93 [DECEDI] (RWED,R,,) DB.RDB DECEDI$ARCHIVE_ 202 [DECEDI] (RWED,R,,) DB.SNP DECEDI$ARCHIVE_DB_ 2414 [DECEDI] (RWED,R,,) CHF.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) CHF.SNP DECEDI$ARCHIVE_DB_ 3224 [DECEDI] (RWED,R,,) CLF.RDA DECEDI$ARCHIVE_DB_ 808 [DECEDI] (RWED,R,,) CLF.SNP DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) MISC_COMS_1.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) MISC_COMS_1.SNP DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) MISC_TRANS_1.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) MISC_TRANS_1.SNP DECEDI$ARCHIVE_DB_ 2012 [DECEDI] (RWED,R,,) THF.RDA DECEDI$ARCHIVE_DB_ 202 [DECEDI] (RWED,R,,) THF.SNP (continued on next page) File Protection on the Installed Files D-29 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-22_(Cont.)_Files_in_DECEDI$TOP:[ARCHIVE_DB]________ Size File__________________(blocksOwner____Protection___________ DECEDI$ARCHIVE_DB_ 2416 [DECEDI] (RWED,R,,) TLF.RDA DECEDI$ARCHIVE_DB_ 404 [DECEDI] (RWED,R,,) TLF.SNP____________________________________________________ D.4.4 Files in DECEDI$TOP:[CVP] Directory files within DECEDI$TOP:[CVP] have the following security: 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+WRITE+EXECUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE Table_D-23_Directory_Files_in_DECEDI$TOP:[CVP]_____________ Size File__________________(blocksOwner____Protection___________ DECEDI$CVP.COM 55 [DECEDI] RWED,RWED,RE,RE DECEDI$CVP_ 22 [DECEDI] RWED,RWED,RE,RE COMPARE.COM DECEDI$CVP_ 39 [DECEDI] RWED,RWED,RE,RE FETCH.EXE DECEDI$CVP_ 11 [DECEDI] RWED,RWED,RE,RE LOOPBACK.COM DECEDI$CVP_RUN_ 5 [DECEDI] RWED,RWED,RE,RE FETCH.COM DECEDI$CVP_SEND.DAT 1 [DECEDI] RWED,RWED,RE,RE (continued on next page) D-30 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-23_(Cont.)_Directory_Files_in_DECEDI$TOP:[CVP]_____ Size File__________________(blocksOwner____Protection___________ DECEDI$CVP_SEND.EXE 38 [DECEDI] RWED,RWED,RE,RE IMPEXP.DIR 1 [DECEDI] RWED,RWED,, WORK.DIR______________1______[DECEDI]_RWED,RWED,,__________ D.4.5 Files in DECEDI$TOP:[DATA] The files in this directory all have the following security: IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-24_Files_in_DECEDI$TOP:[DATA]______________________ Size File____________________(blocksOwner____Protection_________ DECEDI$ACCESS.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$AGREEMENTS_ 3 [DECEDI] RWED,RWED,RE,RE DETAIL_TABLE.FDL DECEDI$AGREEMENTS_ 4 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$CLIENT_ 3 [DECEDI] RWED,RWED,RE,RE APPLICATIONS.FDL DECEDI$CONFIG_ 0 [DECEDI] RWED,RWED,RE,RE LOGICALS.DAT DECEDI$CONTROL_ 2 [DECEDI] RWED,RWED,RE,RE NUM.FDL DECEDI$DATA_DESC.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$DATA_LABEL.FDL 3 [DECEDI] RWED,RWED,RE,RE (continued on next page) File Protection on the Installed Files D-31 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$DATA_SET_ 3 [DECEDI] RWED,RWED,RE,RE ID.DAT DECEDI$DIAL.COM 11 [DECEDI] RWED,RWED,RE,RE DECEDI$DOCUMENT_ 5 [DECEDI] RWED,RWED,RE,RE AUDIT.FDL DECEDI$DOCUMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$DOC_AREA_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$DOC_DESC_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE CODES.FDL DECEDI$ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$FA_MAPPING_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$FORMAT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$IVP_ 3 [DECEDI] RWED,RWED,RE,RE CHECKSUMS.FDL DECEDI$JOB_DESC.FDL 3 [DECEDI] RWED,RWED,RE,RE DECEDI$MGT_CONFIG.FDL 3 [DECEDI] RWED,RWED,RE,RE DECEDI$NODE_ 2 [DECEDI] RWED,RWED,RE,RE CONFIGURATION_ DETAILS.FDL DECEDI$PARAMETERS_ 2 [DECEDI] RWED,RWED,RE,RE FILE.FDL DECEDI$PARTNER_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL (continued on next page) D-32 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$P_DOCUMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_DOC_AREA_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_DOC_DESC_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE CODES.FDL DECEDI$P_ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_SEGMENT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$P_SEG_DESC.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$P_SUB_ELE_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$QUALIFIER_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$RESERVED_DATA_ 3 [DECEDI] RWED,RWED,RE,RE LABELS.FDL DECEDI$RESERVED_SEG_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$RES_DATA_ 220 [DECEDI] RWED,RWED,RE,RE LABELS_EDIF.DAT DECEDI$RES_DATA_ 224 [DECEDI] RWED,RWED,RE,RE LABELS_ODET.DAT DECEDI$RES_DATA_ 224 [DECEDI] RWED,RWED,RE,RE LABELS_TDCC.DAT DECEDI$RES_DATA_ 224 [DECEDI] RWED,RWED,RE,RE LABELS_TRAD.DAT DECEDI$RES_DATA_ 224 [DECEDI] RWED,RWED,RE,RE LABELS_X12.DAT (continued on next page) File Protection on the Installed Files D-33 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$RES_SEG_TABLE_ 12 [DECEDI] RWED,RWED,RE,RE EDIF.DAT DECEDI$RES_SEG_TABLE_ 12 [DECEDI] RWED,RWED,RE,RE ODET.DAT DECEDI$RES_SEG_TABLE_ 12 [DECEDI] RWED,RWED,RE,RE TDCC.DAT DECEDI$RES_SEG_TABLE_ 12 [DECEDI] RWED,RWED,RE,RE TRAD.DAT DECEDI$RES_SEG_TABLE_ 12 [DECEDI] RWED,RWED,RE,RE X12.DAT DECEDI$SCHEDULE.DAT 135 [DECEDI] RWED,RWED,RE,RE DECEDI$SCHEDULE.FDL 3 [DECEDI] RWED,RWED,RE,RE DECEDI$SCR_EDIC_01_ 6 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT DECEDI$SCR_ 9 [DECEDI] RWED,RWED,RE,RE EDIC_02_ PRODUCTION1.DAT DECEDI$SCR_ 5 [DECEDI] RWED,RWED,RE,RE EDIC_03_ PRODUCTION2.DAT DECEDI$SCR_ 5 [DECEDI] RWED,RWED,RE,RE EDIC_04_ PRODUCTION3.DAT DECEDI$SCR_EDIC_05_ 11 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT DECEDI$SCR_GEIS_01_ 3 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT DECEDI$SCR_ 4 [DECEDI] RWED,RWED,RE,RE GEIS_02_ PRODUCTION.DAT (continued on next page) D-34 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE GEIS_03_SENDER_ STATUS.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE GEIS_04_RECEIVER_ STATUS.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE GEIS_05_UNRETRIEVED_ DOCUMENT.DAT DECEDI$SCR_GEIS_06_ 2 [DECEDI] RWED,RWED,RE,RE SENDER_ERROR.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE GEIS_07_SENDER_ SUMMARY.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE GEIS_08_ERROR_ RECOVERY.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE GEIS_09_SENDER_ RETRIEVED_DOC.DAT DECEDI$SCR_GEIS_10_ 12 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT DECEDI$SCR_MCDD_01_ 2 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT DECEDI$SCR_MCDD_02_ 11 [DECEDI] RWED,RWED,RE,RE PRODUCTION.DAT DECEDI$SCR_MCDD_03_ 7 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT DECEDI$SCR_P_GEIS_01_ 4 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT (continued on next page) File Protection on the Installed Files D-35 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$SCR_ 5 [DECEDI] RWED,RWED,RE,RE P_GEIS_02_ PRODUCTION.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_03_SENDER_ STATUS.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_04_RECEIVER_ STATUS.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_05_UNRETRIEVED_ DOC.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_06_SENDER_ ERROR.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_07_SENDER_ SUMMARY.DAT DECEDI$SCR_ 2 [DECEDI] RWED,RWED,RE,RE P_GEIS_08_ERROR_ RECOVERY.DAT DECEDI$SCR_P_GEIS_09_ 2 [DECEDI] RWED,RWED,RE,RE SENDER_DOC.DAT DECEDI$SCR_P_GEIS_10_ 22 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT DECEDI$SCR_P_MCDD_01_ 3 [DECEDI] RWED,RWED,RE,RE LOGIN.DAT DECEDI$SCR_ 3 [DECEDI] RWED,RWED,RE,RE P_MCDD_02_ PRODUCTION.DAT DECEDI$SCR_P_MCDD_03_ 22 [DECEDI] RWED,RWED,RE,RE LOGOUT.DAT (continued on next page) D-36 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$SEGMENT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$SEG_DESC.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$SEQ_ 3 [DECEDI] RWED,RWED,RE,RE HISTORY.FDL DECEDI$SITE_ 2 [DECEDI] RWED,RWED,RE,RE ROUTING.FDL DECEDI$SITE_TABLE.FDL 2 [DECEDI] RWED,RWED,RE,RE DECEDI$SRV_ 582 [DECEDI] RWED,RWED,RE,RE CONFIGURATION.DAT DECEDI$SRV_ 13 [DECEDI] RWED,RWED,RE,RE CONFIGURATION.FDL DECEDI$SRV_CONFIG_ 582 [DECEDI] RWED,RWED,RE,RE DEFS.DAT DECEDI$SRV_ 27 [DECEDI] RWED,RWED,RE,RE PARAMETER.DAT DECEDI$SRV_ 2 [DECEDI] RWED,RWED,RE,RE PARAMETER.FDL DECEDI$SUB_ELE_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$SYSTEM_ 2 [DECEDI] RWED,RWED,RE,RE PARAMETERS.FDL DECEDI$SYSTEM_ 15 [DECEDI] RWED,RWED,RE,RE VERSIONS.DAT DECEDI$SYSTEM_ 2 [DECEDI] RWED,RWED,RE,RE VERSIONS.FDL DECEDI$TEL_ 2 [DECEDI] RWED,RWED,RE,RE TRANSFER.FDL DECEDI$TP_CODE_ 3 [DECEDI] RWED,RWED,RE,RE TRANS.FDL (continued on next page) File Protection on the Installed Files D-37 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$TP_DATA_ 3 [DECEDI] RWED,RWED,RE,RE LABEL.FDL DECEDI$TP_DOCUMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_DOC_AREA_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_ELEMENT_ 2 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_QUAL_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_SEGMENT_ 3 [DECEDI] RWED,RWED,RE,RE TABLE.FDL DECEDI$TP_STD_ 3 [DECEDI] RWED,RWED,RE,RE VERS.FDL DECEDI$TRANSLATION_ 3 [DECEDI] RWED,RWED,RE,RE HISTORY.FDL DECEDI$TRANSMISSION_ 4 [DECEDI] RWED,RWED,RE,RE AUDIT.FDL DECEDI$TRANSMISSION_ 2 [DECEDI] RWED,RWED,RE,RE FILE_DETAILS.FDL DECEDI$TRANSMISSION_ 3 [DECEDI] RWED,RWED,RE,RE HISTORY.FDL DECEDI$VAN_APPEND_ 4 [DECEDI] RWED,RWED,RE,RE SENDFILES.COM DECEDI$VAN_ 3 [DECEDI] RWED,RWED,RE,RE EDIC_APPEND_ XFILES.COM DECEDI$VAN_EDIC_ 5 [DECEDI] RWED,RWED,RE,RE CLEANUP.COM DECEDI$VAN_EDIC_ 3 [DECEDI] RWED,RWED,RE,RE CONVERT.COM (continued on next page) D-38 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-24_(Cont.)_Files_in_DECEDI$TOP:[DATA]______________ Size File____________________(blocksOwner____Protection_________ DECEDI$VAN_EDIC_ 1 [DECEDI] RWED,RWED,RE,RE CONVERT.FDL DECEDI$VAN_EDIC_ 1 [DECEDI] RWED,RWED,RE,RE CONVERT2.FDL DECEDI$VAN_ 2 [DECEDI] RWED,RWED,RE,RE EDIC_DELETE_OLD_ XFILE.COM DECEDI$VAN_ 5 [DECEDI] RWED,RWED,RE,RE EDIC_PARSE_ REPORTS.COM________________________________________________ D.4.6 Files in DECEDI$TOP:[TOOLS] The files in this directory all have the following security: IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=[*,*],ACCESS=NONE Table_D-25_Files_in_DECEDI$TOP:[TOOLS]_____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$ARCHIVE_ 34 [DECEDI] (RWED,RWED,RE,RE) DATABASE.SQL DECEDI$ARCHIVE_DB_ 671 [DECEDI] (RWED,RWED,RE,RE) CREATE.EXE DECEDI$AUDIT_ 37 [DECEDI] (RWED,RWED,RE,RE) DATABASE.SQL DECEDI$AUDIT_ 265 [DECEDI] (RWED,RWED,RE,RE) EXTRACT.COM (continued on next page) File Protection on the Installed Files D-39 File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-25_(Cont.)_Files_in_DECEDI$TOP:[TOOLS]_____________ Size File__________________(blocksOwner____Protection___________ DECEDI$AUDIT_ 860 [DECEDI] (RWED,RWED,RE,RE) EXTRACT.EXE DECEDI$AUDIT_ 3 [DECEDI] (RWED,RWED,RE,RE) EXTRACT_TABLES.DAT DECEDI$AUDIT_USER_ 1 [DECEDI] (RWED,RWED,RE,RE) REF_TABLES.DAT DECEDI$DB_CREATE.EXE 675 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG.COM 5 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG.EXE 82 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_COPY.COM 11 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_DOC.PS 164 [DECEDI] (RWED,RWED,RE,RE) DECEDI$DLG_DOC.TXT 72 [DECEDI] (RWED,RWED,RE,RE) DECEDI$LINK_TUNE_ 3 [DECEDI] (RWED,RWED,RE,RE) DB.COM DECEDI$LINK_TUNE_ 3 [DECEDI] (RWED,RWED,RE,RE) SYINFO.COM DECEDI$MESSAGE_ 148 [DECEDI] (RWED,RWED,RE,RE) UPDATES.COM DECEDI$TAILOR.COM 135 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL.EXE 170 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL_DOC.PS 259 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TEL_DOC.TXT 128 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.EXE 83 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.OBJ 60 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.PS 324 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_DB.TXT 165 [DECEDI] (RWED,RWED,RE,RE) DECEDI$TUNE_ 6 [DECEDI] (RWED,RWED,RE,RE) SYINFO.EXE DECEDI$TUNE_ 5 [DECEDI] (RWED,RWED,RE,RE) SYINFO.OBJ (continued on next page) D-40 File Protection on the Installed Files File Protection on the Installed Files D.4 OpenVMS VAX Server Files Table_D-25_(Cont.)_Files_in_DECEDI$TOP:[TOOLS]_____________ Size File__________________(blocksOwner____Protection___________ DECEDI$V21_ 644 [DECEDI] (RWED,RWED,RE,RE) APPFILMIGR.EXE DECEDI$V21_ARCHIVE_ 651 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.EXE DECEDI$V21_ 39 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.COM DECEDI$V21_ 772 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.EXE DECEDI$X25_FORCE_ 38 [DECEDI] (RWED,RWED,RE,RE) PWD.EXE DECEDI$X25_ 559 [DECEDI] (RWED,RWED,RE,RE) MIGRATE.EXE DECEDI.CRL 19 [DECEDI] (RWED,RWED,RE,RE) DECEDI_SYSTEM_ 2 [DECEDI] (RWED,RWED,RE,RE) CONTEXT.COL DECEDI_USER_ 2 [DECEDI] (RWED,RWED,RE,RE) CONTEXT.COL MTA$XAPI_SHR.EXE_ 1087 [SYSTEM] (RWED,RWED,RWED,RE) PATCH______________________________________________________ D.5 OpenVMS VAX Server FileBridge Directory Structure This section lists the files in the FileBridge directory structure on an OpenVMS VAX Server. For a list of the files in the FileBridge directory structure on an OpenVMS AXP Server, see Section D.2. D.5.1 Files in [FILEBRIDGE] Security for directory files in this directory unless otherwise stated: File Protection on the Installed Files D-41 File Protection on the Installed Files D.5 OpenVMS VAX Server FileBridge Directory Structure DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RE,GROUP:,WORLD: IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=FBR$SUPERVISOR,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE IDENTIFIER=FBR$OPERATIONS,OPTIONS=DEFAULT,ACCESS=READ+EXECUTE IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE IDENTIFIER=FBR$DEVELOPMENT,OPTIONS=DEFAULT,ACCESS=READ+EXECUTE Security for non-directory files in this directory: IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) Table_D-26_Files_in_[FILEBRIDGE]___________________________ Size File__________________(blocksOwner____Protection___________ .DIR[1] 1 [DECEDI] RWE,RWE,, FBR$AUDIT_ 11 [SYSTEM] RWED,RWED,RWED,RE DATABASE.RBR TEST_DB.DIR 1 [DECEDI] RWED,RWED,, [1]This_name_is_the_date_and_time_that_the_directory_was___ created ___________________________________________________________ D.5.2 Files in [FILEBRIDGE.] Table_D-27_Files_in_[FILEBRIDGE.]_______________ Size File__________________(blocksOwner____Protection___________ FBR$DB.DIR 1 [DECEDI] RWE,RWE,, FBR$HISTORY.DIR_______1______[DECEDI]_RWE,RWE,,____________ D-42 File Protection on the Installed Files File Protection on the Installed Files D.5 OpenVMS VAX Server FileBridge Directory Structure D.5.3 Files in [FILEBRIDGE..FBR$DB] Table_D-28_Files_in_[FILEBRIDGE..FBR$DB]________ Size File__________________(blocksOwner____Protection___________ FBR$AUDIT_DATA.RDA 8048 [DECEDI] RWED,R,, FBR$AUDIT_DATA.SNP 404 [DECEDI] RWED,R,, FBR$AUDIT_ 1612 [DECEDI] RWED,R,, DATABASE.RDA FBR$AUDIT_ 87 [DECEDI] RWED,R,, DATABASE.RDB FBR$AUDIT_ 202 [DECEDI] RWED,R,, DATABASE.SNP FBR$AUDIT_INDEX.RDA 208 [DECEDI] RWED,R,, FBR$AUDIT_INDEX.SNP 202 [DECEDI] RWED,R,, FBR$RUN_ID.DAT________1______[DECEDI]_RWED,RWED,RW,________ D.5.4 Files in [FILEBRIDGE.TEST_DB] Security for files in this directory unless otherwise stated: IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE Table_D-29_Files_in_[FILEBRIDGE.TEST_DB]___________________ Size File__________________(blocksOwner____Protection___________ FBR$DB.DIR 1 [DECEDI] RWE,RWE,, FBR$HISTORY.DIR_______1______[DECEDI]_RWE,RWE,,____________ File Protection on the Installed Files D-43 File Protection on the Installed Files D.5 OpenVMS VAX Server FileBridge Directory Structure D.5.5 Files in [FILEBRIDGE.TEST_DB.FBR$DB] Table_D-30_Files_in_[FILEBRIDGE.TEST_DB.FBR$DB]____________ Size File__________________(blocksOwner____Protection___________ FBR$AUDIT_DATA.RDA 8048 [DECEDI] RWED,R,, FBR$AUDIT_DATA.SNP 404 [DECEDI] RWED,R,, FBR$AUDIT_ 1612 [DECEDI] RWED,R,, DATABASE.RDA FBR$AUDIT_ 87 [DECEDI] RWED,R,, DATABASE.RDB FBR$AUDIT_ 202 [DECEDI] RWED,R,, DATABASE.SNP FBR$AUDIT_INDEX.RDA 208 [DECEDI] RWED,R,, FBR$AUDIT_INDEX.SNP 202 [DECEDI] RWED,R,, FBR$RUN_ID.DAT________1______[DECEDI]_RWED,RWED,RW,________ D.6 OpenVMS VAX Server System Directory Structure D.6.1 Files in SYS$COMMON:[SYS$STARTUP] Table_D-31_Files_in_SYS$COMMON:[SYS$STARTUP]_______________ Size File__________________(blocksOwner____Protection___________ DECEDI$SHUTDOWN.COM 34 [SYSTEM] RWED,RWED,RWED, DECEDI$STARTUP.COM 57 [SYSTEM] RWED,RWED,RWED, DECEDI$SYSHUTDOWN.COM 5 [SYSTEM] RWED,RWED,RWED, DECEDI$SYSTARTUP.COM__5______[SYSTEM]_RWED,RWED,RWED,______ D.6.2 Files in SYS$COMMON:[SYSEXE] D-44 File Protection on the Installed Files File Protection on the Installed Files D.6 OpenVMS VAX Server System Directory Structure Table_D-32_Files_in_SYS$COMMON:[SYSEXE]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$3780.EXE 805 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$AFS_MAIN.EXE 799 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$ARCHIVE_ 680 [SYSTEM] (RWED,RWED,RE,RE) SERVER.EXE DECEDI$BISYNC.EXE 39 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$BISYNC2.EXE 804 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CIS.EXE 13 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CLI.EXE 65 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$CNV_ 768 [SYSTEM] (RWED,RWED,RE,RE) EDIFACT.EXE DECEDI$CNV_ 831 [SYSTEM] (RWED,RWED,RE,RE) TRADACOMS.EXE DECEDI$CNV_X12.EXE 1277 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$COMMS_ 700 [SYSTEM] (RWED,RWED,RE,RE) CONTROL.EXE DECEDI$DATA_ 261 [SYSTEM] (RWED,RWED,RE,RE) SERVER.EXE DECEDI$DIAL.EXE 26 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$FS_DECNET.EXE 642 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$FS_MAIN.EXE 849 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$GUI.EXE 1919 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$IMPEXP.EXE 689 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$INTERCHANGE.EXE18211 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$LOGIN.COM 5 [SYSTEM] (RWED,RWED,E,E) DECEDI$LOOK.COM 5 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$LOOK.EVE 1 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$MSF.EXE 1553 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$MST.EXE 197 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$OFTP.EXE 755 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$PEDI.EXE 1091 [SYSTEM] (RWED,RWED,RE,RE) (continued on next page) File Protection on the Installed Files D-45 File Protection on the Installed Files D.6 OpenVMS VAX Server System Directory Structure Table_D-32_(Cont.)_Files_in_SYS$COMMON:[SYSEXE]____________ Size File__________________(blocksOwner____Protection___________ DECEDI$REPOSITORY.CR 43 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SERVICES.EXE 53 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SHUTDOWN.EXE 75 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$STARTUP.EXE 129 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SUB_COPY_ 983 [SYSTEM] (RWED,RWED,RE,RE) FS.EXE DECEDI$SUB_DN_FS.EXE 758 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$SUB_RIP_ 833 [SYSTEM] (RWED,RWED,RE,RE) FS.EXE DECEDI$TFB.EXE 756 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TFB_X12.EXE 1158 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TFS.EXE 706 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$TRNS_ 725 [SYSTEM] (RWED,RWED,RE,RE) EDIFACT.EXE DECEDI$TRNS_ 809 [SYSTEM] (RWED,RWED,RE,RE) TRADACOMS.EXE DECEDI$TRNS_X12.EXE 1547 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$VAN_TRAX.EXE 748 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$X25.EXE 743 [SYSTEM] (RWED,RWED,RE,RE) DECEDI$X400.EXE 960 [SYSTEM] (RWED,RWED,RE,RE) FBR$ARCHIVE.COM 193 [SYSTEM] (RWED,RWED,RE,RE) FBR$DECEDI_ 7 [SYSTEM] (RWED,RWED,RE,RE) EXTRACT.COM FBR$EXTRACT_ 9 [SYSTEM] (RWED,RWED,RE,RE) INSTALL.COM FBR$RECOVER.EXE 491 [SYSTEM] (RWED,RWED,RE,RE) FBR$RUNTIME.EXE 508 [SYSTEM] (RWED,RWED,RE,RE) FBR$TRACKING.EXE 476 [SYSTEM] (RWED,RWED,RE,RE) FBR$UI.EXE____________2664___[SYSTEM]_(RWED,RWED,RE,RE)____ D-46 File Protection on the Installed Files File Protection on the Installed Files D.6 OpenVMS VAX Server System Directory Structure D.6.3 Files in SYS$COMMON:[SYSHLP] Table_D-33_Files_in_SYS$COMMON:[SYSHLP]____________________ Size File___________________(blocksOwner____Protection__________ DECEDI$COMMAND_ 412 [SYSTEM] RWED,RWED,RWED,RE HELP.HLB DECEDI$ELM.HLB 1125 [SYSTEM] RWED,RWED,RWED,RE DECEDI$REVIEW_ 49 [SYSTEM] RWED,RWED,RWED,RE HELP.HLB DECEDI$UI_FIELD_ 587 [SYSTEM] RWED,RWED,RWED,RE HELP.HLB DECEDI$UI_HELP_KEYS_ 9 [SYSTEM] RWED,RWED,RWED,RE ENGLISH.TXT DECEDI021.RELEASE_ 286 [SYSTEM] RWED,RWED,RE,RE NOTES______________________________________________________ D.6.4 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] Table_D-34_Files_in_SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI]____ Size File___________________(blocksOwner____Protection__________ DECEDI$APPSHR.OPT 3 [SYSTEM] RWED,RWED,RWED,RE DECEDI$COMM_ 4 [SYSTEM] RWED,RWED,RWED,RE APPSHR.OPT DECEDI_POST_FETCH.C 17 [SYSTEM] RWED,RWED,RWED,RE EDIFACT_901_ 172 [SYSTEM] RWED,RWED,RWED,RE DIRECTORY.DAT EDIFACT_901_MINVOX_ 172 [SYSTEM] RWED,RWED,RWED,RE DOCUMENT.DAT MINVOX_IN.DAT 3 [SYSTEM] RWED,RWED,RWED,RE MINVOX_IN.FBO 63 [SYSTEM] RWED,RWED,RWED,RE MINVOX_OUT.DAT 2 [SYSTEM] RWED,RWED,RWED,RE (continued on next page) File Protection on the Installed Files D-47 File Protection on the Installed Files D.6 OpenVMS VAX Server System Directory Structure Table D-34 (Cont.) Files in ___________________SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI]_____ Size File___________________(blocksOwner____Protection__________ MINVOX_OUT.FBO 80 [SYSTEM] RWED,RWED,RWED,RE PROFILE-DEC-DIRECT- 3 [SYSTEM] RWED,RWED,RWED,RE UK-LTD.DAT PROFILE-SHINY-NEW- 3 [SYSTEM] RWED,RWED,RWED,RE SYSTEMS.DAT________________________________________________ D.6.5 Files in SYS$COMMON:[SYSLIB] Table_D-35_Files_in_SYS$COMMON:[SYSLIB]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$API_DEF.BAS 15 [SYSTEM] RWED,RWE,RWE,RE DECEDI$API_DEF.COB 15 [SYSTEM] RWED,RWE,RWE,RE DECEDI$API_DEF.FOR 9 [SYSTEM] RWED,RWE,RWE,RE DECEDI$API_DEF.H 11 [SYSTEM] RWED,RWE,RWE,RE DECEDI$API_DEF.LIB 15 [SYSTEM] RWED,RWE,RWE,RE DECEDI$API_DEF.PAS 14 [SYSTEM] RWED,RWE,RWE,RE DECEDI$API_DEF.PLI 12 [SYSTEM] RWED,RWE,RWE,RE DECEDI$APPSHR.EXE 284 [SYSTEM] RWED,RWE,RWE,RE DECEDI$APPSHR_V2.EXE 24 [SYSTEM] RWED,RWE,RWE,RE DECEDI$COMM_ 410 [SYSTEM] RWED,RWE,RWE,RE APPSHR.EXE DECEDI$DATACHECKSHR.EX6 [SYSTEM] RWED,RWED,RE,RE DECEDI$EXTSHR.EXE 1116 [SYSTEM] RWED,RWE,RWE,RE DECEDI$NUMSHR.EXE 152 [SYSTEM] RWED,RWE,RWE,RE DECEDI$PRVSHR.EXE 5 [SYSTEM] RWED,RWE,RWE,RE DECEDI$SECTION.TPU$SEC122N [SYSTEM] RWED,RWED,RE,RE DECEDI$SEQCHECKSHR.EXE17 [SYSTEM] RWED,RWED,RE,RE (continued on next page) D-48 File Protection on the Installed Files File Protection on the Installed Files D.6 OpenVMS VAX Server System Directory Structure Table_D-35_(Cont.)_Files_in_SYS$COMMON:[SYSLIB]____________ Size File__________________(blocksOwner____Protection___________ DECEDI_API_COMMON.H 42 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_DEF.H 10 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_MSGS.H 22 [SYSTEM] RWED,RWE,RWE,RE DECEDI_PLATFORMS.H 12 [SYSTEM] RWED,RWE,RWE,RE FBR$DECEDI_ 111 [SYSTEM] RWED,RWED,RWED,RE EXTRACT.EXE FBR$MESSAGES.H 40 [SYSTEM] RWED,RWED,RWED,RE FBR$MESSAGES.OBJ 92 [SYSTEM] RWED,RWED,RWED,RE FBR$RTLIBRARY.OLB_____505____[SYSTEM]_RWED,RWED,RWED,RE____ D.6.6 Files in SYS$COMMON:[SYSMGR] Table_D-36_Files_in_SYS$COMMON:[SYSMGR]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$DEFINE_ 3 [SYSTEM] RWED,RWED,RWED, MAPPER_LOGICALS.COM DECEDI$LOGICALS.COM 18 [SYSTEM] RWED,RWED,RWED, DECEDI$SET_MAPPER_ 3 [SYSTEM] RWED,RWED,RWED, DATABASE.COM DECEDI$SYLOGICALS.COM_8______[SYSTEM]_RWED,RWED,RWED,______ D.6.7 Files in SYS$COMMON:[SYSMSG] Table_D-37_Files_in_SYS$COMMON:[SYSMSG]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$CMSGS.EXE 30 [SYSTEM] RWED,RWED,RE,RE (continued on next page) File Protection on the Installed Files D-49 File Protection on the Installed Files D.6 OpenVMS VAX Server System Directory Structure Table_D-37_(Cont.)_Files_in_SYS$COMMON:[SYSMSG]____________ Size File__________________(blocksOwner____Protection___________ DECEDI$MESSAGE.EXE____541____[SYSTEM]_RWED,RWED,RE,RE______ D.6.8 Files in SYS$COMMON:[SYSTEST] Table_D-38_Files_in_SYS$COMMON:[SYSTEST]___________________ Size File__________________(blocksOwner____Protection___________ DECEDI$IVP.COM 55 [SYSTEM] RWED,RWED,RWED, DECEDI$IVP_ 414 [SYSTEM] RWED,RWED,RWED, CHECKSUMS.DAT FBR$IVP.COM 18 [SYSTEM] RWED,RWED,RWED, FBR.DIR_______________1______[SYSTEM]_RWED,RWE,RE,_________ D.6.9 Files in SYS$COMMON:[SYSTEST.FBR] Table_D-39_Files_in_SYS$COMMON:[SYSTEST.FBR]_______________ Size File__________________(blocksOwner____Protection___________ FBR$EXAMPLE.DAT 1 [SYSTEM] RWED,RWED,RWED,RE FBR$EXAMPLE.FBO_______376____[SYSTEM]_RWED,RWED,RWED,RE____ D.7 OpenVMS AXP Client Directory Structure D.7.1 Files in DECEDI$TOP:[000000] The files in this directory have the following security unless otherwise stated: D-50 File Protection on the Installed Files File Protection on the Installed Files D.7 OpenVMS AXP Client Directory Structure 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+WRITE+EXECUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE Table_D-40_Files_in_DECEDI$TOP:[000000]____________________ Size File__________________(blocksOwner____Protection___________ DATA.DIR 1 [DECEDI] RWED,RWED,, TOOLS.DIR_____________1______[DECEDI]_RWED,RWED,,__________ D.7.2 Files in DECEDI$TOP:[DATA] The file in this directory has the following security: IDENTIFIER=[DECEDI],ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL IDENTIFIER=DECEDI$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],ACCESS=NONE Table_D-41_Files_in_DECEDI$TOP:[DATA]______________________ Size File__________________(blocksOwner____Protection___________ DECEDI$SYSTEM_ 15 [DECEDI] RWED,RWED,RE,RE VERSIONS.DAT_______________________________________________ D.8 OpenVMS AXP Client System Directory Structure D.8.1 Files in SYS$COMMON:[SYSEXE] File Protection on the Installed Files D-51 File Protection on the Installed Files D.8 OpenVMS AXP Client System Directory Structure Table_D-42_Files_in_SYS$COMMON:[SYSEXE]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$CIS.EXE 24 [SYSTEM] RWED,RWED,RE,RE DECEDI$CLI.EXE 103 [SYSTEM] RWED,RWED,RE,RE DECEDI$LOGIN.COM 5 [SYSTEM] RWED,RWED,E,E DECEDI$LOOK.COM 5 [SYSTEM] RWED,RWED,E,E DECEDI$LOOK.COM 1 [SYSTEM] RWED,RWED,E,E DECEDI$REPOSITORY.CR 43 [DECEDI] RWED,RWED,RE,RE DECEDI_USER_ 11 [SYSTEM] RWED,RWED,RE,RE CONTEXT.CO_________________________________________________ D.8.2 Files in SYS$COMMON:[SYSHLP] Table_D-43_Files_in_SYS$COMMON:[SYSHLP]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI021.RELEASE_ 286 [SYSTEM] RWED,RWED,RWED,RE NOTES______________________________________________________ D.8.3 Files in SYS$COMMON:[SYSLIB] Table_D-44_Files_in_SYS$COMMON:[SYSLIB]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$APPSHR_V2.EXE 45 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_COMMON.H 42 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_DEF.H 10 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_MSGS.H 22 [SYSTEM] RWED,RWE,RWE,RE DECEDI_PLATFORMS.H____12_____[SYSTEM]_RWED,RWE,RWE,RE______ D-52 File Protection on the Installed Files File Protection on the Installed Files D.8 OpenVMS AXP Client System Directory Structure D.8.4 Files in SYS$COMMON:[SYSMSG] Table_D-45_Files_in_SYS$COMMON:[SYSMSG]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$CMSGS.EXE______31_____[SYSTEM]_RWED,RWED,RE,RE______ D.8.5 Files in SYS$COMMON:[SYSTEST] Table_D-46_Files_in_SYS$COMMON:[SYSTEST]___________________ Size File__________________(blocksOwner____Protection___________ DECEDI$IVP.COM 55 [SYSTEM] RWED,RWED,RWED, DECEDI$IVP_ 414 [SYSTEM] RWED,RWED,RWED, CHECKSUMS.DAT______________________________________________ D.9 OpenVMS VAX Client DEC/EDI Directory Structure D.9.1 Files in DECEDI$TOP:[000000] The files in this directory have the following security: File Protection on the Installed Files D-53 File Protection on the Installed Files D.9 OpenVMS VAX Client DEC/EDI Directory Structure 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+WRITE+EXECUTE+DELETE IDENTIFIER=DECEDI$ADMINISTRATOR,ACCESS=READ+WRITE+EXECUTE+DELETE IDENTIFIER=[*,*],OPTIONS=DEFAULT,ACCESS=NONE IDENTIFIER=[*,*],ACCESS=NONE Table_D-47_Files_in_DECEDI$TOP:[000000]____________________ Size File__________________(blocksOwner____Protection___________ DATA.DIR 1 [DECEDI] RWED,RWED,, TOOLS.DIR_____________1______[DECEDI]_RWED,RWED,,__________ D.9.2 Files in DECEDI$TOP:[TOOLS] Table_D-48_Files_in_DECEDI$TOP:[TOOLS]_____________________ Size File__________________(blocksOwner____Protection___________ DECEDI.CRL 19 [DECEDI] RWED,RWED,RE,RE DECEDI_SYSTEM_ 3 [DECEDI] RWED,RWED,RE,RE CONTEXT.COL DECEDI_USER_ 2 [DECEDI] RWED,RWED,RE,RE CONTEXT.COL________________________________________________ D.10 OpenVMS VAX Client System Directory Structure D.10.1 Files in SYS$COMMON:[SYSEXE] D-54 File Protection on the Installed Files File Protection on the Installed Files D.10 OpenVMS VAX Client System Directory Structure Table_D-49_Files_in_SYS$COMMON:[SYSEXE]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$CIS.EXE 13 [SYSTEM] RWED,RWED,RE,RE DECEDI$CLI.EXE 65 [SYSTEM] RWED,RWED,RE,RE DECEDI$LOGIN.COM 5 [SYSTEM] RWED,RWED,E,E DECEDI$LOOK.COM 5 [SYSTEM] RWED,RWED,RE,RE DECEDI$LOOK.EVE 1 [SYSTEM] RWED,RWED,RE,RE DECEDI$REPOSITORY.CR 43 [DECEDI] RWED,RWED,RE,RE DECEDI_USER_ 11 [SYSTEM] RWED,RWED,RE,RE CONTEXT.CO_________________________________________________ D.10.2 Files in SYS$COMMON:[SYSHLP] Table_D-50_Files_in_SYS$COMMON:[SYSHLP]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI021.RELEASE_ 286 [SYSTEM] RWED,RWED,RWED,RE NOTES______________________________________________________ D.10.3 Files in SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI] Table_D-51_Files_in_SYS$COMMON:[SYSHLP.EXAMPLES.DECEDI]____ Size File__________________(blocksOwner____Protection___________ DECEDI$APPSHR.OPT 3 [SYSTEM] RWED,RWED,RWED,RE DECEDI$COMM_ 4 [SYSTEM] RWED,RWED,RWED,RE APPSHR.OPT_________________________________________________ D.10.4 Files in SYS$COMMON:[SYSLIB] File Protection on the Installed Files D-55 File Protection on the Installed Files D.10 OpenVMS VAX Client System Directory Structure Table_D-52_Files_in_SYS$COMMON:[SYSLIB]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$APPSHR_V2.EXE 24 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_COMMON.H 42 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_DEF.H 10 [SYSTEM] RWED,RWE,RWE,RE DECEDI_API_MSGS.H 22 [SYSTEM] RWED,RWE,RWE,RE DECEDI_PLATFORMS.H____12_____[SYSTEM]_RWED,RWE,RWE,RE______ D.10.5 Files in SYS$COMMON:[SYSMSG] Table_D-53_Files_in_SYS$COMMON:[SYSMSG]____________________ Size File__________________(blocksOwner____Protection___________ DECEDI$CMSGS.EXE 30 [SYSTEM] RWED,RWED,RE,RE DECEDI$MESSDCE.EXE____541____[SYSTEM]_RWED,RWED,RE,RE______ D.10.6 Files in SYS$COMMON:[SYSTEST] Table_D-54_Files_in_SYS$COMMON:[SYSTEST]___________________ Size File__________________(blocksOwner____Protection___________ DECEDI$IVP.COM 55 [DECEDI] RWED,RWED,RWED, DECEDI$IVP_ 414 [SYSTEM] RWED,RWED,RWED, CHECKSUMS.DAT______________________________________________ D-56 File Protection on the Installed Files E _________________________________________________________________ DEC/EDI Logical Names E.1 Logical Names All DEC/EDI logical names are entered into logical name tables when DEC/EDI is started partially. These names are defined by the following startup files: o SYS$MANAGER:DECEDI$LOGICALS.COM o 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$AFS_QUE_REFRESH" = "0 06:00:00" "DECEDI$ARCHIVE_DB" = "BITTER$DKB200:[DECEDI.ARCHIVE_ DB]DECEDI$ARCHIVE_DB.RDB" "DECEDI$ARCHREPORTS" = "DECEDI$TOP:[ARCHREPORTS]" "DECEDI$AST" = "DECEDI$DATA:DECEDI$SITE_TABLE.DAT" "DECEDI$AUDIT_DB" = "BITTER$DKB200:[DECEDI.AUDIT_ DB]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$CLIENT_ APPLICATIONS.DAT" "DECEDI$CNT" = "DECEDI$DATA:DECEDI$CONTROL_NUM.DAT" "DECEDI$COM" = "SYS$MANAGER" DEC/EDI Logical Names E-1 DEC/EDI Logical Names E.1 Logical Names "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_ TABLE.DAT" "DECEDI$ERROR" = "DECEDI$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]" "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$N_EDIF_CNV_MAX" = "1" "DECEDI$N_EDIF_TRNS_MAX" = "1" "DECEDI$N_TRAD_CNV_MAX" = "1" "DECEDI$N_TRAD_TRNS_MAX" = "1" E-2 DEC/EDI Logical Names DEC/EDI Logical Names E.1 Logical Names "DECEDI$N_X12_CNV_MAX" = "1" "DECEDI$N_X12_TRNS_MAX" = "1" "DECEDI$PAT" = "DECEDI$NON_UNIQUE_DECEDI$P_DOC_AREA_ TABLE.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]" DEC/EDI Logical Names E-3 DEC/EDI Logical Names E.1 Logical Names "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]" "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" E-4 DEC/EDI Logical Names DEC/EDI Logical Names E.1 Logical Names "DECEDI$UI_HELP_KEYS" = "SYS$HELP:DECEDI$UI_HELP_KEYS_ ENGLISH.TXT" "DECEDI$VANREPORTS" = "DECEDI$TOP:[VANREPORTS]" DEC/EDI Logical Names E-5