DEC/EDI_FileBridge_____________________________ Installing Order Number: AA-Q5QHA-TE Revision/Update Information: New for Version 1.1 Operating System: OpenVMS Version 5.5-2 and later Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ 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, 1994. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: DEC, DECforms, DECnet, DECwindows, OpenVMS, Rdb/VMS, VAX, VAX 9000, VAXcluster, VAXstation, VMS, Digital, and the DIGITAL logo. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.......................................... vi Preparing to Install FileBridge 1.1 Examining the Distribution Kit................ 1-1 1.2 Prerequisite Software and Hardware............ 1-2 1.3 OpenVMS License Management Facility........... 1-3 1.3.1 LMF License PAKs for FileBridge........... 1-3 1.3.2 Termination of License PAKs............... 1-3 1.4 Installation Requirements..................... 1-4 1.4.1 Time...................................... 1-4 1.4.2 Privileges Required to Install FileBridge for DEC/EDI............................... 1-4 1.4.3 Quotas Required for Installation.......... 1-5 1.4.4 Disk Space................................ 1-5 1.4.5 System Parameters......................... 1-6 1.4.6 VMSINSTAL Requirements.................... 1-8 1.4.7 Backing Up Your System Disk............... 1-8 1.5 Preparation for Running the Installation Verification Procedure........................ 1-9 Installing FileBridge 2.1 General Information........................... 2-1 2.1.1 Accessing the Online Release Notes........ 2-1 2.1.2 Files and Logical Names Added to Your System.................................... 2-1 2.1.3 Running the Installation Verification Procedure................................. 2-2 2.1.4 Aborting the Installation................. 2-2 2.2 The Installation Procedure.................... 2-2 2.2.1 Invoking VMSINSTAL........................ 2-2 2.2.2 Installation Questions.................... 2-4 iii 2.2.3 Informational Messages.................... 2-10 2.2.4 Running the Installation Verification Procedure................................. 2-12 2.2.5 Completing the Installation Procedure..... 2-14 2.2.6 Error Recovery............................ 2-14 3 After Installing FileBridge 3.1 Edit the System Startup Procedure............. 3-1 3.2 Adding symbol for DEC/EDI Extract to LOGIN.COM..................................... 3-1 3.3 User Account Requirements..................... 3-1 3.4 Installing FileBridge in a VAX Cluster Environment................................... 3-2 3.5 Defining FileBridge Rights.................... 3-3 3.5.1 The Rights Database....................... 3-3 3.5.1.1 FBR$SUPERVISOR.......................... 3-4 3.5.1.2 FBR$DEVELOPMENT......................... 3-5 3.5.1.3 FBR$OPERATIONS.......................... 3-5 3.6 Recompile FileBridge Tables................... 3-5 3.7 Running the IVP Separately.................... 3-6 3.8 Problems After Installation .................. 3-6 A Sample Installation A.1 Sample........................................ A-1 B FileBridge Files and Logical Names 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 D File Security For The Installed Files iv Tables 1-1 Disk Space Requirements................... 1-6 1-2 Required System Parameter Values.......... 1-6 3-1 User Account Quotas....................... 3-2 C-1 Files in Save-set A....................... C-1 C-2 Files in Save-set B....................... C-1 C-3 Files in Save-set C....................... C-3 v _________________________________________________________________ Preface This book tells you how to install FileBridge. This is one of a set of FileBridge books. The complete list is as follows: o Installing This book describes how to install FileBridge. o Using This book contains task-oriented descriptions of how to use and maintain FileBridge. o Reference This book is a reference manual that describes the FileBridge functionality. o User Interface Description This book describes the screens in the FileBridge user interface. vi 1 _________________________________________________________________ Preparing to Install FileBridge This chapter describes what is included in the software distribution kit, what prerequisite software is required, and how to configure your system. Installing DEC/EDI FileBridge is similar to installing other OpenVMS layered products. You must: 1. Take an inventory of the software distribution kit. 2. Make sure that your system has the prerequisite software and hardware. 3. Prepare your system and its users for installation. 4. Print and read the Release Notes. 5. Perform the installation and run the Installation Verification Procedure (IVP). 6. Perform post-installation and system management procedures. 7. Resume normal operations after you complete the installation. 8. Record the installation of FileBridge and report any problems. 1.1 Examining the Distribution Kit Each kit contains: o A kit bill of materials. o The distribution medium for the component software. o The product documentation: Installing Using Reference Preparing to Install FileBridge 1-1 Preparing to Install FileBridge 1.1 Examining the Distribution Kit User Interface Description The Release Notes To ensure that you have a complete kit, check the kit contents against the kit bill of materials. 1.2 Prerequisite Software and Hardware To install and use FileBridge, you must have: o A valid OpenVMS operating system configuration, Version 5.5-2 or higher. For OpenVMS Version 5.x systems, the following OpenVMS classes are required for full functionality of this layered product: VMS Required Saveset Network Support Programming Support System Programming Support Secure User's Environment Utilities Example Files For more information on OpenVMS classes and tailoring, refer to the OpenVMS operating system installation manual. o DECforms Version 1.3 or higher. Only the runtime is required. o VAX Rdb Version 4.2. Only the runtime is required. A license is provided with OpenVMS, but the media must be obtained separately from Digital. The FileBridge installation procedure checks for prerequisite software. If any prerequisite software is not installed, the installation will fail. You must install prerequisite software before resuming the FileBridge installation. Software that FileBridge works with but that is not required includes: o DEC/EDI, Version V1.3 or higher. This is required to send live documents, translator test, or partner test documents. o CDD/Repository. 1-2 Preparing to Install FileBridge Preparing to Install FileBridge 1.2 Prerequisite Software and Hardware CDD/Repository is used only during FileBridge table development to simplify record structure definition. CDD/Repository is not accessed during runtime. 1.3 OpenVMS License Management Facility This version of FileBridge is licensed under the License Management Facility (LMF). Before the computer system can use FileBridge, the system manager must register and load Product Authorization Keys (PAKs) in the License Data Base for the system. 1.3.1 LMF License PAKs for FileBridge The FileBridge PAK is called FILEBRIDGE-BSE. This base license enables you to use the full functionality of FileBridge. The installation procedure for FileBridge checks for a FileBridge PAK (FILEBRIDGE-BSE) in the License Data Base. If no PAK is present, it warns the system manager or installer, cancels the Installation Verification Procedure (IVP), but continues with the installation. In this event, the system manager should wait until installation is complete, then register and load the appropriate PAK for FileBridge and, finally, run the IVP. 1.3.2 Termination of License PAKs The FileBridge PAKs have a "Termination Date". An attempt to use the OpenVMS "LICENSE LOAD" command to load a PAK with a termination date earlier than the current date will fail with a "license has terminated" message. When the load command is issued directly by the system manager, the fact that the PAK has expired is quite clear. However, all license PAKs are unloaded when a system goes down and are reloaded when the system is rebooted. When PAKs are reloaded in this way, it is easy to overlook the message that reports that a PAK has expired and was not loaded. When an attempt to load or reload a FileBridge license PAK fails because the PAK has expired, subsequent execution of FileBridge will terminate with a message that says only that the use of FileBridge is "not authorized". This Preparing to Install FileBridge 1-3 Preparing to Install FileBridge 1.3 OpenVMS License Management Facility message does *not* report that a PAK is registered but could not be loaded because it has expired. Any user (with or without privileges) can check the LMF License Data Base for FileBridge license PAKs by entering the OpenVMS command: LICENSE LIST FILEBRIDGE* /FULL The system will respond with a listing that includes the termination date of each FileBridge license PAK registered on the system. If the termination date of the PAK is earlier than the current date, a new or modified PAK is required. 1.4 Installation Requirements 1.4.1 Time The installation should take approximately 15 to 20 minutes, depending on your type of media and your system configuration. This does not include time needed for post- installation procedures. For example, installing FileBridge on a VAXstation 3100 takes approximately 15 minutes, and the Installation Verification Procedure (IVP) takes about 10 minutes. 1.4.2 Privileges Required to Install FileBridge for DEC/EDI To install FileBridge for DEC/EDI, We recommend that you be logged in to the SYSTEM account. The account must have SETPRV or the privileges: o CMKRNL o WORLD o SYSPRV The image FBR$DECEDI_EXTRACT.EXE has to be installed in SYS$SHARE with SYSPRV. 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. 1-4 Preparing to Install FileBridge Preparing to Install FileBridge 1.4 Installation Requirements 1.4.3 Quotas Required for Installation The installing account must have the following quotas for a successful installation. o ASTLM = 24 o BIOLM = 20 o BYTLM = 20,480 o DIOLM = 20 o ENQLM = 600 o FILLM = 50 o PGFLQUOTA = 60,000 If necessary, quotas may be changed from an account with SYSTEM or OPERATOR privileges as seen in the following example. $mcr authorize mod /ASTLM=24/DIOLM=20 sho ... exit For substitute account name, such as SYSTEM. 1.4.4 Disk Space Installing FileBridge requires a certain amount of available disk storage space. Once FileBridge is installed, less storage space is required. You will need 40,500 available blocks on the system disk during installation. You can choose where to install the executables, documentation, and database. The default choices install the files on the system disk. We recommend that you do not place the database on the SYSTEM disk because the database can grow substantially. If you install the executables, documentation, and database on the system disk, 33,000 blocks are used. Preparing to Install FileBridge 1-5 Preparing to Install FileBridge 1.4 Installation Requirements If you choose a destination other than the system disk, 3,000 blocks on the system disk are required after installation. In addition, you will have used the space indicated in the following table for the chosen destination: Table_1-1__Disk_Space_Requirements_________________________ Disk_____________Blocks____________________________________ Executables 8000 Documentation 400 Data_____________22000-will_increase_with_usage____________ You must check that the necessary number of blocks are available. To determine the number of available disk blocks on the system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE To determine the number of blocks on the chosen destination, repeat this command for the specified device. 1.4.5 System Parameters The following table lists the minimum required system parameter values for installing FileBridge. Table_1-2__Required_System_Parameter_Values________________ System_Parameter______Value________________________________ GBLPAGES 500 free pages GBLSECTIONS___________4_free_sections______________________ The values for GBLPAGES and GBLSECTIONS in the above table 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. Run the OpenVMS Install Utility (INSTALL) using the following DCL command: 1-6 Preparing to Install FileBridge Preparing to Install FileBridge 1.4 Installation Requirements $INSTALL LIST /GLOBAL /SUMMARY The INSTALL Utility displays a summary of global pages and global sections used by your system, as well as the current number of unused global pages. For example: Summary of Local Memory Global Sections 258 Global Sections Used, 22580/3420 global Pages Used/Unused 2. Determine if the number of unused pages (3420 in the example) is equal to or greater than the number specified in the above table. 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" (258 in the example). 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 Parameter name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections 5. Subtract Global Sections Used in Step 1 (258 in the example) from the current amount in Step 4 (512 in the example). If the difference is less than the number required in the above table, you need to increase the value of the GBLSECTIONS parameter. 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 Preparing to Install FileBridge 1-7 Preparing to Install FileBridge 1.4 Installation Requirements 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 an OpenVMS System in the OpenVMS Documentation on system management. 1.4.6 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Have you set your default device and directory to SYS$UPDATE. o Are you logged in to a privileged account. o Do you have adequate quotas for installation. o Are there any users logged in to the system. If VMSINSTAL detects any problem 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. 1.4.7 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. We recommend 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 documentation set. 1-8 Preparing to Install FileBridge Preparing to Install FileBridge 1.5 Preparation for Running the Installation Verification Procedure 1.5 Preparation for Running the Installation Verification Procedure The account that runs the Installation Verification Procedure (IVP) must be the SYSTEM acocunt, or have the rights identifier FBR$SUPERVISOR, otherwise the IVP fails. If you intend to install FileBridge from an account other than the SYSTEM account, create the FBR$SUPERVISOR rights identifier and grant it to the account, as follows: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> ADD /IDENTIFIER FBR$SUPERVISOR UAF> GRANT /IDENTIFIER username UAF> EXIT where username is the name of the account that is going to perform the installation and run the IVP. Preparing to Install FileBridge 1-9 2 _________________________________________________________________ Installing FileBridge This chapter describes how to install FileBridge for DEC /EDI. This chapter contains a step-by-step description of the installation procedure. 2.1 General Information This section includes information about accessing release notes, determining what files and logical names are added to your system, running the Installation Verification Procedure (IVP), and aborting the installation. 2.1.1 Accessing the Online Release Notes FileBridge for DEC/EDI provides online release notes. It is recommended that you review the release notes before installing FileBridge. If you specify OPTIONS N when you invoke VMSINSTAL, the installation procedure asks you whether you want to display or print the release notes. Thus, you can access the release notes during the installation procedure. After you install FileBridge, the release notes are located in the directory specified during installation for documentation. The directory is given the logical name FBR$DOC, and the release notes are in the following file: FBR$DOC:FBR$011_RELEASE_NOTES.PS 2.1.2 Files and Logical Names Added to Your System The FileBridge installation procedure adds a number of files and logicals to your system. Appendix B describes the changes that the FileBridge installation procedure makes to your system. Installing FileBridge 2-1 Installing FileBridge 2.1 General Information 2.1.3 Running the Installation Verification Procedure The IVP for FileBridge verifies the installation. 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. We recommend that you run the IVP to be sure that FileBridge is installed correctly. The FileBridge IVP will not run correctly as part of the installation, unless you are logged into the SYSTEM account. After FileBridge is installed, you can run the IVP independently to verify that FileBridge is available on your system. You might want to run the IVP after a system failure to be sure that it is still installed correctly. At this time, you do not have to be in the SYSTEM account to run the IVP. You can be in the SYSTEM account or one that has the FBR$SUPERVISOR rights identifier. To run the IVP independently, use the following command: @SYS$TEST:FBR$IVP.COM 2.1.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 start the installation again. 2.2 The Installation Procedure The FileBridge installation process consists of a series of questions and informational messages. The following sections explain how to invoke the VMSINSTAL procedure and answer the installation questions. These sections also explain the information messages displayed by the procedure. 2.2.1 Invoking VMSINSTAL To start the installation procedure, log in to a privileged account, such as SYSTEM and set default to SYS$UPDATE. SET DEFAULT SYS$UPDATE 2-2 Installing FileBridge Installing FileBridge 2.2 The Installation Procedure To invoke VMSINSTAL, enter a command with the following syntax: @VMSINSTAL product-name device-name OPTIONS N product-name The installation name for the product. For FileBridge use the following name: FBR011 device-name The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. You do not need to use the console drive for this installation. If you do use the console drive, once the installation is complete, you should replace any media you removed. 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 shows the command that invokes VMSINSTAL to install FileBridge from tape drive MTA0: and the system response. This example uses the OPTIONS N parameter for printing or displaying release notes. $ @VMSINSTAL FBR011 MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.5-2 It is 29-JAN-1994 at 17:36. Enter a question mark (?) at any time for help. If you do not supply the product name or the device name, VMSINSTAL prompts you for this information later on during the installation process. 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 FileBridge 2-3 Installing FileBridge 2.2 The Installation Procedure 2.2.2 Installation Questions This section discusses the questions that appear during the installation. See Appendix A for a sample installation procedure. An asterisk (*) marks the beginning of each question. Some questions show the default response in brackets, for example [YES]. To choose the default response, press the RETURN key. 1. System backup * Are you satisfied with the backup of your system disk [YES] ? VMSINSTAL asks whether you are satisfied with your system backup. Always backup your system disk before doing an installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 2. Mounting the media Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, FBR011 MOUNTED ON _$MTA0: The following products will be processed: FBR V1.1 Beginning installation of FBR V1.1 at 17:36 %VMSINSTAL-I-RESTORE, Restoring product save set A ... VMSINSTAL prompts you to mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The prompt shows the device name. VMSINSTAL asks you whether you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing FileBridge has been mounted on the specified device and that the installation has begun. If you entered the wrong device when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press CTRL/Y. 2-4 Installing FileBridge Installing FileBridge 2.2 The Installation Procedure 3. Release Notes Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you specified OPTIONS N when you invoked VMSINSTAL, you have four options for reviewing the release notes. If you select option 1, VMSINSTAL displays the release notes immediately on your terminal. You can press CTRL/C to terminate the display at any time. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can enter a queue name or press RETURN to send the file to the default output print device. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and prompts you for a queue name for the printed version. If you select option 4, VMSINSTAL proceeds without displaying or printing the release notes. ________________________ Note ________________________ We recommend that you print and read the release notes at this time, and that you later notify users how to access the release notes. ______________________________________________________ 4. Continuing the installation * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installing FileBridge 2-5 Installing FileBridge 2.2 The Installation Procedure The installation procedure now asks whether 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. The release notes are now located in the following file: SYS$HELP:FBR$T011.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 run the Installation Verification Procedure WARNING: We recommend that the FileBridge installation be run from the System account. Sufficient quotas for running the prerequisites must be available. If you choose to install FileBridge from an account other than System, that account must have the FBR$SUPERVISOR rights identifier. Under these circumstances, do not run the IVP as part of the installation. Run the IVP separately after the installation is complete. * Do you want to run the IVP after the installation [YES]? The installation procedure asks whether you want to run the IVP. The IVP for FileBridge verifies a successful installation. You should run the IVP. 6. Specifying a directory for the FileBridge executables FileBridge requires 40,500 blocks of temporary space on the system disk during installation. Following installation, 33,000 blocks of permanent space are required on the system disk if you use the installation defaults. If you specify an alternate location, you must be sure the following space is available: 2-6 Installing FileBridge Installing FileBridge 2.2 The Installation Procedure Executables 8,000 blocks Documentation 400 blocks Database 22,000 blocks System Disk (IVP,helps, and SYS$SHARE) 2,000 blocks The executables for FileBridge normally reside in SYS$COMMON:[SYSEXE]. Or, you may specify an alternate location. The system logical FBR$EXE will contain the name of the directory. Enter the full pathname for the directory where the FileBridge programs are to reside. The directory will be created if it does not already exist. * Directory name [SYS$COMMON:[SYSEXE]]: VMSINSTAL asks you where it should put the FileBridge executables. The installation procedure will create the directory for you if it does not already exist. The FBR$EXE system-wide logical will be defined as this directory specification. Press RETURN to accept the default location of [SYS$COMMON:[SYSEXE]]. 7. Specifying a directory for the FileBridge database FileBridge Databases reside in a directory tree. FBR$HOME specifies the root of this tree. The system logical FBR$LIBRARY specifies the location of the LIVE database and the process logical for FBR$LIBRARY specifies the location of the TEST database. The first time you install FileBridge, you are required to 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 a the directory name TESTDB. FileBridge Audit Databases and FileBridge History Files must reside in a directory tree that has access rights for FileBridge Users. FBR$HOME specifies the root of this tree. FBR$HOME has a subdirectory for each instance of a FileBridge Database. The installation creates two instances, namely the Live Database and the Test Database. For each instance, two subdirectories are created: 1. FBR$DB -- contains the actual Audit Database files. Installing FileBridge 2-7 Installing FileBridge 2.2 The Installation Procedure 2. FBR$HISTORY -- contains the history files for each FileBridge operation if the history controls are enabled. We recommend that you choose a location other than the system disk for FBR$HOME. Enter the top level device and directory specification for FBR$HOME. * Directory name [SYS$SYSDEVICE:[FILEBRIDGE]]: WARNING: SYS$SYSDEVICE: 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 FileBridge. If you are re-installing 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 value of FBR$HOME has been determined from a previous installation. You can keep the current value or change it. The current value of FBR$HOME is SYS$SYSDEVICE:[FILEBRIDGE] * Do you want to change the value of FBR$HOME [NO]? 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. 2-8 Installing FileBridge Installing FileBridge 2.2 The Installation Procedure If the installation does not find system logicals for FBR$HOME and FBR$LIBRARY, it tries to determine these logicals from the FBR$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. ***************************************************** 8. Specifying a directory for the FileBridge documentation The FileBridge documentation will be placed in the directory that you specify. Enter the full pathname for the directory where the FileBridge documentation is to reside. The directory will be created for you if it does not already exist. * Directory name [SYS$SYSDEVICE:[FILEBRIDGE]]: %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... The FileBridge installation kit is made up of three save sets (A, B, and C). Save set A is restored at the beginning of the installation process and the remaining save sets are restored at this point in the process. See Appendix C for a description of each save set. 9. Special Notifications At this point in the installation, special notifications will be listed. For example: *************************************************************** PLEASE NOTE: All FileBridge tables (.FBO files) MUST be recompiled after this version V1.1-01 has been installed. Tables which are not recompiled will FAIL at runtime. Use the following command to recompile any FileBridge tables: $ FILEBRIDGE DEFINE/COMPILE .FBO Installing FileBridge 2-9 Installing FileBridge 2.2 The Installation Procedure This version of DEC/EDI FileBridge contains audit and security features. Please read the installation guide, release notes and manual carefully so that the audit and security features do not cause unnecessary difficulty. ****************************************************************** 10.Creating or retaining an Audit Database If you are creating databases, you will see messages like the following: Exported by Rdb/VMS V4.2-0 Export/Import utility A component of VAX SQL V4.2-0 Previous name was FBR$AUDIT_ROOT:[FBR$DB]FBR$AUDIT_DATABASE It was logically exported on 20-DEC-1993 14:24:48.60 Database NUMBER OF USERS is 50 Database NUMBER OF VAXCLUSTER NODES is 16 Database NUMBER OF DBR BUFFERS is 20 Database SNAPSHOT is ENABLED Database SNAPSHOT is IMMEDIATE Database BUFFER SIZE is 12 blocks Database NUMBER OF BUFFERS is 20 IMPORTing STORAGE AREA: RDB$SYSTEM IMPORTing STORAGE AREA: EVENT_DATA_AREA IMPORTing STORAGE AREA: EVENT_INDEX_AREA IMPORTing relation EVENT FileBridge is ready to be installed. 11.Questions about continuing the installation * Do you want to continue this installation: [YES]? No further questions will be asked during the installation. Informational and success messages will be displayed indicating the remaining events that will take place. 2.2.3 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. VMSINSTAL moves the new or modified files to their target directories, updates DCL tables, and purges appropriate files. The procedure displays the following types of messages: 2-10 Installing FileBridge Installing FileBridge 2.2 The Installation Procedure %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.FBR]. This installation added or modified the following files: SYS$LIBRARY:DCLTABLES.EXE SYS$LIBRARY:FBR$RTLIBRARY.OLB SYS$LIBRARY:FBR$MESSAGES.OBJ SYS$LIBRARY:FBR$MESSAGES.H SYS$SHARE:FBR$DECEDI_EXTRACT.EXE SYS$HELP:FBR$HELP.HLP SYS$STARTUP:FBR$STARTUP.COM SYS$TEST:FBR$IVP.COM SYS$TEST:[FBR]FBR$EXAMPLE.FBO SYS$TEST:[FBR]FBR$EXAMPLE.DAT FBR$EXE:FBR$UI.EXE FBR$EXE:FBR$RUNTIME.EXE FBR$EXE:FBR$TRACKING.EXE FBR$EXE:FBR$RECOVER.EXE FBR$EXE:FBR$DECEDI_EXTRACT.EXE FBR$EXE:FBR$EXTRACT_INSTALL.COM FBR$DOC:FBR$INSTAL.PS FBR$LIBRARY:FBR$AUDIT_DATABASE.RBR FBR$LIBRARY:FBR$AUDIT_DATABASE.RDB FBR$LIBRARY:FBR$AUDIT_DATABASE.RDA FBR$LIBRARY:FBR$AUDIT_DATABASE.SNP FBR$LIBRARY:FBR$AUDIT_DATA.RDA FBR$LIBRARY:FBR$AUDIT_DATA.SNP FBR$LIBRARY:FBR$AUDIT_INDEX.RDA FBR$LIBRARY:FBR$AUDIT_INDEX.SNP FBR$LIBRARY:FBR$RUN_ID.DAT SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_DATABASE.RBR SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_DATABASE.RDB SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_DATABASE.RDA SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_DATABASE.SNP SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_DATA.RDA SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_DATA.SNP SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_INDEX.RDA SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$AUDIT_INDEX.SNP SYS$SYSDEVICE:[FILEBRIDGE.TEST_DB]:FBR$RUN_ID.DAT For automatic startup of FileBridge when the system bootstraps, modify SYS$MANAGER:SYSTARTUP_V5.COM to invoke the command procedure SYS$STARTUP:FBR$STARTUP.COM Installing FileBridge 2-11 Installing FileBridge 2.2 The Installation Procedure %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... FileBridge Database Archive Procedure - Version V1.0-01 The FileBridge PRIMARY audit database is being initialized as: SYS$SYSDEVICE:[FILEBRIDGE.931229171341.FBR$DB] %FBR-I-LNM, FBR$AUDIT_ROOT is defined as: SYS$SYSDEVICE:[FILEBRIDGE.931229171341.] %FBR-I-LNM, FBR$LIBRARY is defined as: SYS$SYSDEVICE:[FILEBRIDGE.931229171341.FBR$DB] %FBR-I-LNM, FBR$HISTORY is defined as: SYS$SYSDEVICE:[FILEBRIDGE.931229171341.FBR$HISTORY] %INSTALL-E-FAIL, failed to CREATE entry for DISK$VMSRL5: -INSTALL-E-EXISTS, Known File Entry for a version of this file already exists Ignore previous error message from INSTALL Image will be replaced. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files contained within this installation kit to their target directories. 2.2.4 Running the Installation Verification Procedure If you chose to run the IVP, VMSINSTAL runs it now. The procedure displays the following messages. **************************************************************** FILEBRIDGE Installation Verification Procedure **************************************************************** Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V1.1-01 2-12 Installing FileBridge Installing FileBridge 2.2 The Installation Procedure %FBR-I-LNM, Process logical name for FBR$LIBRARY is: LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$DB] %FBR-I-LNM, Process logical name for FBR$HISTORY is: LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$HISTORY] %FBR-I-LNM, Process logical name for FBR$AUDIT_ROOT is: LOCAL1:[FILEBRIDGE.HOME.TEST_DB.] "FBR$HOME" = "LOCAL1:[FILEBRIDGE.HOME]" (LNM$SYSTEM_TABLE) "FBR$EXE" = "LOCAL1:[FILEBRIDGE.EXE]" (LNM$SYSTEM_TABLE) "FBR$LIBRARY" = "LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$DB]" (LNM$PROCESS_TABLE) "FBR$LIBRARY" = "LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$DB]" (LNM$SYSTEM_TABLE) "FBR$HISTORY" = "LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$HISTORY]" (LNM$PROCESS_TABLE) "FBR$HISTORY" = "LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$HISTORY]" (LNM$SYSTEM_TABLE) "FBR$AUDIT_ROOT" = "LOCAL1:[FILEBRIDGE.HOME.TEST_DB.]" (LNM$PROCESS_TABLE) "FBR$AUDIT_ROOT" = "LOCAL1:[FILEBRIDGE.HOME.940209145708.]" (LNM$SYSTEM_TABLE) Now Doing: FILEBRIDGE DEFINE/COMPILE FBR$EXAMPLE.FBO Copyright Digital Equipment Corporation 1990,1994. All rights reserved. Generating a listing in FBR$EXAMPLE.LIS Parsing the table... Compiling the table... FileBridge Tracking Run ID: 000048 Compile Complete Now Doing: FILEBRIDGE SEND FBR$EXAMPLE.FBO FBR$EXAMPLE.DAT Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Tracking Run ID: 000049 Document AP_O_0000000001 generated %FBR-S-SUCCESS_SEND, Normal completion - SEND Now Doing: FILEBRIDGE TRACKING/OUT=FBR$EXAMPLE.AUDIT Now Doing: FILEBRIDGE RECOVER/run=000049 Installing FileBridge 2-13 Installing FileBridge 2.2 The Installation Procedure Copyright Digital Equipment Corporation 1991,1993. All rights reserved. FileBridge Tracking Run ID: 000050 %FBR-E-AUD_ALREADY_COM, Run already marked as complete with END PROCESS event Did not post END_PROCESS events for any incomplete runs. There were 0 errors. FILEBRIDGE Installation Verification Procedure completed successfully. If the IVP ran successfully you will see the following message: FILEBRIDGE Installation Verification Procedure completed successfully. ************************************************************************ IVP for FileBridge for DEC/EDI V1.1-01 successful. ************************************************************************ 2.2.5 Completing the Installation Procedure The following messages indicate that the installation is complete: Installation of FBR V1.1 completed at 17:42 VMSINSTAL procedure done at 17:42 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.2.6 Error Recovery If errors occur during the installation or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the procedure displays the following messages: %VMSINSTAL-E-INSFAIL, The installation of FBR V1.1 has failed. 2-14 Installing FileBridge Installing FileBridge 2.2 The Installation Procedure If the IVP fails, the procedure displays the following messages: FILEBRIDGE Installation Verification Procedure failed. ****************************************************************** IVP for FileBridge for DEC/EDI V1.1-01 failed. ****************************************************************** %VMSINSTAL-E-IVPFAIL, The IVP for FBR V1.1 has failed. Errors might occur during the installation if any of the following conditions exist: o The version of the operation system is incorrect. o A required software version is incorrect. o Quotas are insufficient. o System parameter values are insufficient. For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on software installation and on system messages and recovery procedures. If any of these error messages are displayed, 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 FileBridge 2-15 3 _________________________________________________________________ After Installing FileBridge After installing FileBridge, you need to perform the following tasks: o Edit the system startup procedure. o Define FileBridge Rights. o Run the IVP separately (if it wasn't run during the installation). 3.1 Edit the System Startup Procedure To make sure that FileBridge starts properly after a system reboot, you must add the following line to the system startup procedure, SYS$MANAGER:SYSTARTUP_V5.COM: $ @SYS$STARTUP:FBR$STARTUP.COM 3.2 Adding symbol for DEC/EDI Extract to LOGIN.COM For FileBridge DEC/EDI EXTRACT to function properly, each user must have the following symbol in the login.com file. $ FBR$DECEDI_EXTRACT :== $SYS$SHARE:FBR$DECEDI_EXTRACT 3.3 User Account Requirements To work with FileBridge, user accounts on your system must have certain privileges and quotas. This section contains information on these requirements. To use FileBridge, each account must have at least the TMPMBX and NETMBX privileges. After Installing FileBridge 3-1 After Installing FileBridge 3.3 User Account Requirements You must make sure that the appropriate user accounts have sufficient quotas to be able to use FileBridge. The values suggested are minimum settings; the settings required by users on your system might differ substantially. The suggested values are specific only to the use of FileBridge, although they include the values required for the FileBridge prerequisite layered products. You should add the values required for other OpenVMS layered products to the value you choose to use for FileBridge and modify the values for each user as needed. Table 3-1 summarizes the required user account quotas. Table_3-1__User_Account_Quotas_____________________________ Account Quota_________Value________________________________________ ASTLM 22 BIOLM 20 BYTLM 20,480 DIOLM 20 ENQLM 600[1] FILLM 50 PGFLQUOTA 60,000 [1]This_value_should_be_raised_to_2000_if_CDD/Repository_or the FileBridge TRACKING command is used. ___________________________________________________________ 3.4 Installing FileBridge in a VAX Cluster Environment If you intend to execute this layered product on other nodes in your VAXcluster, and you have the appropriate software license, you must replace DCLTABLES, and execute the startup on the other nodes by issuing the following command on each node (using a suitably privileged account): $mcr sysman set env/cluster do install replace sys$share:dcltables do @sys$startup:fbr$startup do install sys$share:fbr$decedi_extract /open/head/exec/priv=syspr exit 3-2 After Installing FileBridge After Installing FileBridge 3.4 Installing FileBridge in a VAX Cluster Environment If you receive a warning that the global page table is full you must reboot your system. Failure to do so will prevent any users from logging on the system. Any users who are logged in when you replace the dcl tables will have to log out and log back in before they will be able to use FileBridge. 3.5 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.5.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. After Installing FileBridge 3-3 After Installing FileBridge 3.5 Defining FileBridge Rights 3. FBR$OPERATIONS Users assigned to this category generally only process documents in a production environment, preferably a production library. 3.5.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 production 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 The 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 The 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. These modules should be placed in the production directory along with the FileBridge tables. The supervisor must 3-4 After Installing FileBridge After Installing FileBridge 3.5 Defining FileBridge Rights set the Shared Image filename in the FileBridge table to point to the production directory before compiling the table. This should not be the FBR$LIBRARY directory but could be a subdirectory under FBR$HOME. o The executables. The FileBridge runtime program and the FileBridge User Interface can be placed in READ ONLY access protected directory at installation time. 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.5.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.5.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.6 Recompile FileBridge Tables All FileBridge tables (.FBO files) must be recompiled after installing this version (V1.1-01). This can be done in batch using the command FILEBRIDGE DEFINE/COMPILE for each table. Failure to recompile will result in failure at runtime. After Installing FileBridge 3-5 After Installing FileBridge 3.7 Running the IVP Separately 3.7 Running the IVP Separately You can run the IVP independently by executing the following DCL command: $ @SYS$TEST:FBR$IVP This command file runs the IVP to check the validity of the installation. 3.8 Problems After Installation If you have problems after the installation, contact your Digital support representitive. U.S. customers who encounter a problem while using FileBridge can report it to Digital by telephoning the Digital Customer Support Center (CSC) at 1-800-354- 9000. (Customers with service contracts can also use an electronic means such as DSNlink.) Customers without a service contract can arrange for per-call support. The CSC will need the following information: o The name and version number of the operating system you are using o The FileBridge and version number you are using o The hardware system you are using (such as a model number) o A brief description of the problem (one sentence if possible) o Whether or not the problem is critical o Any other information that is helpful, such as the specific commands you used to run the software, the error messages displayed, and source listings of the relevant software module or lines of code If the problem is related to FileBridge documentation, you can do any of the following: o Report the problem to the CSC (if you have a service contract and the problem is severe). 3-6 After Installing FileBridge After Installing FileBridge 3.8 Problems After Installation o Fill out the Reader's Comments form (in the back of the document that contains the error) and send the form to Digital. If you are reporting a specific error, be sure to include the section and page number where the error occurred. After Installing FileBridge 3-7 A _________________________________________________________________ Sample Installation This appendix contains a sample installation of FileBridge. The sample installation assumes that no users are logged on to your system, and that OPTIONS N is specified to print the Release Notes. The Installation Verification Procedure (IVP) runs at the end of the installation. A.1 Sample VAX/VMS Software Product Installation Procedure V5.5-2 It is 22-FEB-1994 at 12:01. 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: _FTA14: * 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: FBR V1.1 Beginning installation of FBR V1.1 at 12:01 %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 1990,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. Sample Installation A-1 Sample Installation A.1 Sample This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. WARNING: Digital recommends that the FileBridge installation be run from the SYSTEM account. Sufficient quotas for running the prerequisites must be available. If you choose to install FileBridge from an account other than SYSTEM, that account must have the FBR$SUPERVISOR rights identifier to enable the IVP. * Do you want to run the IVP after the installation [YES]? y Installation should take approximately 15 to 20 minutes, depending on your type of media and your system configuration. The Installation Verification Procedure (IVP) takes about 10 additional minutes. FileBridge requires 40,500 blocks of temporary space on the system disk during installation. Following installation, 33,000 blocks of permanent space are required on the system disk if you use the installation defaults. If you specify an alternate location, you must be sure the following space is available: Executables 8,000 blocks Documentation 400 blocks Database 22,000 blocks System Disk (IVP,helps, and SYS$SHARE) 2,000 blocks The executables for FileBridge normally reside in SYS$COMMON:[SYSEXE]. Or, you may specify an alternate location. The system logical FBR$EXE will contain the name of the directory. Enter the full pathname for the directory where the FileBridge programs are to reside. The directory will be created if it does not already exist. * Directory name [SYS$COMMON:[SYSEXE]]: local1:[filebridge.exe] The location of FBR$HOME has been determined from a previous installation. You can keep the current value or change it. The current value of FBR$HOME is LOCAL1:[FILEBRIDGE.HOME] * Do you want to change the value of FBR$HOME [NO]? A-2 Sample Installation Sample Installation A.1 Sample 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 LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$DB] * Do you want to change the primary database [NO]? The FileBridge documentation will be placed in the directory that you specify. Enter the full pathname for the directory where the FileBridge documentation is to reside. The directory will be created for you if it does not already exist. * Directory name [SYS$SYSDEVICE:[FILEBRIDGE]]: local1:[filebridge.doc] %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... *********************************************************************** PLEASE NOTE: All FileBridge tables (.FBO files) MUST be recompiled after this version V1.1-01 has been installed. Tables which are not recompiled will FAIL at runtime. Use the following command to recompile any FileBridge tables: $ FILEBRIDGE DEFINE/COMPILE .FBO This version of DEC/EDI FileBridge contains audit and security features. Please read the installation guide, release notes and manual carefully so that the audit and security features do not cause unnecessary difficulty. *********************************************************************** %CREATE-I-EXISTS, LOCAL1:[FILEBRIDGE.EXE] already exists %CREATE-I-EXISTS, LOCAL1:[FILEBRIDGE.HOME] already exists %CREATE-I-EXISTS, LOCAL1:[FILEBRIDGE.HOME.TEST_DB] already exists %CREATE-I-EXISTS, LOCAL1:[FILEBRIDGE.DOC] already exists Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V1.1-01 %FBR-F-EXISTS, Database already exists in target directory. FileBridge is ready to be installed. * Do you want to continue this installation: [YES]? y Sample Installation A-3 Sample Installation A.1 Sample No further questions will be asked during the installation. Informational and success messages will be displayed indicating the remaining events that will take place. %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.FBR]. %CREATE-I-EXISTS, VMI$COMMON:[SYSTEST.FBR] already exists This installation added or modified the following files: SYS$LIBRARY:DCLTABLES.EXE SYS$LIBRARY:FBR$RTLIBRARY.OLB SYS$LIBRARY:FBR$MESSAGES.OBJ SYS$LIBRARY:FBR$MESSAGES.H SYS$SHARE:FBR$DECEDI_EXTRACT.EXE SYS$HELP:FBR$HELP.HLP SYS$STARTUP:FBR$STARTUP.COM SYS$TEST:FBR$IVP.COM SYS$TEST:[FBR]FBR$EXAMPLE.FBO SYS$TEST:[FBR]FBR$EXAMPLE.DAT FBR$EXE:FBR$UI.EXE FBR$EXE:FBR$RUNTIME.EXE FBR$EXE:FBR$TRACKING.EXE FBR$EXE:FBR$RECOVER.EXE FBR$EXE:FBR$DECEDI_EXTRACT.EXE FBR$EXE:FBR$EXTRACT_INSTALL.COM FBR$DOC:FBR$INSTAL.PS FBR$DOC:FBR$011_RELEASE_NOTES.PS For automatic startup of FileBridge after a system reboot, please modify the system startup procedure to run the command procedure SYS$STARTUP:FBR$STARTUP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V1.1-01 The FileBridge PRIMARY audit database is being initialized as: LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$DB] A-4 Sample Installation Sample Installation A.1 Sample %FBR-I-LNM, FBR$AUDIT_ROOT is defined as: LOCAL1:[FILEBRIDGE.HOME.940209145708.] %FBR-I-LNM, FBR$LIBRARY is defined as: LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$DB] %FBR-I-LNM, FBR$HISTORY is defined as: LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$HISTORY] %INSTALL-E-FAIL, failed to CREATE entry for DISK$VMSRL5:FBR$DECEDI_EXTRACT.EXE -INSTALL-E-EXISTS, Known File Entry for a version of this file already exists Ignore previous error message from INSTALL Image will be replaced. Copyright Digital Equipment Corporation 1990,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. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ********************************************************************* Executing IVP for FileBridge for DEC/EDI V1.1-01 ********************************************************************* Copyright Digital Equipment Corporation 1990,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. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Sample Installation A-5 Sample Installation A.1 Sample Setting default to SYS$COMMON:[SYSTEST.FBR] **************************************************************** * FILEBRIDGE Installation Verification Procedure **************************************************************** Copyright Digital Equipment Corporation 1990,1994. All rights reserved. FileBridge Database Archive Procedure - Version V1.1-01 %FBR-I-LNM, Process logical name for FBR$LIBRARY is: LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$DB] %FBR-I-LNM, Process logical name for FBR$HISTORY is: LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$HISTORY] %FBR-I-LNM, Process logical name for FBR$AUDIT_ROOT is: LOCAL1:[FILEBRIDGE.HOME.TEST_DB.] "FBR$HOME" = "LOCAL1:[FILEBRIDGE.HOME]" (LNM$SYSTEM_TABLE) "FBR$EXE" = "LOCAL1:[FILEBRIDGE.EXE]" (LNM$SYSTEM_TABLE) "FBR$LIBRARY" = "LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$DB]" (LNM$PROCESS_TABLE) "FBR$LIBRARY" = "LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$DB]" (LNM$SYSTEM_TABLE) "FBR$HISTORY" = "LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$HISTORY]" (LNM$PROCESS_TABLE) "FBR$HISTORY" = "LOCAL1:[FILEBRIDGE.HOME.940209145708.FBR$HISTORY]" (LNM$SYSTEM_TABLE) "FBR$AUDIT_ROOT" = "LOCAL1:[FILEBRIDGE.HOME.TEST_DB.]" (LNM$PROCESS_TABLE) "FBR$AUDIT_ROOT" = "LOCAL1:[FILEBRIDGE.HOME.940209145708.]" (LNM$SYSTEM_TABLE) Now Doing: FILEBRIDGE DEFINE/COMPILE FBR$EXAMPLE.FBO Copyright Digital Equipment Corporation 1990,1994. All rights reserved. Generating a listing in FBR$EXAMPLE.LIS Parsing the table... Compiling the table... FileBridge Tracking Run ID: 000048 Compile Complete Now Doing: FILEBRIDGE SEND FBR$EXAMPLE.FBO FBR$EXAMPLE.DAT Copyright Digital Equipment Corporation 1990,1994. All rights reserved. A-6 Sample Installation Sample Installation A.1 Sample FileBridge Tracking Run ID: 000049 Document AP_O_0000000001 generated %FBR-S-SUCCESS_SEND, Normal completion - SEND Now Doing: FILEBRIDGE TRACKING/OUT=FBR$EXAMPLE.AUDIT Now Doing: FILEBRIDGE RECOVER/run=000049 Copyright Digital Equipment Corporation 1991,1993. All rights reserved. FileBridge Tracking Run ID: 000050 %FBR-E-AUD_ALREADY_COM, Run already marked as complete with END PROCESS event Did not post END_PROCESS events for any incomplete runs. There were 0 errors. FILEBRIDGE Installation Verification Procedure completed successfully. ********************************************************************* IVP for FileBridge for DEC/EDI V1.1-01 successful. ********************************************************************* Installation of FBR V1.1 completed at 12:08 VMSINSTAL procedure done at 12:08 Sample Installation A-7 B _________________________________________________________________ FileBridge Files and Logical Names The FileBridge installation procedure installs a number of files on your system and defines several logical names. The following is a list of all files installed on your system when FileBridge is installed. SYS$LIBRARY:FBR$RTLIBRARY.OLB SYS$LIBRARY:FBR$MESSAGES.OBJ SYS$LIBRARY:FBR$MESSAGES.H SYS$SHARE:FBR$DECEDI_EXTRACT.EXE FBR$EXE:FBR$UI.EXE FBR$EXE:FBR$RUNTIME.EXE FBR$EXE:FBR$TRACKING.EXE FBR$EXE:FBR$RECOVER.EXE FBR$EXE:FBR$DECEDI_EXTRACT.EXE FBR$EXE:FBR$EXTRACT_INSTALL.COM SYS$STARTUP:FBR$STARTUP.COM SYS$TEST:FBR$IVP.COM SYS$TEST:[FBR]FBR$EXAMPLE.FBO SYS$TEST:[FBR]FBR$EXAMPLE.DAT FBR$INSTAL.PS If you created a live database as part of your installation, the following files will be installed on your system. FBR$LIBRARY:FBR$AUDIT_DATABASE.RBR FBR$LIBRARY:FBR$AUDIT_IMPORT_DATABASE.COM FBR$LIBRARY:FBR$AUDIT_DATABASE.RDB FBR$LIBRARY:FBR$AUDIT_DATABASE.RDA FBR$LIBRARY:FBR$AUDIT_DATABASE.SNP FBR$LIBRARY:FBR$AUDIT_DATA.RDA FBR$LIBRARY:FBR$AUDIT_DATA.SNP FBR$LIBRARY:FBR$AUDIT_INDEX.RDA FBR$LIBRARY:FBR$AUDIT_INDEX.SNP FBR$LIBRARY:FBR$RUN_ID.DAT FileBridge Files and Logical Names B-1 FileBridge Files and Logical Names If you created a test database as part of your installation, the following files will be located in the directory TEST_DB.FBR$DB under FBR$HOME. FBR$AUDIT_DATABASE.RBR FBR$AUDIT_IMPORT_DATABASE.COM FBR$AUDIT_DATABASE.RDB FBR$AUDIT_DATABASE.RDA FBR$AUDIT_DATABASE.SNP FBR$AUDIT_DATA.RDA FBR$AUDIT_DATA.SNP FBR$AUDIT_INDEX.RDA FBR$AUDIT_INDEX.SNP FBR$RUN_ID.DAT The following files on your system are modified during the installation process. SYS$LIBRARY:DCLTABLES.EXE SYS$HELP:HELPLIB.HLB The installation procedure creates the FBR$STARTUP.COM file and places it in SYS$STARTUP. This command procedure defines the following system-wide logicals: o FBR$EXE o FBR$LIBRARY o FBR$HISTORY o FBR$AUDIT_ROOT B-2 FileBridge Files and Logical Names C _________________________________________________________________ Files in the Installation Kit This appendix lists the files that go into the different save sets and shows where the files are moved to during the installation process. C.1 Save-set A Table_C-1_Files_in_Save-set_A______________________________ Filename___________________Size(blocks)Location_on_System__ KITINSTAL.COM 148 FBR$011.RELEASE_NOTES______356_________SYS$HELP____________ C.2 Save-set B Table_C-2_Files_in_Save-set_B______________________________ Filename___________________Size(blocks)Location_on_System__ FBR$DCL.CLD 11 dcl tables are updated FBR$DECEDI_EXTRACT.COM 7 installer specifies FBR$DECEDI_EXTRACT.EXE 217 normally deleted at end of installation FBR$HELP.HLP 452 help library is updated FBR$IVP.COM 17 SYS$TEST FBR$EXAMPLE.FBO 376 [SYSTEST.FBR] FBR$EXAMPLE.DAT 1 [SYSTEST.FBR] (continued on next page) Files in the Installation Kit C-1 Files in the Installation Kit C.2 Save-set B Table_C-2_(Cont.)__Files_in_Save-set_B_____________________ Filename___________________Size(blocks)Location_on_System__ FBR$RTLIBRARY.OLB 459 SYS$LIBRARY FBR$MESSAGES.OBJ 92 SYS$LIBRARY FBR$MESSAGES.H 61 SYS$LIBRARY FBR$UI.EXE 2707 installer specifies FBR$UI_LIST.OBJ 93 deleted at end of installation FBR$UI_TRACKING.OBJ 85 deleted at end of installation FBR$UI_SELECT.OBJ 60 deleted at end of installation FBR$RECOVER.OBJ 37 deleted at end of installation FBR$RPT_TRACKING.OBJ 58 deleted at end of installation NOTIFY.TXT 2 deleted at end of installation FBR$TBL_HANDLER.OBJ 49 deleted at end of installation FBR$ISLOGICAL.OBJ 6 deleted at end of installation FBR$FUTIL.OBJ 27 deleted at end of installation FBR$AUDIT.OBJ 30 deleted at end of installation FBR$RUNTIME.EXE 510 installer specifies FBR$TRACKING.EXE 592 installer specifies FBR$AUDIT_DATABASE.RBR 12 installer specifies FBR$ARCHIVE.COM 160 installer specifies FBR$RECOVER.EXE 515 installer specifies FBR$EXTRACT_INSTALL.COM____9___________installer_specifies_ C-2 Files in the Installation Kit Files in the Installation Kit C.3 Save-set C C.3 Save-set C Table_C-3_Files_in_Save-set_C______________________________ Filename___________________Size(blocks)Location_on_System__ FBR$INSTAL.PS 578 installer specifies FBR$011_RELEASE_NOTES.PS___1030________installer_specifies_ Files in the Installation Kit C-3 D _________________________________________________________________ File Security For The Installed Files This appendix lists the security for the files that are installed by the installation procedure. Files in SYS$COMMON:[SYSLIB] FBR$DECEDI_EXTRACT.EXE [SYSTEM] (RWED,RWED,RWED,RE) FBR$MESSAGES.H [SYSTEM] (RWED,RWED,RWED,RE) FBR$MESSAGES.OBJ [SYSTEM] (RWED,RWED,RWED,RE) FBR$RTLIBRARY.OLB [SYSTEM] (RWED,RWED,RWED,RE) Total of 4 files. Files in SYS$COMMON:[SYS$STARTUP] FBR$STARTUP.COM [SYSTEM] (RWED,RE,,) Total of 1 file. Files in fSYS$COMMON:[SYSTEST] FBR$IVP.COM [SYSTEM] (RWED,RE,,) Total of 1 file. Files in SYS$COMMON:[SYSTEST.FBR] FBR$EXAMPLE.AUDIT [SYSTEM] (RWED,RE,,) FBR$EXAMPLE.DAT [SYSTEM] (RWED,RE,,) FBR$EXAMPLE.FBO [SYSTEM] (RWED,RE,,) FBR$EXAMPLE.LIS [SYSTEM] (RWED,RE,,) FBR$LOCAL_TEST_OUT.INHOUSE [SYSTEM] (RWED,RE,,) Total of 5 files. File Security For The Installed Files D-1 File Security For The Installed Files Files in LOCAL1:[FILEBRIDGE.EXE] FBR$ARCHIVE.COM [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$DECEDI_EXTRACT.COM [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$EXTRACT_INSTALL.COM [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR,ACCESS=READ+WRITE+EXECUTE +DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$RECOVER.EXE [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$RUNTIME.EXE [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$TRACKING.EXE [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$UI.EXE [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) Total of 7 files. D-2 File Security For The Installed Files File Security For The Installed Files Files in LOCAL1:[FILEBRIDGE.DOC] FBR$INSTAL.PS [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$011_RELEASE_NOTES.PS [SYSTEM] (RWED,RWED,RWED,RE) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) Total of 2 files. Files in LOCAL1:[FILEBRIDGE.HOME.940126092904.FBR$DB] FBR$AUDIT_DATA.RDA [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_DATA.SNP [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_DATABASE.RDA [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_DATABASE.RDB [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) File Security For The Installed Files D-3 File Security For The Installed Files FBR$AUDIT_DATABASE.SNP [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_INDEX.RDA [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_INDEX.SNP [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$RUN_ID.DAT [SYSTEM] (RWED,RWED,RW,) (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) Total of 8 files. D-4 File Security For The Installed Files File Security For The Installed Files Files in LOCAL1:[FILEBRIDGE.HOME.TEST_DB] FBR$DB.DIR [SYSTEM] (RWE,RWE,RE,E) (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) FBR$HISTORY.DIR [SYSTEM] (RWE,RWE,RE,E) (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) Total of 2 files. Files in LOCAL1:[FILEBRIDGE.HOME.TEST_DB.FBR$DB] FBR$AUDIT_DATA.RDA [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_DATA.SNP [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) File Security For The Installed Files D-5 File Security For The Installed Files FBR$AUDIT_DATABASE.RDA [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_DATABASE.RDB [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_DATABASE.SNP [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_INDEX.RDA [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) FBR$AUDIT_INDEX.SNP [SYSTEM] (RWED,R,,) (IDENTIFIER=FBR$SUPERVISOR, ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL) (IDENTIFIER=FBR$OPERATIONS,ACCESS=READ+EXECUTE) (IDENTIFIER=FBR$DEVELOPMENT,ACCESS=READ+EXECUTE) D-6 File Security For The Installed Files File Security For The Installed Files FBR$RUN_ID.DAT [SYSTEM] (RWED,RWED,RW,) (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) Total of 8 files. File Security For The Installed Files D-7