TeamRoute_for_ALL-IN-1________________________ Installation and System Management Guide Order Number: AA-PF29A-TE June 1992 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: This is a new manual. Operating System: ALL-IN-1 Version 2.4 or higher Software Version: TeamRoute for ALL-IN- 1 Version 1.0 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ June 1992 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. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1992. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, DECforms, DECnet, DECwindows, PATHWORKS, TeamRoute, VAX Notes, VAX VTX, VAX Basic, VAX C, VAX FMS, 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. ZK-5883 This document was prepared using VAX DOCUMENT, Version 2.0. ________________________________________________________________ Contents Preface.................................................. vii 1 Overview 1.1 Routing Package Processing...................... 1-1 1.2 Client/Server Model............................. 1-2 1.3 Programming Functions........................... 1-2 1.4 Templates....................................... 1-3 1.5 Routing Packages................................ 1-4 1.5.1 Roles ........................................ 1-5 1.5.2 Routing ...................................... 1-5 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 Installation Procedure Requirements............. 2-1 2.2.1 Modification of Source Files ................. 2-1 2.2.2 WordPerfect Integration on ALL-IN-1 System ... 2-2 2.2.3 Privileges and Disk Space .................... 2-3 2.2.4 System Parameters ............................ 2-3 2.2.4.1 Checking System Parameter Values........... 2-4 2.2.4.2 Calculating the Values for GBLPAGES and GBLSECTIONS................................ 2-5 2.2.4.3 Changing System Parameter Values with AUTOGEN.................................... 2-6 2.2.5 Process Account Quotas ....................... 2-7 2.2.6 VMSINSTAL Requirements ....................... 2-8 2.2.7 Backing Up Your System Disk .................. 2-9 iii 3 Installing TeamRoute for ALL-IN-1 3.1 Installation.................................... 3-1 3.2 Additional Language Installation................ 3-11 3.3 Error Recovery.................................. 3-12 3.4 Returning to Your Previous ALL-IN-1 System...... 3-12 4 After Installing TeamRoute 4.1 Manually Updating a Customized ALL-IN-1 System.. 4-1 4.2 Updating ALL-IN-1 Forms to Support TeamRoute.... 4-5 4.2.1 Updating Form MAIN ........................... 4-5 4.2.2 Updating Form DEFAULT ........................ 4-8 4.2.3 Updating Forms SM2 and SM_DEFAULT ............ 4-8 4.3 Determining and Reporting Problems.............. 4-9 5 Managing TeamRoute Services 5.1 Managing TeamRoute Accounts..................... 5-2 5.1.1 Using the TeamRoute Account Index and Menu ... 5-5 5.2 Managing the Service Agent...................... 5-6 5.2.1 Setting the Wait Interval .................... 5-10 5.2.2 Using the Service Agent Log File ............. 5-11 5.2.3 Using the Service Agent Transaction File ..... 5-11 5.2.4 Tracing Service Agent Activity ............... 5-12 5.3 Managing the Application Registration File...... 5-13 5.3.1 Using the Application Index and Menu ......... 5-15 5.4 Troubleshooting................................. 5-16 A Sample Installation B Files and Logical Names Installed on Your System B.1 File Names...................................... B-1 B.1.1 SYS$STARTUP ................................. B-2 B.1.2 SYS$HELP .................................... B-2 B.1.3 SYS$SHARE ................................... B-2 B.1.4 SYS$MESSAGE ................................. B-2 B.1.5 TMRA1$DATA_SHARE ............................ B-2 B.1.6 TMRA1$LIB_LLV ............................... B-3 B.1.7 TMRA1$LIB_SHARE ............................. B-4 B.1.8 TMRA1$SA_CODE ............................... B-7 B.1.9 TMRA1$SA_DATA ............................... B-9 iv B.1.10 TMRA1$SA_LOG ................................ B-9 B.1.11 TMRA1$A1 .................................... B-9 B.1.12 TMRA1$SITE_LIB_LLV .......................... B-9 B.1.13 TMRA1$BUILD_LLV ............................. B-10 B.1.14 TMRA1$BUILD_SHARE ........................... B-10 B.1.15 OA$LIB_SHARE ................................ B-10 B.2 Logical Names................................... 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 F Special Customizations Index Figures 1-2 Physical Template with Work-Item Copies ...... 1-3 5-1 TeamRoute System Management Menu ............. 5-1 5-2 Manage TeamRoute User Accounts Menu .......... 5-2 5-3 Manage TeamRoute Account Index Menu .......... 5-5 5-4 TeamRoute Manage Service Agents Menu ......... 5-7 5-5 Manage TeamRoute Application Registration File Menu.......................................... 5-13 5-6 Index Menu ................................... 5-15 v Tables 2-1 Minimum Required System Parameter Values ..... 2-4 2-2 Process Account Quotas for the Installing Account....................................... 2-7 5-1 Manage TeamRoute User Accounts Menu Options .. 5-4 5-2 Manage TeamRoute Account Index Menu Options .. 5-6 5-3 Manage Service Agents Menu Options ........... 5-7 5-4 Manage TeamRoute Application Registration File Menu Options.................................. 5-14 5-5 Index Menu Options ........................... 5-15 D-1 Transaction File Fixed-Length Fields ......... D-2 D-2 Transaction File Variable-Length Fields ...... D-3 vi ________________________________________________________________ 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 guides you through installation. o Chapter 4 identifies the post-installation requisites. o Chapter 5 tells you how to start and maintain TeamRoute services. o Appendix A contains a sample listing from a typical installation. o Appendix B lists the installation files. o Appendix C lists diagnostic messages. o Appendix D describes the transaction file. vii 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. o Appendix F describes how to customize TeamRoute for ALL-IN-1 systems if you have third-party applications not listed in Chapter 4, or asset packages that change either OASDF.BLI or OAGBL.BLI. 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 Figure 1 shows the conventions used in this manual: 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. 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.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-2 Overview Overview 1.4 Templates 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. 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 Overview 1-3 Overview 1.4 Templates - 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 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) 1-4 Overview Overview 1.5 Routing Packages 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. 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. Overview 1-5 Overview 1.5 Routing Packages 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. 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. 1-6 Overview 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 2.4 installed on your system before installing TeamRoute. 2.2 Installation Procedure Requirements This section and those that follow discuss various requirements for installing TeamRoute. The installation takes approximately 60 to 90 minutes. 2.2.1 Modification of Source Files Installation of TeamRoute for ALL-IN-1 requires that the following ALL-IN-1 source files be modified: o OAGBL.BLI o OASDF.BLI o OASYMMSG.MAR Preparing to Install TeamRoute for ALL-IN-1 2-1 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements If these files have not previously been changed by another ALL-IN-1 application, the TeamRoute changes to these files are automatically added to your system by the TeamRoute for ALL-IN-1 installation. However, if these files have previously been changed, you must manually merge the TeamRoute changes. The following Digital ALL-IN-1 applications also modify some of these source files and can conflict with TeamRoute: o ALL-IN-1 Shared File Cabinet Package (SFCP)-Uses OASDF.BLI o ALL-IN-1 DeskTop Services for DECwindows[TM]-Uses OASDF.BLI and OAGBL.BLI o WPS-PLUS Version 4.0 Option for ALL-IN-1 Version 2.4- Uses OASYMMSG.MAR o ALL-IN-1 Personal Assistant-Uses OASYMMSG.MAR o Electronic Authorization and Routing System for ALL-IN- 1 (EARS)-Uses OASYMMSG.MAR Other third party applications may also customize the source files. Before installing TeamRoute for ALL-IN-1 review which, if any of the above are installed on your ALL-IN-1 Version 2.4 system. If you have any of the applications described in this section on your ALL-IN-1 system, you should follow the procedures described in Chapter 4 after you install TeamRoute for ALL-IN-1. 2.2.2 WordPerfect Integration on ALL-IN-1 System If WordPerfect[TM] for ALL-IN-1 Integration is installed on your ALL-IN-1 system, you need to move the ALL-IN-1 SITELINK24.COM file. WordPerfect provides a SITELINK24.COM to the ALL-IN-1 OA$SITE_BUILD_SHARE directory. Before installing TeamRoute for ALL-IN-1, move SITELINK24.COM to OA$BUILD_SHARE if it is not already there. The TeamRoute for ALL-IN-1 installation can then automatically add TeamRoute link options to the file. 2-2 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements 2.2.3 Privileges and Disk Space 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. The free disk storage space requirements for installing TeamRoute for ALL-IN-1 include: o 32,000 free blocks on the kit working device o 11,000 free blocks on the device that will contain the TeamRoute for ALL-IN-1 files and service agent account (you will be prompted for information on this device during the installation) o 10,000 free blocks on the disk that contains your ALL- IN-1 directories To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 2.2.4 System Parameters Installing TeamRoute requires certain system parameter settings. Table 2-1 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. Preparing to Install TeamRoute for ALL-IN-1 2-3 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements Table_2-1_Minimum_Required_System_Parameter_Values________ System_Parameter___________Minimum_Value__________________ GBLPAGES[1] n + 900 GBLSECTIONS[1] n + 15 [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 Check system parameter values o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the VMS AUTOGEN command procedure o Set dynamic parameters (such as CLISYMTBL) with the VMS System Generation Utility (SYSGEN) 2.2.4.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility (SYSGEN): $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 2-1. The following example displays the value for the WSMAX system parameter: SYSGEN> SHOW WSMAX After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 2-4 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements 2.2.4.2 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 GLBPAGES and GBLSECTIONS system parameters. The n + 500 value for GBLPAGES and the n + 15 value for GBLSECTIONS in Table 2-1 indicate that you must have at least 500 unused global pages and 15 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: 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 500. If the number of unused pages is less than 500, 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 Preparing to Install TeamRoute for ALL-IN-1 2-5 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements 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.2.4.3 describes the procedures for increasing these values using AUTOGEN. Refer to the documentation for the VMS System Management Subkit for information on using AUTOGEN. 2.2.4.3 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 add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example: WSMAX = 1024 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 2-6 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements 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.2.5 Process Account Quotas The account you use to install TeamRoute must have suffi- cient quotas to enable you to perform the installation. Table 2-2 summarizes the process quotas required for the installation account. Table 2-2 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: Preparing to Install TeamRoute for ALL-IN-1 2-7 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements $ 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 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.2.6 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks whether: o You have set your default device and directory to SYS$UPDATE o You are logged in to a privileged account o You have adequate quotas for installation o DECnet is running o Any users are logged in to the system The VMSINSTAL requires that the installation account have a minimum of the following quotas: ASTLM = 24 BIOLM = 18 BYTLM = 40,000 DIOLM = 18 ENQLM = 30 FILLM = 20 2-8 Preparing to Install TeamRoute for ALL-IN-1 Preparing to Install TeamRoute for ALL-IN-1 2.2 Installation Procedure Requirements 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.2.7 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. 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. Preparing to Install TeamRoute for ALL-IN-1 2-9 3 ________________________________________________________________ Installing TeamRoute for ALL-IN-1 This chapter tells you how to install 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 files it has created up to that point and exits. You can then start the installation again. 1. Invoke VMSINSTAL. $ @SYS$UPDATE:VMSINSTAL TMRA1010 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: TMRA1010 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. Installing TeamRoute for ALL-IN-1 3-1 Installing TeamRoute for ALL-IN-1 3.1 Installation 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). 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. 3-2 Installing TeamRoute for ALL-IN-1 Installing TeamRoute for ALL-IN-1 3.1 Installation $ @SYS$UPDATE:VMSINSTAL TMRA1010 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.0 Beginning installation of TMRA1 V1.0 at 20:01 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 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. Installing TeamRoute for ALL-IN-1 3-3 Installing TeamRoute for ALL-IN-1 3.1 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. 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. 3-4 Installing TeamRoute for ALL-IN-1 Installing TeamRoute for ALL-IN-1 3.1 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:TMRA1010.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 To perform a full installation, type 1 and press RETURN, as shown: * What type of installation do you wish to perform [1]: 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. 6. Specify a password for the TMRA1SERVICE account. * Please enter a password for the TMRA1SERVICE account: Enter a password of between 8 and 31 characters. Help is available by typing a question mark (?). 7. Specify a unique UIC. * Please enter a UIC for the TMRA1SERVICE account (include brackets): Help to choose a UIC is available by typing a question mark (?). Installing TeamRoute for ALL-IN-1 3-5 Installing TeamRoute for ALL-IN-1 3.1 Installation 8. Specify a default device for TMRA1SERVICE account and TeamRoute files. * Enter the device to accommodate TeamRoute for ALL-IN-1 files: 9. 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 (ISO 3166) 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 (?). 10.Replace ALL-IN-1 source files. The TeamRoute for ALL-IN-1 application requires that customizations must be made to the following ALL-IN-1 source files. o OAGBL.BLI o OASDF.BLI o OASYMMSG.MAR If you are unsure if these source files have already been customized on your ALL-IN-1 system, answer NO to the following question. The TeamRoute modifications will then need to be applied manually. (See Chapter 4 for more information.) * Do you want the installation to replace these modules [NO]? If your ALL-IN-1 system has no customizations, answer YES to this question. The ALL-IN-1 source files will be updated automatically and ALL-IN-1 will be relinked during the TeamRoute installation. If you know that these source files have been changed by another ALL-IN- 1 application, answer NO and update the source files manually. 3-6 Installing TeamRoute for ALL-IN-1 Installing TeamRoute for ALL-IN-1 3.1 Installation The following Digital ALL-IN-1 applications modify some of the source files and can conflict with TeamRoute: o ALL-IN-1 Shared File Cabinet Package (SFCP)-Uses OASDF.BLI o ALL-IN-1 DeskTop Services for DECwindows-Uses OASDF.BLI and OAGBL.BLI o WPS-PLUS Version 4.0 Option for ALL-IN-1 Version 2.4-Uses OASYMMSG.MAR o ALL-IN-1 Personal Assistant-Uses OASYMMSG.MAR o Electronic Authorization and Routing System for ALL-IN-1 (EARS)-Uses OASYMMSG.MAR 11.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]: 12.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. 13.Purge files. * Do you want to purge files replaced by this installation [YES]? 14.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. 15.Answer ALL-IN-1 Link questions. Installing TeamRoute for ALL-IN-1 3-7 Installing TeamRoute for ALL-IN-1 3.1 Installation If you chose to automatically update the ALL-IN-1 source files described in step 8, you are required to answer the ALL-IN-1 link questions. 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 System Management Guide. 16.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. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. 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 If you chose to automatically update the ALL-IN-1 source files, ALL-IN-1 is relinked. o ALL-IN-1 forms are updated. 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 4 if the installation procedure reports that a manual update is required. 3-8 Installing TeamRoute for ALL-IN-1 Installing TeamRoute for ALL-IN-1 3.1 Installation TeamRoute for ALL-IN-1 modifies forms MAIN, DEFAULT, SM2 and SM_DEFAULT. The installation will display one of the following messages for each of these forms: %TMRA1-I-NOCUSTOM, Element MAIN.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. %TMRA1-W-CUSTOM, Element MAIN.FRM has already been modified -TMRA1-W-CUSTOM, and 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. After these informational messages the following message is displayed: %VMSINSTAL-I-MOVEFILES, Files will be moved to their target directories... 17.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 Installing the new ALL-IN-1 images. This is done only if the installation was able to update the ALL-IN-1 source files described in step 10. 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 to reflect the customization of forms MAIN, DEFAULT, SM2 and SM_DEFAULT (this is done for each form based on whether the installation was able to automatically update the form or not). o Running the TeamRoute for ALL-IN-1 startup procedure. This procedure defines all TeamRoute for ALL-IN-1 logicals, compiles and installs the TeamRoute form libraries, and starts the service agent. If the installation did not update the Installing TeamRoute for ALL-IN-1 3-9 Installing TeamRoute for ALL-IN-1 3.1 Installation ALL-IN-1 source files, then only the logicals are defined. 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 12. 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 4. 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. Please update form MAIN If the installation did not update the ALL-IN-1 source files, the following message is displayed: You chose not to automatically update the ALL-IN-1 source files OAGBL, OASDF, and OASYMMSG.MAR. Please ensure that you follow instructions in chapter 4 of the installation guide to add the TeamRoute changes to your ALL-IN-1 system. 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. 18.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. 3-10 Installing TeamRoute for ALL-IN-1 Installing TeamRoute for ALL-IN-1 3.1 Installation 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. 19.End the installation procedure. Installation of TMRA1 V1.0 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. 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. However, for step 5, choose installation type (2). The installation of additional languages asks fewer questions and the process take less time. Installing TeamRoute for ALL-IN-1 3-11 Installing TeamRoute for ALL-IN-1 3.3 Error Recovery 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. 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. 3.4 Returning to Your Previous ALL-IN-1 System If you chose to automatically update the ALL-IN-1 source files, after the installation of TeamRoute, you may find that site customizations from your previous ALL-IN-1 system do not function. In this situation, you can return to your previous ALL-IN-1 system. The TeamRoute installation does not purge the old ALL-IN-1 main (OA$LIB_SHARE:OA$MAIN.EXE) or local language image (SYS$SHARE:OA$LLVlanguage.EXE). To restore your previous ALL-IN-1 system, delete the new system images. You also should remove the TeamRoute startup commands from OA$SITE_BUILD_SHARE:A1V24_SITE_START.COM and the TeamRoute link options from OA$BUILD_SHARE:SITELINK24.COM. Then, perform an ALL-IN-1 startup to install the old images. 3-12 Installing TeamRoute for ALL-IN-1 Installing TeamRoute for ALL-IN-1 3.4 Returning to Your Previous ALL-IN-1 System You can reinstall TeamRoute again at a convenient time and manually update the source files so that your site customizations can be preserved. After you successfully install TeamRoute, you may want to purge the old ALL-IN-1 images to regain disk space. Installing TeamRoute for ALL-IN-1 3-13 4 ________________________________________________________________ After Installing TeamRoute If you were instructed to do so by the installation, after installing TeamRoute, you should complete the operations listed in the following steps. 1. Update your customized ALL-IN-1 system. 2. Update ALL-IN-1 forms to support TeamRoute. 4.1 Manually Updating a Customized ALL-IN-1 System The installation of TeamRoute for ALL-IN-1 modifies the following ALL-IN-1 source files: o OAGBL.BLI o OASDF.BLI o OASYMMSG.MAR The following Digital ALL-IN-1 applications also modify some of the same source files: o ALL-IN-1 Shared File Cabinet Package (SFCP)-Uses OASDF.BLI o ALL-IN-1 DeskTop Services for DECwindows-Uses OASDF.BLI and OAGBL.BLI o WPS-PLUS Version 4.0 Option for ALL-IN-1 Version 2.4- Uses OASYMMSG.MAR o ALL-IN-1 Personal Assistant-Uses OASYMMSG.MAR o Electronic Autorization and Routing System for ALL-IN-1 (EARS)-Uses OASYMMSG.MAR If you have any of these products installed you should have chosen not to automatically update the ALL-IN-1 source files during the TeamRoute Installation. After Installing TeamRoute 4-1 After Installing TeamRoute 4.1 Manually Updating a Customized ALL-IN-1 System The instructions that follow explain how to add TeamRoute customizations to an ALL-IN-1 system with one or more of the above applications. 1. Log in to the ALL-IN-1 Manager's account and set default directory to OA$SITE_BUILD_SHARE $ SET DEFAULT OA$SITE_BUILD_SHARE If OAGBL.BLI, OASDF.BLI, or OASYMMSG.MAR have been customized previously, they should reside in OA$SITE_ BUILD_SHARE. 2. If one or more of these three files are not located in OA$SITE_BUILD_SHARE, they have not been previously customized. For any of these files not previously customized, select the appropriate procedure from the following list: o For OAGBL.BLI, do the following: $ COPY TMRA1$BUILD_SHARE:OAGBL.BLI_AFTER_TMR OAGBL.BLI $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR - TMRA1$BUILD_SHARE:OAGBL.OBJ_AFTER_TMR o For OASDF.BLI, do the following: $ COPY TMRA1$BUILD_SHARE:OASDF.BLI_AFTER_TMR OASDF.BLI $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR - TMRA1$BUILD_SHARE:OASDF.OBJ_AFTER_TMR o For OASYMMSG.MAR, do the following: $ COPY TMRA1$BUILD_SHARE:OASYMMSG.MAR_AFTER_TMR OASYMMSG.MAR $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR - TMRA1$BUILD_SHARE:OASYMMSG.OBJ_AFTER_TMR 3. The TeamRoute for ALL-IN-1 installation provides a combination of prebuilt object files for OAGBL and OASDF. These files allow TeamRoute to be included on a system that has previously been installed with the ALL-IN-1 Shared File Cabinet Package (SFCP), ALL-IN-1 DeskTop Services for DECwindows, or both products. o If your ALL-IN-1 system has ALL-IN-1 DeskTop Services for DECwindows installed, replace the version of OAGBL.OBJ that includes both the TeamRoute changes and ALL-IN-1 DeskTop Services 4-2 After Installing TeamRoute After Installing TeamRoute 4.1 Manually Updating a Customized ALL-IN-1 System for DECwindows changes. Use the following command lines: $ COPY TMRA1$BUILD_SHARE:OAGBL.BLI_AFTER_TMR_MICA OAGBL.BLI $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR.OLB - TMRA1$BUILD_SHARE:OAGBL.OBJ_AFTER_TMR_MICA You also need to replace the version of OASDF.OBJ that includes both the TeamRoute changes and ALL-IN- 1 DeskTop Services for DECwindows changes. Use the following command lines: $ COPY TMRA1$BUILD_SHARE:OASDF.BLI_AFTER_TMR_MICA OASDF.BLI $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR.OLB - TMRA1$BUILD_SHARE:OASDF.OBJ_AFTER_TMR_MICA o If your ALL-IN-1 system has ALL-IN-1 Shared File Cabinet Package (SFCP) installed, replace the version of OASDF.OBJ that includes both the TeamRoute changes and SFCP changes. Use the following command lines: $ COPY TMRA1$BUILD_SHARE:OASDF.BLI_AFTER_TMR_SFCP OASDF.BLI $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR.OLB - TMRA1$BUILD_SHARE:OASDF.OBJ_AFTER_TMR_SFCP o If your ALL-IN-1 system has both ALL-IN-1 DeskTop Services for DECwindows and SFCP installed, replace the version of OASDF.OBJ that includes the TeamRoute, ALL-IN-1 DeskTop Services for DECwindows, and SFCP changes. Use the following command lines: $ COPY TMRA1$BUILD_SHARE:OASDF.BLI_AFTER_TMR_MICA_SFCP OASDF.BLI $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR.OLB - TMRA1$BUILD_SHARE:OASDF.OBJ_AFTER_TMR_MICA_SFCP 4. If your ALL-IN-1 system has any of the following software installed, you need to manually update OASYMMSG.MAR. o WPS-PLUS Version 4.0 Option for ALL-IN-1 Version 2.4 o ALL-IN-1 Personal Assistant o Electronic Autorization and Routing System for ALL- IN-1 (EARS) After Installing TeamRoute 4-3 After Installing TeamRoute 4.1 Manually Updating a Customized ALL-IN-1 System To update OASYMMSG.MAR, edit it from OA$SITE_BUILD_SHARE. Include TMRA1$BUILD_SHARE:OASYMMSG.TMR_EXTRACT into the $msg_table table in strict alphabetical order. On most systems this is after the following line: $msg TMRE_MORE_HRD_CHOICE ; Compile a new OASYMMSG.OBJ by typing the following command: $ MACRO OASYMMSG Replace OASYMMSG in the ALL-IN-1 object library by typing the following command: $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR.OLB OASYMMSG 5. If your ALL-IN-1 system has other third party applications or asset packages that change either OASDF.BLI or OAGBL.BLI, you need a BLISS compiler to merge the TeamRoute changes. See Appendix F for more information. 6. Put a copy of the TeamRoute message file in the ALL-IN- 1 object library, using the following command: $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR - TMRA1$BUILD_LLV:OA$TMR$MESSAGES_NOTEXT.OBJ 7. If you have a customized site link file, the instal- lation automatically adds the correct link options to the ALL-IN-1 site link files SITELINK24.COM and SITELLV.COM. 8. Relink ALL-IN-1 using the using the following commands: $ SET DEFAULT OA$BUILD_SHARE $ @A1LNKDRV The procedure A1LNKDRV asks the same questions as those that were asked when you installed ALL-IN-1. Default answers will be provided which are the same as those you specified during the ALL-IN-1 installation. If you accept the default answers, press in answer to each question. You can display help for any question by entering a question mark (?). For further information on relinking ALL-IN-1, see the ALL-IN-1 Management Guide. 4-4 After Installing TeamRoute After Installing TeamRoute 4.1 Manually Updating a Customized ALL-IN-1 System 9. When A1LNKDRV completes, it leaves a set of image files in the OA$BUILD_SHARE directory. Only the main ALL-IN-1 image OA$MAIN.EXE and the language image (if you linked a multilingual system) OA$LLVENGLISH.EXE are modified by the TeamRoute for ALL-IN-1 installation. Copy these images to their target directories with the following commands: $ COPY OA$MAIN.EXE OA$LIB_SHARE:OA$MAIN.EXE/LOG $ COPY OA$LLVENGLISH.EXE SYS$COMMON:[SYSLIB]OA$LLVENGLISH.EXE/LOG Make sure these images are owned by the ALL-IN-1 manager's VMS account and that they have W:RE access. When you have copied the images you need, run the ALL- IN-1 startup procedure to install them, as shown: $ @SYS$MANAGER:A1V24START.COM OA$DATA_SHARE: This command also acts on the contents of the SITE start command procedures to start TeamRoute for ALL-IN- 1. After copying the new ALL-IN-1 images to their correct locations and restarting ALL-IN-1, you can purge the old images to regain disk space. You also can delete images created by the link from OA$BUILD_SHARE. 4.2 Updating ALL-IN-1 Forms to Support TeamRoute 4.2.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, following the steps listed: 1. Type ALLIN1/USER=MANAGER and press . 2. Select CM to enter customization management. 3. Type SEL and press . Complete the fields as follows and press : Name: MAIN Type: FRM Language: ENGLISH After Installing TeamRoute 4-5 After Installing TeamRoute 4.2 Updating ALL-IN-1 Forms to Support TeamRoute 4. Type R and press to read the entry for the form. Look at the field labeled Live:, it will either be Y or N. Press to return to the menu. 5. If the form is Live then type CFL and press to copy the form from the live area to the development area. 6. Type E and press to edit the form. 7. Type S and press to edit the screen image. 8. Select LAYOUT and using the FMS editor add an option for TeamRoute, as shown: TMR TeamRoute 9. Ater the text, type two spaces then create a field of 30 characters in length. This will display the number of new TeamRoute routing packages. 10.Exit the layout by typing GOLD-7 to return to the Form Editor menu. 11.Type ASSIGN and press to assign the name TMR_ COUNT to the new field. Mark the field as Display Only. 12.After you have assigned the field name, return to the Form Editor menu and type EXIT and press . 13.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) 14.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 . 15.Select E to edit the form. 16.Select ND to edit the form's named data Update the named data on the form with the following information (the bolded code indicates new named data): 4-6 After Installing TeamRoute After Installing TeamRoute 4.2 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 TMRA1$LIB:TMR$CL_OPEN_LIBRARY" ;;OA$_TMR_MO_TEAMROUTE;; FORM TMR$MAIN$MENU 17.Exit the editor. Ignore the library messages that appear. 18.Press when the message Press RETURN to continue appears The Enter Details of Change to Element form appears. Complete this form as you wish and press . The message Element modified appears. 19.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; this will be done by the ALL-IN-1 Manager 20.Select SM to enter the ALL-IN-1 Management menu. 21.Select CSZ to enter the System Customization Management menu. 22.Select PME to enter the Process Marked Elements form. 23.Select ML to move the MAIN form to the live area. The following message appears: Element moved to live area by MANAGER at hh:mm on dd-mmm-yyyy 24.Press to return to the System Customization Management menu. A warning message appears stating that you have changed forms libraries and advising you to select the PCF (Precompile a form library) option. After Installing TeamRoute 4-7 After Installing TeamRoute 4.2 Updating ALL-IN-1 Forms to Support TeamRoute 25.Press . 26.Select PCF to precompile the form library. 27.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] 28.Select Y. The following message appears: OA$SITE_LIB_ENGLISH:SITEOAFORM.FLB precompiled and installed 29.Type EX and press to exit ALL-IN-1. 30.Log out of the ALLIN1 account. 4.2.2 Updating Form DEFAULT See Section 4.2.1. Follow the instructions in steps 1 through 5 to select form DEFAULT for editing. Then, follow the instructions in steps 15 through 30. For step 16, add the following named data after the line with the word MENU. ;;OA$_TMR_MO_TEAMROUTE;; DO TMRA1$LIB:TMR$CL_OPEN_LIBRARY\FORM TMR$MAIN$MENU 4.2.3 Updating Forms SM2 and SM_DEFAULT See Section 4.2.1. Follow the instructions in steps 1 through 8 to select form SM2 for editing and add the TeamRoute management option to the screen image, as shown: MTS Manage TeamRoute system Follow the instructions in steps 12 through 19. For step 16, add the following named data at the end: ;;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 SM2. To complete the operation, follow the instructions in steps 20 through 30. 4-8 After Installing TeamRoute After Installing TeamRoute 4.3 Determining and Reporting Problems 4.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. See the release notes for TeamRoute for information on how to submit an SPR. After Installing TeamRoute 4-9 5 ________________________________________________________________ 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 or administrator privileges to manage TeamRoute services. 3. Select SM to display the ALL-IN-1 Management menu. 4. Select MTS (Manage TeamRoute system) from the ALL-IN-1 Management menu. TeamRoute displays its system management menu, as shown in Figure 5-1. Figure 5-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 5-1 Managing TeamRoute Services 5.1 Managing TeamRoute Accounts 5.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 5-2: Figure 5-2 Manage TeamRoute User Accounts Menu ____________________________________________________________________________ Manage TeamRoute User Accounts SEL Select Account: SMITH C Create E Edit D Delete ENA Enable TeamRoute account P Print DIS Disable TeamRoute account R Read I Index RI Recall index ____________________________________________________________________________ 5-2 Managing TeamRoute Services Managing TeamRoute Services 5.1 Managing TeamRoute Accounts Table 5-1 describes the options available on the Manage TeamRoute User Accounts menu. Managing TeamRoute Services 5-3 Managing TeamRoute Services 5.1 Managing TeamRoute Accounts Table_5-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 press without a value in the account name 5-4 Managing field,uallSTeamRoute account records are displayed. If you enter an account name, only that record is displayed. See Section 5.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.____________ Managing TeamRoute Services 5.1 Managing TeamRoute Accounts 5.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 5-3. Figure 5-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 5-5 Managing TeamRoute Services 5.1 Managing TeamRoute Accounts Table 5-2 describes the options available on the Manage TeamRoute Account Index menu. Table_5-2_Manage_TeamRoute_Account_Index_Menu_Options_____ Option_Description________________________________________ C,E,D,PFunctions the same as on the Manage TeamRoute Application Registration File menu (see Table 5-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.______________ 5.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 5-4. 5-6 Managing TeamRoute Services Managing TeamRoute Services 5.2 Managing the Service Agent Figure 5-4 TeamRoute Manage Service Agents Menu ------------------------------------------------------------------------------ Bob Smith 30-Dec-1991 Manage Service Agents Account Name: TMRA1SA1 SEL Select Number: 001 Current Date: 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 5-3 describes the options available on the Manage Service Agents menu. Table_5-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 5-7 Managing TeamRoute Services 5.2 Managing the Service Agent Table_5-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 Return 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 5.2.1). Press Return 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 5.2.2 for more information. PL Prints the log file. (continued on next page) 5-8 Managing TeamRoute Services Managing TeamRoute Services 5.2 Managing the Service Agent Table_5-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 5.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 5-9 Managing TeamRoute Services 5.2 Managing the Service Agent Table_5-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.______ 5.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. 5-10 Managing TeamRoute Services Managing TeamRoute Services 5.2 Managing the Service Agent 5.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. 5.2.3 Using the Service Agent Transaction File The service agent maintains a transaction file that contains information about its routine processing. By default, the transaction file is stored in a directory with the logical name TMRA1$SA_DATA. The name of the transaction 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 5-3). Managing TeamRoute Services 5-11 Managing TeamRoute Services 5.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. 5.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" 5-12 Managing TeamRoute Services Managing TeamRoute Services 5.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. 5.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 5-5. Figure 5-5 Manage TeamRoute Application Registration File Menu _______________________________________________________________________ Manage TeamRoute Application Registration File SEL Select Application: DEFAULT Description: Default if variables C Create Script: TMRA1$LIB:TMRA1$DEFAULT_APPL.SCR E Edit D Delete P Print R Read I Index ________________________________________________________________________ Managing TeamRoute Services 5-13 Managing TeamRoute Services 5.3 Managing the Application Registration File Table 5-4 describes the options available on the Manage TeamRoute Application Registration File menu. Table 5-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 Return 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 Return, all application records are displayed. If you enter a name, only that record is _______displayed._See_Section_5.3.1_for_more_information._ 5-14 Managing TeamRoute Services Managing TeamRoute Services 5.3 Managing the Application Registration File 5.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 5-6. Figure 5-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 5-5 describes the options available on the Manage TeamRoute Application Registration File Index menu. Table_5-5_Index_Menu_Options______________________________ Option___Description______________________________________ C,E,D,P,RFunctions the same as on the Manage TeamRoute Application Registration File menu (see Table 5-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 5-15 Managing TeamRoute Services 5.4 Troubleshooting 5.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 5.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 System 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. 5-16 Managing TeamRoute Services Managing TeamRoute Services 5.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 5-17 A ________________________________________________________________ Sample Installation This appendix contains two sample installation listings. In the first sample, TeamRoute for ALL-IN-1 is installed for only one language. The second sample listing shows the installation of an additional language. In these 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. VAX/VMS Software Product Installation Procedure V5.4 It is 16-MAY-1992 at 15:50. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: _RTA2: * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? y The following products will be processed: TMRA1 V1.0 Beginning installation of TMRA1 V1.0 at 15:50 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above Sample Installation A-1 Sample Installation * Select option [2]: 4 * Do you want to continue the installation [NO]? yes %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ******************************************************************************** TMRA1 V1.0 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 * What type of installation do you wish to perform [1]: ? Select the number that describes the type of installation required. 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 V2.4 system. You can only install a TeamRoute for ALL-IN-1 additional language on an ALL-IN-1 V2.4 system which already has the language you propose to add installed. * 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 V2.4 IOS installed and started. %TMRA1-I-CHKLOG, Checking ALL-IN-1 logicals that this installation will use. %TMRA1-I-CKSPA1, Checking for sufficient free space on the ALL-IN-1 disk. %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. A-2 Sample Installation Sample Installation * Please enter a password for the TMRA1SERVICE account: Enter a password of between 8 and 31 characters in length. The password must only be composed of alphanumeric characters, dollar signs, and underscores. * Please enter a password for the TMRA1SERVICE account: * Please confirm the password you have specified: * Please enter a UIC for the TMRA1SERVICE account (include brackets): ? 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]? yes Owner Username UIC Account Privs Pri Directory SYSTEM MANAGER SYSTEM [1,4] SYSTEM All 4 SYS$SYSROOT:[SYSMGR] FIELD SERVICE FIELD [1,10] FIELD All 4 SYS$SYSROOT:[SYSMAINT] MBMANAGER MBMANAGER [2,6] All 4 SYS$SYSDEVICE:[MB$.TOOLS] MBMANAGER MBWATCH [2,6] All 4 SYS$SYSDEVICE:[MB$.MB.MB$SCRATCH] MBMANAGER MRNET [2,6] All 4 SYS$SYSDEVICE:[MB$.MR.SCR] MBMANAGER MRMANAGER [2,6] All 4 SYS$SYSDEVICE:[MB$.MR.WRK] MBMANAGER DDSNET [2,6] All 4 SYS$SYSDEVICE:[MB$.DDS.SCR] ALLIN1 [3,6] All 4 USER1:[ALLIN1] DEFAULT [200,200] Normal 4 Disuser NEWS$SERVER [333,333] Normal 4 Disuser MIRRO$SERVER DEFAULT MIRRO$SERVER [376,367] DECNET Normal 4 SYS$SPECIFIC:[MIRRO$SERVER] VPM$SERVER DEFAULT VPM$SERVER [376,370] DECNET Normal 4 SYS$SPECIFIC:[VPM$SERVER] NML$SERVER DEFAULT NML$SERVER [376,371] DECNET Normal 4 SYS$SPECIFIC:[NML$SERVER] PHONE$SERVER DEFAULT PHONE$SERVER [376,372] DECNET Normal 4 SYS$SPECIFIC:[PHONE$SERVER] FAL$SERVER DEFAULT FAL$SERVER [376,373] DECNET Normal 4 SYS$SPECIFIC:[FAL$SERVER] MAIL$SERVER DEFAULT MAIL$SERVER [376,374] DECNET Normal 4 SYS$SPECIFIC:[MAIL$SERVER] DECNET DEFAULT DECNET [376,376] DECNET Normal 4 SYS$SPECIFIC:[DECNET] NOTES SERVER NOTES$SERVER [376,377] DECNET Normal 4 SYS$SYSDEVICE:[NOTES$SERVER] Chris Tostevin-Hall CHRIS [444,1] Normal 4 USER1:[EBDA1_USERS.CHRIS] Stuart Maurice MAURICE [444,446] Normal 4 USER1:[MAURICE] Maurice Stuart STUART [444,447] Normal 4 USER1:[EBDA1_USERS.STUART] Sample Installation A-3 Sample Installation * Please enter a UIC for the TMRA1SERVICE account (include brackets): [200,202] * Enter the device to accommodate TeamRoute for ALL-IN-1 files: ? Enter the name of the disk which will hold the TeamRoute files and the Service Agent account files. If possible a device that does NOT have disk quotas enabled should be chosen. However, if this is not possible, then the installation procedure will assign a disk quota of 50000 blocks to the service agent. Note that if the service agent runs out of disk quota, it will be unable to receive and process document updates, and the routing of all documents initiated from this node/cluster will be stalled. * Enter the device to accommodate TeamRoute for ALL-IN-1 files: user1 %TMRA1-I-CHKQUO, Determining whether disk quotas enabled on USER1:... %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 TMRA1LEN010.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-CHKLIC, Checking product licence is registered and loaded %TMRA1-I-RUNA1, Running ALL-IN-1 to obtain VMS account of MANAGER... A-4 Sample Installation Sample Installation **IMPORTANT** The TeamRoute for ALL-IN-1 application requires that customizations are made to the following ALL-IN-1 source files:- OAGBL.BLI, OASDF.BLI and OASYMMSG.MAR. If you are unsure whether these files have already been customized on your ALL-IN-1 system, answer NO to the following question. The TeamRoute modifications will then need to be applied manually. See the section "After Installing TeamRoute" in the Installation Guide. The following products will conflict with TeamRoute:- ALL-IN-1 Shared File Cabinet Package ( OASDF.BLI ) ALL-IN-1 DeskTop for VMS DECwindows ( OASDF.BLI & OAGBL.BLI ) WPS-PLUS V4.0 Option for ALL--IN--1 V2.4 ( OASYMMSG.MAR ) ALL-IN-1 Personal Assistant ( OASYMMSG.MAR ) Electronic Authorization and Routing System ( OASYMMSG.MAR ) * Do you want the installation to replace these modules [NO]? yes 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]: * Do you want all ALL-IN-1 users to be registered as TeamRoute users [YES]? ? TeamRoute for ALL-IN-1 holds a list of registered TeamRoute subscribers in a profile data file. If you answer YES to the question all existing ALL-IN-1 users will be registered and enabled as TeamRoute subscribers. If you answer NO, no TeamRoute subscribers will be registered. The profile can be modified by using the Manage TeamRoute System (MTS) management interface to restrict or grant TeamRoute authorization. * 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. Sample Installation A-5 Sample Installation %TMRA1-I-SAVED_ANS_1, Default answers are being taken from saved answers file %TMRA1-I-SAVED_ANS_2, which was created on 18-MAR-1992 17:30:33.64 * Do you want to incorporate DATATRIEVE [NO]? %TMRA1-I-DTRNOLINK, DATATRIEVE will not be linked with ALL-IN-1 * Do you want to incorporate WPS-PLUS [YES]? %TMRA1-I-WPSLINK, The WPS-PLUS editor will be linked with ALL-IN-1 * Do you want to incorporate ACMS [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-MRVEROK, Your Message Router version is V3.1 %TMRA1-I-DDS, DDS support will be included in the link %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. %TMRA1-I-CHECKDIR, 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-ADDFORMS, Inserting forms into TMRA1SERVICE USER form library. %TMRA1-I-INSTA1FI, Installing TMRA1SERVICE ALL-IN-1 files. %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-UPDOLB, Updating ALL-IN-1 Object library OALIBR.OLB... A-6 Sample Installation Sample Installation %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 Linking the Background Formatter Linking the TM Server Linking the OA$SUBMIT image Linking the MAILCOUNT 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 SM2.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 SM2 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 * ************************************************************** Sample Installation A-7 Sample Installation %TMRA1-I-POSTINST, Performing post installation tasks... %TMRA1-I-SETACL, Setting ownership ACLs on TeamRoute development files... %TMRA1-I-RUNA1, Running ALL-IN-1 to create a profile entry for the -TMRA1-I-RUNA1, Service Agent and update ALL-IN-1 FORMAT and CM data sets... %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_ELEMENTS.DAT with new elements..." %OA-I-LASTLINE, "Updating ALL-IN-1 CM data sets..." %OA-I-LASTLINE, "Compiling and installing OA$SITE_LIB_ENGLISH:SITEOAFORM" SYSTEM finished using ALL-IN-1 at 16-MAY-1992 16:41 %TMRA1-I-START, Running the TeamRoute for ALL-IN-1 startup... Running startup for TeamRoute V1.0 for ALL-IN-1 V2.4... Installing TeamRoute images Defining TeamRoute language independent logical names Defining TeamRoute ENGLISH language logical names Running ALL-IN-1 to compile TeamRoute ENGLISH form libraries... %OA-I-LASTLINE, "Compiling and installing TMRA1$LIB_LLV:TMRFLB" %OA-I-LASTLINE, "Compiling and installing TMRA1$LIB_LLV:TMRMGR" SYSTEM finished using ALL-IN-1 at 16-MAY-1992 16:42 Starting the TeamRoute Service Agent... %TMRA1-I-RUNA1, Running ALL-IN-1 to populate the TeamRoute profile... SYSTEM finished using ALL-IN-1 at 16-MAY-1992 16:42 ************************************************************** * 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 VMSINSTAL procedure done at 16:43 A-8 Sample Installation Sample Installation The following sample listing shows the installation of an additional language. VAX/VMS Software Product Installation Procedure V5.4 It is 17-MAY-1992 at 10:45. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: _RTA2: * 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: TMRA1 V1.0 Beginning installation of TMRA1 V1.0 at 10:45 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? yes %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ******************************************************************************** TMRA1 V1.0 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 Sample Installation A-9 Sample Installation * What type of installation do you wish to perform [1]: 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 V2.4 IOS installed and started. %TMRA1-I-CHKLOG, Checking ALL-IN-1 logicals that this installation will use. %TMRA1-I-CKSPA1, Checking for sufficient free space on the ALL-IN-1 disk. %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): du %TMRA1LBR-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-CHKLIC, Checking product licence is registered and loaded %TMRA1-I-RUNA1, Running ALL-IN-1 to obtain VMS account of MANAGER... %TMRA1-I-A1LNKQ, ALL-IN-1 link questions will now be asked. During your first language installation you have elected 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 have elected to integrate WPS-PLUS. It means that you can access WPS-PLUS as an additional editor from your ALL-IN-1 as well. During your first language installation you have elected 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 user through the Set Working Conditions option. Alphanumeric Date Numeric Date A-10 Sample Installation Sample Installation 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 * 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 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. %TMRA1-I-CHECKDIR, Creating TMRA1SERVICE directory and subdirectories... %TMRA1-I-INSTLANG, Installing GERMAN language specific files... %TMRA1-I-ADDHLP, Adding TeamRoute Help libraries to OAHELP... %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. %TMRA1-I-NOCUSTOM, Element DEFAULT.FRM has not previously been modified. -TMRA1-I-NOCUSTOM, This element will be automatically updated. Sample Installation A-11 Sample Installation %TMRA1-I-NOCUSTOM, Element SM2.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 SM2 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-POSTINST, Performing post installation tasks... %TMRA1-I-SETACL, Setting ownership ACLs on TeamRoute development files... %TMRA1-I-RUNA1, Running ALL-IN-1 to update CM_SDC_ELEMENTS.DAT -TMRA1-I-RUNA1, with GERMAN TeamRoute ALL-IN-1 Client elements... %OA-I-LASTLINE, "Updating ALL-IN-1 CM data sets..." %OA-I-LASTLINE, "Compiling and installing OA$SITE_LIB_GERMAN:SITEOAFORM" SYSTEM finished using ALL-IN-1 at 17-MAY-1992 11:02 %TMRA1-I-START, Running the TeamRoute for ALL-IN-1 startup... Running startup for TeamRoute V1.0 for ALL-IN-1 V2.4... Installing TeamRoute images Defining TeamRoute language independent logical names Defining TeamRoute ENGLISH language logical names Running ALL-IN-1 to compile ENGLISH TeamRoute form libraries... %OA-I-LASTLINE, "Compiling and installing TMRA1$LIB_LLV:TMRFLB" %OA-I-LASTLINE, "Compiling and installing TMRA1$LIB_LLV:TMRMGR" SYSTEM finished using ALL-IN-1 at 17-MAY-1992 11:03 Starting the TeamRoute Service Agent... Running startup for TeamRoute V1.0 for ALL-IN-1 V2.4... Defining TeamRoute GERMAN language logical names Running ALL-IN-1 to compile GERMAN TeamRoute form libraries... %SYSTEM-E-NOSUCHSEC, no such (global) section %OA-I-LASTLINE, "Compiling and installing TMRA1$LIB_LLV:TMRFLB" %SYSTEM-E-NOSUCHSEC, no such (global) section %OA-I-LASTLINE, "Compiling and installing TMRA1$LIB_LLV:TMRMGR" A-12 Sample Installation Sample Installation SYSTEM finished using ALL-IN-1 at 17-MAY-1992 11:03 ************************************************************** * 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.0 completed at 11:04 VMSINSTAL procedure done at 11:18 Sample Installation A-13 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. B.1 File Names This section lists the locations on your system where files are created when you install TeamRoute: o SYS$STARTUP o SYS$HELP o SYS$SHARE o SYS$MESSAGE o TMRA1$DATA_SHARE o TMRA1$LIB_LLV o TMRA1$LIB_SHARE o TMRA1$SA_CODE o TMRA1$SA_DATA o TMRA1$SA_LOG o TMRA1$A1 o TMRA1$SITE_LIB_LLV o TMRA1$BUILD_LLV o TMRA1$BUILD_SHARE o OA$LIB_SHARE Files and Logical Names Installed on Your System B-1 Files and Logical Names Installed on Your System B.1 File Names The following sections list the files created at a particular location. B.1.1 SYS$STARTUP This section lists the files created in location SYS$STARTUP when you install TeamRoute: o TMRA1$STARTUP.COM B.1.2 SYS$HELP This section lists the files created in location SYS$HELP when you install TeamRoute: o TMR$TCU_HELP.HLB o TMRA1010.RELEASE_NOTES B.1.3 SYS$SHARE This section lists the files created in location SYS$SHARE when you install TeamRoute: o TMR$RTL_SHR.EXE o TMRA1$API_SHR.EXE B.1.4 SYS$MESSAGE This section lists the files created in location SYS$MESSAGE when you install TeamRoute: o TMR$RTLMSG_SHR.EXE B.1.5 TMRA1$DATA_SHARE This section lists the files created in location TMRA1$DATA_SHARE when you install TeamRoute: o TMRA1$APPLICATION.DAT o TMRA1$DATA_TYPE.DAT o TMRA1$PROFILE.DAT B-2 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.1 File Names B.1.6 TMRA1$LIB_LLV This section lists the files created in location TMRA1$LIB_LLV when you install TeamRoute: o TMR$CL_EMPTY.TXT o TMR$CL_DISPLAY_PACKAGE_HELP.BLP o TMR$CL_DISPLAY_ROLE_HELP.BLP o TMR$CL_DISPLAY_ROLE_REQS.BLP o TMR$CL_DISPLAY_ROLE_RIGHTS.BLP o TMR$CL_NO_PACKAGE_HELP.BLP o TMR$CL_NO_ROLE_HELP.BLP o TMR$CL_PRINT_HEADER.BLP o TMR$CL_PRINT_PACKAGE.BLP o TMR$CL_READ_ATTACHMENT.BLP o TMR$CL_READ_PACKAGE.BLP o TMR$CL_READ_SIGNATURE.BLP o TMRA1$DEFAULT_APPL.COM o TMRA1$DEFAULT_APPL.EXE o TMRA1$DEFAULT_APPL.SCP o TMR$CL_DISPLAY_HISTORY.BLP o TMR$CL_DISPLAY_ROLE.BLP o TMR$CL_FORMAT_PRINT.COM o TMR$CL_READ_SERVICE_MSG.BLP o TMR$CL_READ_STATUS.BLP o TMR$CL_SAMPLE_ACCREQ.FGN o TMR$CL_SAMPLE_ACTION.FGN o TMR$CL_SAMPLE_ANSWER.FGN o TMR$CL_SAMPLE_DOCREV.FGN o TMR$CL_SAMPLE_MEETING.FGN o TMR$CL_SAMPLE_READACK.FGN Files and Logical Names Installed on Your System B-3 Files and Logical Names Installed on Your System B.1 File Names o TMR$CL_SAMPLE_TELEPHONE.FGN o TMR$CL_SAMPLE_TRAVELREQ.FGN o TMR$CL_SHOW_COMPONENTS.BLP o TMR$CL_SHOW_SERVICE_MSG.BLP o TMR$CL_SHOW_STATUS.BLP o TMR$SM_MAR_PRINTHEADER.BLP o TMR$SM_MAR_PRINTTEMPLATE.BLP o TMR$SM_MEA_PRINTHEADER.BLP o TMR$SM_MEA_PRINTTEMPLATE.BLP o TMR$SM_MSA_PRINTHEADER.BLP o TMR$SM_MSA_PRINTTEMPLATE.BLP o TMR$SM_PRINTFORMAT.BLP o TMR$SM_SETUP.SCP o TMR$SM_SMSA_STARTUP.COM o TMRFLB.FLB o TMRFLB.FLC o TMRMGR.FLB o TMRMGR.FLC B.1.7 TMRA1$LIB_SHARE This section lists the files created in location TMRA1$LIB_SHARE when you install TeamRoute: o TMR$CL_ADD_SIGNATURE.SCP o TMR$CL_DELETE_SIGNATURE.SCP o TMR$CL_DISPLAY_PACKAGE_HELP.SCP o TMR$CL_DISPLAY_ROLE.SCP o TMR$CL_DISPLAY_ROLE_HELP.SCP o TMR$CL_FILE_TEXT.SCP o TMR$CL_GET_PACKAGE_ATTRIBUTES.SCP o TMR$CL_PRINT.SCP B-4 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.1 File Names o TMR$CL_PROCESS_NEW_PACKAGE.SCP o TMR$CL_READ_COMPONENTS.SCP o TMR$CL_READ_PACKAGE.SCP o TMR$CL_ATTACH.SCP o TMR$CL_ATTACH_DOCUMENT.SCP o TMR$CL_BYPASS_RECIPIENT.SCP o TMR$CL_CHECK_REQUESTS.SCP o TMR$CL_CREATE.SCP o TMR$CL_CREATE_ROUTING_LIST.SCP o TMR$CL_CREATE_SAMPLE_TEMPLATES.SCP o TMR$CL_CREATE_TEMPLATE.SCP o TMR$CL_DATA_FILES_TO_FILECAB.SCP o TMR$CL_DATA_FILES_TO_OASHARE.SCP o TMR$CL_DELETE.SCP o TMR$CL_DETACH.SCP o TMR$CL_DISPLAY_HISTORY.SCP o TMR$CL_EDIT.SCP o TMR$CL_EDIT_ATTACHMENT.SCP o TMR$CL_FILE_ATTACHMENT.SCP o TMR$CL_FORMAT_EDIT.SCP o TMR$CL_FORMAT_READ.SCP o TMR$CL_GET_ATTACHMENT_KEY.SCP o TMR$CL_GET_GROUP_NUMBER.COM o TMR$CL_GET_GROUP_NUMBER.SCP o TMR$CL_GET_NUM_ATTACHMENTS.SCP o TMR$CL_GET_PENDING.SCP o TMR$CL_GET_PROFILE_INFO.SCP o TMR$CL_GET_ROLE_ID.SCP o TMR$CL_GOLDF.SCP Files and Logical Names Installed on Your System B-5 Files and Logical Names Installed on Your System B.1 File Names o TMR$CL_GOLDQ.SCP o TMR$CL_IMPORT_TEMPLATE.SCP o TMR$CL_INDEX_ATTACHMENTS.SCP o TMR$CL_INDEX_SIGNATURES.SCP o TMR$CL_MODIFY_HEADER.SCP o TMR$CL_OPEN_LIBRARY.SCP o TMR$CL_PROCESS_APPLICATION.SCP o TMR$CL_PROCESS_ATTACHMENTS.SCP o TMR$CL_PROCESS_COMPONENTS.SCP o TMR$CL_READ.SCP o TMR$CL_READ_NEW.SCP o TMR$CL_READ_SERVICE_MSG.SCP o TMR$CL_REFILE_DOCUMENT.SCP o TMR$CL_REMOVE_SIGNATURE.SCP o TMR$CL_ROUTE_VALID.SCP o TMR$CL_RUN_APPLICATION.SCP o TMR$CL_SELECT.SCP o TMR$CL_SELECT_DOCUMENT.SCP o TMR$CL_SEND.SCP o TMR$CL_SERVICE_AGENT_REQUEST.SCP o TMR$CL_SET_NEW_TMRDOC.SCP o TMR$CL_SHOW_COMPONENTS.SCP o TMR$CL_SHOW_ROLE.SCP o TMR$CL_SHOW_ROUTING_LIST.SCP o TMR$CL_SHOW_STATUS.SCP o TMR$CL_SIGN_DOCUMENT.SCP o TMR$CL_TRACK_DOCUMENT.SCP o TMR$CL_UPDATE_ATTACHMENT.SCP o TMR$CL_VALIDATE_FOLDER.SCP B-6 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.1 File Names o TMR$CL_YESNO_PROMPT.SCP o TMR$SM_ADD_USERS.SCP o TMR$SM_APPLICATION_FILE_STARTUP.COM o TMR$SM_MAR_PRINT.SCP o TMR$SM_MEA_PRINT.SCP o TMR$SM_MSA_PRINT.SCP o TMR$SM_OPENLIB.SCP o TMR$SM_PROFILE.FDL o TMR$SM_PROFILE_STARTUP.COM o TMR$SM_RENAME_FILES.COM o TMR$SM_RESTART_SERVICE_AGENT.COM o TMR$SM_RUNCHECK.COM o TMR$SM_STOP_SERVICE_AGENT.COM o TMR$SM_SUBMIT_SERVICE_AGENT.COM o TMR$SM_SUSPEND_SERVICE_AGENT.COM o TMRA1$DATA_TYPE.FDL o TMRA1$DATA_TYPE.SCP B.1.8 TMRA1$SA_CODE This section lists the files created in location TMRA1$SA_ CODE when you install TeamRoute: o TMR$SA_ATTACH_ATTACHMENT.SCP o TMR$SA_BATCH_SERVICE_AGENT.COM o TMR$SA_BUILD_ROUTING_COPY.SCP o TMR$SA_BYPASS_CURRENT_RECIPIENT.SCP o TMR$SA_CHECK_BLOCKSIZE.COM o TMR$SA_CONTROL_FILE.SCP o TMR$SA_CONTROL_FILE_STARTUP.COM o TMR$SA_CREATE_ROUTING_COPY.SCP o TMR$SA_CREATE_SERVICE_MESSAGE.SCP Files and Logical Names Installed on Your System B-7 Files and Logical Names Installed on Your System B.1 File Names o TMR$SA_DELETE_MASTER.SCP o TMR$SA_FIFO_ORDER.SCP o TMR$SA_FILE_HEADER.SCP o TMR$SA_GET_FILESPEC.SCP o TMR$SA_HIBERNATE_SERVICE_AGENT.SCP o TMR$SA_INIT_SERVICE_AGENT.COM o TMR$SA_LOG.SCP o TMR$SA_NEW_MASTER.SCP o TMR$SA_OCTAL.COM o TMR$SA_OPENLIB.SCP o TMR$SA_PROCESS_HIGH.SCP o TMR$SA_PROCESS_LOW.SCP o TMR$SA_RENAME_FILES.COM o TMR$SA_SA_REPLY.SCP o TMR$SA_SEPARATE_ATTACHMENTS.SCP o TMR$SA_SERVICE_AGENT.COM o TMR$SA_SERVICE_AGENT_SCRIPT.SCP o TMR$SA_SETPROTECTION.COM o TMR$SA_SETUP.COM o TMR$SA_SETUP.SCP o TMR$SA_SET_ACLS.COM o TMR$SA_SET_ACLS.SCP o TMR$SA_SHUTDOWN_CHECK.COM o TMR$SA_TRACE_OFF.SCP o TMR$SA_TRACE_ON.SCP o TMR$SA_TRACKING.SCP o TMR$SA_TRANSACTION.FDL o TMR$SA_TRANSACTION.SCP o TMR$SA_TRANSACTION_STARTUP.COM B-8 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.1 File Names o TMR$SA_UPDATE_CONTROL_FILE.COM o TMR$SA_UPDATE_REQUEST.SCP o TMR$SA_VARIABLE.SCP o TMR$SA_WRITELOG.COM B.1.9 TMRA1$SA_DATA This section lists the files created in location TMRA1$SA_ DATA when you install TeamRoute: o TMR$SA_CONTROL_FILE.DAT o TMR$SA_LOG_FILE.FDL o TMR$SM_APPLICATION_FILE.FDL B.1.10 TMRA1$SA_LOG This section lists the files created in location TMRA1$SA_ LOG when you install TeamRoute: o TMR$SA_INIT_SERVICE_AGENT.LOG o TMRA1SA1.LOG B.1.11 TMRA1$A1 This section lists the files created in location TMRA1$A1 when you install TeamRoute: o TMR$SA_SETUP.COM B.1.12 TMRA1$SITE_LIB_LLV This section lists the files created in location TMRA1$SITE_LIB_LLV when you install TeamRoute: o SITETMRFLB.FLB o SITETMRMGR.FLB Files and Logical Names Installed on Your System B-9 Files and Logical Names Installed on Your System B.1 File Names B.1.13 TMRA1$BUILD_LLV This section lists the files created in location TMRA1$BUILD_LLV when you install TeamRoute: o OA$TMR$MESSAGES.MSG o OA$TMR$MESSAGES_NOTEXT.OBJ o OA$TMR$MESSAGES_TEXT.OBJ o TMRA1$HELP.HLB o TMRA1$HELP_SOURCE.HLB o TMRA1$SM_HELP.HLB o TMRA1$SM_HELPSOURCE.HLB B.1.14 TMRA1$BUILD_SHARE This section lists the files created in location TMRA1$BUILD_SHARE when you install TeamRoute: o OA$TMR$LIBRARY.OLB o OA$TMR$OAGBL_INCLUDE.L32 o TMR$RTL_DUMP.EXE o TMR$TCU.EXE o TMRRTL.H B.1.15 OA$LIB_SHARE This section lists the files created in location OA$LIB_ SHARE when you install TeamRoute: o TMR.COM o TMR.SCP o TMR.CMU B-10 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.2 Logical Names B.2 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. o TMRA1$A1 o TMRA1$A1PREFIX o TMRA1$API_SHR o TMRA1$BLP o TMRA1$BLP_ENGLISH o TMRA1$BLP_LLV o TMRA1$BLP_SHARE o TMRA1$BUILD o TMRA1$BUILD_ENGLISH o TMRA1$BUILD_LLV o TMRA1$BUILD_SHARE o TMRA1$DATA o TMRA1$DATA_ENGLISH o TMRA1$DATA_LLV o TMRA1$DATA_SHARE o TMRA1$DO o TMRA1$DO_ENGLISH o TMRA1$DO_LLV o TMRA1$DO_SHARE o TMRA1$DUMP_AREA o TMRA1$LIB o TMRA1$LIB_ENGLISH o TMRA1$LIB_LLV Files and Logical Names Installed on Your System B-11 Files and Logical Names Installed on Your System B.2 Logical Names o TMRA1$LIB_SHARE o TMRA1$LOG o TMRA1$PROCPREFIX o TMRA1$PROFILE_SA o TMRA1$SA$TRANSFILE o TMRA1$SA$USERNAME o TMRA1$SABATCH o TMRA1$SADEVICE o TMRA1$SATRACE o TMRA1$SAVERSION o TMRA1$SA_CODE o TMRA1$SA_DATA o TMRA1$SA_LOG o TMRA1$SCP o TMRA1$SCP_ENGLISH o TMRA1$SCP_LLV o TMRA1$SCP_SHARE o TMRA1$SERVICE o TMRA1$SERVICE_DIRECTORY o TMRA1$SITE_BLP_ENGLISH o TMRA1$SITE_BLP_LLV o TMRA1$SITE_BLP_SHARE o TMRA1$SITE_BUILD_ENGLISH o TMRA1$SITE_BUILD_LLV o TMRA1$SITE_BUILD_SHARE o TMRA1$SITE_DATA_ENGLISH o TMRA1$SITE_DATA_LLV o TMRA1$SITE_DATA_SHARE o TMRA1$SITE_DEV_ENGLISH B-12 Files and Logical Names Installed on Your System Files and Logical Names Installed on Your System B.2 Logical Names o TMRA1$SITE_DEV_LLV o TMRA1$SITE_DEV_SHARE o TMRA1$SITE_DO_ENGLISH o TMRA1$SITE_DO_LLV o TMRA1$SITE_DO_SHARE o TMRA1$SITE_LIB_ENGLISH o TMRA1$SITE_LIB_LLV o TMRA1$SITE_LIB_SHARE o TMRA1$SITE_SCP_ENGLISH o TMRA1$SITE_SCP_LLV o TMRA1$SITE_SCP_SHARE o TMRA1$SOURCES o TMRA1$TMRA1SA Files and Logical Names Installed on Your System B-13 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 user 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 _____________________for_this_version).___________________ 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. (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 F ________________________________________________________________ Special Customizations This appendix lists the steps you should follow if your ALL-IN-1 system has third-party applications not listed in Chapter 4, or asset packages that change either OASDF.BLI or OAGBL.BLI. To customize ALL-IN-1 systems to support TeamRoute in these situations, you need a BLISS compiler to merge the TeamRoute changes. Follow the listed instructions very carefully: 1. Make the changes to OAGBL.BLI or OASDF.BLI, as listed: o For OAGBL.BLI, do the following: Add the line: LIBRARY 'TMRA1$BUILD_SHARE:OA$TMR$OAGBL_INCLUDE'; after the line: LIBRARY 'SYS$LIBRARY:XPORT'; Locate the table named OA$AT_SYMBOLS. Include the references found in TMRA1$BUILD_SHARE:OAGBL.TMR_ EXTRACT1 in that table in alphabetical order. Locate the table named OA$AT_PUTSYMBOLS. Include the references found in TMRA1$BUILD_SHARE:OAGBL.TMR_ EXTRACT2 in that table in alphabetical order. Locate the line that starts with $DSAB(NAME='OA$MAIDES', as show: Special Customizations F-1 Special Customizations !- $DSAB(NAME='OA$MAIDES',ACTION=OA$TBL_TABLE_ACTION,OPEN=1, CHOICES=1, CLASS=DATA, TYPE=DAT$K_TABLE, DATA_RAB=PLIT( OA$GT_ASCIC_DEST_ALLIN1, OA$GT_ASCIC_DEST_ALL_IN_1, OA$GT_ASCIC_DEST_NO_MAIL, OA$GT_ASCIC_DEST_PRINTER, OA$GT_ASCIC_PAPER_MAIL, OA$GT_ASCIC_HARD_COPY, OA$GT_ASCIC_DEST_VMSMAIL, OA$GT_ASCIC_DEST_VAXMAIL)); !+ You need to add one line to the bottom of the existing DSAB definition so that it now ends with the the following line: UPLIT(%ASCIC'TMR'))); The only difference is the addition of UPLIT(%ASCIC'TMR'). o For OASDF.BLI, do the following: Add the line: OA$TMR$DISPATCH: WEAK, after the lines: EXTERNAL ROUTINE !+ VMSINSTAL BEGIN EXTERNAL ROUTINES Locate the table named CMD TABLE. Add the following line to that table, in alphabetical order: <'TMR',OA$TMR$DISPATCH>, 2. After you made changes to OAGBL.BLI or OASDF.BLI, recompile the changed modules. You must have BLISS installed on your system to do so. To find out if BLISS is installed, issue the following command: $ DIRECTORY SYS$SYSTEM:BLISS32.EXE Contact your Digital representative if you do not have the BLISS programming language on your system. F-2 Special Customizations Special Customizations OAGBL.BLI and OASDF.BLI both reference OAMAC.L32. Use the following command to create that file and to recompile both .BLI files: $ BLISS/LIBRARY=FAC$COMMON:OAMAC.L32 FAC$COMMON:OAMAC.REQ $ BLISS OAGBL $ BLISS OASDF 3. Move any new object modules into the ALL-IN-1 object library, OALIBR.OLB, as follows: $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR OAGBL $ LIBRARY/REPLACE OA$BUILD_SHARE:OALIBR OASDF 4. To regain disk space, you can optionally delete the object files using the following commands: $ DELETE OAGBL.OBJ; $ DELETE OASDF.OBJ; Special Customizations F-3 ________________________________________________________________ Index A Diagnostic messages ___________________________ (cont'd) Action control list and service agent log setting, C-7 file, 5-11 Application Programming and service agent Interface (API), 1-2 transaction file, 5-11 Application registration error messages, C-5 to file, 5-13 C-8 Attachments informational messages, definition of, 1-6 C-1 to a template, 1-4 warning messages, C-2 to AUTOGEN C-5 changing system values Disk space, 2-3 with, 2-6 B E__________________________ ___________________________ Error Bypass request recovery of, 3-12 on deleted master, C-3 Error condition C not correctable, C-2 ___________________________ steps in correcting, C-2 Carbon copy, 1-5 Error messages, C-5 to C-8 Conventions, viii Customized system F__________________________ updating to include File names, B-1 TeamRoute, 4-1 Files installed, B-1 D__________________________ Data type of attachments, 1-6 Detached process, C-1 Diagnostic messages Index-1 G__________________________ N__________________________ GBLPAGES Notification messages, C-5 calculating values for, 2-5 O__________________________ GBLSECTIONS OA$LIB_SHARE files, B-10 calculating values for, 2-5 P ___________________________ I__________________________ Parameters Informational messages, C-1 changing system values Installation with AUTOGEN, 2-6 additional languages, checking system values, 3-11 2-4 after installing required, 2-3 TeamRoute, 4-1 system, 2-3 basic kit, 3-1 Personal template, 1-3 of TeamRoute, 3-1 Privileges, 2-3 preparations and Problems determining and reporting requirements, 2-1 , 4-9 procedure requirements, Processing requests, 1-4 2-1 Profile entry sample, A-1 not found, C-7 L__________________________ Q__________________________ Log file Quotas for the service agent, process account, 2-7 5-11 Logical names, B-11 R__________________________ installed, B-1 Release notes, 2-1 M Requests ___________________________ high-priority unknown or Mail invalid, C-7 modifying users' low-priority unknown or destination, E-1 invalid, C-5 MAILbus, 1-2 Role definition of, 1-5 Routing, 1-5 Routing copy, 1-5 Routing list definition of, 1-5 Index-2 Routing package Subscriber (cont'd) completed master, C-3 unfound profile entry, creation, 1-4 C-7 definition of, 1-4 SYS$HELP files, B-2 events, 1-5 SYS$MESSAGE files, B-2 not TeamRoute, C-6 SYS$SHARE files, B-2 processing requests, 1-4 SYS$STARTUP files, B-2 processing with errors, System disk C-2 backing up, 2-9 routing, 1-5 tracking, 1-6 T__________________________ tracking report, C-7 Teamform application, 1-3 types, 1-4 Template, 1-3 to 1-4 unfound attachments, C-6 Templates unfound data files, C-6 supplied, 1-3 Run-Time Library (RTL), 1-2 TMRA1$A1 files, B-9 S TMRA1$BUILD_LLV files, B-10 ___________________________ TMRA1$BUILD_SHARE files, Scripts, 5-13 B-10 Server domain, 1-2 TMRA1$DATA_SHARE files, B-2 Service agent TMRA1$LIB_LLV files, B-3 and unknown or invalid TMRA1$LIB_SHARE files, B-4 request, C-5, C-7 TMRA1$SA_CODE files, B-7 log file, 5-11 TMRA1$SA_DATA files, B-9 states of, 5-10 TMRA1$SA_LOG files, B-9 stopping, C-1 TMRA1$SITE_LIB_LLV files, submitting, 5-10, C-1 B-9 suspending, 5-10, C-1 Tracking, 1-6 transaction file, 5-11 Tracking report, C-7 unfound profile entry, Transaction file, D-1 C-7 for service agent, 5-11 Signatures, 1-6 Transaction record Software fixed-length fields, D-2 Prerequisite, 2-1 format, D-2 Special customizations variable-length fields, to support asset packages D-3 , F-1 Transaction types, D-1 to support third part applications, F-1 U__________________________ State Users of service agent, C-5 Subscriber, 1-2 See Subscriber bypassing deleted recipient, C-3 Index-3 V__________________________ W__________________________ Variables, 1-3 Wait interval VMSINSTAL changing default, 5-10 requirements, 2-8 Warning messages, C-2 to C-5 Index-4