TeamRoute_for_ALL-IN-1________________________ Installation and System Management Guide Order Number: AA-PWNRA-TE January 1993 This manual provides information on installing and managing TeamRoute for ALL-IN-1. TeamRoute produces and directs routing packages across heterogeneous local-area and wide-area networks. Revision/Update Information: Revised for TeamRoute Version 1.1. Operating System: VMS Version 5.4 or higher, ALL-IN-1 Version 3.0-1. Software Version: TeamRoute for ALL-IN- 1 Version 1.1. Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ January 1993 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1993. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, DECforms, DECnet, DECwindows, PATHWORKS, TeamRoute, VAX Basic, VAX C, VAX FMS, VAX Notes, VAX VTX, VMS, WPS-PLUS, and the DIGITAL logo. The following are third-party trademarks: DeskTop is a registered trademark of DeskTop Software Corporation. IBM is a registered trademark of International Business Machines Corporation. MS-DOS is a registered trademark of Microsoft Corporation. Lotus and 1-2-3 are registered trademarks of Lotus Development Corporation. WordPerfect is a trademark of WordPerfect Corporation. UNIX is a registered trademark of UNIX System Laboratory, Inc. Windows is a trademark of Microsoft Corporation. This document is available on CDROM. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. vii 1 Overview 1.1 Routing Package Processing................... 1-1 1.2 Client/Server Model.......................... 1-2 1.3 Programming Functions........................ 1-3 1.4 Templates.................................... 1-3 1.5 Routing Packages............................. 1-4 1.5.1 Roles.................................... 1-5 1.5.2 Routing.................................. 1-6 1.5.3 Tracking................................. 1-6 1.5.4 Attachments.............................. 1-6 1.5.5 Signatures............................... 1-6 2 Preparing to Install TeamRoute for ALL-IN-1 2.1 Prerequisite Software........................ 2-1 2.2 VMS License Management Facility.............. 2-2 2.3 Installation Procedure Requirements.......... 2-2 2.3.1 Checking the ALL-IN-1 Site Link Files.... 2-2 2.3.2 Checking ALL-IN-1 Logicals............... 2-3 2.3.3 Privileges............................... 2-4 2.3.4 Disk Space Requirements.................. 2-4 2.3.5 System Parameters........................ 2-6 2.3.5.1 Calculating the Values for GBLPAGES and GBLSECTIONS............................ 2-6 2.3.5.2 Changing System Parameter Values with AUTOGEN................................ 2-8 2.3.6 Process Account Quotas................... 2-9 2.3.7 VMSINSTAL Requirements................... 2-10 2.3.8 Backing Up Your System Disk.............. 2-10 iii 3 Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation................................. 3-1 3.2 Additional Language Installation............. 3-12 3.3 Error Recovery............................... 3-12 4 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.1 Preparing to Upgrade TeamRoute............... 4-1 4.1.1 Updating the A1V30SITE_START.COM, SITELINK30 and SITELLV Files............. 4-2 4.1.2 Defining the TeamRoute Logicals.......... 4-3 4.2 Upgrading your System to TeamRoute Version 1.1 ......................................... 4-3 4.3 Upgrading Additional Languages............... 4-4 4.4 Upgrading your Customizations to TeamRoute Version 1.0 ................................. 4-4 4.4.1 Removing your Customizations from Live Before an Upgrade ....................... 4-5 4.4.1.1 Files and Forms in the TeamRoute Site Directory for Primary Language......... 4-5 4.4.1.2 Files and Forms in the TeamRoute Site Directory for Secondary Language....... 4-6 4.4.1.3 Files in the TeamRoute Site Share Directory ............................. 4-7 4.4.2 Restoring your Customizations on TeamRoute Version 1.1 ................... 4-7 4.4.2.1 Forms in the TeamRoute Site Directory for the Primary Language............... 4-7 4.4.2.2 Boilerplate Files, Scripts, and Other Files in the TeamRoute Site Directory for Primary Language................... 4-9 4.4.2.3 Files and Forms in the TeamRoute Site Directory for Secondary Languages...... 4-10 4.4.2.4 Files in the TeamRoute Site Share Directory.............................. 4-10 iv 5 After Installing TeamRoute 5.1 Updating ALL-IN-1 Forms to Support TeamRoute.................................... 5-1 5.1.1 Updating Form MAIN....................... 5-1 5.1.2 Updating Form DEFAULT.................... 5-4 5.1.3 Updating Forms SM$MAIN2 and SM_DEFAULT... 5-4 5.2 Compiling and Installing the ALL-IN-1 Text Library (A1TXL.TXL) ......................... 5-5 5.3 Determining and Reporting Problems........... 5-5 6 Managing TeamRoute Services 6.1 Managing TeamRoute Accounts.................. 6-2 6.1.1 Using the TeamRoute Account Index and Menu..................................... 6-5 6.2 Managing the Service Agent................... 6-6 6.2.1 Setting the Wait Interval................ 6-10 6.2.2 Using the Service Agent Log File......... 6-11 6.2.3 Using the Service Agent Transaction File..................................... 6-11 6.2.4 Tracing Service Agent Activity........... 6-12 6.3 Managing the Application Registration File... 6-13 6.3.1 Using the Application Index and Menu..... 6-15 6.4 Troubleshooting.............................. 6-16 A Sample Installation A.1 Installation of TeamRoute on a System for the First Time................................... A-1 A.2 Upgrade Installation of TeamRoute............ A-8 A.3 Installation of an Additional TeamRoute Language..................................... A-15 B Files and Logical Names Installed on Your System B.1 File Names................................... B-1 B.1.1 Files Placed on the System Disk.......... B-1 B.1.2 Files Placed in the ALL-IN-1 Directory... B-1 B.1.3 Files Installed in TeamRoute for ALL-IN-1 Directories.............................. B-2 B.1.4 Forms and Scripts not in TeamRoute Version 1.1 ............................. B-6 v B.2 Logical Names and Search Lists............... B-6 B.2.1 TeamRoute Logical Names.................. B-6 B.2.2 Logicals Added to Each ALL-IN-1 Language Logical Table (OA$language_TABLE)........ B-9 B.2.3 Logical Search Lists..................... B-10 B.3 ALL-IN-1 Files Modified by TeamRoute......... B-11 C Handling Diagnostics C.1 Informational Messages....................... C-1 C.2 Warning and Error Messages................... C-2 C.2.1 Warning Messages......................... C-2 C.2.2 Error Messages........................... C-5 D Transaction File D.1 Overview..................................... D-1 D.2 Record Format................................ D-2 D.2.1 Fixed-Length Fields...................... D-2 D.2.2 Variable-Length Fields................... D-3 E Modifying User Mail Destinations Index Figures 1-1 TeamRoute Client/Service Agent Domain.... 1-2 1-2 Physical Template with Work-Item Copies................................... 1-3 6-1 TeamRoute System Management Menu......... 6-1 6-2 Manage TeamRoute User Accounts Menu...... 6-2 6-3 Manage TeamRoute Account Index Menu...... 6-5 6-4 TeamRoute Manage Service Agents Menu..... 6-7 6-5 Manage TeamRoute Application Registration File Menu................................ 6-13 6-6 Index Menu............................... 6-15 vi Tables 1 Conventions.............................. viii 2-1 Disk Space Requirements.................. 2-4 2-2 Minimum Required System Parameter Values................................... 2-6 2-3 Process Account Quotas for the Installing Account.................................. 2-9 6-1 Manage TeamRoute User Accounts Menu Options.................................. 6-4 6-2 Manage TeamRoute Account Index Menu Options.................................. 6-6 6-3 Manage Service Agents Menu Options....... 6-7 6-4 Manage TeamRoute Application Registration File Menu Options........................ 6-14 6-5 Index Menu Options....................... 6-15 D-1 Transaction File Fixed-Length Fields..... D-2 D-2 Transaction File Variable-Length Fields................................... D-3 vii ________________________________________________________________ Preface This manual tells you how to install TeamRoute[TM] for ALL-IN-1[TM] on your ALL-IN-1 system; locate the online release notes; and set up the Service Agent, clients, and registered application files. After you install TeamRoute, you can obtain detailed information about the system management commands by using online help. Intended Audience This manual is intended for experienced ALL-IN-1 system managers. Document Structure The information in this manual is divided as follows: o Chapter 1 provides an overview of TeamRoute. o Chapter 2 identifies the installation prerequisites. o Chapter 3 describes how to install TeamRoute on your system for the first time. o Chapter 4 describes how to upgrade a TeamRoute system to Version 1.1. o Chapter 5 identifies the post-installation requisites. o Chapter 6 tells you how to start and maintain TeamRoute services. o Appendix A contains sample listings from typical installations. o Appendix B lists the installation files. o Appendix C lists diagnostic messages. vii o Appendix D describes the transaction file. o Appendix E explains how to modify the mail destination of your system's ALL-IN-1 users who will be using TeamRoute for ALL-IN-1. Online help provides assistance on TeamRoute system management functions. Associated Documents The following documentation provides related information: o ALL-IN-1 Management Guide o TeamRoute for ALL-IN-1 User Guide o TeamRoute Programming Guide o Documentation for the VMS System Management Subkit Conventions Table 1 shows the conventions used in this manual: Table_1_Conventions_______________________________________ Convention_______Meaning__________________________________ ALL-IN-1[TM] Means ALL-IN-1 Integrated Office System Server for OpenVMS TeamRoute[TM] Means TeamRoute for ALL-IN-1 Signifies the key to press when following instructions. The box encloses the name of the key on your keyboard. The Enter key on some keyboards is equivalent to the Return key on other keyboards. boldface type Boldface type in examples indicates user input. Brackets [] Surround default values throughout the _________________installation_procedure___________________ viii 1 ________________________________________________________________ Overview This chapter provides an overview of TeamRoute for ALL-IN-1. For specific information on its use or details of its components, see the following chapters, appendixes, and the appropriate online help. 1.1 Routing Package Processing TeamRoute allows you to initiate, send, approve, and track routing packages between members and teams in the distributed environment of your organization. TeamRoute accommodates the primary attributes of your paper-based document processing systems with added flexibility, security, and efficiency. TeamRoute uses the routing package as the model for gathering, disseminating, processing, and presenting information. You select a template and create a routing package from that template. As part of the routing package creation process, you perform the following operations: o Specify routing information, including the role each recipient can perform. o View the form associated with the routing package (if applicable). Respond to the application prompts, as appropriate. o Attach relevant package components (if applicable). After you create the routing package, send it to your specified recipients for processing and either approval or disapproval. TeamRoute uses a client/server model. In this model, you interact with routing packages using a TeamRoute client. The client accesses a TeamRoute server to complete its processing and manage routing packages. Overview 1-1 Overview 1.1 Routing Package Processing The TeamRoute for ALL-IN-1 client extends ALL-IN-1 Integrated Office System/VT to provide character-cell access to all TeamRoute document processing functions. From the ALL-IN-1 Integrated Office System, you can access TeamRoute as a separate subsystem. Routing packages are received, filed, and organized in a separate inbox in your file cabinet. You can use ALL-IN-1 nicknames to send TeamRoute routing packages. 1.2 Client/Server Model This model supports interaction among a heterogeneous group of clients and between multiple server domains. Clients are connected to a server through a service agent, as shown in Figure 1-1. A server domain includes all service agents and clients associated with a particular server. Service domains are connected by the Digital[TM] MAILbus. TeamRoute allows your organization to be distributed across a wide area, local area network, or combination of networks. Figure 1-1 TeamRoute Client/Service Agent Domain WIDE The TeamRoute server provides a management utility specific to your ALL-IN-1 environment. Select the utility from the ALL-IN-1 Management menu to centrally manage TeamRoute system operations on your cluster. There are no special utilities to run for file cabinet maintenance. You can back up or restore subscriber areas on the server using standard VMS[TM] utilities. 1-2 Overview Overview 1.3 Programming Functions 1.3 Programming Functions TeamRoute for ALL-IN-1 provides an application programming interface (API). The API allows you to use ALL-IN-1 scripts to link with new and existing applications. TeamRoute also includes a run-time library (RTL) that can be used from all supported platforms. 1.4 Templates A TeamRoute template is an electronic structure from which routing packages are created. Templates contain default routing information and subscriber receipt actions for the routing packages. A TeamRoute template behaves somewhat like a physical template that is capable of producing multiple copies with the same structural attributes (as in Figure 1-2). Figure 1-2 Physical Template with Work-Item Copies TeamRoute provides several predefined templates, including: o Action Item Tracking o Document Review and Signoff o Account Request Form o Answer a Question o Telephone Slip o Travel Authorization o Read and Acknowledge These templates demonstrate the capabilities of TeamRoute and allow you to create related routing packages for use in your organization. Overview 1-3 Overview 1.4 Templates You can use these templates as supplied, customize them, or create new templates using the Template Creation utility (TCU). TeamRoute templates contain the following information: o General information, which includes: - Designer name - Creation date - Title - Subject - Routing package description o Subscriber roles o Role instructions o Attachments Attachments become part of all routing packages created from the template. o Form o Predefined routing list 1.5 Routing Packages A TeamRoute routing package is created by an initiator from a template and sent to recipients. Routing packages are similar to highly structured mail messages that include routing information as well as processing requests for each recipient. Routing packages can take many forms, including: o Information requests o Collaborative document editing and review cycles o Action item tracking o System problem reporting and tracking o Travel authorization requests o Property removal requests 1-4 Overview Overview 1.5 Routing Packages o Office equipment orders To create a routing package follow these steps: 1. Select a template 2. Fill in the routing list and the subject 3. View the associated form and supply information requested (if required) 4. Add attachments (if required) 5. Sign the routing package (if required) After you create a routing package, you can modify it, delete it, or send it to the recipients on the routing list. From the master, Routing and Carbon copies are sent to the recipients. Routing copies go to recipients who interact with the routing packages; for example, by adding attachments or approving it. Typically, carbon copies go to recipients who are allowed to only read the routing package. Recipients can save their routing or carbon copies in their personal file cabinets. The following sections provide additional information on TeamRoute routing packages. 1.5.1 Roles Roles define a set of rights (what you can do), requests (what you should do), and optionally, the name of an application associated with the role. During the lifecycle of a routing package, all participants play one or more specified roles. For example, you may be allowed to approve the routing package at one step, but only receive a carbon copy at another step. Roles are specified in the templates and are assigned by the routing package initiators. Overview 1-5 Overview 1.5 Routing Packages 1.5.2 Routing Routing package routing is defined by a routing list. TeamRoute generally sends routing packages according to the position of the recipients in the routing list. It updates the master if any of the recipients update their routing copy, then sends a copy of the updated master to the next recipient on the list. The routing package history records the path taken by a routing package during its lifecycle. 1.5.3 Tracking You can track the progress of a TeamRoute routing package if your role permits it. A tracking report contains the state of the routing package at the time the report was sent. The report also contains the attachments and signatures added to the routing package up to the time the report was sent. You also can use the routing package's history to monitor its progress. 1.5.4 Attachments Attachments allow you to include files that have been created by other applications in your environment to a TeamRoute routing package. An attachment can have any datatype that is recognized by your environment. Both routing package initiators and recipients can add attachments if allowed by their role. If allowed, routing package initiators also can remove attachments. Attachments are marked with your name, an attachment ID, the local date and time of addition, subject, data type, and file name. 1.5.5 Signatures Signatures are a password protected function that indicates your approval, disapproval, or acknowledgment regarding a routing package. The signature is associated with all nonrevisable attachments and the values of key data fields on a form that are present when a routing package is signed. If an attachment is subsequently removed or a key field value altered, the signature becomes invalid. 1-6 Overview Overview 1.5 Routing Packages When you sign a routing package, TeamRoute adds your name and the date and time. Recipients viewing signatures are shown which signatures are still valid. Overview 1-7 2 ________________________________________________________________ Preparing to Install TeamRoute for ALL-IN-1 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. TeamRoute provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 3.1. 2.1 Prerequisite Software You must have ALL-IN-1 Version 3.0-1 installed on your system before installing TeamRoute. The installation of TeamRoute on a coexistent ALL-IN-1 system is not supported. If you attempt to do so, the installation will fail. Because the TeamRoute for ALL-IN-1 installation updates the ALL-IN-1 forms and files, you must shut down ALL-IN-1 for the duration of the installation. You should plan to perform the installation at a time that causes the least inconvenience to the ALL-IN-1 users. See the ALL- IN-1 Management Guide for details on how to shut down ALL-IN-1. Preparing to Install TeamRoute for ALL-IN-1 2-1 Preparing to Install TeamRoute for ALL-IN-1 2.2 VMS License Management Facility 2.2 VMS License Management Facility The license registration information you need is contained in the Product Authorization Key (PAK). The PAK is a paper certificate that contains information about the license you need to run a particular piece of software. You must register and load your license for TeamRoute before you start the installation procedure. To register a license under VMS, first log into 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 License PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. A number of different licensing styles are available for TeamRoute. If you have a personal use license for TeamRoute, you must make sure that all users of TeamRoute are named when you register the license. Any user who is not named on the personal use license will not be able to send TeamRoute packages. For complete information on using LMF, see the VMS License Management Utility Manual. 2.3 Installation Procedure Requirements This section and those that follow discuss various requirements for installing TeamRoute. The installation takes approximately 60 to 90 minutes. 2.3.1 Checking the ALL-IN-1 Site Link Files The TeamRoute installation automatically adds information to the ALL-IN-1 site link files during the installation. TeamRoute expects to find these files in the directory OA$BUILD_LLV. Before you begin the installation, you should make sure that the following files are in the directory OA$BUILD_LLV: 2-2 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements o SITELINK30.COM o SITELLV.COM (if your ALL-IN-1 system is linked as a multilingual system) If no existing site link files are found in the OA$BUILD_ LLV directory, TeamRoute creates new files during the installation. Some other applications provide site link files in different directories. If no existing site link files are found in the OA$BUILD_LLV directory, check the locations of the site link files on your system as follows: $ DIR OA$BUILD:SITELINK30.COM $ DIR OA$BUILD:SITELLV.COM If versions of these files are in any directory other than OA$BUILD_LLV, check that the applications referred to in the files are currently integrated with your ALL-IN-1 system. If this is the case, move the files to OA$BUILD_ LLV. TeamRoute will automatically update the files during the installation. When you relink ALL-IN-1, you must set the default directory to OA$BUILD_LLV, as stated in the ALL-IN-1 Management Guide. This ensures that all applications on your system are linked. If your existing site link files are not in the OA$BUILD_ LLV directory, existing applications may not be included in the ALL-IN-1 relink during the TeamRoute installation. 2.3.2 Checking ALL-IN-1 Logicals If the ALL-IN-1 logical OA$MTI_TRNS is defined on your system, it must be set to 0 in order for TeamRoute to run correctly. To check the value of the logical, enter the following command: $ SHOW LOGICAL OA$MTI_TRNS If the value is 0, or if the logical is not defined on your system, take no further action. Preparing to Install TeamRoute for ALL-IN-1 2-3 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements If the logial is set to 1, it means that your ALL-IN-1 system is configured to force all mail, sent from your ALL-IN-1 system to a remote system, to be converted to ASCII text. Before you change the configuration of your ALL-IN-1 system, check the reasons why this configuration is being used. To change the value of the logical, use the following command: $ DEFINE/SYSTEM/EXECUTIVE OA$MTI_TRNS 0 2.3.3 Privileges To install TeamRoute, you must be logged in to an account that has SETPRV or at least the following privileges: o CMKRNL o WORLD o SYSPRV Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation. 2.3.4 Disk Space Requirements The following table shows the free disk storage space requirements (in blocks) for installing TeamRoute. These disk space requirements apply to both first time and upgrade installations. Table_2-1_Disk_Space_Requirements_________________________ Additional Language Device___________________Full_InstallationInstallation__ Kit Working Device 19000 7000 (continued on next page) 2-4 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements Table_2-1_(Cont.)_Disk_Space_Requirements_________________ Additional Language Device___________________Full_InstallationInstallation__ This disk space is needed during the installation and will be the system disk unless an alternate working device is used System Disk 1500 600 ALL-IN-1 Shared Library 10000 1000 Files This is the device that holds the directory which is pointed to by the logical OA$LIB_SHARE ALL-IN-1 Shared Data 2000 2000 Files This is the device that holds the directory which is pointed to by the logical OA$DATA_SHARE ALL-IN-1 Language Files 1000 1000 This is the device that holds the directory which is pointed to by the logical OA$LIB_lanaguage, where language is the language that you are installing TeamRoute files 8000 3000 This is the device specified during the installation______________________________________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: Preparing to Install TeamRoute for ALL-IN-1 2-5 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements $ SHOW DEVICE SYS$SYSDEVICE 2.3.5 System Parameters Installing TeamRoute requires certain system parameter settings. Table 2-2 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. Table_2-2_Minimum_Required_System_Parameter_Values________ System_Parameter___________Minimum_Value__________________ GBLPAGES[1] n + 1400 GBLSECTIONS[1] n + 10 [1]The_values_listed_for_these_system_parameters_represent the number of free global pages and global sections required for the installation, not the total number you need to run your system and other software. __________________________________________________________ The following sections show you how to: o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the VMS AUTOGEN command procedure 2.3.5.1 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run TeamRoute, you must have sufficient free global pages and global sections. You must first find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the GBLPAGES and GBLSECTIONS system parameters. The n + 1400 value for GBLPAGES and the n + 10 value for GBLSECTIONS in Table 2-2 indicate that you must have at least 1400 unused global pages and 10 unused global 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: 2-6 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements 1. Run the VMS Install Utility (INSTALL) using the following DCL command: $ INSTALL LIST /GLOBAL /SUMMARY The VMS 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 global pages (3420 in the example) is equal to or greater than 900. If the number of unused pages is less than 900, you need to increase the value for GBLPAGES. 3. Note the amount shown for Global Sections Used (258 in the example). 4. Run the System Generation Utility (SYSGEN) and use the SHOW command to determine how many global sections have been allocated. For example: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLSECTIONS 512 250 20 4095 Sections 5. Subtract the amount shown in the summary (258 in the example) from the amount allocated. If the difference is less than 15, you need to increase the value of the GBLSECTIONS parameter. Section 2.3.5.2 describes the procedures for increasing these values using AUTOGEN. Refer to the documentation for the VMS System Management Subkit for information on using AUTOGEN. Preparing to Install TeamRoute for ALL-IN-1 2-7 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements 2.3.5.2 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD_. The increase should be based on your system's needs. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 Note that when you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the documentation for the VMS System Management Subkit. 2-8 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements 2.3.6 Process Account Quotas The account you use to install TeamRoute must have suffi- cient quotas to enable you to perform the installation. Table 2-3 summarizes the process quotas required for the installation account. Table 2-3 Process Account Quotas for the Installing __________Account_________________________________________ Account_Quota____Value____________________________________ ASTLM 24 BIOLM 18 BYTLM 40,000 DIOLM 18 ENQLM 30 FILLM 20 PRCLM 8 WSDEF____________256______________________________________ User account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility (AUTHORIZE) 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 UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SYSTEM To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SYSTEM account and then exits from the utility: UAF> MODIFY SYSTEM /FILLM=50 UAF> EXIT Preparing to Install TeamRoute for ALL-IN-1 2-9 Preparing to Install TeamRoute for ALL-IN-1 2.3 Installation Procedure Requirements After you exit from the utility, the 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 documentation for the VMS System Management Subkit. 2.3.7 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks whether: o You are logged in to a privileged account o You have adequate quotas for installation o Any users are logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you 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. 2.3.8 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. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the documentation for the VMS System Management Subkit. 2-10 Preparing to Install TeamRoute for ALL-IN-1 3 ________________________________________________________________ Installing TeamRoute for ALL-IN-1 for the First Time This chapter tells you how to install TeamRoute for ALL-IN-1. In order to install TeamRoute for ALL-IN-1 Version 1.1, you must have ALL-IN-1 Version 3.0-1 installed on your system. If ALL-IN-1 Version 3.0-1 is not installed, the installation fails and a warning message is displayed. Upgrade your ALL-IN-1 system to Version 3.0-1, and restart the installation of TeamRoute for ALL-IN-1. 3.1 Installation The TeamRoute installation procedure consists of a series of questions and informational messages. To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, the installation procedure deletes all temporary files it has created up to that point and exits. You can then start the installation again. 1. Invoke VMSINSTAL. $ @SYS$UPDATE:VMSINSTAL TMRA1011 MTA0: OPTIONS N To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The following list defines the elements of the VMSINSTAL command line: saveset-name The installation name for the component. For TeamRoute, use the following installation name: TMRA1011 Installing TeamRoute for ALL-IN-1 for the First Time 3-1 Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation 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. 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 complete. OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. There are several other options you can select when you invoke VMSINSTAL. o Auto_answer option (A): Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). o Get save set option (G): Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L): Logs all activity to the terminal during installation. o Alternate root option (R): Lets you install the product to a system root other than that of the running system. See the VMS documentation on software installation in the VMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A,N). 3-2 Installing TeamRoute for ALL-IN-1 for the First Time Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation The following example invokes VMSINSTAL to install TeamRoute from tape drive MTA0: and shows the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL TMRA1011 MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.4 It is dd-mmm-yyyy at hh:mm. 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 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. 2. Confirm 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 RETURN. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 3. Mount the media. Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, TMRA1 MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: TMRA1 V1.1 Beginning installation of TMRA1 V1.1 at 20:01 %VMSINSTAL-I-RESTORE, Restoring product saveset A... Installing TeamRoute for ALL-IN-1 for the First Time 3-3 Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if 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 TeamRoute has been mounted on the specified device and that the installation has begun. If you entered the wrong device name 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. 4. Select a release notes option. If you specified OPTIONS N when you started the installation, VMSINSTAL asks a question on release notes. There are four options: 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 select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue: * Queue name [SYS$PRINT]: You can press RETURN to send the file to the default output print device or you can enter another queue name. 3-4 Installing TeamRoute for ALL-IN-1 for the First Time Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. Release notes are always copied to the system help directory when option 4 is selected. Select option 4 if you reviewed the release notes and are restarting the installation. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [NO]?: YES To continue the installation, enter YES. Otherwise, press RETURN. In either case, VMSINSTAL copies the release notes to a file in the SYS$HELP directory and displays the following message: %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. The release notes are moved to the following file: SYS$HELP:TMRA1011.RELEASE_NOTES 5. Specify installation type. You can select the type of installation you want to perform, as shown: This procedure supports the following installation paths :- (1) First full installation of TeamRoute for ALL-IN-1 (2) Installation of an additional TeamRoute language only (3) Upgrade installation of TeamRoute for ALL-IN-1 (4) Upgrade an additional TeamRoute language only To perform a full installation, type 1 and press RETURN, as shown: * What type of installation do you wish to perform: 1 If you choose a full installation of TeamRoute, the language of the TeamRoute kit that you are installing must be the same as the default language of your ALL-IN-1 system. You can only install a TeamRoute for ALL-IN-1 additional language on an ALL-IN-1 system which already has the language you propose to add installed. Installing TeamRoute for ALL-IN-1 for the First Time 3-5 Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation 6. Specify a unique UIC for the TMRA1SERVICE account. * Please enter a UIC for the TMRA1SERVICE account: Help to choose a UIC is available by typing a question mark (?). 7. Specify a default device for TMRA1SERVICE account and TeamRoute files. * Enter the device to accommodate TeamRoute for ALL-IN-1 files [USER1:]: 8. Specify the language of the installation. * Enter language code for this installation (2 Characters): TeamRoute for ALL-IN-1 installation supports the installation of multiple languages. Each TeamRoute for ALL-IN-1 kit consists of four language independent savesets and one language saveset. The name of the language component saveset includes the two character country code. So that the installation can build the language component saveset name, you are required to specify the language of your TeamRoute for ALL-IN-1 kit. For English, enter the country code EN. Help is available by typing a question mark (?). There is a special consideration for the British language version. Because there are no differences between the English language and British language versions of TeamRoute, if your ALL-IN-1 system is a British language version, you will have been supplied with an English language TeamRoute kit. In this situation, you need to specify EN in response to this question. However, the installation detects that your ALL-IN-1 system is a British language version, and installs the TeamRoute kit as a British language version. (Note that the TeamRoute language code EN is different from the language codes used for ALL-IN-1, which are GB or US.) 3-6 Installing TeamRoute for ALL-IN-1 for the First Time Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation 9. Register a Product Authorization Key (PAK). * Does this product have an authorization key registered and loaded? If you have registered your PAK for TeamRoute Version 1.1, enter YES and continue the installation. If you have not registered and loaded your PAK, you must do so before continuing the installation. Log in to another session and register the PAK. You can then continue with the installation by entering YES. 10.Specify a system batch queue. To start the TeamRoute Service Agent process, a startup procedure is submitted to a system batch queue. * On which batch queue do you want the startup to run [SYS$BATCH]: 11.Register all ALL-IN-1 users as TeamRoute users. * Do you want all ALL-IN-1 users to be registered as TeamRoute users [YES]? If you answer YES to this question, an automatic postinstallation script will run to populate the TeamRoute for ALL-IN-1 profile, using the existing accounts in your ALL-IN-1 profile file. All accounts will have their mail destination field updated to TMR. If you answer NO to this question, you can register individual users in the TeamRoute Profile using the Manage Accounts option on the TeamRoute System Management menu. See Section 6.1 for more information. After the installation is complete, please check the type of license your TeamRoute system has. Register your TMR subscribers with the License Management Facility (LMF) if necessary. Subscribers with any license can run TeamRoute, but if they only have a personal use license and they are not registered with LMF, all attempts to send a TeamRoute routing package will fail. 12.Answer ALL-IN-1 Link questions. Installing TeamRoute for ALL-IN-1 for the First Time 3-7 Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation The defaults to these questions are the answers that were given during the last relink of your ALL-IN-1 system. For more information about linking the ALL-IN-1 images, see the ALL-IN-1 Management Guide. The only ALL-IN-1 images that are linked are: o OA$MAIN o On multilingual systems, OA$LLVlanguage, where language is the language of the TeamRoute kit that is being installed, not the primary language. 13.Run the TeamRoute for ALL-IN-1 Installation Verification procedure. * Do you want to run the IVP after the installation [YES]? A TeamRoute IVP is available. It verifies that all TeamRoute files have been installed on your system. Digital recommends that you run the IVP. 14.Read 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. The installation then performs the following func- tions: o TeamRoute and TeamRoute Service Agent directories are created. o An ALL-IN-1 directory and associated files are created for the TeamRoute Service Agent. o ALL-IN-1 Help is updated to include help for TeamRoute. o TeamRoute code integrations are performed, by modifying various ALL-IN-1 files. (A full list of modified ALL-IN-1 files is found in Appendix B. o ALL-IN-1 is relinked. o ALL-IN-1 forms are updated. 3-8 Installing TeamRoute for ALL-IN-1 for the First Time Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation To successfully install TeamRoute for ALL-IN-1, it is necessary to update several ALL-IN-1 forms. If these forms have NOT already been customized by another application, the installation procedure will attempt to automatically provide them to your system's site area. However, if the installation procedure finds that the form is already customized, then it will be necessary to perform the update manually. See Chapter 5 if the installation procedure reports that a manual update is required. TeamRoute for ALL-IN-1 modifies forms MAIN, DEFAULT, SM$MAIN2 and SM_DEFAULT. (In previous versions of ALL- IN-1, form SM$MAIN2 was called SM2.) The installation will display one of the following messages for each of these forms: %TMRA1-I-NOCUSTOM, Form MAIN.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-W-CUSTOM, Form MAIN.FRM has already been modified and -TMRA1-W-CUSTOM, therefore cannot be automatically updated. -TMRA1-W-CUSTOM, Please see the installation guide for details -TMRA1-W-CUSTOM, of how to perform the update of this element -TMRA1-W-CUSTOM, manually. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories. The following message is displayed: %VMSINSTAL-I-MOVEFILES, Files will be moved to their target directories... 15.Automatic postinstallation procedures. When all files have been moved to their target directories the postinstallation phase will begin. The tasks performed during this phase are as follows: o Setting ownerships, protections and access control lists (ACLs) on TeamRoute files. o Running the TeamRoute for ALL-IN-1 startup procedure. o Compiling and installing the ALL-IN-1 custom application message file SITE$OA.A1$MSG to make TeamRoute messages available Installing TeamRoute for ALL-IN-1 for the First Time 3-9 Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation o Creating an ALL-IN-1 profile entry for the Service Agent. o Updating the ALL-IN-1 format data file with the MSG:TMR record for TeamRoute. o Populating the ALL-IN-1 elements data file with all the customizable TeamRoute for ALL-IN-1 elements. o Updating the ALL-IN-1 Customization Management data sets: CM$APP, CM$MAF, CM$AUTH$LOCATIONS, CM$FORM$LIBS, and CM$AUTH$USERS. Note that only MANAGER is added to the file CM$AUTH$USERS. o Updating the ALL-IN-1 customization management data sets to reflect the customization of forms MAIN, DEFAULT, SM$MAIN2 and SM_DEFAULT (this is done for each form based on whether the installation was able to automatically update the form or not). o Populating the TeamRoute for ALL-IN-1 profile with all ALL-IN-1 users. This procedure is conditional on the answer given to the installation question detailed in step 11. o Starting the Service Agent. When the automatic postinstallation procedures have completed, informational text is displayed to remind you of any manual postinstallation tasks that are necessary. If manual tasks are required, see Chapter 5. If the installation was unable to update the necessary ALL-IN-1 forms, the following message is displayed (this example shows that form MAIN requires a manual update): IMPORTANT ========= To complete the installation of TeamRoute for ALL-IN-1, it is necessary to perform the following manual tasks. Please refer to the section "After Installing TeamRoute" in the Installation Guide. Compile and install the ALL-IN-1 base text library (A1TXL.TXL) Please update form MAIN 3-10 Installing TeamRoute for ALL-IN-1 for the First Time Installing TeamRoute for ALL-IN-1 for the First Time 3.1 Installation If you chose not to register all ALL-IN-1 users in the TeamRoute for ALL-IN-1 profile, the following message is displayed: You chose not to register all existing ALL-IN-1 users as TeamRoute subscribers. Remember to register specific ALL-IN-1 TeamRoute users in the TeamRoute user profile. 16.Troubleshooting the IVP After the postinstallation phase is complete, the TeamRoute IVP runs. The IVP produces a log file SYS$TEST:TMRA1$IVP.LOG. If the IVP does not run successfully, investigate the problem by looking at this log file. If you want to run the IVP outside the installation, type the following command line from a privileged account. $ @SYS$TEST:TMRA1$IVP language In this command line, language is the language of your installed TeamRoute kit. 17.End the installation procedure. Installation of TMRA1 V1.1 completed at hh:mm VMSINSTAL procedure done at hh:mm The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss 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. Installing TeamRoute for ALL-IN-1 for the First Time 3-11 Installing TeamRoute for ALL-IN-1 for the First Time 3.2 Additional Language Installation 3.2 Additional Language Installation If your ALL-IN-1 system has additional languages installed, the TeamRoute for ALL-IN-1 installation procedure allows you to install TeamRoute for each additional language. To install an additional TeamRoute language, follow the instructions listed in Section 3.1. The installation of additional languages asks fewer questions and the process take less time. The following steps are different: o In step 5, choose installation type (2) o In step 12, during the ALL-IN-1 link questions, you are asked the following question: * Do you want these graphics copied to the ALL-IN-1 Library Directory [NO]:? Press to accept the default answer. Your answer to this question does not affect the installation. 3.3 Error Recovery If errors occur during the installation, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of TMRA1 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 VMS help library is currently in use. o The product license has not been registered and loaded. 3-12 Installing TeamRoute for ALL-IN-1 for the First Time Installing TeamRoute for ALL-IN-1 for the First Time 3.3 Error Recovery For descriptions of the error messages generated by these conditions, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, take the action described in the message. For information on installation requirements, see Chapter 2. Installing TeamRoute for ALL-IN-1 for the First Time 3-13 4 ________________________________________________________________ Upgrading from a Previous Version of TeamRoute for ALL-IN-1 If you have previously installed TeamRoute Version 1.0, you can upgrade your system to Version 1.1. This preserves the Service Agent account, the user profile, and (if they are defined) the logicals you used with V1.0. If you customized TeamRoute Version 1.0, you can preserve any customizations you made by following the instructions in Section 4.4. The following sections describe how to: o Prepare your system for upgrading o Upgrade your system to TeamRoute Version 1.1 o Upgrade any additional languages you may have installed o Upgrade manually any customizations you have made to Version 1.0 In order to upgrade to TeamRoute Version 1.1, you must have ALL-IN-1 Version 3.0-1 installed on your system. 4.1 Preparing to Upgrade TeamRoute Before you upgrade your system, read Chapter 2, which lists the prerequisite software and requirements for the installation. You should also read the online Release Notes before proceeding with the installation. Before you begin the upgrade installation, you should check that: o The TeamRoute logicals are defined If the TeamRoute logicals are not defined, the upgrade installation will fail. To define the logicals, follow the instructions in Section 4.1.2. Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4-1 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.1 Preparing to Upgrade TeamRoute o Your TeamRoute Version 1.0 system has not been customized. If your system has been customized, you must remove the customized elements manually before you begin the installation, and then restore them when the installation is complete. (Please note that this refers only to elements of the TeamRoute system that have been customized: these have the prefix TMR. It does not refer to any ALL-IN-1 elements that may have been customized.) See Section 4.4.1 and Section 4.4.2 for instructions on how to do this. If your TeamRoute Version 1.0 system was cus- tomized, follow the instructions in Section 4.4.1 before you begin the upgrade. Otherwise, your customizations may interfere with the correct functioning of Version 1.1 of the product. 4.1.1 Updating the A1V30SITE_START.COM, SITELINK30 and SITELLV Files For TeamRoute Version 1.0, lines were added by TeamRoute to the following files in ALL-IN-1 Version 2.4 o A1V24SITE_START.COM o SITELINK24 o SITELLV When you upgrade ALL-IN-1 to Version 3.0, you do not need to carry over the TeamRoute lines to the new versions of these files, A1V30SITE_START.COM, SITELINK30 and SITELLV as the installation of TeamRoute automatically adds the appropriate lines to these files. If you have already carried over the TeamRoute lines to the new versions of the files, the TeamRoute Version 1.1 installation preserves the lines, so you do not need to change the files again. 4-2 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.1 Preparing to Upgrade TeamRoute 4.1.2 Defining the TeamRoute Logicals You should define the TeamRoute logicals before you begin the upgrade installation, in case they have been deleted or corrupted. To define the logicals: 1. Type ALLIN1/USER=MANAGER and press . 2. View the ALL-IN-1 Version 2.4 site startup file. If you have renamed this file to A1V30_SITE_START, as described in the ALL-IN-1 documentation, type the following command: $ TYPE OA$SITE_BUILD_SHARE:A1V30_SITE_START.COM If you have not renamed the file, type the following command: $ TYPE OA$SITE_BUILD_SHARE:A1V24_SITE_START.COM Search the file for the line that is labeled as the TeamRoute Version 1.0 startup (this line may be different for each site): $!******************************** $!* Start TeamRoute for ALL-IN-1 * $!******************************** $ @SYS$STARTUP:TMRA1$STARTUP USER1:[TMRASERVICE] SHARE SYS$BATCH $! 3. Run the line to start up TeamRoute: $ @SYS$STARTUP:TMRA1$STARTUP USER1:[TMRASERVICE] SHARE SYS$BATCH 4.2 Upgrading your System to TeamRoute Version 1.1 To upgrade your system to TeamRoute Version 1.1, follow the instructions in Section 3.1. However, for step 5, choose installation type (3): (3) Upgrade installation of TeamRoute for ALL-IN-1 For an upgrade, the installation asks fewer questions. You will not be asked the questions in steps 6, 7, 10 and 11. Also, not all of the tasks described in steps 14 and 15 are performed by the installation. Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4-3 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.2 Upgrading your System to TeamRoute Version 1.1 During the installation, you will be asked whether you want to purge existing TeamRoute files. Digital recommends that you purge the files, to save disk space. Any data you supplied to TeamRoute will be preserved for use with TeamRoute Version 1.1. The upgrade installation installs the new TeamRoute files in the appropriate directories. The following information is preserved from Version 1.0: o All information relating to the Service Agent account o All information in the TeamRoute users' profile o All existing TeamRoute packages 4.3 Upgrading Additional Languages If your TeamRoute Version 1.0 system had additional languages installed, you should upgrade these when you upgrade your TeamRoute system. To upgrade an additional TeamRoute language, you must first upgrade your TeamRoute system, as described in Section 4.2. Then upgrade each additional language separately, by following the instructions listed in Section 3.1. However, for step 5, choose installation type (4): (4) Upgrade an additional TeamRoute language only 4.4 Upgrading your Customizations to TeamRoute Version 1.0 If your TeamRoute Version 1.0 has been customized, you must save the customizations manually, before you begin the upgrade installation. Then after the upgrade is complete, you can restore the customizations to your new Version 1.1 system. (Please note that this refers only to elements of the TeamRoute system that have been customized: these have the prefix TMR. It does not refer to any ALL-IN-1 elements that may have been customized.) 4-4 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.4 Upgrading your Customizations to TeamRoute Version 1.0 Section 4.4.1 describes how to save any existing customizations before the upgrade. It also describes how to check whether your system has been customized, if you are unsure. Section 4.4.2 describes how to restore the customizations to the new Version 1.1 system. 4.4.1 Removing your Customizations from Live Before an Upgrade Any TeamRoute element that has been customized must be removed from live and copied to a safe area before TeamRoute is installed. Due to changes to Customization Management in ALL-IN-1 Version 3.0, you cannot use CM to remove the existing customized elements. You must follow the procedures described in the following sections. 4.4.1.1 Files and Forms in the TeamRoute Site Directory for Primary Language To check for and save any customized files in the Site Directory for the Primary language, follow these steps: 1. At VMS level, set the default directory to the TeamRoute Site Directory: $ SET DEFAULT TMRA1$SITE_LIB_LLV 2. Do a directory listing to see which files have been customized: $ DIRECTORY SITETMRFLB.FLB;1 SITETMRMGR.FLB;1 TMR$CL_DISPLAY_ROLE_HELP.BLP;1 All files that are in Site Directory have been customized. In this example, the boilerplate TMR$CL_ DISPLAY_ROLE_HELP.BLP has been customized. 3. Rename any customized files to include the suffix _V1: $ RENAME TMR$CL_DISPLAY_ROLE_HELP.BLP TMR$CL_DISPLAY_ROLE_HELP_V1.BLP Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4-5 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.4 Upgrading your Customizations to TeamRoute Version 1.0 4. Find out which TeamRoute forms have been customized and moved to live: $ FMS/DIRECTORY SITETMRFLB Library USER1:[TMRA1SERVICE.SITE.LIB_ENGLISH]SITETMRFLB.FLB;2, created: 21-FEB-1992 12:01 Date and time of last modification: 14-OCT-1992 13:30 TMR$ARG$MAIN_MENU_COMMON TMR$MAIN$MENU All files that are listed have been customized. 5. Make a copy of the site directory, calling it SITETMRFLB_V1.FLB: $ COPY SITETMRFLB.FLB SITETMRFLB_V1.FLB 6. Delete the forms from the original form directory: $ FMS/LIBRARY/DELETE SITETMRFLB/form_name=TMR$ARG$MAIN_MENU_COMMON $ FMS/LIBRARY/DELETE SITETMRFLB/form_name=TMR$MAIN$MENU You must delete the existing forms to prevent TeamRoute Version 1.1 from using them in preference to the new Version 1.1 forms. Follow the same steps to save and delete forms in the management site form directory, SITETMRMGR.FLB. However, do not copy the form DEFAULT in the SITETMRMGR.FLB directory. 4.4.1.2 Files and Forms in the TeamRoute Site Directory for Secondary Language To save and delete the files and forms in the Site Directory for Secondary Languages, follow the steps given in Section 4.4.1.1 for the Primary Language area. However, for the first step, set the default directory to the Secondary Language area: $ SET DEFAULT TMRA1$SITE_LIB_language 4-6 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.4 Upgrading your Customizations to TeamRoute Version 1.0 4.4.1.3 Files in the TeamRoute Site Share Directory To rename the files in the Site Share Directory, follow the steps given in Section 4.4.1.1. However, for the first step, set the default directory to the Site Share Directory: $ SET DEFAULT TMRA1$SITE_LIB_SHARE 4.4.2 Restoring your Customizations on TeamRoute Version 1.1 After you have upgraded TeamRoute, restore your original customizations to the new Version 1.1 forms. Section 4.4.2.1 and Section 4.4.2.2 and describe how to restore the customizations to the forms and other files in the Site Directory for the Primary language. Section 4.4.2.3 describes the procedure for the forms and files in the Site Directory for Secondary languages. Section 4.4.2.4 describes the procedure for the forms and files in the Site Share Directory Appendix B lists the scripts and forms that have been deleted since TeamRoute Version 1.0. Any customizations you made to these elements in Version 1.0 cannot be used in Version 1.1. 4.4.2.1 Forms in the TeamRoute Site Directory for the Primary Language To incorporate customizations to the forms in the Site Directory for the Primary language, follow these steps: 1. Type ALLIN1/USER=MANAGER and press . 2. Type CM to enter customization management. 3. To create new entries in CM for the forms that you renamed in Section 4.4.1.1. Type C and press . Fill in the fields. Do not press . Make sure that you include the _V1 suffix in the name of the form. For example, to create a new entry to restore the customizations to the form TMR$MAIN$MENU, type: Element: TMR$MAIN$MENU_V1 Type: FRM Area: TMR_language Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4-7 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.4 Upgrading your Customizations to TeamRoute Version 1.0 where language is the name of the primary language you have installed. 4. Press Next Screen. This allows you to use existing elements as a template for the new form. Choose option A. Enter the name of the form, and the name of the Version 1.0 site directory, SITETMRFLB_ V1.FLB. You must enter the full directory specifica- tion, for example: Form name: TMR$MAIN$MENU_V1 Library: TMRA1$SITE_LIB_language:SITETMRFLB_V1.FLB 5. At the form editor menu, enter FORM at the Phase Choice field: Phase Choice: FORM Change the form name to include the suffix _V1. Enter EXIT to leave the form editor menu. Enter Y to save changes. The new element you have created is now identical to the customized element in Version 1.0. 6. Fill in the site modification log. 7. At the CM menu, select the P option. Select DIF, to compare the file you have created with equivalent base form in Version 1.1. 8. You are given a choice of which form components you wish to compare; select ND. Then at the next prompt, choose B: Site or Base (S/B)? B Fill in the Name: field with the name of the equivalent base form in Version 1.1, and press . This is the same as the new form you have created, but without the _V1 suffix, for example: Name: TMR$MAIN$MENU You are given a choice of which form component of the base form you wish to use. Enter ND again. 9. Fill in the print queue and press to print a hard copy of the differences between the two forms. 4-8 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.4 Upgrading your Customizations to TeamRoute Version 1.0 10.Repeat steps 7 through 9, However, in step 8, select IM instead of ND. 11.Repeat steps 7 through 9 again, This time, in step 8, select FV instead of ND. This will give you print-outs of all the differences between the new base form in Version 1.1, and the customized version of the same form in Version 1.0. Identify which of these differences are the result of customizations that were made to the form for Version 1.0. 12.At the CM menu, select ABE. Select the name of the new base form, for example, TMR$MAIN$MENU. Copy this element to the development area, using the CO option. 13.Using CM, select the form you have just moved to the development area. Edit the form to incorporate the changes listed in the three print-outs. When you have incorporated all the changes, move the form to the live area. 4.4.2.2 Boilerplate Files, Scripts, and Other Files in the TeamRoute Site Directory for Primary Language Follow the instructions in Section 4.4.2.1. The instruc- tions for files that are not forms are slightly different in the following steps: o Step 4: When you have selected option A, Type the name of the template file in the Filename: field, and press . When you have selected the file to use as a template, you are put into an editor to allow you to modify the new file you are creating. Exit the editor to save the file without making any changes. o Step 8: After you have selected DIF, you are given only one option, ET. Select this option. Ignore steps 10 through 11. Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4-9 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 4.4 Upgrading your Customizations to TeamRoute Version 1.0 4.4.2.3 Files and Forms in the TeamRoute Site Directory for Secondary Languages Follow the instructions in Section 4.4.2.1 and Section 4.4.2.2. The following steps are different: o In step 3, fill in the Area: field with the name of the TeamRoute secondary language area o In step 4, replace the Site Directory for the Primary language (TMRA1$SITE_LIB_LLV) with the the name of the Site Directory for the Secondary language that you are using 4.4.2.4 Files in the TeamRoute Site Share Directory Follow the instructions in Section 4.4.2.2. The following steps are different: o In step 3, fill in the Area: field with the name of the TeamRoute site share area o In step 4, replace the Site Directory for the Primary language (TMRA1$SITE_LIB_LLV) with the the name of the Site Share Directory 4-10 Upgrading from a Previous Version of TeamRoute for ALL-IN-1 5 ________________________________________________________________ After Installing TeamRoute After installing TeamRoute, you should complete the operations listed in the following steps: o If you were instructed to do so by the installation, update ALL-IN-1 forms to support TeamRoute o Compile and install the ALL-IN-1 text library 5.1 Updating ALL-IN-1 Forms to Support TeamRoute You should have a thorough working knowledge of ALL-IN-1 System Management and ALL-IN-1 Customization Management. If you have less experience, consult your ALL-IN-1 system manager before proceeding. 5.1.1 Updating Form MAIN If the installation reported that this form could not be updated automatically due to previous customization, you must add the TeamRoute changes manually. The rest of this section describes how to add the TMR option to form MAIN. If form MAIN is not appropriate for your environment, put the TMR option on another form (for example, on MAIN2), using the instructions in this section as a guide. 1. Type ALLIN1/USER=MANAGER and press . 2. Select CM to enter customization management. 3. Type SEL and press . After Installing TeamRoute 5-1 After Installing TeamRoute 5.1 Updating ALL-IN-1 Forms to Support TeamRoute Complete the fields as follows and press : Name: MAIN Type: FRM Language: ENGLISH (or the language of your TeamRoute kit if different) 4. Type E and press to edit the form. 5. Type S and press to edit the screen image. 6. Select LAYOUT and using the FMS editor add an option for TeamRoute, as shown: TMR TeamRoute 7. After the text, type 13 spaces then create a field of 30 characters in length. This will display the number of new TeamRoute routing packages. 8. Exit the layout by typing GOLD-7 to return to the Form Editor menu. 9. Type ASSIGN and press . Choose option 2 on the Assign Attributes To submenu. Assign the name TMR_COUNT to the new field. Mark the field as Display Only. 10.After you have assigned the field name, return to the Form Editor menu and type EXIT and press . 11.Confirm that you want to save the form by typing Y in answer to the following prompt: Do you want to save this form? (Y/N) 12.Press when the message Press RETURN to continue appears. The Customization Management - Site Modification Log form appears. Complete the fields as you wish and press . 13.Select E to edit the form. 14.Select ND to edit the form's named data Update the named data on the form with the following information (the bolded text indicates new named data): 5-2 After Installing TeamRoute After Installing TeamRoute 5.1 Updating ALL-IN-1 Forms to Support TeamRoute ;;.TYPE;; MENU /USER=USER/TITLE=TITLE/MAIL=MAIL/CHOICE=CHOICE/DATE=DATE/MORE='MAIN2' /CLEAR/GET=DAY,OA$DAY;MEETIN,OA$MEETING_COUNT_DISPLAY/HARD=OA$_MAIN_HRD_MAIN /GET=TMR_COUNT,OA$TMR$COUNT_DISPLAY/PRE="DO TMR$CL_OPEN_LIBRARY" ;;OA$_TMR_MO_TEAMROUTE;; FORM TMR$MAIN$MENU 15.Exit the editor. 16.Select MLA to move the MAIN form to the live area. If the MAIN form has already been modified, the following message is displayed: Element is already live - still copy? [Y/N] Select Y. In response, the following message is displayed: Element marked for moving to the live area 17.Select AM to enter the ALL-IN-1 Application Maintainer menu. 18.Select PME to enter the Process Marked Elements form. 19.Select ML to move the MAIN form to the live area. The following message appears: Element moved to live 20.Press . A warning message appears stating that you have changed a form in SITEOAFORM.FLB, and advising you to select the PCF (Precompile a form library) option. 21.Press . 22.Select PCF to precompile the form library. 23.Type the following and press : OA$SITE_LIB_ENGLISH:SITEOAFORM.FLB The following message appears: Do you want to install the new .FLC [Y/N] After Installing TeamRoute 5-3 After Installing TeamRoute 5.1 Updating ALL-IN-1 Forms to Support TeamRoute 24.Select Y. The following message appears: OA$SITE_LIB_ENGLISH:SITEOAFORM.FLB precompiled and installed The modified form is now available to users entering ALL-IN-1. 5.1.2 Updating Form DEFAULT See Section 5.1.1. Follow the instructions in steps 1 through 3 to select form DEFAULT for editing. Then, follow the instructions in steps 13 through 24. For step 14, add the following named data after the line with the word MENU. ;;OA$_TMR_MO_TEAMROUTE;; DO TMR$CL_OPEN_LIBRARY\FORM TMR$MAIN$MENU 5.1.3 Updating Forms SM$MAIN2 and SM_DEFAULT See Section 5.1.1. Follow the instructions in steps 1 through 6 to select form SM$MAIN2 for editing and add the TeamRoute management option to the screen image, as shown: MTS Manage TeamRoute system Follow the instructions in steps 10 through 16. For step 14, add the following named data at the end: ;;OA$_TMR_MO_MTS;; DO TMRA1$LIB:TMR$SM_OPENLIB\FORM TMR$SM$MTS$MENU Next, you must move the form SM_DEFAULT to the live area, without editing it. The form SM_DEFAULT does not have to be modified, but does need to be moved to the live area because it is referenced by form SM$MAIN2. To do this, select the form by following steps 1 through 3, then follow the instructions in step 16. (If the form is already in the live area, you do not need to move it.) Once you have marked all of the necessary forms for moving to the live area, complete the operation by following the instructions in steps 17 through 24. In steps 20 through 24, the form library SITEMANAGER is used instead of SITEOAFORM. So for step 23, type the following and press : 5-4 After Installing TeamRoute After Installing TeamRoute 5.1 Updating ALL-IN-1 Forms to Support TeamRoute OA$SITE_LIB_ENGLISH:SITEMANAGER.FLB 5.2 Compiling and Installing the ALL-IN-1 Text Library (A1TXL.TXL) Before TeamRoute can be run, you must place some of the TeamRoute script and boilerplate files into the ALL-IN-1 text library, A1TXL.TXL. 1. Type ALLIN1/USER=MANAGER and press . 2. Select MGT to enter system management. 3. Select CSZ to enter the System Customization Management menu. 4. Select CTX to compile the text library. You are asked to confirm this. Press to confirm. 5.3 Determining and Reporting Problems If you encounter a problem while using TeamRoute, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Reader's Comments form if the problem has to do with the TeamRoute documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. After Installing TeamRoute 5-5 6 ________________________________________________________________ Managing TeamRoute Services This chapter explains how to manage TeamRoute services. To begin this process, follow these steps: 1. Install the product on your system. 2. Log in to the ALL-IN-1 manager account or an account with the necessary privileges. You must have ALL-IN-1 manager privileges to manage TeamRoute services. 3. Enter MGT to display the ALL-IN-1 Management menu. 4. Enter MTS (Manage TeamRoute system) from the ALL-IN-1 Management menu. TeamRoute displays its system management menu, as shown in Figure 6-1. Figure 6-1 TeamRoute System Management Menu __________________________________________________________________ TeamRoute System Management MAC Manage accounts MSA Manage Service Agents MAR Manage application registration _________________________________________________________________ 5. Select an option. The following sections discuss these options. Managing TeamRoute Services 6-1 Managing TeamRoute Services 6.1 Managing TeamRoute Accounts 6.1 Managing TeamRoute Accounts You register ALL-IN-1 users as TeamRoute subscribers by adding an entry for each subscriber in the TeamRoute profile file. A profile record consists of the following fields: o ALL-IN-1 account name o Date you registered the subscriber o Date you modified the entry o Enabled flag To add or modify subscriber registrations, select the MAC (Manage Accounts) option from the TeamRoute System Management menu. TeamRoute displays the Manage TeamRoute User Accounts menu, as show in Figure 6-2: Figure 6-2 Manage TeamRoute User Accounts Menu ____________________________________________________________________ Manage TeamRoute User Accounts SEL Select Account: SMITH C Create E Edit D Delete ENA Enable TMR account P Print DIS Disable TMR account R Read I Index RI Recall index RTS Recreate TMR_SUBSCRIBERS ____________________________________________________________________ 6-2 Managing TeamRoute Services Managing TeamRoute Services 6.1 Managing TeamRoute Accounts Table 6-1 describes the options available on the Manage TeamRoute User Accounts menu. Managing TeamRoute Services 6-3 Managing TeamRoute Services 6.1 Managing TeamRoute Accounts Table_6-1_Manage_TeamRoute_User_Accounts_Menu_Options_____ Option_Description________________________________________ SEL Displays the Account Selection screen, prompting you for a subscriber name. If you press the FIND key, a list of all registered subscribers is displayed. C Displays the TeamRoute Profile file entry screen, which prompts you for the TeamRoute account name and the value of the account enabled flag. The account name and the account enabled flag are mandatory. The account name must be a valid ALL-IN-1 username. The account enabled flag can have a value of Y or N. The TeamRoute account name field has a maximum of 30 characters and the account enabled flag field has a maximum of 1 character. You can create multiple TeamRoute accounts. Press EXIT (the key) when finished. When you create a new TeamRoute account, the mail destination field of the associated ALL-IN-1 account is updated to TMR. E Displays the TeamRoute profile file entry screen for the current record. If there is no current record, you must use SEL from the MAC menu to select a record. You can modify only the account enabled flag. To change the TeamRoute account name, you must delete the record. D Displays the TeamRoute profile file entry screen for the current record and erases the current record. If there is no current record, you must use SEL from the MAC menu to selection a record. A message requests that you press to confirm the deletion. Press EXIT if you choose not to delete the current record. P Prints the complete TeamRoute profile file using the default printer, unless you specify otherwise in the ALL-IN-1 print selection screen that TeamRoute displays. R Displays a read-only version of the TeamRoute Account record entry screen for the current TeamRoute account. I Displays an Account name selection screen. If you 6-4 Managing pressoiwithout a value in the account name field, all TeamRoute account records are displayed. If you enter an account name, only that record is displayed. See Section 6.1.1 for more information. RI Displays the last selected index listing of TeamRoute accounts. ENA Enables the current TeamRoute account. DIS Disables the current TeamRoute account. RTS Creates a new TMR_SUBSCRIBERS system distribution _______list.______________________________________________ Managing TeamRoute Services 6.1 Managing TeamRoute Accounts 6.1.1 Using the TeamRoute Account Index and Menu The Index of TeamRoute Accounts displays the following information: o TeamRoute Account name o Date you added the account o Date you modified the account o Account enabled flag You can use the and keys, and up and down arrow keys to move in the scrolled display. The key allows you to read the current selected record. Use the key or the up and down arrows keys to select a record. Use the key to display the Index menu, which is shown in Figure 6-3. Figure 6-3 Manage TeamRoute Account Index Menu __________________________________________________________________ Index Menu C Create ENA Enable E Edit DIS Disable D Delete P Print ALL Select all R Read CAS Cancel all selected XP Multiple print XD Multiple delete __________________________________________________________________ Managing TeamRoute Services 6-5 Managing TeamRoute Services 6.1 Managing TeamRoute Accounts Table 6-2 describes the options available on the Manage TeamRoute Account Index menu. Table_6-2_Manage_TeamRoute_Account_Index_Menu_Options_____ Option________Description_________________________________ C,E,D,P,R Functions the same as on the Manage TeamRoute Application Registration File menu (see Table 6-4) on the record that is currently marked with a > in the index (not the record selected with an X). Use the arrow keys to scroll the > pointer. Full field values are displayed. ENA Enables all selected account records. DIS Disables all selected account records. ALL Selects all account records. CAS Cancels all selected account records. XP Prints all selected account records (not the one marked with the pointer, unless it is selected with an x). XD____________Deletes_all_selected_account_records._______ 6.2 Managing the Service Agent To manage the service agent, select the MSA option from the Manage TeamRoute menu. TeamRoute displays the Manage Service Agents menu, as shown in Figure 6-4. 6-6 Managing TeamRoute Services Managing TeamRoute Services 6.2 Managing the Service Agent Figure 6-4 TeamRoute Manage Service Agents Menu ------------------------------------------------------------------ Bob Smith 30-Dec-1991 Manage Service Agents Account Name: TMRA1SA1 SEL Select Number: 001 Date Started: 30-DEC-1991 11:19 P Print Previous Date: 24-DEC-1991 14:52 R Read Wait Interval: 00:01:00 Status: STOP PENDING ST Start Service Agent RL Read log file SU Suspend Service Agent PL Print log file RE Resume Service Agent RT Read transaction file SP Stop Service Agent PT Print transaction file SW Set wait interval SLF Switch log file SR Set rollover value STF Switch transaction file Enter option and press RETURN ----------------------------------------------------------------------- Table 6-3 describes the options available on the Manage Service Agents menu. Table_6-3_Manage_Service_Agents_Menu_Options______________ Option_Description________________________________________ SEL Displays the Select Service Agent Account screen with which you can enter a name. If you press the Find key, the TMRA1SA1 service agent is selected. P Prints the current values in the service agent control file using the default printer, unless you specify otherwise in the ALL-IN-1 print selection screen that appears. (continued on next page) Managing TeamRoute Services 6-7 Managing TeamRoute Services 6.2 Managing the Service Agent Table_6-3_(Cont.)_Manage_Service_Agents_Menu_Options______ Option_Description________________________________________ R Displays a read-only list of the current values in the service agent control file. Press to exit this screen. ST Starts the service agent and changes its status to RUN PENDING. When the service agent actually starts, the status is updated to RUNNING. SU Suspends the service agent and changes its status to SUSPEND PENDING. When the service agent actually suspends, the status is updated to SUSPENDED. This command causes the service agent to exit ALL-IN-1, but remain in the detatched process. Requests can be sent to the service agent, but they are not processed until you resume it. RE Resumes the service agent and changes its status to RUN PENDING. When the service agent actually resumes, the status is updated to RUNNING. The service agent logs back into the ALL-IN-1 account and continues to process requests. SP Requests that the service agent stop and changes its status to STOP PENDING. When the service agent actually stops the status is updated to STOPPED. SW Displays a list of the current values in the service agent control file. You can edit the wait interval (see Section 6.2.1). Press to exit this screen. SR Sets the rollover value (in blocks) for the transaction file. The default value is 600 blocks. RL Displays the log file. Use the Next Screen and Prev Screen keys to scroll. See Section 6.2.2 for more information. PL Prints the log file. (continued on next page) 6-8 Managing TeamRoute Services Managing TeamRoute Services 6.2 Managing the Service Agent Table_6-3_(Cont.)_Manage_Service_Agents_Menu_Options______ Option_Description________________________________________ RT Displays the transaction file. Use the Next Screen and Prev Screen keys to scroll. See Section 6.2.3 for more information. PT Prints the transaction file. SLF Closes the current log file and renames it and all logs files with the same name to TMRA1$SA_ LOG:TMRA1SA1.LOG_timestamp. The value for timestamp is the time stamp for the file, for example, 1992021310393560 (10:39:35.60 hours on 13 February 1992). More than one log file with the name TMRA1SA1.LOG can exist if a new log file was started due to conflicting access. A conflict can occur if the log file is read through ALL-IN-1 and an ALL-IN-1 script attempts to write to the log file at the same time. In this situation, a new log file is created. A conflict also can occur if the log file is accessed by a command procedure. The command procedure attempts to access the log file five times, pausing five minutes between attempts. If the log file cannot be accessed after five attempts, a new log file is created. (continued on next page) Managing TeamRoute Services 6-9 Managing TeamRoute Services 6.2 Managing the Service Agent Table_6-3_(Cont.)_Manage_Service_Agents_Menu_Options______ Option_Description________________________________________ STF Closes the current transaction file and renames it and all transaction files with the same name to TMRA1$SA_DATA:TMR$SA_TRANSACTION.DAT_timestamp. The value for timestamp is the time stamp for the file, for example, 1992021310393560 (10:39:35.60 hours on 13 February 1992). More than one transaction file with the name TMR$SA_ TRANSACTION.DAT can exist if a new transaction file was started due to conflicting access. A conflict can occur if the transaction file is read through ALL-IN-1 and an ALL-IN-1 script attempts to write to the transaction file at the same time. In this _______situation,_a_new_transaction_file_is_created.______ 6.2.1 Setting the Wait Interval The service agent is a detached process that does not require a batch queue; therefore, it does not need to resubmit itself to run periodically. Instead, it hibernates for a defined period of time (a default wait interval of five minutes, or 00:05:00) when no requests are present. Additionally, when the service agent is suspended, it uses the wait interval to intermittently check for a changed status. You can reset the wait interval using the SW option. The wait interval has the form HH:MM:SS, with the following limits: o HH-Any number between 00 and 23 o MM and SS-Any number between 00 and 59 If the specified value is outside the limit, the wait interval defaults to 00:05:00. 6-10 Managing TeamRoute Services Managing TeamRoute Services 6.2 Managing the Service Agent 6.2.2 Using the Service Agent Log File The service agent maintains a log file that contains: o The times when the service agent is submitted, stopped, suspended, and started o Diagnostic messages By default, the log file is stored in a directory with the logical name TMRA1$SA_LOG. Its name is service_agent_ account_name.LOG. You can use the RL option or the following command to read the log file when the service agent is running or stopped: $ TYPE TMRA1$SA_LOG:service_agent_account_name_version.LOG The log file can grow large from successive executions. If needed, use the SLF option to start a new one. You then can copy the old file to another directory or delete it. To display lines longer than 80 characters while you are using the RL option, type WS (wide screen). To list other display options, press GOLD M from the RL screen. 6.2.3 Using the Service Agent Transaction File The service agent maintains a transaction file that contains information about its routine processing. By de- fault, the transaction file is stored in a directory with the logical name TMRA1$SA_DATA. The name of the transac- tion file is TMR$SA_TRANSACTION.DAT. You can use the RT option or the following command to read the transaction file whether the service agent is running or stopped: $ TYPE TMRA1$SA_DATA:TMR$SA_TRANSACTION.DAT The transaction file can grow large from successive executions. If needed, use the STF option to start a new one. You then can copy the old file to another directory or delete it. The service agent automatically rolls over the transaction file based on the value you specified through the SR option on the Manage Service Agents menu (see Table 6-3). Managing TeamRoute Services 6-11 Managing TeamRoute Services 6.2 Managing the Service Agent Records in a transaction file are formatted as a series of fields, some of fixed length and some of variable length. All fields are separated by a comma (,). The following example shows typical transaction records. 19911108202426,BR,BOB SMITH ,68963180,NODENM,001,,,TMR_FOLDER 004503,BOB SMITH 19911108202505,LC,BOB SMITH ,68963180,NODENM,001,,,7,7 8,SMITH,, [TMRA1SA1]SMITH 004504,BOB SMITH In this example, the text is wrapped to fit the manual page. To display lines longer than 80 characters while you are using the RT option, type WS (wide screen). To list other display options, press GOLD M from the RT screen. See Appendix D for more information on the transaction file. 6.2.4 Tracing Service Agent Activity If an error occurs repeatedly, it can be helpful to place the service agent in trace mode. This is done by following these steps: 1. Stop the service agent using the Manage Service Agents menu. 2. At the DCL level, enter the following command: $ DEFINE/SYSTEM/EXEC TMRA1$SATRACE "1" 3. Start the service agent using the Manage Service Agents menu. This starts the ALL-IN-1 tracing process. The trace file is located in the following file: [TMRA1SERVICE.SA.TMRA1SA1.A1]A1TRACE.LOG. It is important to turn off tracing after processing, because the trace file will become very large. To turn tracing off, follow these steps: 1. Stop the service agent using the Manage Service Agents menu. 2. At the DCL level, enter the following command: $ DEFINE/SYSTEM/EXEC TMRA1$SATRACE "0" 6-12 Managing TeamRoute Services Managing TeamRoute Services 6.2 Managing the Service Agent 3. Start the service agent using the Manage Service Agents menu. You cannot access the trace file until the service agent has been stopped. You may want to delete old trace files to conserve disk space. 6.3 Managing the Application Registration File The registration file determines which applications are available on the system for use by TeamRoute routing packages. It consists of a set of records, one record for each application. Each record has three fields: o Application name o Script file specification o One-line description (up to 60 alphanumeric characters) To register new applications or modify existing ones, select the MAR (Manage TeamRoute application registration) option from the TeamRoute System Management menu. TeamRoute displays the Manage TeamRoute Application Registration File menu, as shown in Figure 6-5. Figure 6-5 Manage TeamRoute Application Registration File Menu _________________________________________________________________ Manage TeamRoute Application Registration File SEL Select Application: TEAMFORM Description: Default if variables C Create Script: TMRA1$LIB:TMRA1$TEAMFORM.SCP E Edit D Delete P Print R Read I Index __________________________________________________________________ Managing TeamRoute Services 6-13 Managing TeamRoute Services 6.3 Managing the Application Registration File Table 6-4 describes the options available on the Manage TeamRoute Application Registration File menu. Table 6-4 Manage TeamRoute Application Registration File __________Menu_Options____________________________________ Option_Description________________________________________ SEL Displays the TeamRoute Application Registration File screen, prompting you for an application name. If you press the Find key, a list of all registered applications is displayed. C Displays the Application Definition screen, prompting you for the name, description, and script for the application you wish to register. Only the name is mandatory, and no two applications can share the same name. All three fields have a maximum of 60 characters. Press Exit when finished. E Displays the Application Definition screen for the current application record. You can modify all fields except the name. To change the name, you must delete the current record and create a new one. D Erases the current application record. A message asks you to press to confirm the deletion. Press Exit (KP0) instead if you choose not to delete the current record. P Prints the current application record using the default printer, unless you specify otherwise in the ALL-IN-1 print selection screen that appears. R Displays a read-only version of the Application Definition screen for the current application record. I Displays an application selection screen. If you then press , all application records are displayed. If you enter a name, only that record is _______displayed._See_Section_6.3.1_for_more_information._ 6-14 Managing TeamRoute Services Managing TeamRoute Services 6.3 Managing the Application Registration File 6.3.1 Using the Application Index and Menu The Index of Applications display may truncate long application records. The GOLD/F and GOLD/V commands are not available. However, you can use GOLD/M to display the Index menu, as shown in Figure 6-6. Figure 6-6 Index Menu _______________________________________________________ Index Menu C Create All Select all E Edit CAS Cancel all selected D Delete P Print XP Multiple print R Read XD Multiple delete ________________________________________________________ Table 6-5 describes the options available on the Manage TeamRoute Application Registration File Index menu. Table_6-5_Index_Menu_Options______________________________ Option___Description______________________________________ C,E,D,P,RFunctions the same as on the Manage TeamRoute Application Registration File menu (see Table 6-4) on the record that is currently marked with a > in the index (not the record selected with an X). Use the arrow keys to scroll the > pointer. Full field values are displayed. ALL Selects all application records. CAS Cancels all selected application records. XP Prints all selected application records (not the one marked with the pointer, unless it is selected with an x). XD_______Deletes_all_selected_application_records.________ Managing TeamRoute Services 6-15 Managing TeamRoute Services 6.4 Troubleshooting 6.4 Troubleshooting If there are TeamRoute routing packages that have been sent, but have not been received, check the following areas to determine the problem: 1. Find out if the service agent process is running. From the DCL prompt ($), type the following command to get a list of all processes on your system: $ SHOW SYSTEM/OUT=LIST.TXT Search the output file you created to see if the service agent process exists: $ SEARCH LIST.TXT "TMRA1$SA_1" You should see VMS process information similar to the following example displayed on your screen: 2020148B TMRA1$SA_1 HIB 2 194572 0 01:08:14.51 13273 2825 If the process TMRA1$SA_1 is not on the system, the process information will not display. This means the service agent process does not exist and has to be created by starting the service agent. Start the service agent using the TeamRoute Manage Service Agents menu (see Section 6.2). 2. Access the TeamRoute Manage Service Agent menu. Check the item block for the status of the service agent. If the status is STOPPED, start the service agent. 3. Check the mail destinations for the accounts that have not received TeamRoute routing packages. Use the ALL-IN-1 System Management Manage User Accounts menu. Check to see if the mail destination fields for the accounts are set to TMR. If not, update the fields to TMR (see the ALL-IN-1 Management Guide for more information). 4. Check that your ALL-IN-1 Sender and Fetcher are in a batch queue. Use the ALL-IN-1 Manage Messaging menu. Display the status by using choice DS. Check the queue SM MM DQ. Are there any messages to be sent? If so, select RS to run the sender. 6-16 Managing TeamRoute Services Managing TeamRoute Services 6.4 Troubleshooting 5. Use the following command to see if the logical TMRA1$SABATCH is assigned to an existing batch queue. $ SHOW LOGICAL TMRA1$SABATCH If there is no batch queue for TMRA1$SABATCH, create one, or reassign TMRA1$SABATCH to an existing batch queue. Managing TeamRoute Services 6-17 A ________________________________________________________________ Sample Installation This appendix contains three sample installation listings: o Installation of TeamRoute on a system for the first time o Upgrade installation of TeamRoute o Installation of an additional TeamRoute language In the following sample installations, no users are logged on to the system. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. The IVP runs at the end of each installation. A.1 Installation of TeamRoute on a System for the First Time The following script is an example installation where TeamRoute is installed on a system for the first time: VAX/VMS Software Product Installation Procedure V5.5 It is 14-JAN-1993 at 12:32. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: TMRA1 V1.1 Beginning installation of TMRA1 V1.1 at 12:32 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Sample Installation A-1 Sample Installation A.1 Installation of TeamRoute on a System for the First Time ************************************************************************ TMRA1 V1.1 Kit Installation Procedure Copyright (c) Digital Equipment Corporation. 1992. All Rights Reserved. ************************************************************************ This procedure supports the following installation paths :- (1) First full installation of TeamRoute for ALL-IN-1 (2) Installation of an additional TeamRoute language only (3) Upgrade installation of TeamRoute for ALL-IN-1 (4) Upgrade an additional TeamRoute language only * What type of installation do you wish to perform: 1 %TMRA1-I-FULL, This is a full installation of TeamRoute for ALL-IN-1. %TMRA1-I-CHECKS, Performing pre-installation checks... %TMRA1-I-CHKVMS, Checking your system's VMS version. %TMRA1-I-CHKSPA, Checking for sufficient free space on the kit working disk. %TMRA1-I-CHKGBL, Checking for sufficient free global pages and global sections. %TMRA1-I-CHKA1, Checking that ALL-IN-1 IOS is installed. %TMRA1-I-CHKLOG, Checking ALL-IN-1 logicals that this installation will use. %TMRA1-I-CHKSHT, Checking that ALL-IN-1 has been shutdown. To ensure that the TeamRoute for ALL-IN-1 Service Agent runs with the correct quotas, this installation procedure will create an account for the service agent. This account, TMRA1SERVICE, has no special privileges. * Please enter a UIC for the TMRA1SERVICE account: ? The UIC value, specified in octal, is a group and member number separated by a comma and enclosed in brackets. The group number must be in the range 1-37776 (octal), the member number in the range 0-1777776 (octal). Please ensure that the UIC you specify is not already in use on your system. You should NOT specify a group number in the system range (normally 1-10 octal). * Would you like to see the UICs presently in use on your system [NO]? * Please enter a UIC for the TMRA1SERVICE account: 200,202 * Enter the device to accommodate TeamRoute for ALL-IN-1 files: user2 A-2 Sample Installation Sample Installation A.1 Installation of TeamRoute on a System for the First Time %TMRA1-I-CHKQUO, Determining whether disk quotas enabled on USER2:... %TMRA1-I-QUOTOK, Disk quotas are not enabled. The installation will continue %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named TMRA1SERVICE. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier TMRA1SERVICE value: [000200,000202] added to rights data base %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named TMRA1SERVICE. %UAF-I-MDFYMSG, user record(s) updated %TMRA1-I-GRNTADMIN, Granting OA$ADMIN rights identifier to TMRA1SERVICE. %UAF-I-GRANTMSG, identifier OA$ADMIN granted to TMRA1SERVICE * Enter language code for this installation (2 Characters): ? Enter the two character (ISO 3166) standard language code that you wish this installation to use. The code you enter is used to construct the language saveset name used by the installation procedure. E.g. for ENGLISH you enter EN. The installation will then look for a language saveset called TMRA1LEN011.A * Enter language code for this installation (2 Characters): en %TMRA1LEN-I-RESLANG, Restoring the LANGUAGE saveset... %VMSINSTAL-I-RESTORE, Restoring product save set A ... %TMRA1-I-LANG, The language of this TeamRoute kit is ENGLISH. %TMRA1-I-CHKDSK, Checking disk space... %TMRA1-I-DSKSPA, Checking space on the ALL-IN-1 ENGLISH files disk. %TMRA1-I-DSKSPA, Checking space on the system disk. %TMRA1-I-DSKSPA, Checking space on the ALL-IN-1 shared data files disk. %TMRA1-I-DSKSPA, Checking space on the TeamRoute target disk. %TMRA1-I-DSKSPA, Checking free space on the ALL-IN-1 shared library files disk. Product: TMRA1-EN Producer: DEC Version: 1.1 Release Date: Sample Installation A-3 Sample Installation A.1 Installation of TeamRoute on a System for the First Time * Does this product have an authorization key registered and loaded? yes %TMRA1-I-CHKLIC, Checking TMRA1-EN licence is registered and loaded Access granted %TMRA1-I-RUNA1, Running ALL-IN-1 to obtain VMS account of ALL-IN-1 MANAGER... * Do you want all ALL-IN-1 users to be registered as TeamRoute users [YES]? %TMRA1-I-A1LNKQ, ALL-IN-1 link questions will now be asked. %TMRA1-I-SAVED_ANS_1, Default answers are being taken from saved answers file %TMRA1-I-SAVED_ANS_2, which was created on 10-JAN-1993 11:25:16.92 * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]? %TMRA1-I-DTRNOLINK, DATATRIEVE will not be linked with ALL-IN-1 * Do you want to link WPS-PLUS with ALL-IN-1 [NO]? %TMRA1-I-WPSNOLINK, The WPS-PLUS editor will not be linked with ALL-IN-1 * Do you want to integrate ACMS with ALL-IN-1 [NO]? %TMRA1-I-ACMSNOLINK, ACMS will not be linked with ALL-IN-1 * Do you want to build a MULTI-LANGUAGE system [YES]? %TMRA1-I-MLLINK, ALL-IN-1 will be linked as a multi-language system * Which date format do you require [1]: %TMRA1-I-DATEFORMAT, Date format DD-MMM-YYYY and MM/DD/YY (1) has been selected %TMRA1-I-NODDS, DDS support will not be included in the link %TMRA1-W-NOCDA, CDA support prerequisites not found, so ALL-IN-1 cannot link with it. %TMRA1-I-A1LNKQ, End of ALL-IN-1 link questions. * Do you want to run the IVP after the installation [YES]? All questions have now been completed. The installation will take another 30-60 minutes. %TMRA1-I-CREATDIR, Creating TMRA1SERVICE directory and subdirectories... %TMRA1-I-CREA1ACC, Creating ALL-IN-1 directories and files for the -TMRA1-I-CREA1ACC, TeamRoute SERVICE AGENT account... %TMRA1-I-GETA1FIL, Copying ALL-IN-1 user files from template directory. %TMRA1-I-CREA1DIR, Creating TMRA1SERVICE A1 and [.DOC#] directories. %TMRA1-I-INSTA1FI, Installing TMRA1SERVICE ALL-IN-1 files. A-4 Sample Installation Sample Installation A.1 Installation of TeamRoute on a System for the First Time %TMRA1-I-INSTLANG, Installing ENGLISH language specific files... %VMSINSTAL-I-RESTORE, Restoring product save set B ... %TMRA1-I-INSTCLFIL, Installing client files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %TMRA1-I-INSTSAFIL, Installing service agent and system management files... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %TMRA1-I-INSTCLFIL, Installing build files... %TMRA1-I-INSTEXEFIL, Installing executable files... %TMRA1-I-ADDHLP, Adding TeamRoute Help libraries to OAHELP... %TMRA1-I-ADDMSG, Adding TeamRoute messages to SITE$OA.A1$MSG... %TMRA1-I-RUNA1, Running ALL-IN-1 to define TeamRoute READ and WRITE special -TMRA1-I-RUNA1, symbols and also to add the TMR site defined function... %TMRA1-I-UPDOB, Updating ALL-IN-1 Object library SITEOALIBR.OLB... %TMRA1-I-A1LNK, Relinking ALL-IN-1 to include TeamRoute... Linking the OA$LLVENGLISH.EXE Building shared image modules Shared image modules built Linking the OA$MAIN image %TMRA1-I-LNKOK, The ALL-IN-1 link has completed successfully. To successfully install TeamRoute for ALL-IN-1, it is necessary to update several ALL-IN-1 forms. If these forms have NOT already been customized by another application, the installation procedure will attempt to automatically provide them to your system's site area. However, if the installation procedure finds that the form is already customized, then it will be necessary to perform the update manually. Please refer to the section "After Installing TeamRoute" in the Installation guide if the installation procedure reports that a manual update is required. %TMRA1-I-NOCUSTOM, Element MAIN.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-I-NOCUSTOM, Element DEFAULT.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-I-NOCUSTOM, Element SM$MAIN2.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-I-NOCUSTOM, Element SM_DEFAULT.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. Sample Installation A-5 Sample Installation A.1 Installation of TeamRoute on a System for the First Time %TMRA1-I-FRMUPD, Form MAIN will be updated in SITEOAFORM.FLB %TMRA1-I-FRMUPD, Form DEFAULT will be updated in SITEOAFORM.FLB %TMRA1-I-FRMUPD, Form SM$MAIN2 will be updated in SITEMANAGER.FLB %TMRA1-I-FRMUPD, Form SM_DEFAULT will be updated in SITEMANAGER.FLB %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ************************************************************** * Automatic Postinstallation tasks will now be performed * ************************************************************** %TMRA1-I-SETACL, Setting ownership ACLs on TeamRoute development files... %TMRA1-I-START, Defining TeamRoute for ALL-IN-1 logicals... ================================================= Running startup for TeamRoute V1.1 for ALL-IN-1 ================================================= Installing TeamRoute images Defining TeamRoute language independent logical names Defining TeamRoute ENGLISH language logical names %OA-I-LASTLINE, ALL-IN-1 Running to compile and install site application - %OA-I-LASTLINE, message file to include TeamRoute message symbols... %OA-I-CMPFILE, Processing USER2:[ALLIN1_ENGLISH.SITE.SOURCES_ENGLISH] SITE$OA.A1$MSG;11 %OA-I-CMPSTS, 896 symbols used, 0 duplicates %OA-I-CMPEND, Symbols total: 896 symbols, Section file 53908 bytes long SYSTEM finished using ALL-IN-1 at 14-Jan-1993 13:25 %OA-I-LASTLINE, ALL-IN-1 Running to compile and install - %OA-I-LASTLINE, ENGLISH TeamRoute form libraries... %OA-I-LASTLINE, Compiling TMRA1$LIB_LLV:TMRFLB... %OA-I-LASTLINE, Compiling TMRA1$LIB_LLV:TMRMGR... SYSTEM finished using ALL-IN-1 at 14-Jan-1993 13:25 %OA-I-LASTLINE, ALL-IN-1 Running... %OA-I-LASTLINE, Creating profile entry for TeamRoute Service Agent... %OA-I-LASTLINE, Creating MSG:TMR record in FORMAT data file... %OA-I-LASTLINE, Updating CM$SDC.DAT with new SHARE elements... A-6 Sample Installation Sample Installation A.1 Installation of TeamRoute on a System for the First Time SYSTEM finished using ALL-IN-1 at 14-Jan-1993 13:26 %OA-I-LASTLINE, ALL-IN-1 Running... %OA-I-LASTLINE, Updating CM$SDC.DAT with new ENGLISH elements... %OA-I-LASTLINE, Updating ALL-IN-1 CM data sets... %OA-I-LASTLINE, "Compiling and installing OA$SITE_LIB_ENGLISH:SITEOAFORM" %OA-I-LASTLINE, "Compiling and installing OA$SITE_LIB_ENGLISH:SITEMANAGER" %OA-I-LASTLINE, Defining Customization Management logicals... SYSTEM finished using ALL-IN-1 at 14-Jan-1993 13:27 %OA-I-LASTLINE, ALL-IN-1 Running to populate the TeamRoute profile... SYSTEM finished using ALL-IN-1 at 14-Jan-1993 13:28 Starting the TeamRoute Service Agent... ************************************************************** * The Installation of TeamRoute for ALL-IN-1 has completed. * ************************************************************** ************************************************************** * Running the TMRA1 Installation Verification Procedure. * ************************************************************** The IVP has completed successfully See log file SYS$TEST:TMRA1$IVP.LOG for details Installation of TMRA1 V1.1 completed at 13:28 VMSINSTAL procedure done at 13:29 Sample Installation A-7 Sample Installation A.2 Upgrade Installation of TeamRoute A.2 Upgrade Installation of TeamRoute The following example script shows an upgrade installation from TeamRoute Version 1.0 to TeamRoute Version1.1: VAX/VMS Software Product Installation Procedure V5.5 It is 14-JAN-1993 at 16:48. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: TMRA1 V1.1 Beginning installation of TMRA1 V1.1 at 16:48 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ******************************************************************** TMRA1 V1.1 Kit Installation Procedure Copyright (c) Digital Equipment Corporation. 1992. All Rights Reserved. ********************************************************************* This procedure supports the following installation paths :- (1) First full installation of TeamRoute for ALL-IN-1 (2) Installation of an additional TeamRoute language only (3) Upgrade installation of TeamRoute for ALL-IN-1 (4) Upgrade an additional TeamRoute language only * What type of installation do you wish to perform: 3 %TMRA1-I-FULLUPG, This is an upgrade installation of TeamRoute for ALL-IN-1. A-8 Sample Installation Sample Installation A.2 Upgrade Installation of TeamRoute %TMRA1-I-CHECKS, Performing pre-installation checks... %TMRA1-I-CHKVMS, Checking your system's VMS version. %TMRA1-I-CHKSPA, Checking for sufficient free space on the kit working disk. %TMRA1-I-CHKGBL, Checking for sufficient free global pages and global sections. %TMRA1-I-CHKA1, Checking that ALL-IN-1 IOS is installed. %TMRA1-I-CHKLOG, Checking ALL-IN-1 logicals that this installation will use. %TMRA1-I-CHKSHT, Checking that ALL-IN-1 has been shutdown. %TMRA1-I-STOPSA, TeamRoute has previously been installed. Running -TMRA1-I-STOPSA, TMR$SM_STOP_SERVICE_AGENT to stop the Service Agent. * Enter language code for this installation (2 Characters): en %TMRA1LEN-I-RESLANG, Restoring the LANGUAGE saveset... %VMSINSTAL-I-RESTORE, Restoring product save set A ... %TMRA1-I-LANG, The language of this TeamRoute kit is ENGLISH. %TMRA1-I-CHKDSK, Checking disk space... %TMRA1-I-DSKSPA, Checking space on the ALL-IN-1 ENGLISH files disk. %TMRA1-I-DSKSPA, Checking space on the system disk. %TMRA1-I-DSKSPA, Checking space on the ALL-IN-1 shared data files disk. %TMRA1-I-DSKSPA, Checking space on the TeamRoute target disk. %TMRA1-I-DSKSPA, Checking free space on the ALL-IN-1 shared library files disk. Product: TMRA1-EN Producer: DEC Version: 1.1 Release Date: * Does this product have an authorization key registered and loaded? y %TMRA1-I-CHKLIC, Checking TMRA1-EN licence is registered and loaded Access granted %TMRA1-I-RUNA1, Running ALL-IN-1 to obtain VMS account of ALL-IN-1 MANAGER... %TMRA1-I-A1LNKQ, ALL-IN-1 link questions will now be asked. Sample Installation A-9 Sample Installation A.2 Upgrade Installation of TeamRoute %TMRA1-I-SAVED_ANS_1, Default answers are being taken from saved answers file %TMRA1-I-SAVED_ANS_2, which was created on 14-JAN-1993 12:48:52.46 * Do you want to integrate DATATRIEVE with ALL-IN-1 [NO]? %TMRA1-I-DTRNOLINK, DATATRIEVE will not be linked with ALL-IN-1 * Do you want to link WPS-PLUS with ALL-IN-1 [NO]? %TMRA1-I-WPSNOLINK, The WPS-PLUS editor will not be linked with ALL-IN-1 * Do you want to integrate ACMS with ALL-IN-1 [NO]? %TMRA1-I-ACMSNOLINK, ACMS will not be linked with ALL-IN-1 * Do you want to build a MULTI-LANGUAGE system [YES]? %TMRA1-I-MLLINK, ALL-IN-1 will be linked as a multi-language system * Which date format do you require [1]: %TMRA1-I-DATEFORMAT, Date format DD-MMM-YYYY and MM/DD/YY (1) has been selected %TMRA1-I-NODDS, DDS support will not be included in the link %TMRA1-W-NOCDA, CDA support prerequisites not found, so ALL-IN-1 cannot link with it. %TMRA1-I-A1LNKQ, End of ALL-IN-1 link questions. * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? All questions have now been completed. The installation will take another 30-60 minutes. A-10 Sample Installation Sample Installation A.2 Upgrade Installation of TeamRoute %TMRA1-I-CHECKDIR, Checking TMRA1SERVICE directory and subdirectories... %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.BLP_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SOURCES_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.DATA_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.DO_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.LIB_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SCP_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.DUMP_AREA] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.LOG] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.BLP_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.SOURCES_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DATA_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_TMR_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DO_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.LIB_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.SCP_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_SHARE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_SHARE.SCP] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_SHARE.BLP] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_SHARE.COM] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_SHARE.DO] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_SHARE.FDL] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SA] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SA.CODE] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SA.DATA] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SA.LOG] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.BLP_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SOURCES_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.DATA_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.DO_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.LIB_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SCP_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.BLP_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.SOURCES_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DATA_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DO_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.LIB_ENGLISH] already exists Sample Installation A-11 Sample Installation A.2 Upgrade Installation of TeamRoute %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.SCP_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_TMR_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_ENGLISH] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_ENGLISH.SCP] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_ENGLISH.BLP] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_ENGLISH.COM] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_ENGLISH.DO] already exists %CREATE-I-EXISTS, USER2:[TMRA1SERVICE.SITE.DEV_REC_TMR_ENGLISH.FRM] already exists %TMRA1-I-INSTLANG, Installing ENGLISH language specific files... %VMSINSTAL-I-RESTORE, Restoring product save set B ... %TMRA1-I-INSTCLFIL, Installing client files... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %TMRA1-I-INSTSAFIL, Installing service agent and system management files... %VMSINSTAL-I-RESTORE, Restoring product save set D ... %TMRA1-I-INSTCLFIL, Installing build files... %TMRA1-I-INSTEXEFIL, Installing executable files... %TMRA1-I-ADDHLP, Adding TeamRoute Help libraries to OAHELP... %TMRA1-I-ADDMSG, Adding TeamRoute messages to SITE$OA.A1$MSG... %TMRA1-I-RUNA1, Running ALL-IN-1 to define TeamRoute READ and WRITE special -TMRA1-I-RUNA1, symbols and also to add the TMR site defined function... %TMRA1-I-UPDOB, Updating ALL-IN-1 Object library SITEOALIBR.OLB... %TMRA1-I-A1LNK, Relinking ALL-IN-1 to include TeamRoute... Linking the OA$LLVENGLISH.EXE Building shared image modules Shared image modules built Linking the OA$MAIN image %TMRA1-I-LNKOK, The ALL-IN-1 link has completed successfully. To successfully install TeamRoute for ALL-IN-1, it is necessary to update several ALL-IN-1 forms. If these forms have NOT already been customized by another application, the installation procedure will attempt to automatically provide them to your system's site area. However, if the installation procedure finds that the form is already customized, then it will be necessary to perform the update manually. A-12 Sample Installation Sample Installation A.2 Upgrade Installation of TeamRoute Please refer to the section "After Installing TeamRoute" in the Installation guide if the installation procedure reports that a manual update is required. %TMRA1-W-CUSTOM, Form MAIN.FRM has already been modified and -TMRA1-W-CUSTOM, therefore cannot be automatically updated. -TMRA1-W-CUSTOM, Please see the installation guide for details of how to -TMRA1-W-CUSTOM, perform the update of this element manually. %TMRA1-W-CUSTOM, Form DEFAULT.FRM has already been modified and -TMRA1-W-CUSTOM, therefore cannot be automatically updated. -TMRA1-W-CUSTOM, Please see the installation guide for details of how to -TMRA1-W-CUSTOM, perform the update of this element manually. %TMRA1-W-CUSTOM, Form SM$MAIN2.FRM has already been modified and -TMRA1-W-CUSTOM, therefore cannot be automatically updated. -TMRA1-W-CUSTOM, Please see the installation guide for details of how to -TMRA1-W-CUSTOM, perform the update of this element manually. %TMRA1-W-CUSTOM, Form SM_DEFAULT.FRM has already been modified and -TMRA1-W-CUSTOM, therefore cannot be automatically updated. -TMRA1-W-CUSTOM, Please see the installation guide for details of how to TMRA1-W-CUSTOM, perform the update of this element manually. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ************************************************************** * Automatic Postinstallation tasks will now be performed * ************************************************************** %TMRA1-I-SETACL, Setting ownership ACLs on TeamRoute development files... %TMRA1-I-START, Defining TeamRoute for ALL-IN-1 logicals... ================================================= Running startup for TeamRoute V1.1 for ALL-IN-1 ================================================= Installing TeamRoute images Defining TeamRoute language independent logical names Defining TeamRoute ENGLISH language logical names Deleting old versions of files that have moved... Sample Installation A-13 Sample Installation A.2 Upgrade Installation of TeamRoute %OA-I-LASTLINE, ALL-IN-1 Running to compile and install site application - %OA-I-LASTLINE, message file to include TeamRoute message symbols... %OA-I-CMPFILE, Processing USER2:[ALLIN1_ENGLISH.SITE.SOURCES_ENGLISH] SITE$OA.A1$MSG;12 %OA-I-CMPSTS, 896 symbols used, 0 duplicates %OA-I-CMPEND, Symbols total: 896 symbols, Section file 53908 bytes long SYSTEM finished using ALL-IN-1 at 14-Jan-1993 17:27 %OA-I-LASTLINE, ALL-IN-1 Running to compile and install - %OA-I-LASTLINE, ENGLISH TeamRoute form libraries... %OA-I-LASTLINE, Compiling TMRA1$LIB_LLV:TMRFLB... %OA-I-LASTLINE, Compiling TMRA1$LIB_LLV:TMRMGR... SYSTEM finished using ALL-IN-1 at 14-Jan-1993 17:28 %OA-I-LASTLINE, ALL-IN-1 Running to remove old TeamRoute records from CM... SYSTEM finished using ALL-IN-1 at 14-Jan-1993 17:28 %OA-I-LASTLINE, ALL-IN-1 Running... %OA-I-LASTLINE, Updating profile entry for TeamRoute Service Agent... %OA-I-LASTLINE, Updating MSG:TMR record in FORMAT data file... %OA-I-LASTLINE, Updating CM$SDC.DAT with new SHARE elements... SYSTEM finished using ALL-IN-1 at 14-Jan-1993 17:29 %OA-I-LASTLINE, ALL-IN-1 Running... %OA-I-LASTLINE, Updating CM$SDC.DAT with new ENGLISH elements... %OA-I-LASTLINE, Updating ALL-IN-1 CM data sets... %OA-I-LASTLINE, Defining Customization Management logicals... SYSTEM finished using ALL-IN-1 at 14-Jan-1993 17:30 Starting the TeamRoute Service Agent... A-14 Sample Installation Sample Installation A.2 Upgrade Installation of TeamRoute IMPORTANT ========= To complete the installation of TeamRoute for ALL-IN-1 it is necessary to perform the following manual tasks. Please refer to the section "After Installing TeamRoute" in the Installation Guide. Compile and install the ALL-IN-1 base text library (A1TXL.TXL). Please update form MAIN. Please update form DEFAULT. Please update form SM$MAIN2. Please update form SM_DEFAULT. ************************************************************** * The Installation of TeamRoute for ALL-IN-1 has completed. * ************************************************************** ************************************************************** * Running the TMRA1 Installation Verification Procedure. * ************************************************************** The IVP has completed successfully See log file SYS$TEST:TMRA1$IVP.LOG for details Installation of TMRA1 V1.1 completed at 17:30 VMSINSTAL procedure done at 17:31 A.3 Installation of an Additional TeamRoute Language The following sample script shows the installation of an additional TeamRoute language: VAX/VMS Software Product Installation Procedure V5.5 It is 14-JAN-1993 at 14:37. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: TMRA1$SA_1 * 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: Sample Installation A-15 Sample Installation A.3 Installation of an Additional TeamRoute Language TMRA1 V1.1 Beginning installation of TMRA1 V1.1 at 14:37 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ************************************************************************** TMRA1 V1.1 Kit Installation Procedure Copyright (c) Digital Equipment Corporation. 1992. All Rights Reserved. ************************************************************************** This procedure supports the following installation paths :- (1) First full installation of TeamRoute for ALL-IN-1 (2) Installation of an additional TeamRoute language only (3) Upgrade installation of TeamRoute for ALL-IN-1 (4) Upgrade an additional TeamRoute language only * What type of installation do you wish to perform: 2 %TMRA1-I-SEC, This installation will add an additional language -TMRA1-I-SEC, to an existing TeamRoute for ALL-IN-1 base. %TMRA1-I-CHECKS, Performing pre-installation checks... %TMRA1-I-CHKVMS, Checking your system's VMS version. %TMRA1-I-CHKSPA, Checking for sufficient free space on the kit working disk. %TMRA1-I-CHKGBL, Checking for sufficient free global pages and global sections. %TMRA1-I-CHKA1, Checking that ALL-IN-1 IOS is installed. %TMRA1-I-CHKLOG, Checking ALL-IN-1 logicals that this installation will use. %TMRA1-I-CHKSHT, Checking that ALL-IN-1 has been shutdown. %TMRA1-I-STOPSA, TeamRoute has previously been installed. Running -TMRA1-I-STOPSA, TMR$SM_STOP_SERVICE_AGENT to stop the Service Agent. * Enter language code for this installation (2 Characters): de %TMRA1LDE-I-RESLANG, Restoring the LANGUAGE saveset... %VMSINSTAL-I-RESTORE, Restoring product save set A ... %TMRA1-I-LANG, The language of this TeamRoute kit is GERMAN. %TMRA1-I-CHKDSK, Checking disk space... %TMRA1-I-DSKSPA, Checking space on the ALL-IN-1 GERMAN files disk. %TMRA1-I-DSKSPA, Checking space on the system disk. A-16 Sample Installation Sample Installation A.3 Installation of an Additional TeamRoute Language %TMRA1-I-DSKSPA, Checking space on the ALL-IN-1 shared data files disk. %TMRA1-I-DSKSPA, Checking space on the TeamRoute target disk. %TMRA1-I-DSKSPA, Checking free space on the ALL-IN-1 shared library files disk. Product: TMRA1-DE Producer: DEC Version: 1.1 Release Date: * Does this product have an authorization key registered and loaded? yes %TMRA1-I-CHKLIC, Checking TMRA1-DE licence is registered and loaded Access granted %TMRA1-I-RUNA1, Running ALL-IN-1 to obtain VMS account of ALL-IN-1 MANAGER... %TMRA1-I-A1LNKQ, ALL-IN-1 link questions will now be asked. During your first language installation you chose to install ALL-IN-1 without DATATRIEVE, so this tool will NOT be available from your ALL-IN-1. During your first language installation you chose to install ALL-IN-1 without WPS-PLUS, so WPS-PLUS can not be accessed from your ALL-IN-1. This kit contains a library of Encapsulated PostScript(R) graphics and PostScript(R) Page Overlay samples specific to the ''A1$LANGUAGE' system. * Do you want these graphics copied to the ALL-IN-1 library directory [NO]? During your first language installation you chose to install ALL-IN-1 without ACMS, so this tool will NOT be available from your ALL-IN-1. ALL-IN-1 allows you to select a default date format for each language you have installed. This will become the default ALL-IN-1 date format for each user (on a per language basis.) This may be changed by each user through the Set Working Conditions option on the User Setup Menu. Alphanumeric Date Numeric Date Sample Installation A-17 Sample Installation A.3 Installation of an Additional TeamRoute Language 1 DD-MMM-YYYY MM/DD/YY (Standard Default) 2 DD-MMM-YYYY DD/MM/YY 3 DD-MMM-YYYY YY/MM/DD 4 YYYY-MMM-DD MM/DD/YY 5 YYYY-MMM-DD DD/MM/YY 6 YYYY-MMM-DD YY/MM/DD 7 ***** Reserved (Means system default) ***** 8 DD-MM-YYYY DD/MM/YY (Numeric format) 9 MM-DD-YYYY MM/DD/YY (Numeric format) * Which date format do you require [1]: %TMRA1-I-DATEFORMAT, Date format DD-MMM-YYYY and MM/DD/YY (1) has been selected %TMRA1-I-A1LNKQ, End of ALL-IN-1 link questions. * Do you want to run the IVP after the installation [YES]? All questions have now been completed. The installation will take another 30-60 minutes. %TMRA1-I-CREATDIR, Creating TMRA1SERVICE directory and subdirectories... %TMRA1-I-INSTLANG, Installing GERMAN language specific files... %TMRA1-I-ADDHLP, Adding TeamRoute Help libraries to OAHELP... %TMRA1-I-ADDMSG, Adding TeamRoute messages to SITE$OA.A1$MSG... %TMRA1-I-A1LNK, Relinking ALL-IN-1 to include TeamRoute... Linking the OA$LLVGERMAN.EXE %TMRA1-I-LNKOK, The ALL-IN-1 link has completed successfully. To successfully install TeamRoute for ALL-IN-1, it is necessary to update several ALL-IN-1 forms. If these forms have NOT already been customized by another application, the installation procedure will attempt to automatically provide them to your system's site area. However, if the installation procedure finds that the form is already customized, then it will be necessary to perform the update manually. Please refer to the section "After Installing TeamRoute" in the Installation guide if the installation procedure reports that a manual update is required. %TMRA1-I-NOCUSTOM, Element MAIN.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. A-18 Sample Installation Sample Installation A.3 Installation of an Additional TeamRoute Language %TMRA1-I-NOCUSTOM, Element DEFAULT.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-I-NOCUSTOM, Element SM$MAIN2.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-I-NOCUSTOM, Element SM_DEFAULT.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-I-FRMUPD, Form MAIN will be updated in SITEOAFORM.FLB %TMRA1-I-FRMUPD, Form DEFAULT will be updated in SITEOAFORM.FLB %TMRA1-I-FRMUPD, Form SM$MAIN2 will be updated in SITEMANAGER.FLB %TMRA1-I-FRMUPD, Form SM_DEFAULT will be updated in SITEMANAGER.FLB %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ************************************************************** * Automatic Postinstallation tasks will now be performed * ************************************************************** %TMRA1-I-SETACL, Setting ownership ACLs on TeamRoute development files... %TMRA1-I-START, Defining TeamRoute for ALL-IN-1 logicals... ================================================= Running startup for TeamRoute V1.1 for ALL-IN-1 ================================================= Installing TeamRoute images Defining TeamRoute language independent logical names Defining TeamRoute ENGLISH language logical names ================================================= Running startup for TeamRoute V1.1 for ALL-IN-1 ================================================= Defining TeamRoute GERMAN language logical names %OA-I-LASTLINE, ALL-IN-1 Running to compile and install site application - %OA-I-LASTLINE, message file to include TeamRoute message symbols... %OA-I-CMPFILE, Processing USER2:[ALLIN1_GERMAN.SITE.SOURCES_GERMAN] SITE$OA.A1$MSG;6 %OA-I-CMPSTS, 896 symbols used, 0 duplicates %OA-I-CMPEND, Symbols total: 896 symbols, Section file 53912 bytes long SYSTEM beendet die Arbeit mit ALL-IN-1 am 14.Jan.1993 14.52 Sample Installation A-19 Sample Installation A.3 Installation of an Additional TeamRoute Language %OA-I-LASTLINE, ALL-IN-1 Running to compile and install - %OA-I-LASTLINE, GERMAN TeamRoute form libraries... %OA-I-LASTLINE, Compiling TMRA1$LIB_LLV:TMRFLB... %OA-I-LASTLINE, Compiling TMRA1$LIB_LLV:TMRMGR... SYSTEM beendet die Arbeit mit ALL-IN-1 am 14.Jan.1993 14.53 %OA-I-LASTLINE, ALL-IN-1 Running... %OA-I-LASTLINE, Updating CM$SDC.DAT with new GERMAN elements... %OA-I-LASTLINE, Updating ALL-IN-1 CM data sets... %OA-I-LASTLINE, "Compiling and installing OA$SITE_LIB_ENGLISH:SITEOAFORM" %OA-I-LASTLINE, "Compiling and installing OA$SITE_LIB_ENGLISH:SITEMANAGER" %OA-I-LASTLINE, Defining Customization Management logicals... SYSTEM beendet die Arbeit mit ALL-IN-1 am 14.Jan.1993 14.55 Starting the TeamRoute Service Agent... ************************************************************** * The Installation of TeamRoute for ALL-IN-1 has completed. * ************************************************************** ************************************************************** * Running the TMRA1 Installation Verification Procedure. * ************************************************************** The IVP has completed successfully See log file SYS$TEST:TMRA1$IVP.LOG for details Installation of TMRA1 V1.1 completed at 14:55 VMSINSTAL procedure done at 14:55 A-20 Sample Installation B ________________________________________________________________ Files and Logical Names Installed on Your System The TeamRoute installation procedure installs a number of files on your system and defines some logical names. Section Section B.1 lists these files and their locations. Section B.2 lists the logical names that are added to the system logical name table. Section B.3 lists the ALL-IN-1 files that TeamRoute modifies during the installation. B.1 File Names The following sections list the files created in the various directories. B.1.1 Files Placed on the System Disk The following files are placed on the system disk: SYS$COMMON:[SYSHLP]TMR$TCU_HELP.HLB SYS$COMMON:[SYSHLP]TMRA1011.RELEASE_NOTES SYS$COMMON:[SYSLIB]TMRA1$API_SHR.EXE SYS$COMMON:[SYSLIB]TMRA1$RTL_SHR.EXE SYS$COMMON:[SYSMSG]TMRA1$RTLMSG_SHR.EXE SYS$COMMON:[SYS$STARTUP]TMRA1$STARTUP.COM SYS$COMMON:[SYSTEST]TMRA1$IVP.COM B.1.2 Files Placed in the ALL-IN-1 Directory The following files are placed in the ALL-IN-1 directories during the TeamRoute installation: OA$LIB_SHARE:TMR.COM OA$LIB_SHARE:TMR.CMU OA$LIB_SHARE:TMR.SCP OA$SITE_LIB:SITE_SM_RENAME.COM Files and Logical Names Installed on Your System B-1 Files and Logical Names Installed on Your System B.1 File Names B.1.3 Files Installed in TeamRoute for ALL-IN-1 Directories The TeamRoute installation installs files in the following directories: In TMRA1$BLP_LLV: TMR$CL_DISPLAY_HISTORY.BLP TMR$CL_DISPLAY_REROUTE_HELP.BLP TMR$CL_DISPLAY_ROLE.BLP TMR$CL_DISPLAY_ROLE_HELP.BLP TMR$CL_DISPLAY_ROLE_REQS.BLP TMR$CL_DISPLAY_ROLE_RIGHTS.BLP TMR$CL_NO_PACKAGE_HELP.BLP TMR$CL_NO_ROLE_HELP.BLP TMR$CL_PRINT_HEADER.BLP TMR$CL_READ_ATTACHMENT.BLP TMR$CL_READ_PACKAGE.BLP TMR$CL_READ_SERVICE_MSG.BLP TMR$CL_READ_SIGNATURE.BLP TMR$CL_READ_STATUS.BLP TMR$CL_SHOW_COMPONENTS.BLP TMR$CL_SHOW_SERVICE_MSG.BLP TMR$CL_SHOW_STATUS.BLP In TMRA1$BLP_SHARE: TMR$CL_DISPLAY_PACKAGE_HELP.BLP TMR$CL_PRINT_PACKAGE.BLP In TMRA1$DATA_SHARE: TMRA1$APPLICATION.DAT TMRA1$DATA_TYPE.DAT TMRA1$PROFILE.DAT In TMRA1$DO_SHARE: B-2 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.1 File Names TMR$CL_ADD_ATTACHMENT.SCP TMR$CL_ADD_SIGNATURE.SCP TMR$CL_ATTACH.SCP TMR$CL_ATTACH_DOCUMENT.SCP TMR$CL_BYPASS_RECIPIENT.SCP TMR$CL_CHECK_REQUESTS.SCP TMR$CL_CREATE.SCP TMR$CL_CREATE_ROUTING_LIST.SCP TMR$CL_CREATE_SAMPLE_TEMPLATES.SCP TMR$CL_CREATE_TEMPLATE.SCP TMR$CL_DATA_FILES_TO_FILECAB.SCP TMR$CL_DATA_FILES_TO_OASHARE.SCP TMR$CL_DELETE.SCP TMR$CL_DELETE_SIGNATURE.SCP TMR$CL_DETACH.SCP TMR$CL_DISPLAY_HISTORY.SCP TMR$CL_EDIT.SCP TMR$CL_EDIT_ATTACHMENT.SCP TMR$CL_FILE_ATTACHMENT.SCP TMR$CL_FILE_TEXT.SCP TMR$CL_FORMAT_EDIT.SCP TMR$CL_FORMAT_PRINT.SCP TMR$CL_FORMAT_READ.SCP TMR$CL_GET_ATTACHMENT_KEY.SCP TMR$CL_GET_GROUP_NUMBER.SCP TMR$CL_GET_NUM_ATTACHMENTS.SCP TMR$CL_GET_PACKAGE_ATTRIBUTES.SCP TMR$CL_GET_PENDING.SCP TMR$CL_GET_PROFILE_INFO.SCP TMR$CL_GET_ROLE_ID.SCP TMR$CL_IMPORT_TEMPLATE.SCP TMR$CL_INDEX_ATTACHMENTS.SCP TMR$CL_INDEX_SIGNATURES.SCP TMR$CL_MODIFY_HEADER.SCP TMR$CL_OPEN_LIBRARY.SCP TMR$CL_PRINT.SCP TMR$CL_PROCESS_APPLICATION.SCP TMR$CL_PROCESS_ATTACHMENTS.SCP TMR$CL_PROCESS_COMPONENTS.SCP TMR$CL_PROCESS_NEW_PACKAGE.SCP TMR$CL_READ.SCP TMR$CL_READ_COMPONENTS.SCP TMR$CL_READ_NEW.SCP TMR$CL_READ_PACKAGE.SCP TMR$CL_READ_SERVICE_MSG.SCP TMR$CL_REFILE_DOCUMENT.SCP TMR$CL_REMOVE_SIGNATURE.SCP TMR$CL_ROUTE_VALID.SCP TMR$CL_RUN_APPLICATION.SCP TMR$CL_SELECT.SCP TMR$CL_SELECT_DOCUMENT.SCP TMR$CL_SEND.SCP TMR$CL_SERVICE_AGENT_REQUEST.SCP TMR$CL_SET_NEW_TMRDOC.SCP TMR$CL_SHOW_COMPONENTS.SCP TMR$CL_SHOW_ROLE.SCP TMR$CL_SHOW_ROUTING_LIST.SCP TMR$CL_SHOW_STATUS.SCP TMR$CL_SIGN_DOCUMENT.SCP TMR$CL_TRACK_DOCUMENT.SCP TMR$CL_UPDATE_ATTACHMENT.SCP TMR$CL_VALIDATE_ADDRESS.SCP TMR$CL_VALIDATE_FOLDER.SCP TMR$CL_YESNO_PROMPT.SCP In TMRA1$LIB_LLV: Files and Logical Names Installed on Your System B-3 Files and Logical Names Installed on Your System B.1 File Names TMR$CL_EMPTY.TXT TMR$CL_FORMAT_PRINT.COM TMR$CL_SAMPLE_ACCREQ.FGN TMR$CL_SAMPLE_ACTION.FGN TMR$CL_SAMPLE_ANSWER.FGN TMR$CL_SAMPLE_DOCREV.FGN TMR$CL_SAMPLE_MEETING.FGN TMR$CL_SAMPLE_READACK.FGN TMR$CL_SAMPLE_TELEPHONE.FGN TMR$CL_SAMPLE_TRAVELREQ.FGN TMR$SM_CHKLICVERSION.SCP TMR$SM_MAR_PRINTHEADER.BLP TMR$SM_MAR_PRINTTEMPLATE.BLP TMR$SM_MEA_PRINTHEADER.BLP TMR$SM_MEA_PRINTTEMPLATE.BLP TMR$SM_MSA_PRINTHEADER.BLP TMR$SM_MSA_PRINTTEMPLATE.BLP TMR$SM_PRINTFORMAT.BLP TMR$SM_SETUP.SCP TMR$SM_SMSA_STARTUP.COM TMRA1$TEAMFORM.COM TMRA1$TEAMFORM.EXE TMRA1$TEAMFORM.SCP TMRFLB.FLB TMRFLB.FLC TMRMGR.FLB TMRMGR.FLC In TMRA1$LIB_SHARE: TMR$CL_GET_GROUP_NUMBER.COM TMR$SM_ADD_USERS.SCP TMR$SM_APPLICATION_FILE_STARTUP.COM TMR$SM_CHKLICENSE.EXE TMR$SM_CREATE_TMRSUBSCRIBERS.SCP TMR$SM_MAR_PRINT.SCP TMR$SM_MEA_PRINT.SCP TMR$SM_MSA_PRINT.SCP TMR$SM_OPENLIB.SCP TMR$SM_PROFILE.FDL TMR$SM_PROFILE_STARTUP.COM TMR$SM_RENAME_FILES.COM TMR$SM_RESTART_SERVICE_AGENT.COM TMR$SM_RUNCHECK.COM TMR$SM_STOP_SERVICE_AGENT.COM TMR$SM_SUBMIT_SERVICE_AGENT.COM TMR$SM_SUSPEND_SERVICE_AGENT.COM TMRA1$DATA_TYPE.FDL TMRA1$DATA_TYPE.SCP TMRA1$RTL_DUMP.EXE TMRA1$TCU.EXE B-4 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.1 File Names In TMRA1$SA_CODE: TMR$SA_ATTACH_ATTACHMENT.SCP TMR$SA_BATCH_SERVICE_AGENT.COM TMR$SA_BUILD_ROUTING_COPY.SCP TMR$SA_BYPASS_CURRENT_RECIPIENT.SCP TMR$SA_CHECKLICENSE.COM TMR$SA_CHECK_BLOCKSIZE.COM TMR$SA_CONTROL_FILE.SCP TMR$SA_CONTROL_FILE_STARTUP.COM TMR$SA_CREATE_ROUTING_COPY.SCP TMR$SA_CREATE_SERVICE_MESSAGE.SCP TMR$SA_DELETE_MASTER.SCP TMR$SA_FIFO_ORDER.SCP TMR$SA_FILE_HEADER.SCP TMR$SA_GET_FILESPEC.SCP TMR$SA_HIBERNATE_SERVICE_AGENT.SCP TMR$SA_INIT_SERVICE_AGENT.COM TMR$SA_LOG.SCP TMR$SA_NEW_MASTER.SCP TMR$SA_OCTAL.COM TMR$SA_OPENLIB.SCP TMR$SA_PROCESS_HIGH.SCP TMR$SA_PROCESS_LOW.SCP TMR$SA_RENAME_FILES.COM TMR$SA_SA_REPLY.SCP TMR$SA_SEPARATE_ATTACHMENTS.SCP TMR$SA_SERVICE_AGENT.COM TMR$SA_SERVICE_AGENT_SCRIPT.SCP TMR$SA_SETPROTECTION.COM TMR$SA_SETUP.COM TMR$SA_SETUP.SCP TMR$SA_SET_ACLS.COM TMR$SA_SET_ACLS.SCP TMR$SA_SHUTDOWN_CHECK.COM TMR$SA_TRACE_OFF.SCP TMR$SA_TRACE_ON.SCP TMR$SA_TRACKING.SCP TMR$SA_TRANSACTION.FDL TMR$SA_TRANSACTION.SCP TMR$SA_TRANSACTION_STARTUP.COM TMR$SA_UPDATE_CONTROL_FILE.COM TMR$SA_UPDATE_REQUEST.SCP TMR$SA_VARIABLE.SCP TMR$SA_WRITELOG.COM In TMRA1$SA_DATA: TMR$SA_CONTROL_FILE.DAT TMR$SA_LOG_FILE.FDL TMR$SA_TRANSACTION.DAT TMR$SM_APPLICATION_FILE.FDL In TMRA1$SCP_SHARE: TMR$CL_GOLDF.SCP TMR$CL_GOLDQ.SCP In TMRA1$SITE_DEV_LLV: CM$SITEHIST.DAT DEVELOP.FLB In TMRA1$SITE_DEV_SHARE: CM$SITEHIST.DAT In TMRA1$SITE_LIB_LLV: SITETMRFLB.FLB SITETMRMGR.FLB Files and Logical Names Installed on Your System B-5 Files and Logical Names Installed on Your System B.1 File Names In TMRA1$BUILD_LLV: OA$TMR$MESSAGES.MSG OA$TMR$MESSAGES_NOTEXT.OBJ OA$TMR$MESSAGES_TEXT.OBJ In TMRA1$BUILD_SHARE: OA$TMR$LIBRARY.OLB SITELINK.COM SITELLV_TMR.COM TMRRTL.H B.1.4 Forms and Scripts not in TeamRoute Version 1.1 The following forms have been deleted since TeamRoute Version 1.0: TMR$ARG$REFILE_DOCUMENT TMR$MENU$SHOW TMR$SM$MAC$INDEX$MENU TMR$SM$MAC$INDEX$MENU2 TMR$MEA$OPTIONS TMR$ARG$DOCRECOG The following scripts have been deleted since TeamRoute Version 1.0: TMR$CL_DISPLAY_PACKAGE_HELP.SCP TMR$CL_DISPLAY_ROLE.SCP TMR$CL_DISPLAY_ROLE_HELP.SCP B.2 Logical Names and Search Lists This section lists the logical names and search lists defined by TeamRoute. B.2.1 TeamRoute Logical Names The logical names in the following list are entered into the system logical name table when TeamRoute is installed. These names are stored in the product's startup file. They are automatically entered into the system logical name table whenever the system reboots or whenever the software is invoked. B-6 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.2 Logical Names and Search Lists ________________________________________________________________ Logical_Name______________Translation___________________________ OA$SITE_DEV_REC_TMR_ disk$:[TMRA1SERVICE.SITE.DEV_REC_TMR_ language language] OA$SITE_DEV_REC_TMR_ disk$:[TMRA1SERVICE.SITE.DEV_REC_TMR_ SHARE SHARE] OA$SITE_DEV_TMR_language disk$:[TMRA1SERVICE.SITE.DEV_TMR_ language] OA$SITE_DEV_TMR_SHARE disk$:[TMRA1SERVICE.SITE.DEV_TMR_ SHARE] TMRA1$A1 disk$:[TMRA1SERVICE.SA.TMRA1SA1.A1] TMRA1$A1PREFIX TMRA1SA TMRA1$API_SHR SYS$SHARE:TMRA1$API_SHR.EXE TMRA1$BLP_language disk$:[TMRA1SERVICE.BLP_language] TMRA1$BLP_LLV disk$:[TMRA1SERVICE.BLP_language] TMRA1$BLP_SHARE disk$:[TMRA1SERVICE.BLP_SHARE] TMRA1$BUILD_language disk$:[TMRA1SERVICE.SOURCES_language] TMRA1$BUILD_LLV disk$:[TMRA1SERVICE.SOURCES_language] TMRA1$BUILD_SHARE disk$:[TMRA1SERVICE.SOURCES_SHARE] TMRA1$DATA_language disk$:[TMRA1SERVICE.DATA_language] TMRA1$DATA_LLV disk$:[TMRA1SERVICE.DATA_language] TMRA1$DATA_SHARE disk$:[TMRA1SERVICE.DATA_SHARE] TMRA1$DO_language disk$:[TMRA1SERVICE.DO_language] TMRA1$DO_LLV disk$:[TMRA1SERVICE.DO_language] TMRA1$DO_SHARE disk$:[TMRA1SERVICE.DO_SHARE] TMRA1$DUMP_AREA disk$:[TMRA1SERVICE.DUMP_AREA] TMRA1$LIB_language disk$:[TMRA1SERVICE.LIB_language] TMRA1$LIB_LLV disk$:[TMRA1SERVICE.LIB_language] TMRA1$LIB_SHARE disk$:[TMRA1SERVICE.LIB_SHARE] TMRA1$LOG disk$:[TMRA1SERVICE.LOG] TMRA1$PROCPREFIX TMRA1$SA_ TMRA1$PROFILE_SA TMRA1SA1 TMRA1$SA$TRANSFILE TMRA1$SA_DATA:TMR$SA_TRANSACTION.DAT TMRA1$SA$USERNAME TMRA1SA1 Files and Logical Names Installed on Your System B-7 Files and Logical Names Installed on Your System B.2 Logical Names and Search Lists ________________________________________________________________ Logical_Name______________Translation___________________________ TMRA1$SABATCH SYS$BATCH TMRA1$SADEVICE disk$: TMRA1$SATRACE 0 TMRA1$SAVERSION 1 TMRA1$SA_CODE disk$:[TMRA1SERVICE.SA.CODE] TMRA1$SA_DATA disk$:[TMRA1SERVICE.SA.DATA] TMRA1$SA_LOG disk$:[TMRA1SERVICE.SA.LOG] TMRA1$SCP_language disk$:[TMRA1SERVICE.SCP_language] TMRA1$SCP_LLV disk$:[TMRA1SERVICE.SCP_language] TMRA1$SCP_SHARE disk$:[TMRA1SERVICE.SCP_SHARE] TMRA1$SERVICE TMRA1SERVICE TMRA1$SERVICE_DIRECTORY disk$:[TMRA1SERVICE] TMRA1$SITE_BLP_language disk$:[TMRA1SERVICE.SITE.BLP_language] TMRA1$SITE_BLP_LLV disk$:[TMRA1SERVICE.SITE.BLP_language] TMRA1$SITE_BLP_SHARE disk$:[TMRA1SERVICE.SITE.BLP_SHARE] TMRA1$SITE_BUILD_ disk$:[TMRA1SERVICE.SITE.SOURCES_ language language] TMRA1$SITE_BUILD_LLV disk$:[TMRA1SERVICE.SITE.SOURCES_ language] TMRA1$SITE_BUILD_SHARE disk$:[TMRA1SERVICE.SITE.SOURCES_ SHARE] TMRA1$SITE_DATA_language disk$:[TMRA1SERVICE.SITE.DATA_ language] TMRA1$SITE_DATA_LLV disk$:[TMRA1SERVICE.SITE.DATA_ language] TMRA1$SITE_DATA_SHARE disk$:[TMRA1SERVICE.SITE.DATA_SHARE] TMRA1$SITE_DEV_language disk$:[TMRA1SERVICE.SITE.DEV_TMR_ language] TMRA1$SITE_DEV_LLV disk$:[TMRA1SERVICE.SITE.DEV_TMR_ language] TMRA1$SITE_DEV_SHARE disk$:[TMRA1SERVICE.SITE.DEV_TMR_ SHARE] TMRA1$SITE_DO_language disk$:[TMRA1SERVICE.SITE.DO_language] B-8 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.2 Logical Names and Search Lists ________________________________________________________________ Logical_Name______________Translation___________________________ TMRA1$SITE_DO_LLV disk$:[TMRA1SERVICE.SITE.DO_language] TMRA1$SITE_DO_SHARE disk$:[TMRA1SERVICE.SITE.DO_SHARE] TMRA1$SITE_LIB_language disk$:[TMRA1SERVICE.SITE.LIB_language] TMRA1$SITE_LIB_LLV disk$:[TMRA1SERVICE.SITE.LIB_language] TMRA1$SITE_LIB_SHARE disk$:[TMRA1SERVICE.SITE.LIB_SHARE] TMRA1$SITE_SCP_language disk$:[TMRA1SERVICE.SITE.SCP_language] TMRA1$SITE_SCP_LLV disk$:[TMRA1SERVICE.SITE.SCP_language] TMRA1$SITE_SCP_SHARE disk$:[TMRA1SERVICE.SITE.SCP_SHARE] TMRA1$SOURCES disk$:[TMRA1SERVICE.SOURCES] TMRA1$TMRA1SA_____________SA____________________________________ B.2.2 Logicals Added to Each ALL-IN-1 Language Logical Table (OA$language_TABLE) The following logicals are added to the logical table for each ALL-IN-1 language on your system. ________________________________________________________________ Logical___________________Translation___________________________ TMRA1$BLP_LLV disk$:[TMRA1SERVICE.BLP_language] TMRA1$BUILD_LLV disk$:[TMRA1SERVICE.SOURCES_language] TMRA1$DATA_LLV disk$:[TMRA1SERVICE.DATA_language] TMRA1$DO_LLV disk$:[TMRA1SERVICE.DO_language] TMRA1$LIB_LLV disk$:[TMRA1SERVICE.LIB_language] TMRA1$SCP_LLV disk$:[TMRA1SERVICE.SCP_language] TMRA1$SITE_BLP_LLV disk$:[TMRA1SERVICE.SITE.BLP_language] TMRA1$SITE_BUILD_LLV disk$:[TMRA1SERVICE.SITE.SOURCES_ language] TMRA1$SITE_DATA_LLV disk$:[TMRA1SERVICE.SITE.DATA_ language] TMRA1$SITE_DEV_LLV disk$:[TMRA1SERVICE.SITE.DEV_TMR_ language] TMRA1$SITE_DO_LLV disk$:[TMRA1SERVICE.SITE.DO_language] TMRA1$SITE_LIB_LLV disk$:[TMRA1SERVICE.SITE.LIB_language] Files and Logical Names Installed on Your System B-9 Files and Logical Names Installed on Your System B.2 Logical Names and Search Lists ________________________________________________________________ Logical___________________Translation___________________________ TMRA1$SITE_SCP_LLV________disk$:[TMRA1SERVICE.SITE.SCP_language] B.2.3 Logical Search Lists The following logical search lists are defined when TeamRoute is installed. __________________________________________________________ Search_List_______________Translation_____________________ TMRA1$BLP TMRA1$SITE_BLP_LLV TMRA1$SITE_BLP_SHARE TMRA1$BLP_LLV TMRA1$BLP_SHARE TMRA1$BUILD TMRA1$SITE_BUILD_LLV TMRA1$SITE_BUILD_SHARE TMRA1$BUILD_LLV TMRA1$BUILD_SHARE TMRA1$DATA TMRA1$SITE_DATA_LLV TMRA1$SITE_DATA_SHARE TMRA1$DATA_LLV TMRA1$DATA_SHARE TMRA1$DO TMRA1$SITE_DO_LLV TMRA1$SITE_DO_SHARE TMRA1$DO_LLV TMRA1$DO_SHARE TMRA1$LIB TMRA1$SITE_LIB_LLV TMRA1$SITE_LIB_SHARE TMRA1$LIB_LLV TMRA1$LIB_SHARE TMRA1$SCP TMRA1$SITE_SCP_LLV TMRA1$SITE_SCP_SHARE TMRA1$SCP_LLV __________________________TMRA1$SCP_SHARE_________________ B-10 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.3 ALL-IN-1 Files Modified by TeamRoute B.3 ALL-IN-1 Files Modified by TeamRoute TeamRoute modifies the following ALL-IN-1 files during the installation. OA$LIB_SHARE:OA$MAIN.EXE OA$SITE_BUILD_LLV:SITE$OA.A1$MSG OA$SITE_DEV_LLV:SITE$OA.A1$MSG OA$SITE_LIB_LLV:SITE$OA_SYM.A1$SECTION OA$SITE_BUILD_SHARE:A1V30_SITE_START.COM OA$SITE_BUILD_SHARE:OA$SCT$SDF.DAT OA$SITE_BUILD_SHARE:OA$SCT$SYMBOLS_READ.DAT OA$SITE_BUILD_SHARE:OA$SCT$SYMBOLS_WRITE.DAT OA$SITE_DEV_SHARE:OA$SCT$SDF.DAT OA$SITE_DEV_SHARE:OA$SCT$SYMBOLS_READ.DAT OA$SITE_DEV_SHARE:OA$SCT$SYMBOLS_WRITE.DAT OA$SITE_DEV_SHARE:CM$SITEHIST.DAT OA$SITE_DEV_LLV:CM$SITEHIST.DAT OA$BUILD_LLV:SITELINK30.COM OA$BUILD_LLV:SITELLV.COM OA$DATA_SHARE:CM$APP.DAT OA$DATA_SHARE:CM$AUTH$LOCATIONS.DAT OA$DATA_SHARE:CM$AUTH$USERS.DAT OA$DATA_SHARE:CM$FORM$LIBS.DAT OA$DATA_SHARE:CM$MAF.DAT OA$DATA_SHARE:CM$SDC.DAT OA$DATA_SHARE:CM$SITELOG.DAT For multi-lingual ALL-IN-1 systems, SYS$COMMON:[SYSLIB]OA$LLVlanguage.EXE is also modified. The following files in OA$SITE_BUILD_SHARE:SITEOALIBR.OLB are modified: OA$SCT$SDF.OBJ OA$SCT$SYMBOLS_READ.OBJ OA$SCT$SYMBOLS_WRITE.OBJ The following files in OA$SITE_LIB_LLV:SITEOAFORM.FLB are modified: MAIN.FRM DEFAULT.FRM Files and Logical Names Installed on Your System B-11 Files and Logical Names Installed on Your System B.3 ALL-IN-1 Files Modified by TeamRoute The following file in OA$SITE_LIB_LLV:SITEMANAGER.FLB is modified: SM$MAIN2 If the file OA$SITE_LIB:SITE_SM_RENAME.COM already exists on the system, it is modified by TeamRoute during the installation. If it does not already exist, it is created. B-12 Files and Logical Names Installed on Your System C ________________________________________________________________ Handling Diagnostics This appendix describes the following types of diagnostic messages, which TeamRoute writes to the log file: o Informational o Warning o Error C.1 Informational Messages The following informational messages are part of the normal execution of the service agent within the DCL command procedure. They require no action from you. All informational messages begin with %TMRA1$SA-I-. RUNREQUEST, SA has received a run request Explanation: The service agent has received an execution or start request. Its state is RUNNING. START, SA started run on: node_name Explanation: The service agent detached process has begun. STOPREQUEST, SA has received a stop request Explanation: The service agent has received a stop request and will exit from the detached process. Its state is STOPPED. SUSPENDREQUEST, SA has received a suspend request Explanation: The service agent has received a suspend request and will halt the ALL-IN-1 processing portion of the procedure. Its state is SUSPENDED. Handling Diagnostics C-1 Handling Diagnostics C.2 Warning and Error Messages C.2 Warning and Error Messages The following sections list error condition messages that are part of the execution of the service agent in the ALL-IN-1 command procedure. Error conditions do not stop the service agent, but they can prevent the service Agent from processing a particular request or routing package. To correct error conditions, you perform the following steps: 1. Suspend the service agent. 2. Log in to the service agent ALL-IN-1 account. 3. Perform the specific correction for the error (described below for the error condition flagged by each diagnostic). 4. Restart the service agent. In some cases, the error cannot be corrected because a routing package is invalid or inappropriate. In these cases, you can delete the routing package or return it to its initiator for correction. C.2.1 Warning Messages The following warning messages typically do not represent conditions that prevent the service agent from processing the current routing package. They require no action from you. All warning messages begin with %TMRA1$SA-W-. ACCOUNTNOTAVAIL, SA has determined that SA Account is not available: account Explanation: The service agent has checked for the service agent ALL-IN-1 account and found it is not available. The service agent cannot log into ALL-IN-1 if the account is not available. The service agent process will exit and the process will stop. No processing can be done until the situation is corrected. User Action: Check to see if the service agent ALL-IN-1 account exists. C-2 Handling Diagnostics Handling Diagnostics C.2 Warning and Error Messages BYPASSERROR_NOMASTER, SA cannot bypass a recipient, cannot locate master routing package: folder/docnum Explanation: The service agent could not locate a master routing package during a bypass request. The routing package may have been previously deleted. No action is required. CONTROLFILE_ERROR, SA cannot update the control file. Explanation: The service agent was not able to update the control file. It is possible that it was being accessed by system management. No correction is necessary. DELETEERROR_NOMASTER, SA cannot delete a master, routing package not found: folder/docnum Explanation: The service agent could not locate a master routing package during a delete request. The routing package may have been previously deleted. You do not need to correct this error. ERROR_MASTER_TERM, SA received a bypass request on a completed master routing package: folder/docnum Explanation: The service agent has received a request from an initiator to bypass a recipient. The target master routing package has already been completed. No action can be taken on this request. NONDELIVERY, SA received a non-delivery message, service message sent to: user Explanation: The service agent received a nondelivery message with a TeamRoute routing package attached. The failed delivery could either be a Tracking Copy, a Routing Copy or an unexpected TeamRoute type. This could have been the result of sending a routing copy to a recipient who is not a TeamRoute subscriber. A service message has been sent to the subscriber. No action is required; however, you may want to determine why a TeamRoute routing package could not be delivered to the subscriber. Handling Diagnostics C-3 Handling Diagnostics C.2 Warning and Error Messages NOTALLOWED, SA found a request for function not allowed on a completed routing package: folder/docnum/function Explanation: Requested function is not allowed on a completed TeamRoute master. No correction is necessary. NOTAVAILABLE, SA has determined that ALL-IN-1 is not available. Explanation: The service agent has checked for ALL-IN-1 and found it is not running. The service agent cannot log into ALL-IN-1 if it is not running. The service agent process waits for the set wait time and will attempt to access ALL-IN-1 again. SERVICENONDELIVERY, A service message was returned as a nondelivery message. Explanation: A service message was returned to the service agent as a nondelivery message. In practice, this would occur only if the initiator or recipient of a routing package are not able to receive TeamRoute routing packages. Check that the intended recipient of the service message has a valid, enabled TeamRoute account. No further service messages will be sent to that address. TMRUNKNOWN, SA received unexpected TMR request; type : TeamRoute routing package type Explanation: The service agent received a TeamRoute routing package of unknown type. No action is required. TRACKMASTERERROR, SA cannot select a master routing package while creating a tracking report: folder/docnum Explanation: The service agent cannot locate a master routing package. It is possible that the master routing package has already been deleted. A tracking report will not be made. C-4 Handling Diagnostics Handling Diagnostics C.2 Warning and Error Messages UPDATE_BYPASSED, SA cannot apply update, recipient was bypassed: user Explanation: A routing package update was received by the service agent, but the sender was bypassed on the routing list. The update will not be applied to the master routing package. Routing will continue and no corrections are necessary. UPDATE_NOTCURRENT, SA cannot apply update, user not current recipient: user Explanation: An update was received by the service agent, but the sender is not the current recipient. This occurs when the recipient has been bypassed or deleted on the routing list. The update will not be applied to the master routing package. Routing will continue and no corrections are necessary. UNKNOWNLOW, SA found an unknown or invalid type low-priority request: type/state Explanation: The service agent received a request which has an unknown type. This occurs when non-TeamRoute routing packages or regular mail messages are sent to the service agent. You generally do not have to correct this problem. The TMR_ UNKNOWN_LOW folder will contain all unknown requests that are mailed to the service Agent. You may want to review and purge these messages periodically. C.2.2 Error Messages The following messages represent error conditions that can prevent a service Agent from processing the current routing package or request. All error messages begin with %TMRA1$SA-E-. Handling Diagnostics C-5 Handling Diagnostics C.2 Warning and Error Messages ATTACHERROR, SA error separating attachments; none found in: folder/docnum Explanation: The TeamRoute routing package indicated there were attachments, but none were found. It is possible that the routing package initiator deleted the attachments outside the TeamRoute subsystem. If this is not the case, please submit an SPR. Otherwise, no action is required. A service message was sent to the initiator of the routing package. BYPASSMASTER, SA is bypassing new master routing package: folder/master_docnum Explanation: A possible TeamRoute master routing package was sent to the service agent but it could not be pro- cessed. This error occurs when the routing package files cannot be opened by the TeamRoute subsystem, because the document is not a TeamRoute routing package. The initiator has already received notification that this document could not be processed. No action is required. DATAERROR, SA has found an error separating data files; none found in : folder/docnum/type Explanation: The TeamRoute routing package indicated there were data files, but none were found. It is possible that the routing package initiator detached the data files outside the TeamRoute subsystem. If this is not the case, please submit an SPR. Otherwise, no action is required. A service message was sent to the sender of the routing package. NOTAUTHORIZED, SA cannot process new routing package, user account not enabled. Explanation: The subscriber is not allowed to use TeamRoute. The user's account is probably not enabled as a TeamRoute subscriber. User Action: If appropriate, use the Manage Accounts option on the Manage TeamRoute System menu to set the user's TeamRoute account to ENABLED. C-6 Handling Diagnostics Handling Diagnostics C.2 Warning and Error Messages PROFILEEMPTY, SA could not find the profile entry for: user_name Explanation: See the description for the following message. PROFILEEMPTY, SA could not find the profile entry for SA: sa_name Explanation: The service agent attempted to set ACLs on the master or the attachments but could not read the initiator's or service agent's profile. The ACLs could not be set. Check the profile for the service agent and the initiator, and correct the profile problem. TRACKING, SA is unable to create a tracking report, master routing package was deleted: requester/docnum Explanation: The service agent is unable to create a tracking report. The master routing package was previously deleted. UNKNOWNHIGH, SA found an unknown or invalid high-priority request: type/folder/docnum Explanation: The service agent found an unknown type of TeamRoute request in the high priority queue. The routing package will be copied to the folder TMR_UNKNOWN_HIGH. The routing package type, folder, and number are included with the message. User Action: From the service agent ALL-IN-1 account: 1. Read the routing package. 2. If necessary, delete the routing package and ask the initiator to resend it. Handling Diagnostics C-7 Handling Diagnostics C.2 Warning and Error Messages UPDATEMASTERERROR, SA cannot select a master routing package while processing an update: folder/docnum Explanation: An update package was received by the service agent but the master routing package could not be located. The master may have been deleted. The update package will be moved to the TMRSA_UPDATE_ERROR folder. The update will not be applied to the master routing package, and routing will not continue. A service notice will be sent to the initiator. C-8 Handling Diagnostics D ________________________________________________________________ Transaction File This appendix provides an overview of the transaction file and detailed descriptions of its record format. D.1 Overview The transaction file is an ASCII sequential file, with variable-length records, produced by the TeamRoute Service Agent. A record is written to this file for each transaction that the Service Agent performs. The list of transaction types includes: o (BR) Begin routing request received o (BY) Bypass recipient performed o (CC) Carbon copy sent o (IP) Interpersonal mail received o (RC) Routing copy sent o (RR) Reset routing performed o (SN) Service notice sent o (TC) Tracking report sent o (TR) Tracking request received o (UP) Update applied o (DM) Delete master o (RC) Routing completed Transaction File D-1 Transaction File D.2 Record Format D.2 Record Format Each record in the transaction log file has two parts, a fixed-length part and a variable-length part. The fixed- length part of the record is common to all transaction types listed above, while the variable-length part differs based upon the type of transaction being recorded. All fields in each transaction log record contain ASCII data. This allows you to view the file using simple mechanisms such as the VMS TYPE command. Where possible, field data has been abbreviated to conserve space. For example, the transaction type field is recorded as a two- character mnemonic (see Section D.1). Each transaction type can have different fields recorded in the variable- length part of the record. All fields form a comma- separated list. D.2.1 Fixed-Length Fields Table D-1 lists the fixed-length fields of a transaction log record. Each field is separated by a comma (,). If a field is unavailable, the field size is filled with spaces. Table_D-1_Transaction_File_Fixed-Length_Fields____________ Field_________Size___Description__________________________ TIMESTAMP 14 A datetime stamped representing the datetime when the record was recorded. This field is in the format: YYYYMMDDHHSSCC. TRANS_ID 2 A two-character mnemonic describing the type of transaction record that follows (see Section D.1). (continued on next page) D-2 Transaction File Transaction File D.2 Record Format Table_D-1_(Cont.)_Transaction_File_Fixed-Length_Fields____ Field_________Size___Description__________________________ USER_ID 12 This field contains an identifier for the subscriber that owns the master copy document for which this transaction is being recorded. The source of this field is the ALL-IN-1 full name, which is truncated to 12 characters. DOC_ID 8 The identifier for the master routing package for which the transaction is being recorded. NODE_NAME 6 Node on which the Service Agent was running when the transaction record was written. SA_ID 3 This is an identifier/mnemonic for the Service Agent that wrote the _____________________transaction_log_record_(always_001)._ D.2.2 Variable-Length Fields Table D-2 lists the variable-length fields of a trans- action log record by transaction code. Each field is separated by a comma (,). If a field is unavailable, a comma is used as a placeholder. Table_D-2_Transaction_File_Variable-Length_Fields_________ Field__________Description________________________________ Transaction_code:_BR_(Begin_Routing_Request)______________ IPMID The interpersonal message identifier of the mail message for this inbound Begin Routing Request. SUBMIT_DATE The date that the Begin Routing Request was processed by the Service Agent. (continued on next page) Transaction File D-3 Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ Field__________Description________________________________ Transaction_code:_BR_(Begin_Routing_Request)______________ MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. __________________________________________________________ Transaction_code:_BY_(Bypass_Request)_____________________ IPMID The interpersonal message identifier of the mail message for this inbound Bypass Request. SUBMIT_DATE The date that the Bypass Request was processed by the Service Agent. STEP_ID The identifier of the Routing Step in the master routing package that is the target of the Bypass. RECIP_ID The identifier of the Routing Recipient (within the Step) in the master routing package that is the target of the Bypass. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. (continued on next page) D-4 Transaction File Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_CC_(Carbon_Copy_Sent)___________________ IPMID The interpersonal message identifier of the mail message for this outbound Carbon Copy. SUBMIT_DATE The date that the Carbon Copy was submitted to the mail transport. STEP_ID The identifier of the Routing Step in the master routing package for which the Carbon Copy was sent. RECIP_ID The identifier of the Routing Recipient (within the Step) in the master routing package for which the Carbon Copy was sent. TOADDR The name/mail address of the recipient of the carbon copy. This is typically the to field found in the header of the mail message in which the carbon copy is contained. RETRIES Not applicable to this Service Agent. This space is reserved for compatibility with other Service Agent transaction logs. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. (continued on next page) Transaction File D-5 Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_IP_(IPMAIL_(IOS_ALL-IN-1_mail)_Received) IPMID The interpersonal message identifier of the mail message for this inbound interpersonal mail message. SUBMIT_DATE The date that the Interpersonal Mail message was submitted to the mail transport. FULL_NAME The full subscriber name of the sender. This may have been truncated in the fixed- length section. (continued on next page) D-6 Transaction File Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_RC_(Routing_Copy_Sent)__________________ IPMID The interpersonal message identifier of the mail message for this outbound Routing Copy. SUBMIT_DATE The date that the Routing Copy was submitted to the mail transport. STEP_ID The identifier of the Routing Step in the master routing package for which the Routing Copy was sent. RECIP_ID The identifier of the Routing Recipient (within the Step) in the master routing package for which the Routing Copy was sent. TOADDR The name/mail address of the recipient of the Routing Copy. This is typically the to field found in the header of the mail message in which the routing copy is contained. RETRIES Not applicable to this Service Agent. This space is reserved for compatibility with other Service Agent transaction logs. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. (continued on next page) Transaction File D-7 Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_RR_(Reset_Routing_Request)______________ IPMID The interpersonal message identifier of the mail message for this Reset Routing Request. SUBMIT_DATE The date that the Reset Routing Request was processed by the Service Agent. STEP_ID The identifier of the Routing Step in the master routing package that is the target of the Reset. RECIP_ID The identifier of the Routing Recipient (within the Step) in the master routing package that is the target of the Reset. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. (continued on next page) D-8 Transaction File Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_SN_(Service_Notice_Sent)________________ IPMID The interpersonal message identifier of the mail message for this outbound Service Notice. SUBMIT_DATE The date that the Service Notice was submitted to the mail transport. TOADDR The name/mail address of the recipient of the service notice. This is typically the to field found in the header of the mail message in which the service notice is contained. The same service notice can be sent to the recipient and the initiator if there is an update error. If this occurs, both names are listed in this field, separated by an ampersand sign (&). The recipient name is second. RETRIES Not applicable. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. TYPE The type of Service Notice created. (continued on next page) Transaction File D-9 Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_TC_(Tracking_Report_Sent)_______________ IPMID The interpersonal message identifier of the mail message for this outbound Tracking Report. SUBMIT_DATE The date that the Tracking Report was submitted to the mail transport. STEP_ID The identifier of the Routing Step in the master routing package for which the Tracking Report was sent. RECIP_ID The identifier of the Routing Recipient (within the Step) in the master routing package for which the Tracking Report was sent. TOADDR The name/mail address of the recipient of the tracking report. This is typically the to field found in the header of the mail message in which the tracking report is contained. RETRIES Not applicable. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. (continued on next page) D-10 Transaction File Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_TR_(Tracking_Request_Received)__________ IPMID The interpersonal message identifier of the mail message for this inbound Tracking Request. SUBMIT_DATE The date that the Tracking Request was submitted to the mail transport. STEP_ID The identifier of the Routing Step in the master routing package for which the Tracking Report was requested. RECIP_ID The identifier of the Routing Recipient (within the Step) in the master routing package for which the Tracking Report was requested. SENDER The name/mail address of the sender of the tracking request. This is typically the from field found in the header of the mail message in which the tracking request was contained. RETRIES Not applicable. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. (continued on next page) Transaction File D-11 Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_UP_(Update_Applied)_____________________ IPMID The interpersonal message identifier of the mail message for this inbound Update Request. SUBMIT_DATE The date that the Update file was submitted to the mail transport. STEP_ID The identifier of the Routing Step in the master routing package that contains the recipient who created the Update. RECIP_ID The identifier of the Routing Recipient (within the Step) in the master routing package who created the Update. SENDER The name/mail address of the sender of the update file. This is typically the from field found in the header of the mail message in which the update file was contained. RETRIES Not applicable. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. (continued on next page) D-12 Transaction File Transaction File D.2 Record Format Table_D-2_(Cont.)_Transaction_File_Variable-Length_Fields_ __________________________________________________________ Transaction_code:_DM_(Delete_Master)______________________ IPMID The interpersonal message identifier of the mail message for this inbound Delete Request. SUBMIT_DATE The date that the Delete request was processed by the Service Agent. SENDER The name/mail address of the sender of the Delete request. This is typically the from field found in the header of the mail message in which the update file was contained. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- length section. __________________________________________________________ Transaction_code:_RC_(Routing_Completed)__________________ DATE_ The date that the routing package was COMPLETED completed. MASTER_COPY The folder/docnum of the master routing package. FULL_NAME The full subscriber name of the initiator. This may have been truncated in the fixed- _______________length_section.____________________________ Transaction File D-13 E ________________________________________________________________ Modifying User Mail Destinations You must modify the mail destination of your system's ALL-IN-1 users who will be using TeamRoute for ALL-IN-1. The new destination should be TMR. To modify users' mail destination: 1. Type ALL-IN-1/USER=MANAGER and press . 2. Go to the Maintain User Accounts menu. 3. Select an ALL-IN-1 user's account using the Select option. 4. Select E to enter the Edit Account Details form. 5. Press NEXT SCREEN three times. The Edit Account Details-Continued (3) form is displayed. 6. Modify the Mail Destination field to TMR and press . The following message is displayed: Press RETURN if entry is complete, or EXIT to correct 7. Press . You are returned to the Maintain User Accounts menu. To continue modifying users' mail destinations, return to step 3 and repeat the process. Modifying User Mail Destinations E-1 ________________________________________________________________ Index A__________________________ C__________________________ A1TXL.TXL (text library) Carbon copy, 1-5 compiling and installing, Conventions, viii 5-5 Customizations Action control list restoring to new version setting, C-7 of product, 4-7 ALL-IN-1 text library saving existing, 4-5 compiling and installing, 5-5 D__________________________ Application Programming Data type Interface (API), 1-3 of attachments, 1-6 Application registration Detached process, C-1 file, 6-13 Diagnostic messages Attachments and service agent log definition of, 1-6 file, 6-11 to a template, 1-4 and service agent AUTOGEN transaction file, 6-11 changing system values error messages, C-5 to with, 2-8 C-8 B informational messages, ___________________________ C-1 Backing up the system disk, warning messages, C-2 to 2-10 C-5 Bypass request Disk space, 2-4 on deleted master, C-3 E__________________________ Error recovery of, 3-12 Index-1 Error condition not correctable, C-2 L__________________________ steps in correcting, C-2 License Error messages, C-5 to C-8 registering, 2-2 Log file F__________________________ for the service agent, File names, B-1 6-11 Files Logical names, B-6 installed, B-1 installed, B-1 Forms Logicals updating, 5-1 checking, 2-3 DEFAULT, 5-4 MAIN, 5-1 M__________________________ SM$MAIN2, 5-4 Mail SM_DEFAULT, 5-4 modifying users' G destination, E-1 ___________________________ MAILbus, 1-2 GBLPAGES calculating values for, N__________________________ 2-6 Notification messages, C-5 GBLSECTIONS calculating values for, O 2-6 ___________________________ OA$MTI_TRNS logical I__________________________ checking, 2-3 Informational messages, P C-1 ___________________________ Installation parameters additional languages, required values for, 2-6 3-12 Parameters after installing changing system values TeamRoute, 5-1 with AUTOGEN, 2-8 basic kit, 3-1 Personal template, 1-4 of TeamRoute, 3-1 Privileges, 2-4 preparations and Problems requirements, 2-1 determining and reporting procedure requirements, , 5-5 2-2 Process account quotas, sample, A-1 2-9 Processing requests, 1-4 Profile entry not found, C-7 Index-2 Service agent (cont'd) Q__________________________ log file, 6-11 Quotas states of, 6-10 process account, 2-9 stopping, C-1 user account, 2-9 submitting, 6-10, C-1 suspending, 6-10, C-1 R__________________________ transaction file, 6-11 Release notes, 2-1 unfound profile entry, Requests C-7 high-priority unknown or Signatures, 1-6 invalid, C-7 Site link files low-priority unknown or checking, 2-2 invalid, C-5 Software Role Prerequisite, 2-1 definition of, 1-5 State Routing, 1-6 of service agent, C-5 Routing copy, 1-5 Subscriber, 1-2 Routing list bypassing deleted definition of, 1-6 recipient, C-3 Routing package unfound profile entry, completed master, C-3 C-7 creation, 1-5 System disk definition of, 1-4 backing up, 2-10 events, 1-6 system parameters not TeamRoute, C-6 required values for, 2-6 processing requests, 1-4 T processing with errors, ___________________________ C-2 Teamform application, 1-4 routing, 1-6 Template, 1-3 to 1-4 tracking, 1-6 Templates tracking report, C-7 supplied, 1-4 types, 1-4 text library unfound attachments, C-6 compiling and installing, unfound data files, C-6 5-5 Run-Time Library (RTL), Tracking, 1-6 1-3 Tracking report, C-7 Transaction file, D-1 S__________________________ for service agent, 6-11 Scripts, 6-13 Transaction record Server domain, 1-2 fixed-length fields, D-2 Service agent format, D-2 and unknown or invalid variable-length fields, request, C-5, C-7 D-3 Index-3 Transaction types, D-1 Users See Subscriber U__________________________ Upgrading V__________________________ additional languages, 4-4 Variables, 1-4 defining TeamRoute VMSINSTAL logicals, 4-3 invoking, 3-1 installation procedure, requirements, 2-10 4-3 removing existing W__________________________ customizations, 4-5 Wait interval restoring existing changing default, 6-10 customizations, 4-7 Warning messages, C-2 to User account quotas, 2-9 C-5 Index-4