ALL-IN-1
                    TeamLinks_Connection________________________________
                    Installation and Management Guide

                    Revision/Update Information:  Revised for TeamLinks
                                                  Connection Version 2.5

                    Operating System:             OpenVMS VAX Version
                                                  5.5-2 or higher
                                                  OpenVMS Alpha Version
                                                  6.1

                    Software Version:             Version 2.5

 






              ________________________________________________________________
              April 1995

              Possession, use, or copying of the software described in
              this documentation is authorized only pursuant to a valid
              written license from Digital or an authorized sublicensor.

              While Digital believes the information included in this
              publication is correct as of the date of publication, it is
              subject to change without notice.

              Digital Equipment Corporation makes no representations
              that the use of its products in the manner described in
              this publication will not infringe on existing or future
              patent rights, nor do the descriptions contained in this
              publication imply the granting of licenses to make, use,
              or sell equipment or software in accordance with the
              description.

              © Digital Equipment Corporation 1995.

              All Rights Reserved.

              We welcome your comments on this book. Please use one of
              the following ways to send your comments:

              o  Send an electronic mail message to books@reo.mts.dec.com

              o  Send an electronic mail message to
                 S=IDC BOOKS; O=digital; OU1=reo; P=digital; A=CWMail;
                 C=gb

              o  Send a fax to (+44) 1734 206018

              The following are trademarks of Digital Equipment
              Corporation: ALL-IN-1, CDA, DDIF, DEC, DECnet, Digital,
              MAILworks, OpenVMS, PATHWORKS, TeamLinks, VAX, VAX
              DOCUMENT, VMScluster, WPS-PLUS, and the DIGITAL logo.

              Apple, AppleTalk, and Macintosh are registered trademarks
              of Apple Computer, Inc.

              Multinet is a registered trademark of TGV, Inc.

              Windows is a trademark of Microsoft Corporation.

              All other trademarks and registered trademarks are the
              property of their respective holders.

              This document is available on CD-ROM.

              This document was prepared using VAX DOCUMENT, Version 2.1.

 














     _________________________________________________________________

                                                              Contents



     Preface...................................................     ix

     1  Introducing the TeamLinks Connection (TLC)


     2  Differences From TLC Version 2.1

           2.1   Support for OpenVMS Alpha Systems.............    2-1
           2.2   Updated File Cabinet Server...................    2-1
           2.3   Updated PC Broadcast Server...................    2-2
           2.4   Updated AIDA Server...........................    2-3

     3  Known Problems and Restrictions

           3.1   Using the SUBSCRIBERS: Special Address........    3-1
           3.2   CDA Compatibility.............................    3-2
           3.3   Logical Device Names..........................    3-2
           3.4   Partially Successful Operation in the File
                 Cabinet Server................................    3-2
           3.5   Simultaneous Access to a Document.............    3-3
           3.6   Using TeamLinks Remote Connection Manager With
                 Captive ALL-IN-1 Accounts.....................    3-3

     4  Preparing to Install the TLC

           4.1   Types of Installation.........................    4-3
           4.2   Prerequisite Software.........................    4-5
           4.3   Disk Space....................................    4-5
           4.4   Location of Site Link File....................    4-6





                                                                   iii

 







        5  Installing the TLC

              5.1   Keeping a Record of the Installation..........    5-2
              5.2   Running the Installation Procedure............    5-3

        6  Restarting an Installation

              6.1   Recovering from Installation Errors...........    6-1
              6.2   Restoring the Object Libraries................    6-1
              6.3   Running the Postinstallation Procedures.......    6-2

        7  Setting up the TLC

              7.1   License Requirements..........................    7-1
              7.1.1     Choosing a License........................    7-2
              7.1.2     ALL-IN-1 Client Services Access License...    7-3
              7.2   Setting up File Cabinet Servers...............    7-5
              7.3   Setting up Network Transport Mechanisms.......    7-5
              7.3.1     If You Use TCP/IP Transport...............    7-7
              7.3.2     If You Use AppleTalk Transport............    7-8
              7.4   Enabling Non-DECnet Asynchronous
                    Connections...................................    7-8
              7.5   Relinking ALL-IN-1 IOS........................    7-9

        8  Managing AIDA Servers

              8.1   Accessing the Manage AIDA Servers Menu........    8-1
              8.2   How the AIDA Server Works.....................    8-1
              8.3   When are Management Tasks Necessary?..........    8-2
              8.4   What do Management Tasks Involve?.............    8-2
              8.5   Configuring an AIDA Server....................    8-3
              8.6   Tuning an AIDA Server.........................    8-7
              8.6.1     Controlling the Number of Users...........    8-8
              8.6.2     Setting Process Quotas....................    8-9
              8.6.3     Controlling Mail Directory Usage..........   8-10
              8.7   Ensuring Access to Up-to-date Data Files......   8-11
              8.8   Accessing Additional Form Libraries...........   8-12
              8.8.1     Creating an AIDA Library Search Order.....   8-13
              8.8.2     Using a Test Library Search Order.........   8-13
              8.9   Changing the State of an AIDA Server..........   8-14
              8.9.1     Starting an AIDA Server...................   8-16
              8.9.2     Stopping an AIDA Server...................   8-16
              8.10  Monitoring and Controlling Connections to an
                    AIDA Server...................................   8-17

        iv

 







              8.11  Creating an AIDA Server.......................   8-18
              8.12  Removing an AIDA Server.......................   8-18

        9  Managing File Cabinet Servers

              9.1   Overview of the File Cabinet Server...........    9-1
              9.1.1     What the File Cabinet Server Does.........    9-1
              9.1.2     Connections to the File Cabinet Server....    9-1
              9.1.3     Locating File Cabinet Objects.............    9-2
              9.1.4     Opening Drawers...........................    9-2
              9.1.5     The Drawer Cache..........................    9-3
              9.2   Tasks Involved in Managing File Cabinet
                    Servers.......................................    9-3
              9.3   Accessing the Options for Managing File
                    Cabinet Servers...............................    9-5
              9.4   Managing a Remote File Cabinet Server.........    9-6
              9.5   File Cabinet Server Configuration and
                    Attributes....................................    9-7
              9.6   Creating a Local File Cabinet Server..........   9-11
              9.6.1     Enabling Connections to a New File Cabinet
                        Server....................................   9-12
              9.7   Changing File Cabinet Server Configuration and
                    Attributes....................................   9-13
              9.8   Deleting a File Cabinet Server................   9-13
              9.9   Changing the Status of a File Cabinet
                    Server........................................   9-13
              9.9.1     Starting a File Cabinet Server............   9-14
              9.9.2     Stopping a File Cabinet Server............   9-14
              9.9.3     Enabling a File Cabinet Server............   9-14
              9.9.4     Disabling a File Cabinet Server...........   9-15
              9.10  Identifying Clients of the File Cabinet
                    Server........................................   9-15
              9.11  Resetting the Warning for Disk Quota Limit....   9-16
              9.12  Tuning the File Cabinet Server................   9-17
              9.12.1    Monitoring the Performance of the File
                        Cabinet Server............................   9-18
              9.12.2    Tuning File Cabinet Server Process
                        Quotas....................................   9-19
              9.12.3    Setting the Value of CHANNELCNT...........   9-20
              9.12.4    Tuning the File Cabinet Server Drawer
                        Cache.....................................   9-21
              9.12.5    Controlling the Number of Clients.........   9-22



                                                                        v

 







              9.12.6    Setting the Process Priority of the File
                        Cabinet Server............................   9-22

        10  Enabling Broadcast Messages

              10.1  The PC Broadcast Server.......................   10-1
              10.2  ALL-IN-1 Conditions for Enabling Broadcast
                    Messages......................................   10-1
              10.3  The PC Notification Data Set..................   10-3

        11  Tools for Troubleshooting

              11.1  Running the IVP...............................   11-1
              11.2  AIDA Server Log Files.........................   11-2
              11.3  AIDA Server Tracing...........................   11-3
              11.3.1    What You Can Trace........................   11-4
              11.3.2    AIDA Server Trace Files...................   11-4
              11.3.3    Enabling AIDA Server Tracing..............   11-5
              11.3.4    Switching AIDA Server Tracing Off.........   11-7
              11.4  File Cabinet Server Log Files.................   11-7
              11.5  File Cabinet Server Tracing...................   11-8
              11.5.1    Tracing File Cabinet Server Activity......   11-8
              11.5.2    Tracing Client Connections................   11-9
              11.6  PC Broadcast Server Log Files.................   11-9
              11.7  The PC Broadcast Test Program.................  11-10
              11.8  The PC Broadcast Server Test Program..........  11-11
              11.9  Testing Transport Mechanisms for Broadcast
                    Messages......................................  11-11

        12  Solving Problems

              12.1  Problems with Addressing Mail.................   12-1
              12.2  Problems with the File Cabinet Server.........   12-1
              12.2.1    Failure to Connect to the File Cabinet
                        Server....................................   12-1
              12.2.2    File Cabinet Server Fails to Start........   12-3
              12.2.3    Invalid Authentication Information........   12-3
              12.2.4    Thread Access Violation or Internal
                        Error.....................................   12-4
              12.3  Problems with Broadcast Messages..............   12-4
              12.3.1    Checking the RSVD_FOR_TCS Flag............   12-6
              12.3.2    Checking an Entry in the OA$PC_NOTIFY Data
                        Set.......................................   12-6


        vi

 







              12.3.3    Starting and Stopping the PC Broadcast
                        Server....................................   12-6
              12.4  DASL Errors...................................   12-7

        Index


        Tables

              1-1       Components of the TLC.....................    1-1

              4-1       Preparation Tasks.........................    4-1

              4-2       Types of Installation.....................    4-3

              4-3       Disk Space Requirements (in Blocks).......    4-5

              5-1       Information About the Installation
                        Procedure.................................    5-1

              5-2       Installation Procedure ...................    5-3

              7-1       Are Further Licenses Necessary?...........    7-2

              7-2       Licensing Options.........................    7-3

              7-3       Styles of the ALL-IN-1 Client Services
                        Access License............................    7-4

              7-4       Network Transport Mechanisms..............    7-6

              8-1       Displaying the Manage AIDA Servers Menu...    8-1

              8-2       Managing AIDA Servers.....................    8-2

              8-3       AIDA Server Configuration Details.........    8-4

              8-4       Factors That Affect Performance of an AIDA
                        Server....................................    8-7

              8-5       Process Quotas Affecting the AIDA
                        Server....................................    8-9

              8-6       OA$AIDA_FLUSH_TIME Values.................   8-12

              8-7       How to Create an AIDA Library Search
                        Order.....................................   8-13

              8-8       How to Use a Library Search Order for
                        Testing...................................   8-14

              8-9       AIDA Server States........................   8-15

              8-10      Options on the Index of Server Connections
                        Menu......................................   8-17

              9-1       Management Tasks for the File Cabinet
                        Server....................................    9-4

              9-2       Displaying the Manage Servers Menu........    9-6

                                                                      vii

 







              9-3       Creating an Entry for a Remote File
                        Cabinet Server............................    9-7

              9-4       File Cabinet Server Configuration and
                        Attributes................................    9-8

              9-5       Creating a Local File Cabinet Server......   9-12

              9-6       Building an Index of Server Clients.......   9-15

              9-7       Options on the Manage Server Clients Index
                        Menu......................................   9-16

              9-8       Monitoring the Performance of a File
                        Cabinet Server............................   9-18

              9-9       Process Quotas for File Cabinet Servers...   9-19

              9-10      Drawer Cache Attributes...................   9-21

              10-1      ALL-IN-1 Conditions for Enabling Broadcast
                        Messages..................................   10-2

              10-2      OA$PC_NOTIFY Data Set.....................   10-3

              11-1      Troubleshooting Tools.....................   11-1

              11-2      Questions and Answers about AIDA Server
                        Log Files.................................   11-2

              11-3      Activities That You Can Trace.............   11-4

              11-4      Questions and Answers about AIDA Server
                        Trace Files...............................   11-5

              11-5      How to Enable Tracing for an AIDA
                        Server....................................   11-5

              11-6      Questions and Answers about PC Broadcast
                        Server Log Files..........................   11-9

              12-1      How to Solve Problems with Broadcast
                        Messages..................................   12-5

              12-2      Starting and Stopping the PC Broadcast
                        Server....................................   12-6

        viii

 












        _________________________________________________________________

                                                                  Preface



              This document describes how to install, set up, and manage
              the ALL-IN-1 TeamLinks Connection (TLC) Version 2.5.

        Structure of this Document

              Chapter 1 gives a brief description of the TLC.

              Chapter 2 describes the main differences between this
              version and the previous version of the TLC.

              Chapter 3 contains descriptions of known problems and
              restrictions with the TLC.

              Information about preparing to install and installing the
              TLC is in Chapter 4 to Chapter 6.

              Information about managing the TLC is in Chapter 7 to
              Chapter 12.

        Related Documentation

              Use this document in conjunction with the following:

              o   ALL-IN-1 Management Guide

              o  The documentation for your client application








                                                                       ix

 







        Conventions

              The following conventions are used in this document:

              ALL-IN-1         Means the ALL-IN-1[TM] software that is
                               installed on your system, for example,
                               ALL-IN-1 Integrated Office System (IOS)
                               Server or ALL-IN-1 Core Services for
                               OpenVMS[TM] Alpha and OpenVMS VAX[TM]

              OpenVMS Alpha    Means the OpenVMS Alpha operating system

              OpenVMS VAX      Means the OpenVMS VAX operating system

              UCX              Means DEC[TM] TCP/IP Services for OpenVMS

              TLC              Means ALL-IN-1 TeamLinks[TM] Connection

              AIDA Server      Means ALL-IN-1 Distributed Access Server

              Client user      Means a user of a TeamLinks client or of
                               any other client application

              Architecture     This term is used to differentiate between
                               OpenVMS VAX systems and OpenVMS Alpha
                               systems

              Mixed            Means a VMScluster[TM] system that
              architecture     contains both Alpha and VAX nodes
              cluster















        x

 










                                                                        1
        _________________________________________________________________

                               Introducing the TeamLinks Connection (TLC)


              The TeamLinks Connection (TLC) is a set of ALL-IN-1 servers
              that enable client applications such as TeamLinks for
              Windows[TM] and TeamLinks for Macintosh[R] to access
              ALL-IN-1 services, such as addressing, and ALL-IN-1 data.
              Table 1-1 lists the main components of the TLC.

              Table_1-1_Components_of_the_TLC____________________________

                                                       For more
              Component_____Description________________information_______

              File Cabinet  Provides access to         Chapter 9
              Server        drawers and documents
                            in the ALL-IN-1 File
                            Cabinet

              AIDA Server   Provides access to         Chapter 8
                            ALL-IN-1 data

              PC Broadcast  Manages broadcast          Chapter 10
              Server        messages and notification
                            of new mail for PC client
              ______________users________________________________________

              The servers that comprise the TLC are managed from the
              ALL-IN-1 management subsystem.










                           Introducing the TeamLinks Connection (TLC) 1-1

 










                                                                        2
        _________________________________________________________________

                                         Differences From TLC Version 2.1


              This chapter describes the main differences between TLC
              Version 2.5 and the previous version of the TLC (Version
              2.1).

        2.1 Support for OpenVMS Alpha Systems

              You can install TLC Version 2.5 on ALL-IN-1 Version 3.1
              software running on OpenVMS Alpha systems.

        2.2 Updated File Cabinet Server

              TLC Version 2.5 includes a new version of the File Cabinet
              Server. This includes:

              o  Solutions to problems found in earlier versions.

              o  Support for disk quota checking.

                 If disk quotas are enabled, when a client user accesses
                 a drawer, the File Cabinet Server checks the disk quota
                 entry for the owner of the drawer. If the owner of the
                 drawer is low on disk quota, the File Cabinet Server
                 returns a warning status to the client.

                 See Section 9.11 for more details.

                 Note that versions of TeamLinks earlier than Version 2.5
                 do not report the diskquota warning to users.

              o  Support for the selection of documents according to
                 their size.

              o  Improved support for asynchronous access to ALL-IN-1
                 data and services from a remote location by means of a
                 modem connection.

              o  Support for setting the creation date of a document.
                 This enables a DEC MAILworks[TM] drawer to be moved to
                 an ALL-IN-1 File Cabinet drawer without its created date
                 being modified.

                                     Differences From TLC Version 2.1 2-1

 



        Differences From TLC Version 2.1
        2.2 Updated File Cabinet Server


              o  Checks that prevent an existing drawer from being re-
                 added to the file cabinet.

              o  Support for the use of a cluster alias when connecting
                 to the File Cabinet over TCP/IP.

              o  Improved File Cabinet Server logging. Log files are
                 in a different format, and include information about
                 clients. They are now in OA$LOG; not in SYS$MANAGER. See
                 Section 11.4 for information about how to access File
                 Cabinet Server log files.

              o  Improved File Cabinet Server tracing. It is no longer
                 necessary to use a formatting program to read File
                 Cabinet Server trace files. The trace files contain
                 more information than in previous versions.

        2.3 Updated PC Broadcast Server

              The PC Broadcast Server includes the following changes:

              o  Added support for UCX-emulation software.

                 To enable TCP/IP transport for communications between
                 the TLC and client applications, the PC Broadcast Server
                 now supports the use of any of the following products:

                 -  DEC TCP/IP Services for OpenVMS (UCX)

                 -  PathWay from Wollongong

                 -  Multinet[R]

              o  Support for the use of node numbers

                 If you use TCP/IP transport, the PC Broadcast Server
                 supports the use of node numbers as an alternative to
                 node names.

              o  Updated test programs

                 The PC Broadcast test and the PC Broadcast Server test
                 programs have been updated. These test programs now
                 support the AppleTalk[R]/DECnet[TM] Gateway.

        2-2 Differences From TLC Version 2.1

 



                                         Differences From TLC Version 2.1
                                                  2.4 Updated AIDA Server


        2.4 Updated AIDA Server

              TLC Version 2.5 includes a new version of the AIDA Server.
              This includes:

              o  Solutions to problems.

              o  Support for client applications to access additional
                 form libraries.




































                                     Differences From TLC Version 2.1 2-3

 










                                                                        3
        _________________________________________________________________

                                          Known Problems and Restrictions


              This chapter describes known problems and restrictions that
              are in TLC Version 2.5.

        3.1 Using the SUBSCRIBERS: Special Address

              For a user to be able to send mail messages to the
              SUBSCRIBERS: special address, the SUBSCR privilege field
              must be set to Y in the user's ALL-IN-1 account details.

              In addition, for such users to be able to use the
              SUBSCRIBERS: address from TeamLinks, the ALL-IN-1 account
              in which the ALL-IN-1 Sender runs must also have the
              SUBSCR privilege field set to Y. To ensure that this is
              set correctly:

              ___________________________________________________________
              To:________________________Do_this:________________________

              Find the name of the       Search the Sender commmand
              account in which the       procedure, OA$LIB:OAMTISEND.COM,
              sender runs                for the line that begins:

                                         $ ALLIN1/USER=

                                         The name of the account in which
                                         the Sender runs is the name that
                                         follows the equals sign (=).

              Find the value of the      From an ALL-IN-1 account that
              SUBSCR field in the        has PRVCMD, enter:
              details of an ALL-IN-1     <GET PROFIL.PRVSUB["user"]
              account                    user is the name of the ALL-IN-1

                                         account.


                                      Known Problems and Restrictions 3-1

 



        Known Problems and Restrictions
        3.1 Using the SUBSCRIBERS: Special Address

              ___________________________________________________________
              To:________________________Do_this:________________________

              Set the value of the       At the Maintain User Accounts
              SUBSCR field to Y          menu, select the account, then
                                         use the Edit (E) option. Tab to
                                         the SUBSCR field in the ALL-IN-1
              ___________________________privileges_section,_and_enter_Y.


        3.2 CDA Compatibility

              If users work with CDA[TM] documents stored in remote
              File Cabinet drawers, every ALL-IN-1 system on which
              these drawers reside must have CDA support software
              installed and linked to ALL-IN-1. If CDA support software
              is not available on each system, refiling and reading CDA
              documents such as those in DDIF[TM] or DOTS format produces
              inconsistent results.

        3.3 Logical Device Names

              The File Cabinet Server does not support the use of logical
              names longer than 16 characters for devices that hold
              drawers. When a user attempts to create a drawer on a
              device whose logical name is longer than 16 characters,
              the File Cabinet Server logs an error.

              Unpredictable results occur if an existing drawer is
              moved to a device whose logical name is longer than 16
              characters. This can happen, for example, when a user's
              account is moved to another disk.

        3.4 Partially Successful Operation in the File Cabinet Server

              Under very unusual circumstances, when a TeamLinks client
              user moves or deletes a document in the File Cabinet, it is
              possible that an error message similar to the following is
              displayed:

              An error occurred while deleting this message
              The operation was partially successful
              Not all components of the operation were completed successfully

              This occurs when the user's FILECAB.DAT data file is out of
              synchronization with PARTITION.DAT.

              Workaround:

        3-2 Known Problems and Restrictions

 



                                          Known Problems and Restrictions
            3.4 Partially Successful Operation in the File Cabinet Server


              If this problem occurs, rename the user's FILECAB.DAT.
              A new version of the data file is automatically created
              when the user next connects to the ALL-IN-1 File Cabinet.
              This version of the data file contains the user's Main
              drawer. Any other drawers that were previously included in
              the user's File Cabinet must be added to the user's File
              Cabinet again.

        3.5 Simultaneous Access to a Document

              It is possible for users to access their ALL-IN-1 accounts
              simultaneously from a client application and from a VT
              terminal or by terminal emulation. However, if a user does
              this, and accesses the same document both from a TeamLinks
              session and from a terminal session, unexpected results
              may occur in the TeamLinks session. Because the document is
              locked, there is no danger of data loss or corruption.

        3.6 Using TeamLinks Remote Connection Manager With Captive
            ALL-IN-1 Accounts

              If you have users with captive ALL-IN-1 accounts, you
              must make some modifications to enable these users to
              make asynchronous connections using the TeamLinks Remote
              Connection Manager. You must do the following:

              1. On your ALL-IN-1 system:

                 a. Create a command file called TLNK.COM in OA$LIB which
                    includes the following:

                    $ DEFINE TT SYS$COMMAND
                    $ TLNK :== "$SYS$SYSTEM:TLNK$REMOTE.EXE"
                    $ TLNK
                    $ EXIT

                 b. Use Customization Management to create a menu option
                    on the ALL-IN-1 MAIN menu to call the command file,
                    for example, TLNK. In this example, you would add the
                    following entries to the MAIN form:

                    ;;TLNK;;

                    COMMAND OA$LIB:TLNK.COM

                                      Known Problems and Restrictions 3-3

 



        Known Problems and Restrictions
        3.6 Using TeamLinks Remote Connection Manager With Captive ALL-IN-1 Accounts


              2. On each PC you must edit the sample script, SAMPLE2.TLS,
                 for the TeamLinks Remote Connection Manager. Double
                 click on the icon for the TeamLinks Remote Connection
                 Manager.

                 a. Open the sample file, SAMPLE2.TLS.

                 b. Click on the Login tab.

                 c. Remove the line that has the following response:

                    RUN SYS$SYSTEM:TLNK$REMOTE.EXE

                 d. Go to the end of the Prompt and Response table and
                    add two new entries:

                    _____________________________________________________
                    Prompt______________Response__________________Wait___

                    more ...            Add the name of the       5
                                        ALL-IN-1 menu option
                                        that you use to call
                                        the TeamLinks Connection
                                        Broker, for example,
                                        TLNK.

                    Options: WP, EM,    The name of the ALL-IN-1  5
                    [1]                 menu option that you use
                                        to call the TeamLinks
                                        Connection Broker, for
                                        example, TLNK.
                    [1]What_you_enter_here_must_match_what_is_displayed__

                    on_the_menu_when_you_enter_it_in_hard_copy_mode._____

                 e. Click on the Logout tab.

                 f. Enter ^M in the Start up Reponse dialog box.

                 g. Add the following line to the end of the Prompt and
                    Response table:

                    _____________________________________________________
                    Prompt____________________Response__________________Wait

                    Enter your choice from    EXIT                      5
                    the_list_above_______________________________________

                 h. Save the script, for example as CAPTIVE.TLS.

        3-4 Known Problems and Restrictions

 



                                          Known Problems and Restrictions
 Using TeamLinks Remote Connection Manager With Captive ALL-IN-1 Accounts


                 i. Select the Set as Default option from the Script
                    menu.

                 j. Use the TeamLinks Remote Connection Manger to check
                    that you can make a remote connection and disconnect
                    from a remote connection.







































                                      Known Problems and Restrictions 3-5

 










                                                                        4
        _________________________________________________________________

                                             Preparing to Install the TLC


              Table 4-1 shows the tasks you must do in preparation for
              installing the TLC.

              Table_4-1_Preparation_Tasks________________________________

              Task_______________________Details_________________________

              Check the kit contents.    See the bill of materials for
                                         a list of what the distribution
                                         kit should contain. Contact your
                                         Digital representative if your
                                         kit is damaged or incomplete.

              ___________________________________________________________

              Check that the             See Section 4.2 for a list of
              prerequisite software      the prerequisite software.
              is installed.

              ___________________________________________________________

              Check that there is        See Section 4.3.
              enough disk space on
              your system for the
              installation.

              ___________________________________________________________

              Check the location of      For the installation to
              the ALL-IN-1 startup       succeed, this file must be in
              command procedure,         the SYS$COMMON:[SYS$STARTUP]
              A1V3%START.COM[1].         directory.

              [1]%_is_0_or_1,_depending_on_whether_you_are_installing_the

              TLC on an ALL-IN-1 Version 3.0A system or on an ALL-IN-1
              Version 3.1 system.

                                                 (continued on next page)

                                         Preparing to Install the TLC 4-1

 



        Preparing to Install the TLC



              Table_4-1_(Cont.)_Preparation_Tasks________________________

              Task_______________________Details_________________________

              ___________________________________________________________

              Check that the ALL-IN-1    These logical names are
              logical names are defined  defined when you run the
              on your system.            ALL-IN-1 startup procedure,
                                         A1V3%START.COM[1].

              ___________________________________________________________

              Back up disks.             Back up your system disk and
                                         those that contain the following
                                         ALL-IN-1 areas:

                                         o  OA$LIB_SHARE and OA$BUILD_
                                            SHARE

                                         o  OA$LIB_lang[2] and OA$BUILD_
                                            lang[2]

              ___________________________________________________________

              If you are installing on   See Section 4.4.
              an ALL-IN-1 Version 3.0A
              system, check whether the
              system uses a site link
              file, and if so, check
              the location of this
              file.

              ___________________________________________________________

              [1]%_is_0_or_1,_depending_on_whether_you_are_installing_the

              TLC on an ALL-IN-1 Version 3.0A system or on an ALL-IN-1
              Version 3.1 system.
              [2]lang is the primary language when you are doing a fresh
              or update installation, or the language on which you are
              doing an additional language installation.

                                                 (continued on next page)

        4-2 Preparing to Install the TLC

 



                                             Preparing to Install the TLC



              Table_4-1_(Cont.)_Preparation_Tasks________________________

              Task_______________________Details_________________________

              Shut down ALL-IN-1         Because the installation
                                         modifies ALL-IN-1 files, you
                                         must shut down your ALL-IN-1
                                         system for the duration of
                                         the installation. You should
                                         therefore plan to do the
                                         installation at a time that
                                         causes the least inconvenience
                                         to the ALL-IN-1 users.

                                         See the  ALL-IN-1 Management
                                         Guide for details of how to shut
              ___________________________down_ALL-IN-1.__________________

        4.1 Types of Installation

              Table 4-2 shows the types of installation that are
              available for TLC Version 2.5.

              Table_4-2_Types_of_Installation____________________________

              Type of
              InstallationDescription___________Use_When:________________

              Full        Upgrades a TLC        You have not previously
                          Version 2.1           installed TLC Version
                          system or the         2.5.
                          TLC components of
                          ALL-IN-1 Version
                          3.1, preserving
                          configuration data
                          from that system.

              Update      Updates the           You have installed a
                          system, preserving    field test version of TLC
                          configuration data    Version 2.5.
                          from the previous
                          installation.

                                                 (continued on next page)

                                         Preparing to Install the TLC 4-3

 



        Preparing to Install the TLC
        4.1 Types of Installation


              Table_4-2_(Cont.)_Types_of_Installation____________________

              Type of
              InstallationDescription___________Use_When:________________

              Additional  Adds or updates       The following conditions
              language    the TLC elements      apply:
                          that are language-    o  You have already
                          dependent.               installed TLC Version

                                                   2.5.

                                                o  You have a
                                                   multilingual ALL-IN-1
                                                   system[1].

              [1]If_you_have_a_multilingual_system,_after_you_have_______

              installed TLC Version 2.5, you must do an additional
              language installation for each additional language that
              exists on your system.
              ___________________________________________________________

              The installation procedure checks your ALL-IN-1 system
              to determine what type of installation is appropriate, as
              follows:

              o  If TLC Version 2.5 is not installed, the procedure does
                 a full installation.

              o  If TLC Version 2.5 is installed, and there is only one
                 language installed on your system, the procedure does an
                 update installation.

              o  If TLC Version 2.5 is installed, and there is more than
                 one language installed on your system, the procedure
                 prompts you to choose between an update installation and
                 an additional language installation.

              If you have ALL-IN-1 Version 3.1 installed on an Alpha
              system, you must install TLC Version 2.5 both on an Alpha
              node and on a VAX node in the same VMScluster[TM] system.



        4-4 Preparing to Install the TLC

 



                                             Preparing to Install the TLC
                                                4.2 Prerequisite Software


        4.2 Prerequisite Software

              Before you install TLC Version 2.5, one of the following
              must be installed on your system:

              o  ALL-IN-1 Version 3.0A and TLC Version 2.1.

                 You cannot install TLC Version 2.5 on an ALL-IN-1
                 Version 3.0A system that does not have TLC Version 2.1
                 installed.

              o  ALL-IN-1 Version 3.1.

                 This includes all the elements of TLC Version 2.1.

              If you are planning to install TLC Version 2.5 on an
              ALL-IN-1 Version 3.0A system, consider the following:

              o  It is likely that you will have to install ALL-IN-1
                 Version 3.1 before you can upgrade your system to the
                 next version of ALL-IN-1.

              o  If you upgrade your system to ALL-IN-1 Version 3.1
                 after installing TLC Version 2.5, you must reinstall
                 TLC Version 2.5 in order to avoid a degradation of the
                 service provided by the servers.

        4.3 Disk Space

              Table 4-3 shows the amount of disk space required to
              install TLC Version 2.5.

              Table_4-3_Disk_Space_Requirements_(in_Blocks)______________

                                              Full or       Additional
                                              Upgrade       Language
              Area____________________________Installation__Installation_

              System disk, or, if you         20 000        10 000
              specify the VMSINSTAL AWD
              option, alternate working
              device

                                                 (continued on next page)

                                         Preparing to Install the TLC 4-5

 



        Preparing to Install the TLC
        4.3 Disk Space


              Table_4-3_(Cont.)_Disk_Space_Requirements_(in_Blocks)______

                                              Full or       Additional
                                              Upgrade       Language
              Area____________________________Installation__Installation_

              ALL-IN-1 shared library         15 000           -
              (OA$LIB_SHARE and OA$BUILD_
              SHARE)

              ALL-IN-1 primary language         1000          1000
              (OA$LIB_lang[1] and OA$BUILD_
              lang[1])

              ALL-IN-1 shared data (OA$DATA_     100           -
              SHARE)
              [1]lang_is_the_primary_language_when_you_are_doing_a_fresh,

              upgrade, or update installation, or the language on which
              you are doing an additional language installation.
              ___________________________________________________________

              The figures shown in Table 4-3 refer to the space required
              during installation; the permanent disk space requirements
              may be slightly less. For the system disk (containing the
              SYS$SYSTEM and SYS$SHARE areas), the permanent disk space
              required is 1000 blocks.

        4.4 Location of Site Link File

              The TLC installation automatically relinks the ALL-IN-1
              main image. If your ALL-IN-1 system has code-level
              customizations, the TLC installation must use the site-
              specific link file, SITELINK3%.COM, for relinking.

              On ALL-IN-1 Version 3.1 systems, SITELINK31.COM is under
              Customization Management control, so if your system has
              code-level customizations, the TLC installation uses the
              site-specific link file in the live area (OA$SITE_BUILD_
              SHARE_IND). You do not have to specify the location of this
              file during the installation.

              On ALL-IN-1 Version 3.0A systems, SITELINK30.COM is
              normally in the OA$BUILD_LLV directory. However, some
              layered applications provide site link files in different
              directories.

        4-6 Preparing to Install the TLC

 



                                             Preparing to Install the TLC
                                           4.4 Location of Site Link File


              When you install the TLC on an ALL-IN-1 Version 3.0A
              system, you are prompted to specify whether your ALL-IN-1
              system uses a SITELINK30.COM file, and if so, where this
              file is. Therefore, before you install the TLC on an
              ALL-IN-1 Version 3.0A system, check:

              o  Whether there is a SITELINK30.COM on your system, and if
                 so, where it is

              o  Whether the applications to which SITELINK30.COM refers
                 are currently integrated with your ALL-IN-1 system


































                                         Preparing to Install the TLC 4-7

 










                                                                        5
        _________________________________________________________________

                                                       Installing the TLC


              This chapter tells you how to install TLC Version 2.5.

                __________________ Before You Start __________________

                Do not start the installation until you have completed
                the system preparation tasks in Chapter 4.

                ______________________________________________________

              During the installation, a number of cautions and
              informational messages are displayed. Read all the
              displayed messages carefully.

              Table 5-1 gives information that you may need during the
              installation.

              Table_5-1_Information_About_the_Installation_Procedure_____

              Question_________Answer____________________________________

              How long         The installation takes about five to
              does the         ten minutes, depending on the type of
              installation     processor you are using. An additional
              take?            language installation takes a little less
                               time than a full installation.

                                                 (continued on next page)









                                                   Installing the TLC 5-1

 



        Installing the TLC



              Table 5-1 (Cont.) Information About the Installation
              __________________Procedure________________________________

              Question_________Answer____________________________________

              From which       Use the SYSTEM account, or another account
              account should   that has the following privileges set:
              I do the            SYSPRV
              installation?       SYSNAM

                                  PRMGBL
                                  CMKRNL
                                  TMPMBX
                                  NETMBX

              How do I get     Enter ? at any time.
              help?

              What do I        Restart the installation from the
              do if the        beginning.
              installation
              fails before
              the automatic
              postinstalla-
              tion phase?

              How do I         Press CTRL/Y.
              stop the         The installation procedure deletes all
              installation?    files in the installation temporary

                               working directory. Any files that have
                               been written to target locations remain
                               there. The installation does not delete
                               any accounts, identifiers, or directory
                               structures that it has created.

              How do I         See Chapter 6.
              restart the
              installation?______________________________________________

        5.1 Keeping a Record of the Installation

              We recommend that you keep a permanent record of the
              installation. To do this, either use a hardcopy terminal,
              or keep a record of the installation in a log file.

        5-2 Installing the TLC

 



                                                       Installing the TLC
                                 5.1 Keeping a Record of the Installation


              To keep a record in a log file, just before you start the
              installation, enter the following command:

              $ SET HOST 0/LOG=filename

              filename is the name of the log file.

              To use the SET HOST command, you must have DECnet running
              on your system.

        5.2 Running the Installation Procedure

              Table 5-2 lists all the steps for installing TLC Version
              2.5. It contains extracts from an installation log, but
              does not show every message that can be displayed during an
              installation.

        Table_5-2_Installation_Procedure_________________________________

        Step_Action______________________________________________________

        1    Invoke VMSINSTAL:

             $ @SYS$UPDATE:VMSINSTAL TLC025 dev

             dev is the device on which the distribution media is to be
             mounted.

        _________________________________________________________________

        2    Confirm system backup

             * Are you satisfied with the backup of your system disk [YES]?

             If you are satisfied with your system backup, press RETURN.
             Otherwise, enter NO, then back up your system disk before
             restarting the installation.

        _________________________________________________________________

                                                 (continued on next page)




                                                   Installing the TLC 5-3

 



        Installing the TLC
        5.2 Running the Installation Procedure


        Table_5-2_(Cont.)_Installation_Procedure_________________________

        Step_Action______________________________________________________

        3    Mount the distribution media.

             When the installation procedure prompts you to, mount the
             distribution media. Then answer the prompt to continue with
             the installation.
             ____________________________________________________________
             For installation
             type__________________Go_to_________________________________

             Full                  Step 5

             Update or additional  Step 4
             language____________________________________________________

        _________________________________________________________________

        4    Update or additional language installation: Indicate the
             installation type.

             The installation procedure checks your ALL-IN-1 system to
             determine what type of installation to do, as described in
             Section 4.1.

             If TLC Version 2.5 has been installed, and you have a
             multilingual ALL-IN-1 system, the procedure displays the
             following:

             This procedure supports the following installation paths:-

                (1)  Update TeamLinks Connection Software

                (2)  Add or update TeamLinks Connection components for an
                     additional ALL-IN-1 IOS language.

             * What type of installation do you wish to perform:

             If you choose an additional language installation, and there
             is more than one additional language on your system, specify
             the language on which you want the TLC components to be
             installed.

        _________________________________________________________________

                                                 (continued on next page)

        5-4 Installing the TLC

 



                                                       Installing the TLC
                                   5.2 Running the Installation Procedure


        Table_5-2_(Cont.)_Installation_Procedure_________________________

        Step_Action______________________________________________________

        5    Answer the ALL-IN-1 link questions.

             The default answers to the ALL-IN-1 link questions are
             those that were given during the last relink of your
             ALL-IN-1 system. See the  ALL-IN-1 Management Guide for
             more information about linking the ALL-IN-1 image.

             During an additional language installation, the link
             questions include the following:

             * Do you want these graphics copied to the ALL-IN-
             1 library directory [NO]?

             Accept the default answer to this question. Your answer does
             not affect the installation.
             ____________________________________________________________
             If_you_are:_____________________Go_to_______________________

             Installing on ALL-IN-1 Version  Step 6
             3.0A

             Installing on ALL-IN-1 Version  Step 7
             3.1_________________________________________________________

        _________________________________________________________________

                                                 (continued on next page)














                                                   Installing the TLC 5-5

 



        Installing the TLC
        5.2 Running the Installation Procedure


        Table_5-2_(Cont.)_Installation_Procedure_________________________

        Step_Action______________________________________________________

        6    ALL-IN-1 Version 3.0A systems: Answer the ALL-IN-1 site link
             questions.

             * Does your ALL-IN-1 IOS system use a SITELINK30.COM?

             If the installation procedure finds a SITELINK30.COM
             file in the OA$BUILD directories, the default answer
             to this question is YES; if the procedure does not find
             SITELINK30.COM, the default answer is NO.

             If there is no SITELINK30.COM file on your system, or if
             none of the applications referred to in SITELINK30.COM is
             currently integrated with your ALL-IN-1 system, answer NO to
             this question.

             If the applications referred to in SITELINK30.COM are
             currently integrated with your ALL-IN-1 system, answer YES
             to this question. The installation procedure then prompts
             you to specify the location of this file. If the procedure
             cannot find the file in the location you specify, it asks
             again whether your ALL-IN-1 system uses a SITELINK30.COM.

        _________________________________________________________________

        7    Indicate whether replaced files are to be purged.

             * Do you want to purge files replaced by this installation [YES]:

             The installation replaces some TLC files with new versions,
             but does not automatically purge the old files.

             Press RETURN to purge the replaced files, or enter NO to
             keep them.

        _________________________________________________________________

        8    Indicate whether to run the IVP.

             * Do you want to run the IVP after the installation [YES]:

             Press RETURN to run the Installation Verification Procedure
             (IVP) on completion of the installation. The IVP checks that
             the TLC has been correctly installed, and produces a log
             file, OA$IVP:TLC$IVP.LOG.

                                                 (continued on next page)

        5-6 Installing the TLC

 



                                                       Installing the TLC
                                   5.2 Running the Installation Procedure


        Table_5-2_(Cont.)_Installation_Procedure_________________________

        Step_Action______________________________________________________

        _________________________________________________________________

        9    Restart ALL-IN-1 on all nodes.

             After successful completion of the installation, if your
             ALL-IN-1 system runs on more than one node of a cluster,
        _____restart_it_on_each_node.____________________________________


































                                                   Installing the TLC 5-7

 










                                                                        6
        _________________________________________________________________

                                               Restarting an Installation


              This chapter describes how to restart an installation after
              the procedure fails or is stopped before completion.

        6.1 Recovering from Installation Errors

              If an error occurs during the installation, VMSINSTAL
              displays an error message that indicates the cause of the
              failure. If this happens, correct the problem identified by
              the error message, then restart the installation.

        6.2 Restoring the Object Libraries

              The TLC installation updates the ALL-IN-1 object library,
              OALIBR.OLB. Before it does this, the installation procedure
              displays instructions like the following[1]:

              If the installation fails or is abandoned after this point,
              return the object libraries to their original state by executing
              the following commands:

              $ LIBRARY/REPLACE OA$BUILD_SHARE_ARCH:OALIBR.OLB  -
                          OA$BUILD_SHARE_ARCH:*.OBJ*_BEFORE_TLC25/LOG

              If the installation fails, or is stopped, after this
              message is displayed but before the postinstallation phase
              begins (see Section 6.3), follow the displayed instructions
              to restore the object libraries to their original state
              before you restart the installation.



              ____________________
              [1]   The exact location of the object library given in the
                    command depends on the version of ALL-IN-1 on which

                    you are installing TLC Version 2.5.

                                           Restarting an Installation 6-1

 



        Restarting an Installation
        6.3 Running the Postinstallation Procedures


        6.3 Running the Postinstallation Procedures

              At the start of the postinstallation phase, the
              installation procedure displays the following message:

              THE INSTALLATION OF TLC V2.5 FILES HAS NOW COMPLETED.

              THE AUTOMATIC POST-INSTALLATION PROCEDURE WILL NOW BE RUN.

              If the installation fails, or is stopped, after this point,
              you do not have to repeat the installation or replace the
              object libraries. Instead, after correcting any problems
              that occurred, rerun the postinstallation procedure. To do
              this, enter the following command:

              $ @OA$LIB_LLV:TLC$POSTINSTALL

              If an error occurs during the postinstallation procedure,
              to correct the problem, you may need to edit the file,
              OA$LIB_LLV:TLC$POSTINSTALL.COM before rerunning the
              postinstallation procedure.
























        6-2 Restarting an Installation

 










                                                                        7
        _________________________________________________________________

                                                       Setting up the TLC


              This chapter describes setup tasks for the TLC. These tasks
              are:

              o  Ensuring that client users are covered by an appropriate
                 license to access ALL-IN-1 services and data. See
                 Section 7.1.

              o  Setting up File Cabinet Servers. See Section 7.2.

              o  Setting up your system to support network communication
                 between the TLC and client applications. See
                 Section 7.3.

              o  Setting up your system to support non-DECnet
                 asynchronous connections. See Section 7.4.

              o  Maintaining TLC files after relinking ALL-IN-1 IOS. See
                 Section 7.5.

        7.1 License Requirements

              You do not need to register any more licenses on your
              ALL-IN-1 system to allow existing ALL-IN-1 users to use the
              TLC to access their ALL-IN-1 accounts from the TeamLinks
              client or any other client application. For each user who
              accesses their existing ALL-IN-1 account from a TeamLinks
              client, all that is required is the appropriate TeamLinks
              client license, which is obtained through the purchase of
              the client software.

              If you create new ALL-IN-1 accounts, you may need to
              register further licenses, depending on the type of
              licenses you use on your ALL-IN-1 system, as shown in
              Table 7-1.


                                                   Setting up the TLC 7-1

 



        Setting up the TLC
        7.1 License Requirements


              Table_7-1_Are_Further_Licenses_Necessary?__________________

              If_________________________Then____________________________

              Your ALL-IN-1 system is    You do not need to register any
              licensed on a capacity     further license
              basis

              Your ALL-IN-1 system is    You must register an additional
              licensed on a concurrent   license if creating new accounts
              use basis                  leads to both the following
                                         conditions:

                                         o  An increase in the number
                                            of users accessing their
                                            ALL-IN-1 accounts at the same
                                            time

                                         o  This increased number of
                                            concurrent users being
                                            greater than the current
                                            number of license units

              Your ALL-IN-1 system is    For each new account that you
              licensed on a personal     create for a client user, you
              use basis                  must register an additional
              ___________________________license_________________________

        7.1.1 Choosing a License

              The choice of which ALL-IN-1 license to use depends on:

              o  The ALL-IN-1 services that users will access

              o  How users will access those services

              Table 7-2 summarizes the ALL-IN-1 licensing options
              available.







        7-2 Setting up the TLC

 



                                                       Setting up the TLC
                                                 7.1 License Requirements


              Table_7-2_Licensing_Options________________________________

              Available_Services_________________Licensing_Option________

                                                             ALL-IN-1
                                                   ALL-IN-1  Client
                                         ALL-IN-1  Core      Services
              ___________________________IOS_______Services__Access______

              Time Management            Yes       No        No

              WPS-PLUS editor            Yes       No        No

              Group Conferencing (DEC    Yes       Yes       No
              Notes)

              Customization Management   Yes       Yes       No

              System Management          Yes       Yes       Yes
              (from VT or by terminal
              emulation)

              Directory access           Yes       Yes       Yes

              Electronic Messaging       Yes       Yes       Yes

              Shared File Cabinet        Yes       Yes       Yes

              VT or terminal emulation   Yes       Yes       No[1]
              support

              TeamLinks client support   Yes       Yes       Yes
              [1]Support_is_provided_for_the_ALL-IN-1_manager.___________

              ___________________________________________________________

              For details of ALL-IN-1 license options, see your Digital
              representative.

              Whatever type of ALL-IN-1 license you use, client
              users must have an appropriate license for the client
              application.

        7.1.2 ALL-IN-1 Client Services Access License

              If users are to access ALL-IN-1 services and data only from
              a client application, and not directly from a VT terminal
              (or by terminal emulation), the most appropriate type of
              license is the ALL-IN-1 Client Services Access license.
              This is a low-cost license that is tailored to the services
              that the client user can access. It allows users to access
              ALL-IN-1 services by means of the TLC, but not directly
              from a VT terminal or by terminal emulation.

                                                   Setting up the TLC 7-3

 



        Setting up the TLC
        7.1 License Requirements


              Table 7-3 shows the different styles of ALL-IN-1 Client
              Services Access license that are available.

              Table 7-3 Styles of the ALL-IN-1 Client Services Access
              __________License__________________________________________

              Style_______Name________________Description________________

              Personal    ALLIN1CLSVR-        Allows a named user to
              Use         PERSONAL            access ALL-IN-1 services
                                              from a client application.

              Concurrent  ALLIN1CLSVR-USER    Allows a single user to
              Use                             access ALL-IN-1 services
                                              from a client application.
                                              The license is relinquished
                                              for use by any other
                                              client user when the
                                              first user stops accessing
                                              ALL-IN-1 from the client
                                              application.

              Capacity    ALLIN1CLSVR         Suitable for ALL-IN-1
                                              systems dedicated to, or
                                              primarily used by, users
                                              of client applications.
                                              The license provides access
                                              to ALL-IN-1 services on an
                                              unlimited user basis for
              ________________________________client_users.______________

              Each form of the ALL-IN-1 IOS Client Services Access
              license allows one system manager access to ALL-IN-1 IOS
              to manage the TLC from a VT or by terminal emulation. You
              can grant access for additional managers or administrators
              through the use of the ALL-IN-1 Core Services Personal Use
              license. This is the lowest-priced option that allows a
              named individual to access ALL-IN-1 IOS from a VT or by
              terminal emulation. Digital does not recommend the use of
              Concurrent Use licensing for ALL-IN-1 managers.

              If most of your users access ALL-IN-1 services from client
              applications, but a smaller number of users also access
              ALL-IN-1 services from VTs or by terminal emulation,
              you can use a combination of Personal or Concurrent Use

        7-4 Setting up the TLC

 



                                                       Setting up the TLC
                                                 7.1 License Requirements


              licenses for ALL-IN-1 IOS or Core Services in addition to
              the ALLIN1CLSVR license.

                ________________________ Note ________________________

                If you wish to change from using ALLIN1CLSVR personal
                licenses to using an ALLIN1CLSVR capacity license,
                you must unload all the ALLIN1CLSVR personal licenses
                before you load the capacity license.

                ______________________________________________________

        7.2 Setting up File Cabinet Servers

              To ensure that File Cabinet Servers run correctly, do the
              following:

              1. If the TLC is installed on a cluster, make sure there
                 is a File Cabinet Server on each ALL-IN-1 system in
                 the cluster. If any system has no File Cabinet Server,
                 create and start one on that system. See Chapter 9 for
                 details of how to do this.

              2. On each system where the File Cabinet Server runs, make
                 sure that the following SYSGEN parameters are set:

                 ________________________________________________________
                 Parameter_____Value_____________________________________

                 SCSSYSTEMID   The DECnet node address of the node on
                               which the File Cabinet Server is running

                 SCSNODE       The DECnet node name of the node on which
                 ______________the_File_Cabinet_Server_is_running________

        7.3 Setting up Network Transport Mechanisms

              The TLC supports several types of mechanism for
              communicating with client applications. Each type of
              transport mechanism needs different software to support
              it. Table 7-4 shows the supported mechanisms for network
              transport between the TLC and client applications. It also
              shows the additional software that must be installed on the
              server system and on the personal computer (PC) to support
              the transport.

                                                   Setting up the TLC 7-5

 



        Setting up the TLC
        7.3 Setting up Network Transport Mechanisms


              Table_7-4_Network_Transport_Mechanisms_____________________

                        Software Required on    Software Required on the
              Mechanism_the_Server_System_______PC_______________________

              DECnet    DECnet[1]               PATHWORKS[TM] for DOS
                                                Version 4.0 (minimum)

              TCP/IP    DEC TCP/IP Services     One of the supported
                        for OpenVMS (UCX)       TCP/IP stacks (refer to
                        Version 2.0 on a VAX    the documentation for
                        system, or Version 3.0  your client application
                        on an Alpha system      for further details)
                        or
                        Other TCP/IP software
                        that runs in UCX
                        emulation

              AppleTalk AppleTalk/DECnet        AppleTalk-DECnet Tool
                        Gateway                 (part of PATHWORKS for
                                                Macintosh)
              [1]Whether_you_use_DECnet_transport_or_not,_you_must_______

              have DECnet running on the system, because this is an
              installation prerequisite of the ALL-IN-1 system.
              ___________________________________________________________

              You can use any combination of the transport mechanisms
              shown in Table 7-4.

              You can install UCX and the AppleTalk/DECnet Gateway after
              you have installed the TLC.

                ________________________ Note ________________________

                If you use UCX, the TLC servers normally have a UCX
                state of disabled. This is because the servers are
                started in ALL-IN-1; not in UCX.

                ______________________________________________________





        7-6 Setting up the TLC

 



                                                       Setting up the TLC
                              7.3 Setting up Network Transport Mechanisms


        7.3.1 If You Use TCP/IP Transport

              To use the TCP/IP network protocol for communications
              between TLC servers and client applications, do the
              following:

        _________________________________________________________________
        Step_Action______________________________________________________

        1    Make sure the appropriate software is installed (see
             Table 7-4).

        _________________________________________________________________

        2    If you use UCX, make sure that the shareable image,
             UCX$IPC_SHR.EXE, is installed in memory. If it is not
             installed, use the following command to install it:

             $ INSTALL CREATE SYS$SHARE:UCX$IPC_SHR.EXE/OPEN/SHARED/HEADER_RES

             To ensure that this image is always installed, add this
             INSTALL command to your system startup procedure.

        _________________________________________________________________

        3    Make sure that the server's details include TCP/IP
             information.

             For an AIDA Server or a File Cabinet Server to use TCP/IP
             networking, the server's details must include a TCP/IP port
             number. Port numbers must be in the range 1024 to 65535.
             Each server on the system must have a unique port number.

             The default TCP/IP port number of the AIDA Server that is
             created when you first install the TLC is 7300. For the File
             Cabinet Server, this default port number is 7373.

             If you use UCX, an AIDA Server can use a service name
             instead of a port number.

             See Section 8.5 for information about an AIDA Server's
             details, and Section 9.5 for information about a File
             Cabinet Server's details.

        _________________________________________________________________

                                                   Setting up the TLC 7-7

 



        Setting up the TLC
        7.3 Setting up Network Transport Mechanisms

        _________________________________________________________________
        Step_Action______________________________________________________

        4    If you use UCX, and specify a TCP/IP service name for an
             AIDA Server, make sure this name is registered in the
             Internet Services database. To register a name, use the
             following command:

             $ UCX SET SERVICE service/FILE=NL:/USER_NAME=account/PORT=number

             service is the name to use for the service. This is a
             character string up to 15 characters long. Allowable
             characters are:

                Letters (A to Z)
                Numbers (0 to 9)
                The dollar character ($)
                The underscore character (_)

             The first character must not be a number.

             account is the name of any unprivileged OpenVMS account. We
             recommend that you use OAFC$DEFAULT.

        _____number_is_the_port_number_you_want_to_use_for_the_server.___

              See the DEC TCP/IP Services for OpenVMS documentation, or
              the documentation for your UCX-emulation software, for more
              information.

        7.3.2 If You Use AppleTalk Transport

              If you use AppleTalk transport, define the logical name
              OA$PC_ATKGATEWAY on each system that runs the PC Broadcast
              Server (see Section 10.1). Use the following command:

              $ DEFINE/SYSTEM/EXECUTIVE OA$PC_ATKGATEWAY node

              node is the node on which the AppleTalk Gateway is running.

              This is necessary to enable client users to receive
              broadcast messages and notification of new mail.

        7.4 Enabling Non-DECnet Asynchronous Connections

              TeamLinks users can, by means of the TLC, access
              ALL-IN-1 services from a remote location by using a modem
              connection.

        7-8 Setting up the TLC

 



                                                       Setting up the TLC
                         7.4 Enabling Non-DECnet Asynchronous Connections


              To enable users to access ALL-IN-1 services in this way:

              o  Set the SYSGEN parameter, TTY_TYPAHDSZ, to a minimum of
                 1400 characters.

              o  Set the user's OpenVMS account details to have a
                 buffered I/O byte limit of at least 48 000. Add a
                 further 12 000 bytes for each expected network link.
                 An operation such as creating a mail message, attaching
                 documents to it from the File Cabinet, and sending it
                 can use 3 or 4 open network links.

        7.5 Relinking ALL-IN-1 IOS

              After the TLC is installed, if you relink your ALL-IN-1
              system for any of the reasons described in  ALL-IN-1
              Management Guide, copy the image file, OA$AIDA_SECSHR.EXE,
              to SYS$COMMON:[SYSLIB] after the relink.

              See  ALL-IN-1 Management Guide for information about
              relinking ALL-IN-1.
























                                                   Setting up the TLC 7-9

 










                                                                        8
        _________________________________________________________________

                                                    Managing AIDA Servers


              The AIDA Server is a network object that enables users
              of the TeamLinks client and other client applications to
              access ALL-IN-1 data.

        8.1 Accessing the Manage AIDA Servers Menu

              Options for managing AIDA servers are on the Manage AIDA
              Servers menu. Table 8-1 shows how to display this menu.

              Table_8-1_Displaying_the_Manage_AIDA_Servers_Menu__________

              On ALL-IN-1 Version 3.0A
              Systems___________________On_ALL-IN-1_Version_3.1_Systems__

              1. At the ALL-IN-1        1. At the ALL-IN-1 Management
                 Management menu,          menu, use the Manage ALL-IN-1
                 use the Manage AIDA       servers (MSS) option
                 servers (MAS) option   2. At the Manage ALL-IN-1 Servers

                                           menu, use the Manage AIDA
                                           servers (MAS) option

              ___________________________________________________________

        8.2 How the AIDA Server Works

              To access ALL-IN-1 data, a client application connects
              to the AIDA Server, thereby creating a session with the
              AIDA Server. Many AIDA Server sessions can run at the same
              time, thus allowing large numbers of client users to access
              ALL-IN-1 data at the same time.





                                                Managing AIDA Servers 8-1

 



        Managing AIDA Servers
        8.2 How the AIDA Server Works


              Each AIDA Server session is associated with an ALL-IN-1
              account. To access ALL-IN-1 data on behalf of a client
              user, the AIDA Server creates a session associated with
              that user's ALL-IN-1 account. The ALL-IN-1 account used
              determines which personal ALL-IN-1 data, such as nicknames,
              the session can access. The AIDA Server checks that the
              OpenVMS account associated with the ALL-IN-1 account has
              the necessary access rights to the ALL-IN-1 data that is
              requested.

        8.3 When are Management Tasks Necessary?

              When the TLC is installed on your ALL-IN-1 system, a single
              instance of the AIDA Server is created and started on each
              node of the cluster on which ALL-IN-1 IOS is running. This
              server runs with default settings.

              No regular maintenance tasks are necessary to manage AIDA
              servers. Management tasks enable you to:

              o  Change the way the servers run to best suit your site's
                 needs

              o  Identify and solve problems

        8.4 What do Management Tasks Involve?

              Managing AIDA servers involves manipulating variables, as
              shown in Table 8-2.

        Table_8-2_Managing_AIDA_Servers__________________________________

                                                              For further
                                   Involve manipulating       informa-
        These_tasks:_______________these_variables:___________tion:______

        Configuring a server       Configuration details of   See
                                   a server                   Section 8.5

        Optimizing the             Configuration details of   See
        performance of servers     a server                   Section 8.5
                                   Variables shown in         and
                                   Table 8-4                  Section 8.6

                                                 (continued on next page)

        8-2 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                    8.4 What do Management Tasks Involve?


        Table_8-2_(Cont.)_Managing_AIDA_Servers__________________________

                                                              For further
                                   Involve manipulating       informa-
        These_tasks:_______________these_variables:___________tion:______

        Ensuring that servers      Frequency with which       See
        access up-to-date data     servers reopen system      Section 8.7
        files                      files

        Enabling client users to   Library search orders      See
        access additional form                                Section 8.8
        libraries

        Starting, stopping, and    State of a server          See
        disabling a server                                    Section 8.9

        Monitoring and             Connections to a server    See
        controlling connections                               Section 8.10

        Detecting the cause of     Tracing                    See
        problems______________________________________________Section_11.3

        8.5 Configuring an AIDA Server

              When you create a new server or modify the way a server
              runs, you create or edit an entry for the server in the
              server configuration file. This file contains configuration
              details of the server. To see the configuration details
              of a server, use the Read (R) or Print (P) option on the
              Manage AIDA Servers menu.

              Many of the configuration settings have default values. You
              can choose to run a server with these default values, or to
              set your own values.

              Table 8-3 shows the configuration details that you can set
              for an AIDA Server. It also shows the default values that
              apply if you do not set your own values.






                                                Managing AIDA Servers 8-3

 



        Managing AIDA Servers
        8.5 Configuring an AIDA Server


        Table_8-3_AIDA_Server_Configuration_Details______________________

                      Default
        CharacteristicValue_______Description____________________________

        Description   -           A short description that you give to
                                  the server to distinguish it from other
                                  servers on the same node or cluster.
                                  You use this description when you
                                  select a server to work with.

        Node name     -           The name of the node on which the
                                  server runs. This can be any node in
                                  the cluster on which your ALL-IN-1
                                  system is running.

        Startup       -           The name of the batch queue to which
        queue                     the server's startup command file,
                                  OA$LIB:SM_AIDA_START_SERVER.COM, is
                                  submitted. The queue must:

                                  o  Be on the node specified as the Node
                                     name

                                  o  Not be a generic queue

                                  o  Have an entry in the Node Specific
                                     Batch Queues data set (accessed by
                                     the Manage node specific queues
                                     (MNQ) option on the ALL-IN-1
                                     Management menu)

                                  o  Be started

                                                 (continued on next page)










        8-4 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                           8.5 Configuring an AIDA Server


        Table_8-3_(Cont.)_AIDA_Server_Configuration_Details______________

                      Default
        CharacteristicValue_______Description____________________________

        DECnet        OA$AIDA     The name of the DECnet object that
        object                    the server uses to listen for network
                                  connections. This can be either:

                                  o  A name

                                     DECnet object names can be up to
                                     12 characters long. Allowable
                                     characters are letters (A to Z),
                                     numbers (0 to 9), the underscore
                                     character (_), and the dollar
                                     character ($). The first character
                                     in a name must not be a number.

                                  o  A number

                                     DECnet object numbers must be in the
                                     range 0 to 255. Digital recommends
                                     that you avoid using numbers below
                                     128, because these are reserved by
                                     Digital.

                                  Each server on a single node must have
                                  a unique DECnet object name or number.

                                                 (continued on next page)














                                                Managing AIDA Servers 8-5

 



        Managing AIDA Servers
        8.5 Configuring an AIDA Server


        Table_8-3_(Cont.)_AIDA_Server_Configuration_Details______________

                      Default
        CharacteristicValue_______Description____________________________

        TCP/IP port   7300 or     The TCP/IP port number or service name
                      OA$AIDA[1]  that the server uses to listen for
                                  network connections.

                                  If you use UCX, and specify a TCP
                                  /IP service name, the name must be
                                  registered in the Internet Services
                                  database. See Section 7.3.1 for details
                                  of how to do this.

                                  If you use a TCP/IP port number, it
                                  must be in the range 1024 to 65535.
                                  Each server on a single node must have
                                  a unique TCP/IP port number.

        Start server  Y           Determines whether or not the server is
        during                    automatically started during ALL-IN-1
        ALL-IN-1                  startup.
        startup

        Restart       Y           Determines whether or not the server is
        server on                 automatically restarted after failing
        failure                   during operation.

        Delete log    Y           Determines whether or not existing
        files during              error log files are automatically
        server                    deleted when the server starts. See
        startup                   Section 11.2 for information about log
                                  files.

        Delete trace  Y           Determines whether or not old trace
        files during              files are automatically deleted when
        server                    the server starts. See Section 11.3.2
        startup                   for information about trace files.

        [1]The_default_value_for_the_TCP/IP_port_is_that_specified_______

        for the AIDA Server when the TLC was first installed. If UCX
        was present on the system at that time, the value is OA$AIDA;
        otherwise it is 7300.

                                                 (continued on next page)

        8-6 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                           8.5 Configuring an AIDA Server


        Table_8-3_(Cont.)_AIDA_Server_Configuration_Details______________

                      Default
        CharacteristicValue_______Description____________________________

        Maximum       0           The maximum number of client
        number of                 connections that the server accepts.
        connected                 A value of zero means that there
        clients                   is no limit to the number of client
                                  connections. See Section 8.6.1.

        Process       4           The priority of the process in which
        priority[2]               the server runs.

        Process       See Section 8.6.2
        quotas
        [2]If_the_process_priority_has_a_higher_value_than_the_default___

        value, the account used for submitting management batch jobs
        must have the ALTPRI privilege granted. This privilege must be
        granted as both an authorized and a default privilege. If the
        ALTPRI privilege is not granted to the appropriate account,
        the higher setting does not take effect. The account used for
        submitting management batch jobs is specified in the ALL-IN-1
        system policies. See  ALL-IN-1 Management Guide for information
        about defining system policies.
        _________________________________________________________________

        8.6 Tuning an AIDA Server

              Table 8-4 shows the factors that affect the performance of
              an AIDA Server.

        Table_8-4_Factors_That_Affect_Performance_of_an_AIDA_Server______

        Factor___________Description_____________________________________

        Number of        The more users who access a server at the
        concurrent       same time, the slower the performance. See
        users            Section 8.6.1.

        Process quotas   See Section 8.6.2 and the OpenVMS documentation
                         for details of process quotas and system tuning.

                                                 (continued on next page)

                                                Managing AIDA Servers 8-7

 



        Managing AIDA Servers
        8.6 Tuning an AIDA Server


        Table 8-4 (Cont.) Factors That Affect Performance of an AIDA
        __________________Server_________________________________________

        Factor___________Description_____________________________________

        Process          You can set the process priority for the server
        priority         to give the server priority over other processes
                         on the system. This improves the performance
                         of the server, but degrades the performance of
                         other processes.[1]

        Mail directory   Mail directory inquiries sometimes take a long
        usage            time to complete. If several client users
                         use the Mail directory at the same time, the
                         performance of other processes on the server is
                         degraded. See Section 8.6.3.

        Tracing          Performance of the server is slightly degraded
                         if tracing is turned on.
        [1]If_the_process_priority_has_a_higher_value_than_the_default___

        value, the account used for submitting management batch jobs
        must have the ALTPRI privilege granted. This privilege must be
        granted as both an authorized and a default privilege. If the
        ALTPRI privilege is not granted to the appropriate account,
        the higher setting does not take effect. The account used for
        submitting management batch jobs is specified in the ALL-IN-1
        system policies. See  ALL-IN-1 Management Guide for information
        about defining system policies.
        _________________________________________________________________

        8.6.1 Controlling the Number of Users

              You can control the number of concurrent users of a server
              by specifying a value for the Maximum number of connected
              clients in the server's configuration details. A value
              of zero (the default) means that there is no limit to the
              number of client users who can access the server at the
              same time. If you specify a non-zero value, it must be at
              least 10.

              Setting a limit on the number of concurrent users enables
              the server to respond more quickly to requests from users.
              It also reduces the amount of system resources required by
              the server.

        8-8 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                                8.6 Tuning an AIDA Server


              Make sure, however, that when setting a maximum number of
              concurrent users, you specify a number high enough to allow
              all potential client users to access the server at the same
              time. For example, if your system has 100 users who want to
              access their ALL-IN-1 account from a TeamLinks client, set
              the maximum number of concurrent users to at least 100.

              The higher the value that is set for the maximum number
              of concurrent users, the higher the values are for
              the recommended process quotas. If the Maximum number
              of connected clients field has a value of zero, the
              recommended process quotas are calculated as if this field
              had a value of 100.

        8.6.2 Setting Process Quotas

              The process quotas that affect the performance of the AIDA
              Server are shown in Table 8-5. These quotas, together with
              their values, are displayed on the second page of the
              Server Configuration form when you read or edit details
              of a server.

              Table_8-5_Process_Quotas_Affecting_the_AIDA_Server_________

              AST queue limit            (ASTLM)

              Lock queue entry limit     (ENQLM)

              Open file limit            (FILLM)

              Timer queue limit          (TQELM)

              Buffered I/O byte limit    (BYTLM)

              Direct I/O count limit     (DIOLM)

              Buffered I/O count limit   (BIOLM)

              Page file quota            (PGFLQUOTA)

              Working set default        (WSDEFAULT)

              Working set quota          (WSQUOTA)

              Working_set_extent_________(WSEXTENT)______________________

              The recommended values for these process quotas are
              calculated using the following values:

              o  Maximum number of connected clients

              o  The value of the system logical name, OA$DDS_PRIME

                                                Managing AIDA Servers 8-9

 



        Managing AIDA Servers
        8.6 Tuning an AIDA Server


              These values are shown on the second page of the Server
              Configuration form, which is displayed when you read or
              edit details of a server.

              To override the recommended process quota values:

              1. Set the Use recommended process quotas field of the
                 Server Configuration form to N.

              2. Enter the values that you want to use in the Overridden
                 column.

        8.6.3 Controlling Mail Directory Usage

              On a system where the value of the logical name, OA$DDS_
              PRIME, is 1 or 2, client users can initiate Mail directory
              inquiries. A Mail directory inquiry is a single task that
              involves sending the inquiry to a subprocess and waiting
              for the results to be returned. Such an inquiry can take
              some time to complete, particularly if the search criteria
              specified are of a general nature.

              The number of concurrent tasks an AIDA Server can perform
              is limited. The AIDA Server may reach this limit to the
              number of concurrent tasks if several client users request
              Mail directory inquiries at the same time. In such a
              case, the server cannot perform any other tasks until it
              completes a Mail directory inquiry. When this happens, the
              server appears to stop working for a time.

              You can reduce the impact of Mail directory inquiries on
              system performance in the following ways:

              o  Limit the ability of users to specify very broad search
                 criteria when requesting a search.

                 Because of the time taken to return all entries from the
                 Mail directory, the AIDA Server does not initiate a Mail
                 directory inquiry when the client user requesting the
                 inquiry specifies no search criteria. You can further
                 restrict general searches by setting a minimum number
                 of characters that users must specify for the surname
                 (last name) criterion when they request a Mail directory
                 inquiry. To do this, define the system logical name,
                 OA$AIDA_DDS_MIN_SURNAME, to specify this minimum number
                 of characters.

        8-10 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                                8.6 Tuning an AIDA Server


              o  Limit the period of time that the AIDA Server waits for
                 a response from the Mail directory.

                 When the AIDA Server initiates a Mail directory inquiry,
                 it waits for a response from the Mail directory. If it
                 receives no response after a given time, the AIDA Server
                 stops the search. Normally, this waiting time is 60
                 seconds. You can change this waiting time by defining
                 the system logical name, OA$AIDA_DDS_TIMEOUT_SECONDS,
                 to specify the maximum time, in seconds, to wait for a
                 response from the Mail directory.

              o  Increase the maximum number of concurrent tasks the
                 server can do.

                 Do this as follows:

                 1. Use Customization Management to edit the DO script,
                    OA$LIB:SM_AIDA_CALCULATE_QUOTAS.

                 2. Find the following part of the script:

                    .IF oa$dds_prime gt 0
                        .THEN
                            get #pop_dds_max = 5
                            get #pop_threads_max = 15

                 3. Increase the value of #pop_threads_max.

        8.7 Ensuring Access to Up-to-date Data Files

              When a new version of a system data file is created, the
              AIDA Server does not immediately access the new version.
              Normally, the server reopens all system files at midnight
              every night.

              To gain immediate access to a new version of a system data
              file, disable then reenable the server, or stop and restart
              it.

              To increase the frequency with which the AIDA Server
              reopens system data files, define the system logical name,
              OA$AIDA_FLUSH_TIME, setting a delta-time value for the
              frequency with which system files are to be reopened, as
              shown in the examples in Table 8-6.

                                               Managing AIDA Servers 8-11

 



        Managing AIDA Servers
        8.7 Ensuring Access to Up-to-date Data Files


              Table_8-6_OA$AIDA_FLUSH_TIME_Values________________________

                                              Define OA$AIDA_FLUSH_TIME
              To_Reopen_System_Files_Every:___as:________________________

              30 minutes                      0 0:30:0

              Six_hours_______________________0_6:0:0____________________

              When you set a value for OA$AIDA_FLUSH_TIME, this value
              takes effect the next time the AIDA Server reopens system
              data files.

        8.8 Accessing Additional Form Libraries

              By default, the AIDA Server accesses data files that are
              associated with entry forms held in the following standard
              form libraries:

              o  SITEMEMRES

              o  MEMRES

              o  SITEOAFORM

              o  OAFORM

              o  SITEMANAGER

              o  MANAGER

              Alternatively, the AIDA Server can access form libraries
              that are specified in a library search order created for
              your system. The AIDA Server accesses:

              o  Form libraries listed in the AIDA library search order,
                 OA$LIB:AIDA.A1$LSO. All AIDA servers that are started
                 when this search order is present on your system use the
                 form libraries listed here rather than the standard form
                 libraries.

              o  Form libraries listed in a library search order defined
                 by the logical name OA$AIDA_LSO_FILE. All AIDA servers
                 that are started when this logical name is defined on
                 your system use the form libraries listed in this search
                 order rather than the standard form libraries or those
                 listed in the AIDA library search order.

        8-12 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                  8.8 Accessing Additional Form Libraries


                 Use this logical name for testing an application or a
                 library search order before making it available for use
                 by client users. See Table 8-8.

        8.8.1 Creating an AIDA Library Search Order

              To enable client users to access additional form libraries
              on your ALL-IN-1 system, create the library search order,
              AIDA.A1$LSO, and include the libraries that you want users
              to access. See Table 8-7.

              Table_8-7_How_to_Create_an_AIDA_Library_Search_Order_______

              Step__Description__________________________________________

              1     Use Customization Management to create an element
                    with the following characteristics:

                    Name: AIDA

                    Type: LSO

                    Area: SHARE

                    Making sure that SITEMEMRES and MEMRES remain at
                    the top of the list, add the form libraries that the
                    AIDA Server is to access. Include the standard form
                    libraries listed above as well as the additional form
                    library or libraries specific to your system.

              2     Use the MLA option to mark the new element for moving
                    to the live area.

              3     Use the PME option on the Application Maintenance
                    menu to move the element to the live area.

              4     Restart the AIDA Server to enable it to open the form
              ______libraries_listed_in_AIDA.A1$LSO._____________________

        8.8.2 Using a Test Library Search Order

              Use the logical name OA$AIDA_LSO_FILE when testing a new
              application before making it available for use by client
              users. See Table 8-8.

                                               Managing AIDA Servers 8-13

 



        Managing AIDA Servers
        8.8 Accessing Additional Form Libraries


              Table_8-8_How_to_Use_a_Library_Search_Order_for_Testing____

              Step__Description__________________________________________

              1     Use Customization Management to create the library
                    search order and move it to the live area, as
                    described in Table 8-7. Do not use AIDA as the
                    element name.

              2     Make sure that all the AIDA servers on your system
                    are running.

              3     Define the logical name OA$AIDA_LSO_FILE, giving
                    as its value the file specification of the library
                    search order.

              4     Create a new AIDA Server (see Section 8.11), then
                    start it. This server uses the library search order
                    defined by the logical name OA$AIDA_LSO_FILE.

              5     Connect to the new server and check that you can
                    access the data referenced by the libraries listed in
                    the new search order.

              6     Once testing is complete, use Customization
                    Management to create an AIDA library search order
                    element, as described in Table 8-7. Use the test
                    search order as a template.

                    Alternatively, if there is already an AIDA library
                    search order on your system, edit it to add the form
                    library or libraries that you have tested.

              7     Deassign the logical name OA$AIDA_LSO_FILE.

              8     AIDA servers on your system will use the new AIDA
                    library search order the next time they restart. If
                    you want to access the new search order immediately,
                    stop then restart all the AIDA servers on your
              ______system.______________________________________________

        8.9 Changing the State of an AIDA Server

              The state of an AIDA Server determines its availability
              for use by client applications and for manipulation by an
              ALL-IN-1 manager. To see the state of a server, look at the
              current item block or at the Index of Servers.

        8-14 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                 8.9 Changing the State of an AIDA Server


              Table 8-9 shows the states that an AIDA Server can have.

        Table_8-9_AIDA_Server_States_____________________________________

                                           Access for       Access for
        State___Description________________Managers_________Users________

        Running The server's               All operations   Full.
                initialization processes   except Start,
                are complete, and the      Enable, Delete,
                server is able to accept   and Edit.
                connections from client
                applications.

        DisabledClient applications        All operations   Unavailable
                cannot establish new       except Start,    for new
                sessions with the server.  Disable,         sessions.
                Existing sessions are      Delete, and
                unaffected.                Edit.

        StoppingThe server is              Read, Print.     None.
                disconnecting all current
                sessions.

        Stopped All sessions with          Start, Read,     None.
                the server have been       Edit, Print,
                disconnected.              and Delete.

        StartingTransitional state         Read, Print.     None.
                between Stopped and
        ________Running._________________________________________________

              To change the state of a server, use options on the Manage
              AIDA Servers menu, or on the Index of Servers menu. These
              are:

              o  Start server (STA)

              o  Stop server (STO)

              o  Enable server (ENA)

              o  Disable server (DIS)


                                               Managing AIDA Servers 8-15

 



        Managing AIDA Servers
        8.9 Changing the State of an AIDA Server


        8.9.1 Starting an AIDA Server

              To start a server interactively on any node on a cluster in
              which ALL-IN-1 IOS is running, use the Start server (STA)
              option.

              A server's characteristics, as set in the server
              configuration file (see Section 8.5), determine whether
              it starts automatically under the following conditions:

              o  During ALL-IN-1 startup

              o  After failure

              If automatic start fails, the system makes further attempts
              to start the server, up to a maximum of 5 attempts.

              When a server starts, it is able to accept connections from
              clients. You do not have to use the Enable server (ENA)
              option after the server has started.

        8.9.2 Stopping an AIDA Server

              When an AIDA Server stops, any sessions with the server
              are immediately disconnected. Therefore, before you use the
              Stop server (STO) option, it is advisable to:

              1. Disable the server to prevent client users from starting
                 new sessions with the server.

                 Use the Disable server (DIS) option to do this. No
                 new connections can be made to the server when it is
                 Disabled. Existing connections are unaffected.

                 If you disable a server, and then want to allow new
                 connections to be made to it again without stopping it,
                 use the Enable server (ENA) option.

              2. Use the Index of server connections (ISC) option to
                 check whether anyone is using the server. Inform any
                 users who are connected to the server that you intend to
                 stop the server, and warn them that they will be unable
                 to use ALL-IN-1 messaging facilities.

              If there are any connections other than the one to the
              ALL-IN-1 MANAGER account when you use the STO option,
              ALL-IN-1 prompts you to specify whether you want to
              continue to stop the server.

        8-16 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                 8.9 Changing the State of an AIDA Server


              AIDA servers stop automatically when ALL-IN-1 IOS is shut
              down. To receive broadcast messages that warn that ALL-IN-1
              is to be shut down and that ALL-IN-1 has been restarted,
              client users must enable notification from the client
              application.

        8.10 Monitoring and Controlling Connections to an AIDA Server

              Use the Index of server connections (ISC) option to
              create an index of client users who are connected to the
              currently-selected server. The server must be running for
              this option to work.

              The index identifies when each client connection was
              established, and when the latest request was made of the
              server during the session.

              Table 8-10 shows the options you can use from the index of
              server connections to monitor and control connections to
              the server.

              Table_8-10_Options_on_the_Index_of_Server_Connections_Menu_

              Option________Description__________________________________

              Delete        Disconnects a session. Use this option to
                            disconnect a session that is causing problems
                            such as locking a file. When you delete a
                            session, the client user cannot do messaging
                            operations, such as addressing.

                            You cannot use this option to disconnect the
                            session that you are using for managing the
                            server.

              Turn on       Turns on tracing for a session. See
              tracing       Section 11.3.

              Turn off      Turns off tracing for a session. See
              tracing_______Section_11.3.4.______________________________

              In addition to the options shown in Table 8-10, options
              that change the state of a server also affect connections
              to the server (see Section 8.9).

                                               Managing AIDA Servers 8-17

 



        Managing AIDA Servers
        8.11 Creating an AIDA Server


        8.11 Creating an AIDA Server

              When the TLC is installed on your ALL-IN-1 system, a single
              instance of the AIDA Server is created and started on each
              node of the cluster on which ALL-IN-1 IOS is running. This
              is normally adequate to cope with all client connections.
              Normally, you need to create a server only for testing
              purposes (for example, see Section 8.8.2) or to replace a
              server that you have deleted.

              To create a server, do the following:

              1. Select the Create (C) option on the Manage AIDA Servers
                 menu or on the Index of Servers menu.

              2. Complete the details of the server on the Server
                 Configuration form. As a minimum, you must provide the
                 following information:

                 o  Description

                 o  Node name (if ALL-IN-1 runs on more than one node of
                    a cluster)

                 o  DECnet object name, TCP/IP port number, or both.

                 See Table 8-3 for details of the fields in the Server
                 Configuration form. See Section 8.6 for more details of
                 the factors that affect performance of the server.

              When first created, the server has a state of Stopped.
              You must start it before users of client applications can
              connect to the server. Use the Start server (STA) option to
              do this.

              For client users to connect to a server that you create,
              rather than to the default server created when the TLC
              was installed, details of the new server must replace the
              details of the default server in the initialization file
              for the client application.

        8.12 Removing an AIDA Server

              To remove an AIDA Server from your system, use the Delete
              (D) option on the Manage AIDA Servers menu or on the Index
              of Servers menu. Alternatively, to delete more than one
              server, use the Delete all selected (XD) option on the
              Index of Servers menu.

        8-18 Managing AIDA Servers

 



                                                    Managing AIDA Servers
                                             8.12 Removing an AIDA Server


              A server must be stopped before you can delete it. See
              Section 8.9.2 for information about stopping a server.

              When you delete a server, all connections to the server are
              terminated, and all error and trace log files associated
              with the server are deleted.







































                                               Managing AIDA Servers 8-19

 










                                                                        9
        _________________________________________________________________

                                            Managing File Cabinet Servers


              This chapter gives an introduction to the File Cabinet
              Server, and describes the tasks involved in managing File
              Cabinet servers.

              For more information about the ALL-IN-1 File Cabinet,
              see  ALL-IN-1 Application Programming: Guide and  ALL-IN-1
              Management Guide.

        9.1 Overview of the File Cabinet Server

              The following sections describe how the File Cabinet Server
              works, and introduce concepts that you need to understand
              when you manage File Cabinet servers.

        9.1.1 What the File Cabinet Server Does

              The File Cabinet Server enables TeamLinks clients and
              remote ALL-IN-1 VT clients to access drawers and documents
              in the ALL-IN-1 File Cabinet.

              In addition, the File Cabinet Server controls the following
              operations for all clients, including local ALL-IN-1 VT
              clients:

              o  Operations that involve more than one drawer, such as
                 refiling a document to a different drawer

              o  Document reservations

        9.1.2 Connections to the File Cabinet Server

              The File Cabinet Server operates on behalf of each of its
              clients in the context of a connection with that client.
              When a client user chooses an option that requires the
              use of the File Cabinet Server, the client connects to the
              File Cabinet Server. Similarly, when you use options to
              manage the File Cabinet Server, the operations are done in
              the context of a management connection to the server. VT

                                        Managing File Cabinet Servers 9-1

 



        Managing File Cabinet Servers
        9.1 Overview of the File Cabinet Server


              clients are not aware of connecting to the server, unless
              the server is not running, when they receive the message:

              File Cabinet Server is not available

        9.1.3 Locating File Cabinet Objects

              The File Cabinet Server uses the DECnet node name to locate
              File Cabinet objects (drawers, folders and documents),
              When it receives a request for an object, the File Cabinet
              Server uses the DECnet node name associated with the object
              to determine whether the object is in the local ALL-IN-1
              File Cabinet or in another ALL-IN-1 File Cabinet. If the
              object is in a different File Cabinet, the server forwards
              the request to the File Cabinet Server on that ALL-IN-1
              system.

              On receiving a request for an object in the local File
              Cabinet, the File Cabinet Server uses the partition file,
              OA$DATA_SHARE:PARTITION.DAT, to locate the drawer. The
              server checks that the user has access to the drawer, and
              checks their level of access. If the user has the necessary
              levels of access, the server executes the request on behalf
              of the user.

        9.1.4 Opening Drawers

              When it accesses a drawer, or a document within a drawer,
              the File Cabinet Server takes out a lock on the drawer. The
              drawer is then said to be open. Once a drawer is open, it
              remains open in case it is requested again. This minimizes
              the overhead of opening drawers.

              To reduce the load on virtual memory that is imposed by
              keeping large numbers of drawers open, the File Cabinet
              Server includes a maintenance routine that periodically
              closes the least frequently-used drawers. You can specify
              the maximum number of drawers to be left open when this
              maintenance routine runs by changing a setting in the
              server's attributes. See Section 9.12.4.





        9-2 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                                  9.1 Overview of the File Cabinet Server


        9.1.5 The Drawer Cache

              The File Cabinet Server maintains a drawer cache, which
              contains information about the drawers that are open.
              Some of this information, such as that about authorized
              access to a drawer, is liable to change while the drawer
              is open. To reduce the probability of using out-of-date
              information, the File Cabinet Server periodically updates
              this information. The frequency with which the File Cabinet
              Server updates this information is determined by the
              Authorized Timeout attribute. See Table 9-4.

              See Section 9.12.4 for information about controlling the
              size of the drawer cache.

        9.2 Tasks Involved in Managing File Cabinet Servers

              You can manage all the File Cabinet servers on all the
              nodes in the same cluster (known as local nodes). In
              addition, you can do some management of servers on remote
              nodes. See Section 9.4 for details of how to manage remote
              servers.

              Table 9-1 shows the tasks involved in managing File Cabinet
              servers.




















                                        Managing File Cabinet Servers 9-3

 



        Managing File Cabinet Servers
        9.2 Tasks Involved in Managing File Cabinet Servers


        Table_9-1_Management_Tasks_for_the_File_Cabinet_Server___________

                                                         For Further
        Task__________________When_Necessary_____________Information:____

        Creating a File       After installing the       See Section 9.6.
        Cabinet Server        TLC, if there are any
                              ALL-IN-1 systems in the
                              same cluster without a
                              File Cabinet Server.

                              For performance
                              reasons, when there
                              are large numbers of
                              users accessing the
                              ALL-IN-1 File Cabinet. In
                              particular, you should
                              create a second server if
                              you expect the number of
                              active users to exceed
                              500.

        Changing the          When you want to change    See
        configuration or      the way the server runs,   Section 9.7 and
        attributes of a File  or to tune the server for  Section 9.12.
        Cabinet Server        better performance.

        Deleting a File       When you no longer want    See Section 9.8.
        Cabinet Server        the server.

        Starting a File       After editing a server,    See
        Cabinet Server        to bring your changes      Section 9.9.1.
                              into effect.

                              After stopping a server.

        Stopping a File       After editing the server,  See
        Cabinet Server        so that you can restart    Section 9.9.2.
                              it to bring your changes
                              into effect.

                              Before deleting the
                              server.

                                                 (continued on next page)

        9-4 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                      9.2 Tasks Involved in Managing File Cabinet Servers


        Table_9-1_(Cont.)_Management_Tasks_for_the_File_Cabinet_Server___

                                                         For Further
        Task__________________When_Necessary_____________Information:____

        Enabling a File       When the server has been   See
        Cabinet Server        disabled, and you want to  Section 9.9.3.
                              reenable it in order to
                              allow clients to connect
                              to it.

        Disabling a File      When you want to prevent   See
        Cabinet Server        clients connecting to the  Section 9.9.4.
                              server.

        Monitoring            When you want to know      See
        connections to the    about the activity of the  Section 9.10.
        File Cabinet Server   server.

        Resetting the         When you want to change    See
        warning for disk      the point at which the     Section 9.11.
        quota limit           File Cabinet Server
                              issues a warning that
                              the owner of a drawer is
                              approaching their disk
                              quota limit.

        Tuning a File         When you want to improve   See
        Cabinet Server        the performance of the     Section 9.12.
                              server.

        Monitoring the        When you want to know      See
        activity of a File    about the activity of the  Section 11.5.
        Cabinet Server        server, or to diagnose
        ______________________problems_with_the_server.__________________

        9.3 Accessing the Options for Managing File Cabinet Servers

              Most of the tasks shown in Table 9-1 can be done through
              the use of options on the Manage Servers menu. Table 9-2
              shows how to display this menu.




                                        Managing File Cabinet Servers 9-5

 



        Managing File Cabinet Servers
        9.3 Accessing the Options for Managing File Cabinet Servers


              Table_9-2_Displaying_the_Manage_Servers_Menu_______________

              On ALL-IN-1 Version 3.0A       On ALL-IN-1 Version 3.1
              Systems________________________Systems_____________________

              1. At the ALL-IN-1 Management  1. At the ALL-IN-1
                 menu, use the Manage File      Management menu, use the
                 Cabinets (MFC) option          Manage ALL-IN-1 servers
              2. At the Manage File             (MSS) option

                 Cabinets menu, use the      2. At the Manage ALL-IN-1
                 Manage Servers (MS) option     Servers menu, use the
                                                Manage File Cabinet
                                                servers (MFS) option

              ___________________________________________________________

        9.4 Managing a Remote File Cabinet Server

              You can do some management of File Cabinet servers that are
              on remote systems. The following restrictions apply to the
              management of remote servers:

              o  You cannot create a File Cabinet Server on a remote
                 system

              o  You cannot use the Start server (STA) option

              o  You cannot use the Edit (E) option

              o  The Read and Print options show only attributes; not
                 configuration information

              To manage a File Cabinet Server on a remote system:

              1. Ask the manager of the remote system to create a proxy
                 account for you on that system. The account must have
                 the OAFC$SYSMAN rights identifier.

              2. Create an entry for the server in the server master
                 file, OAFC_SERVER_MASTER.DAT, as shown in Table 9-3. To
                 do this, you need the following information:

                    The name of the node where the server is located
                    The DECnet object number of the server
                    The TCP/IP port number of the server

        9-6 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                                9.4 Managing a Remote File Cabinet Server


                 See Table 9-4 for details. Information about the TCP/IP
                 port number is in the Attributes section of this table.

              Table 9-3 Creating an Entry for a Remote File Cabinet
              __________Server___________________________________________

              Step__Action_______________________________________________

              1     Use the Create (C) option on the Manage Servers menu.

              2     Use the Create remote server master entry (CR)
                    option.

              3     Enter details of the server in the Create a Server
                    form. If the server does not use a TCP/IP port, enter
              ______zero_(0)_in_the_Server_port_number_field.____________

        9.5 File Cabinet Server Configuration and Attributes

              When you create a File Cabinet Server or modify the way
              a server works, you create or edit an entry in the master
              file, OAFC_SERVER_MASTER.DAT. This file contains a list of
              all the File Cabinet servers that you manage.

              Table 9-4 shows the details that you can set or change for
              a File Cabinet Server, together with the values that apply
              by default if you do not set your own values. To see the
              settings for a server, use the Read (R) or Print (P) option
              on the Manage Servers menu (see Section 9.3).

                _______________________ Caution _______________________

                Do not change server attributes unless you have a good
                understanding of the File Cabinet Server. Changing
                server attributes affects the performance of the
                server. See Section 9.12 for information about tuning
                the File Cabinet Server.

                ______________________________________________________






                                        Managing File Cabinet Servers 9-7

 



        Managing File Cabinet Servers
        9.5 File Cabinet Server Configuration and Attributes


        Table_9-4_File_Cabinet_Server_Configuration_and_Attributes_______

        Setting_______________Default_Value_________Description__________

        _________________Components_of_the_Server's_Name_________________

        Server node name      -                     The name of the node
                                                    on which the server
                                                    runs.

        Server object number  73[1]                 The DECnet object
                                                    number for the
                                                    server. If you
                                                    create any additional
                                                    server, the object
                                                    number must be:

                                                    o  In the range 128
                                                       to 255

                                                    o  Unique on the node
                                                       where the server
                                                       runs

        _________________________________________________________________
        __________________________Configuration__________________________

        Process Name          node$SRVobj           The name of the
                              node and obj are the  process in which
                              node name and object  the server runs.
                              number specified for
                              the server

        Startup State         ENABLED               Not used. Do not
                                                    change this value.

        [1]The_default_value_for_the_DECnet_object_number_is_the_value___

        used for the server that is created when ALL-IN-1 is installed.

                                                 (continued on next page)




        9-8 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                     9.5 File Cabinet Server Configuration and Attributes


        Table 9-4 (Cont.) File Cabinet Server Configuration and
        __________________Attributes_____________________________________

        Setting_______________Default_Value_________Description__________

        __________________________Configuration__________________________

        Startup Queue         The queue specified   The name of the
                              in system policies    batch queue to
                              for account           which the server's
                              management jobs       startup procedure is
                              (see                  submitted. The queue
                              ALL-IN-1 Management   must be on the same
                              Guide)                node as the server,
                                                    and must not be a
                                                    generic queue.

        Configuration File    OA$DATA_SHARE:        The file containing
                              node$SERVERobj.DAT    details of the
                              node and obj are the  server's attributes.
                              node name and object
                              number specified for
                              the server

        _________________________________________________________________
        ___________________________Attributes____________________________

        Authorized Timeout    600                   The number of seconds
                                                    between updates to
                                                    the information about
                                                    authorized access to
                                                    an open drawer. See
                                                    Section 9.1.5.

        Distribution          OFF                   Not used. Do not
                                                    change this value.

        Drawer Cache          10                    The number of entries
                                                    in the drawer
                                                    cache table. See
                                                    Section 9.12.4.

                                                 (continued on next page)


                                        Managing File Cabinet Servers 9-9

 



        Managing File Cabinet Servers
        9.5 File Cabinet Server Configuration and Attributes


        Table 9-4 (Cont.) File Cabinet Server Configuration and
        __________________Attributes_____________________________________

        Setting_______________Default_Value_________Description__________

        ___________________________Attributes____________________________

        Drawer Timeout        600                   The number of seconds
                                                    between runs of the
                                                    maintenance routine
                                                    that closes the
                                                    least frequently-
                                                    used drawers. See
                                                    Section 9.1.4 and
                                                    Section 9.12.4.

        Max Client Connects   512                   The maximum number
                                                    of concurrent client
                                                    connections that the
                                                    server accepts. See
                                                    Section 9.1.2 and
                                                    Section 9.12.5.

        Max # of Drawers      50                    The maximum number
                                                    of drawers left open
                                                    when the maintenance
                                                    routine closes the
                                                    least frequently-
                                                    used drawers. See
                                                    Section 9.1.4 and
                                                    Section 9.12.4.

                                                 (continued on next page)












        9-10 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                     9.5 File Cabinet Server Configuration and Attributes


        Table 9-4 (Cont.) File Cabinet Server Configuration and
        __________________Attributes_____________________________________

        Setting_______________Default_Value_________Description__________

        ___________________________Attributes____________________________

        Port number           7373[2]               The TCP/IP port
                                                    number for the
                                                    server. If you
                                                    create any additional
                                                    server, the port
                                                    number must be:

                                                    o  In the range 1024
                                                       to 65535

                                                    o  Unique on the node
                                                       where the server
                                                       runs

                                                    If you do not want
                                                    to use the TCP/IP
                                                    network protocol, the
                                                    Server port number
                                                    must have a value of
                                                    zero (0).

        Session Timeout       1200                  The number of
                                                    seconds before
                                                    idle management
                                                    connections are
                                                    disconnected.
        [2]The_default_value_for_the_Server_port_number_is_the_default___

        value used if TCP/IP software was present on your system when the
        TLC Version 2.1 elements were installed.
        _________________________________________________________________

        9.6 Creating a Local File Cabinet Server

              Table 9-5 shows how to create a File Cabinet Server on a
              local node.


                                       Managing File Cabinet Servers 9-11

 



        Managing File Cabinet Servers
        9.6 Creating a Local File Cabinet Server


              Table_9-5_Creating_a_Local_File_Cabinet_Server_____________

              Step__Action_______________________________________________

              1     Use the Create (C) option on the Manage Servers menu.

              2     Use the Create local server (CL) option.

              3     Enter the details of the server in the Create a
                    Server form. See Table 9-4 for details of the
                    possible values you can enter. (Server port number
                    is described in the Attributes section of the table.)

              4     When you press RETURN to complete the Create a Server
                    form, the Manage Servers form is displayed. If you do
                    not want the server to use the default configuration
                    settings or attribute values, enter the values that
              ______you_want_it_to_use._See_Table_9-4.___________________

        9.6.1 Enabling Connections to a New File Cabinet Server

              When ALL-IN-1 VT clients choose options that involve the
              use of the File Cabinet Server, a connection is normally
              made to the default server that was created when ALL-IN-1
              was installed. The DECnet object number of the default
              server is 73, and, if set, the TCP/IP port number is 7373.

              If you create a new File Cabinet Server, and you want
              ALL-IN-1 VT clients to connect to this server rather than
              to the default server, you must define the logical name
              OAFC$SRV_OBJ. Define this logical name in the user process
              of each VT user who is to connect to the new server. Set
              the value of the logical name to be the DECnet object
              number of the new server. For example, if the DECnet object
              number of the new server is 210, define the logical name as
              follows:

              $ DEFINE/PROCESS OAFC$SRV_OBJ 210

              For TeamLinks clients to connect to a File Cabinet Server
              that you create, rather than to the default server,
              details of the new server must replace the details of the
              default server in the initialization file for the client
              application.

        9-12 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
            9.7 Changing File Cabinet Server Configuration and Attributes


        9.7 Changing File Cabinet Server Configuration and Attributes

              Use the Edit (E) option to make changes to the
              configuration or attributes of a File Cabinet Server. See
              Table 9-4 for details of the settings you can change.

              When you change a server's configuration values or
              attributes, the new values take effect the next time you
              start the server.

        9.8 Deleting a File Cabinet Server

              To delete a File Cabinet Server, stop the server, then
              use the Delete (D) option. This removes the server's entry
              in the master file, and, for a local server, deletes the
              configuration file.

                ________________________ Note ________________________

                Do not delete the default server, which has DECnet
                object number 73.

                ______________________________________________________

        9.9 Changing the Status of a File Cabinet Server

              The status of a File Cabinet Server determines its
              availability to client users. To see the status of a
              server, look at the current item block, or use the Show
              server status (SSS) option at an index of servers.

              Options that change the state of the File Cabinet Server
              are:

              o  Start server (STA)

              o  Stop server (STO)

              o  Enable server (ENA)

              o  Disable server (DIS)




                                       Managing File Cabinet Servers 9-13

 



        Managing File Cabinet Servers
        9.9 Changing the Status of a File Cabinet Server


        9.9.1 Starting a File Cabinet Server

              Use the Start server (STA) option on the Manage Servers
              menu to start a File Cabinet Server.

              This option submits a batch job to the startup
              queue specified in the server's configuration
              details. The batch job runs the startup procedure,
              SYS$STARTUP:OAFC$STARTUP.COM, using the process name and
              configuration file specified in the server's configuration
              details.

              Digital recommends that you start the server from the
              ALL-IN-1 manager's ALL-IN-1 account, to ensure that the
              server starts with the appropriate process values.

              You cannot start a server on a remote node.

              The ALL-IN-1 startup procedure starts all the File Cabinet
              servers on the node on which the startup procedure is
              running.

        9.9.2 Stopping a File Cabinet Server

              Use the Stop server (STO) option on the Manage Servers menu
              to stop the selected server.

              When a File Cabinet Server is stopped, it terminates
              existing client connections and accepts no new ones. If
              you stop a server while it is servicing a request for a
              client, the server attempts to complete the request before
              terminating the connection with the client.

              File Cabinet servers stop automatically when ALL-IN-1 is
              shut down.

        9.9.3 Enabling a File Cabinet Server

              Use the Enable server (ENA) option to enable the selected
              File Cabinet Server. When a server is enabled, it accepts
              client connections. The File Cabinet Server must be running
              before you can enable it.



        9-14 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                         9.9 Changing the Status of a File Cabinet Server


        9.9.4 Disabling a File Cabinet Server

              Use the Disable server (DIS) option to prevent clients
              connecting to the selected File Cabinet Server. When a
              server is disabled, it accepts only management connections.
              When you disable a server, it attempts to complete any
              client requests it is servicing, then terminates all client
              connections.

        9.10 Identifying Clients of the File Cabinet Server

              Use the Manage server clients (MSC) option to create an
              index of clients connected to the selected server. The
              server must be running for this option to work.

              When you use the MSC option, you can specify the criteria
              shown in Table 9-6 to select the clients to include in
              the index. Leave this form blank to display all connected
              clients.

              Table_9-6_Building_an_Index_of_Server_Clients______________

              Criterion________Description_______________________________

              Client           The OpenVMS user name of the client. If
                               the client is on a remote node, specify
                               the name of the proxy account that the
                               client uses to access the File Cabinet.

              Originating      The node from which the connection to the
              Node             File Cabinet Server is made. For example,
                               to display connections from a server on a
                               remote node, enter the node name in this
                               field.

              Originating      The OpenVMS user name of the client
              Client           on a remote node. Complete this field
                               to display all the connections for a
                               particular account on a remote system.

              System Mgmt      Specifies whether to include management
              Flag             connections.

                                                 (continued on next page)

                                       Managing File Cabinet Servers 9-15

 



        Managing File Cabinet Servers
        9.10 Identifying Clients of the File Cabinet Server


              Table_9-6_(Cont.)_Building_an_Index_of_Server_Clients______

              Criterion________Description_______________________________

              Local Flag       Specifies whether to include connections
                               from local clients (and remote clients who
                               are accessing the File Cabinet Server by
                               means of a proxy account).

              Remote Flag      Specifies whether to include connections
                               from remote clients.

              Tracing Flag     Specifies whether to include connections
              _________________that_have_tracing_enabled.________________

              Table 9-7 shows the options you can use from the index of
              server clients to monitor and control connections to the
              server.

              Table_9-7_Options_on_the_Manage_Server_Clients_Index_Menu__

              Option________Description__________________________________

              Disconnect a  Disconnects a session. Use this option to
              client        terminate a session that is causing problems.

              Set tracing   Turns on tracing for a selected client or
              on            clients. See Section 11.5.2.

              Set tracing   Turns off tracing for a selected client or
              off___________clients._See_Section_11.5.2._________________

        9.11 Resetting the Warning for Disk Quota Limit

              If disk quotas are enabled, the File Cabinet Server
              normally returns a warning status when opening a drawer
              whose owner is within 200 blocks of their disk quota limit.

              To change the point at which the warning is issued:

              1. On each node where the File Cabinet Server runs, define
                 OAFC$DISKQUOTALIMIT as an executive-mode system logical
                 name. As the value, specify the number of blocks of disk
                 space remaining within a drawer owner's quota when the
                 warning is to be issued.

        9-16 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                          9.11 Resetting the Warning for Disk Quota Limit


                 For example, to specify that a warning is to be returned
                 when a user accesses a drawer whose owner is within 500
                 blocks of their disk quota limit, define the logical
                 name as follows:

                 $ DEFINE/SYSTEM/EXECUTIVE_MODE OAFC$DISKQUOTALIMIT 500

              2. Stop then restart the File Cabinet Server.

              The limit specified as OAFC$DISKQUOTALIMIT applies to all
              users. You cannot specify different limits for different
              users.

        9.12 Tuning the File Cabinet Server

              Factors that affect the performance of the File Cabinet
              Server are:

              o  File Cabinet Server process quotas. See Section 9.12.2.

              o  The SYSGEN parameter CHANNELCNT. See Section 9.12.3.

              o  The size of the File Cabinet Server drawer cache. See
                 Section 9.12.4.

              o  The number of clients connected to a server. See
                 Section 9.12.5.

              When tuning the File Cabinet Server, consider the
              following:

              o  Distribute mail areas and File Cabinet drawers evenly
                 across a number of devices.

                 The File Cabinet Server process has a high I/O rate,
                 while its CPU usage tends to be low. The server process
                 overlaps CPU and I/O activities. If the drawers and
                 mail areas for a system are evenly distributed across
                 a number of devices, the server can take advantage of
                 this and change from being an I/O-intensive process to a
                 CPU-intensive process.

              o  Minimize the page fault rate.

                 Due to its potentially high I/O rate, the page fault
                 rate for the File Cabinet Server should be kept low.
                 Excessive paging results in additional CPU overhead
                 and a delayed client response time. On large systems,
                 depending on the demand for the server, it is possible
                 for the virtual page count of the server process to

                                       Managing File Cabinet Servers 9-17

 



        Managing File Cabinet Servers
        9.12 Tuning the File Cabinet Server


                 exceed 200 000 pages. To avoid File Cabinet Server
                 errors, where memory is available, set the server's
                 working set extent (WSEXTENT) high to keep page faulting
                 to a minimum.

                 The size of the drawer cache can also affect a server's
                 virtual page count. See Section 9.12.4.

        9.12.1 Monitoring the Performance of the File Cabinet Server

              Table 9-8 shows the tools that are available for monitoring
              the performance of a File Cabinet Server.

              Table 9-8 Monitoring the Performance of a File Cabinet
              __________Server___________________________________________

              Tool_____________Description_______________________________

              The Show         This displays details of the system
              resource         resources used by the selected server
              information      since it was started.
              (SRI) option

              The Show audit   This displays a summary of the server
              information      activity. For example, it tells you how
              (SAI) option     many connections have been accepted, and
                               how many have been rejected.

              The SHOW         To display continuously-updated
              PROCESS command  information about the process in which
                               the File Cabinet Server runs, use the
                               following DCL command:

                               SHOW PROCESS/CONTINUOUS/ID=process_id

                               Press E to terminate the display.

              The Monitor      Use the Monitor utility to measure the
              utility          resource usage of the File Cabinet Server
                               relative to other processes on the system.

              Tracing          You can trace the activity of a File
                               Cabinet Server, or of individual clients.
              _________________See_Section_11.5._________________________

        9-18 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                                      9.12 Tuning the File Cabinet Server


        9.12.2 Tuning File Cabinet Server Process Quotas

              The File Cabinet Server startup procedure uses logical
              names to set the quotas for the server process. If any
              of the logical names is not defined, the process uses
              a default value. The default values are set for a File
              Cabinet Server with 50 users connected to it at any one
              time.

              To change the process quotas for File Cabinet servers on
              your system, change the value of these logical names.
              Table 9-9 shows the logical names, default values, and
              recommended settings for each process quota.

        Table_9-9_Process_Quotas_for_File_Cabinet_Servers________________

        Process                          Default
        Quota______Logical_Name__________Value__Recommendation___________

        ASTLM      OAFC$SERVER_ASTLM     1024   Increase by 4 per active
                                                user

        BIOLM      OAFC$SERVER_BIOLM     256    Increase by 4 per active
                                                user

        BYTLM      OAFC$SERVER_BYTLM     512000 Increase by 2000 per
                                                active user

        DIOLM      OAFC$SERVER_DIOLM     256    Increase by 4 per active
                                                user

        ENQLM      OAFC$SERVER_ENQLM     4096   Increase by 4 per active
                                                user

        FILLM      OAFC$SERVER_FILLM     1024   Increase by 4 per active
                                                user

        PGFLQUOTA  OAFC$SERVER_          100000 Increase by 400 per
                   PGFLQUOTA                    active user

        WSEXTENT[1]OAFC$SERVER_WSEXTENT  8192   Increase by 100 [2] per
                                         [2]    active user

        [1]If_the_SYSGEN_parameter_PQL_MWSEXTENT_has_a_value_greater_than

        the WSEXTENT process quota for the File Cabinet Server, the value
        of PQL_MWSEXTENT is used for the File Cabinet Server process.
        [2]On Alpha systems, this value is set in Alpha pages and not
        pagelets. To convert the value to pages, divide it by 16.

                                                 (continued on next page)

                                       Managing File Cabinet Servers 9-19

 



        Managing File Cabinet Servers
        9.12 Tuning the File Cabinet Server


        Table_9-9_(Cont.)_Process_Quotas_for_File_Cabinet_Servers________

        Process                          Default
        Quota______Logical_Name__________Value__Recommendation___________

        WSQUOTA[3] OAFC$SERVER_WSQUOTA   2048
        [2]On_Alpha_systems,_this_value_is2set_in_Alpha_pages_and_not____

        pagelets. To convert the value to pages, divide it by 16.
        [3]If the SYSGEN parameter PQL_MWSQUOTA has a value greater than
        the WSQUOTA process quota for the File Cabinet Server, the value
        of PQL_MWSQUOTA is used for the File Cabinet Server process.
        _________________________________________________________________

        9.12.3 Setting the Value of CHANNELCNT

              The maximum number of I/O channels that can be assigned to
              a process is controlled by the SYSGEN parameter CHANNELCNT.
              Make sure that the value of this parameter is high enough
              for the servers on your system. When setting CHANNELCNT,
              consider the following:

              o  The maximum number of client connections to a File
                 Cabinet Server. Each client uses a minimum of two I/O
                 channels:

                 -  One for the connection to the server

                 -  One for I/O to FILECAB.DAT

              o  The maximum number of drawers that the File Cabinet
                 Server can access simultaneously. Each open drawer uses
                 a minimum of three I/O channels:

                 -  One for DOCDB.DAT

                 -  One for DAF.DAT

                 -  One for RESERVATIONS.DAT

                 The channels used when a drawer is opened continue to
                 be used as long as details of the drawer remain in the
                 drawer cache, even if the requesting client has stopped
                 accessing the drawer.

              If the expected values of these factors lead to a
              requirement for more I/O channels than is permitted by the
              maximum value of CHANNELCNT, create another File Cabinet
              Server.

        9-20 Managing File Cabinet Servers

 



                                            Managing File Cabinet Servers
                                      9.12 Tuning the File Cabinet Server


        9.12.4 Tuning the File Cabinet Server Drawer Cache

              The size of the drawer cache increases with the number
              of open drawers. This increases the server's virtual page
              count.

              You can control the size of the drawer cache by changing
              the value of the server attributes shown in Table 9-10.
              Use the Edit (E) option to change server attributes. See
              Section 9.7.

              Table_9-10_Drawer_Cache_Attributes_________________________

              Server
              Attribute_____DefaultDescription___________________________

              Drawer Cache  10     The number of entries in the drawer
                                   cache table. Add 10 for every 100
                                   active users.

              Max. # of     50     The maximum number of drawers left
              Drawers              open when the maintenance routine
                                   closes the least frequently-used
                                   drawers.

                                   Because clients spend long idle
                                   periods between functions, this value
                                   can be significantly lower than the
                                   total number of connected clients. For
                                   up to 100 users, set to 50. For each
                                   additional 100 users, add 30.

                                                 (continued on next page)












                                       Managing File Cabinet Servers 9-21

 



        Managing File Cabinet Servers
        9.12 Tuning the File Cabinet Server


              Table_9-10_(Cont.)_Drawer_Cache_Attributes_________________

              Server
              Attribute_____DefaultDescription___________________________

              Drawer        600    The interval (in seconds) between each
              Timeout              run of the maintenance routine. If
                                   you decrease this value, the routine
                                   runs more frequently, so the number of
                                   open drawers stays closer to the value
                                   of Max # of drawers. This results in
                                   a lower virtual page count for the
                                   system.

                                   If memory is restricted on your
                                   system, you may need to set this
                                   attribute as low as 180. However,
                                   lowering the value increases I/O and
              _____________________CPU_usage.____________________________

        9.12.5 Controlling the Number of Clients

              Restricting the number of simultaneous client connections
              to a server allows you to control the demand for system
              resources. To do this, edit the server (see Section 9.7)
              and change the value of the Max Client Connects attribute.

        9.12.6 Setting the Process Priority of the File Cabinet Server

              The process priority of the File Cabinet Server is set when
              the server is started. The default priority is 5. To set a
              different process priority:

              1. Define the logical name, OAFC$SERVER_PRIORITY, to
                 specify the priority that you require

              2. Make sure that the ALLIN1 OpenVMS account has the ALTPRI
                 privilege granted as both an authorized and a default
                 privilege






        9-22 Managing File Cabinet Servers

 










                                                                       10
        _________________________________________________________________

                                              Enabling Broadcast Messages


              This chapter describes how your ALL-IN-1 system must be
              set up to allow client users to receive ALL-IN-1 broadcast
              messages (those that warn of ALL-IN-1 shutdown and startup)
              and notification of the receipt of new mail.

              When a client user enables notification from the client
              application, the ALL-IN-1 system is automatically set
              up to enable the user to receive these messages. Under
              normal conditions, there are no management tasks involved
              in enabling broadcast messages. The information in this
              chapter is provided to help you deal with any problems that
              occur.

        10.1 The PC Broadcast Server

              The PC Broadcast Server is a detached process that manages
              broadcast messages and new mail notification for PC users.

              When the TLC is installed, and subsequently, whenever the
              ALL-IN-1 startup procedure runs, the PC Broadcast Server
              is started on each node of the cluster on which ALL-IN-1
              IOS is running. When the PC Broadcast Server starts, a
              detached process, OA$PCBDCST_SRV, is created. In addition,
              a mailbox, OA$PCBDCST_MBX, is created if it does not
              already exist.

        10.2 ALL-IN-1 Conditions for Enabling Broadcast Messages

              For client users to receive notification of new mail and
              broadcast messages, your ALL-IN-1 system must be set up as
              shown in Table 10-1.





                                         Enabling Broadcast Messages 10-1

 



        Enabling Broadcast Messages
        10.2 ALL-IN-1 Conditions for Enabling Broadcast Messages


        Table_10-1_ALL-IN-1_Conditions_for_Enabling_Broadcast_Messages___

        Condition__________________How_to_Set_Up_________________________

        The RSVD_FOR_TCS flag      ALL-IN-1 automatically sets this when
        in the client user's       the user enables notification from the
        ALL-IN-1 profile entry is  client application.
        set to 1.                  See Section 12.3.1 for details about

                                   how to set this flag manually.

        The client user must       ALL-IN-1 automatically creates
        have an entry in the PC    an entry when the user enables
        notification data set,     notification from the client
        OA$PC_NOTIFY.              application. See Section 10.3 for
                                   information about the OA$PC_NOTIFY
                                   data set.

        The PC Broadcast Server    The PC Broadcast Server is started
        must be running.           when you install TLC Version 2.5,
                                   and subsequently, whenever the
                                   ALL-IN-1 startup procedure runs. See
                                   Section 10.1 for information about the
                                   PC Broadcast Server.

        If the client application  See Section 7.3.2.
        uses AppleTalk transport
        to communicate with the
        TLC, the logical name,
        OA$PC_ATK$GATEWAY, must
        be defined.

        Appropriate software       See Table 7-4 for details of the
        must be installed on the   software required to support network
        system.                    transport.

                                   If you wish to support users of
                                   TeamLinks for Windows Version
                                   2.0, and use DECnet transport for
                                   communications between the client
                                   application and the TLC, install
                                   PATHWORKS for OpenVMS Version 4.0
        ___________________________(minimum)_on_the_same_node_as_the_TLC.


        10-2 Enabling Broadcast Messages

 



                                              Enabling Broadcast Messages
                                        10.3 The PC Notification Data Set


        10.3 The PC Notification Data Set

              The PC notification data set, OA$PC_NOTIFY, contains
              information about users who access ALL-IN-1 data from a
              client application. When a user enables notification from a
              client application, a record for that user is automatically
              added to the OA$PC_NOTIFY data set.

                ________________________ Note ________________________

                Users of TeamLinks for Windows must reenable
                notification after upgrading their client software.
                This is to update the OA$PC_NOTIFY data set with the
                correct TRANSPORT value (see Table 10-2).

                ______________________________________________________

              There are no routine management tasks involved in managing
              the OA$PC_NOTIFY data set; it is described here to help
              you solve any problems that client users experience in
              receiving broadcast messages or notification of new mail.

              Table 10-2 shows the information contained in each record
              of the OA$PC_NOTIFY data set.

              Table_10-2_OA$PC_NOTIFY_Data_Set___________________________

              Field_______Description____________________________________

              A1USER      The ALL-IN-1 user name of the client user. This
                          is the key field.

                                                 (continued on next page)












                                         Enabling Broadcast Messages 10-3

 



        Enabling Broadcast Messages
        10.3 The PC Notification Data Set


              Table_10-2_(Cont.)_OA$PC_NOTIFY_Data_Set___________________

              Field_______Description____________________________________

              NODE        The node name of the PC from which the client
                          user connects to ALL-IN-1 IOS. The value
                          of this field depends on the value of the
                          TRANSPORT field, as follows:

                          N or   The DECnet node address of the PC.
                          D

                          U or   The node name of the PC, if defined.
                          T

                          A      The DECnet nodename of the AppleTalk
                                 gateway used to connect to the PC.
                                 If this field has no value, the
                                 notification mechanism uses the value
                                 of the logical name, OA$PC_ATK$GATEWAY.

              PATH        The path used to reach the PC. The value
                          of this field depends on the value of the
                          TRANSPORT field, as follows:

                          N or   Not used.
                          D

                          U      The TCP/IP address of the PC.

                          T      The TCP/IP address of the PC. For
                                 example, node, or node.reo.dec.com,
                                 or 128.4.3.127.

                          A      The AppleTalk NBP name of the Macintosh
                                 machine. Each of the three components of
                                 the name is separated by an equals (=)
                                 sign. For example:

                                 COLE=ALL-IN-
                                 1 Notification=REO_Backbone Reading

                                                 (continued on next page)


        10-4 Enabling Broadcast Messages

 



                                              Enabling Broadcast Messages
                                        10.3 The PC Notification Data Set


              Table_10-2_(Cont.)_OA$PC_NOTIFY_Data_Set___________________

              Field_______Description____________________________________

              TRANSPORT   The transport mechanism that the PC uses to
                          connect to ALL-IN-1 IOS. Permitted values are:

                          N    DECnet NETBIOS datagram transport (used by
                               TeamLinks for Windows Version 2.0)

                          D    DECnet stream transport (used by TeamLinks
                               for Windows Version 2.1 and TeamLinks for
                               Macintosh Version 2.0)

                          U    TCP/IP UDP datagram transport (used by
                               TeamLinks for Windows Version 2.0)

                          T    TCP/IP stream transport (used by TeamLinks
                               for Windows Version 2.1 and TeamLinks for
                               Macintosh Version 2.0)

                          A    AppleTalk transport (used by TeamLinks for
                               Macintosh Version 2.0)

              SUBJECT     A flag that indicates whether the subject
                          of a new mail message is included in the
                          notification message. A value of 1 indicates
                          that the subject is included; a value of 0
              ____________indicates_that_the_subject_is_not_included.____
















                                         Enabling Broadcast Messages 10-5

 










                                                                       11
        _________________________________________________________________

                                                Tools for Troubleshooting


              This chapter describes the tools that are available to
              help you investigate problems with the TLC. These tools are
              shown in Table 11-1.

              Table_11-1_Troubleshooting_Tools___________________________

                                              Where to Find More
              Tool____________________________Information________________

              The installation verification   Section 11.1
              procedure (IVP)

              AIDA Server log files           Section 11.2

              AIDA Server tracing             Section 11.3

              File Cabinet Server log files   Section 11.4

              File Cabinet Server tracing     Section 11.5

              PC Broadcast Server log files   Section 11.6

              PC broadcast test program       Section 11.7

              PC Broadcast Server test        Section 11.8
              program

              Logical name OA$PC_BROADCAST_   Section 11.9
              TRANSPORTS

              Client application log files    See the documentation for
              ________________________________the_client_application.____

        11.1 Running the IVP

              The IVP verifies that the TLC is correctly installed.
              When you install the TLC, you can choose to run the IVP
              immediately after the installation. To run the IVP at any
              time after this, do the following:

              1. Log in to the ALL-IN-1 manager's OpenVMS account.

                                           Tools for Troubleshooting 11-1

 



        Tools for Troubleshooting
        11.1 Running the IVP


              2. Enter the following command:

                 $ @OA$IVP:TLC$IVP

              When you run the IVP after installing the TLC, no log file
              is produced. If the IVP identifies any errors, it displays
              a message.

        11.2 AIDA Server Log Files

              Each AIDA Server process has an associated log file that
              you can use to help you diagnose any problems that occur
              with the server. Table 11-2 shows information about AIDA
              Server log files.

        Table_11-2_Questions_and_Answers_about_AIDA_Server_Log_Files_____

        Question______________Answer_____________________________________

        How can I access      At the Manage AIDA Servers menu or the
        the log files for an  Index of Servers menu, select the server,
        AIDA Server?          then use the Manage error logs (MEL)
                              option. Options on the Manage Error Logs
                              menu enable you to examine the logs, send
                              them as mail messages, or delete them.

        When is a log file    When a server is started.
        created?

        When is a new         A new generation of the log file is
        generation started?   created:

                              o  During server startup, when the process
                                 in which the server runs is created

                              o  The first time an error occurs while the
                                 server is running

                              o  When 1000 lines have been written to the
                                 file

                              o  When the file is locked

                                                 (continued on next page)

        11-2 Tools for Troubleshooting

 



                                                Tools for Troubleshooting
                                               11.2 AIDA Server Log Files


        Table 11-2 (Cont.) Questions and Answers about AIDA Server Log
        ___________________Files_________________________________________

        Question______________Answer_____________________________________

        What do log files     All output messages from the server
        record?               process, including:

                              o  All stages in the startup process

                              o  Any failures in the startup process,
                                 and subsequent retries of the startup
                                 process

                              o  Major errors and events that occur while
                                 the server is active

                              o  Shutdown

        When are log files    A server's log files are deleted:
        deleted?              o  If the Delete log files during

                                 server startup field in the server's
                                 configuration record contains a value of
                                 Y, when the server next starts

                              o  When the server is deleted

                              o  When you use the Delete (D) option or
                                 the Delete all selected (XD) option on
                                 the Manage Error Logs index menu

        _________________________________________________________________

                ________________________ Note ________________________

                If a shortage of disk space prevents an AIDA Server
                log file from being written, the server process
                continues, without logging messages.

                ______________________________________________________

        11.3 AIDA Server Tracing

              A tracing facility allows you to keep a record of AIDA
              Server activities, and gives more information than that
              recorded in the standard log file.

                                           Tools for Troubleshooting 11-3

 



        Tools for Troubleshooting
        11.3 AIDA Server Tracing


        11.3.1 What You Can Trace

              Table 11-3 shows the types of activity you can trace for
              an AIDA Server, together with the labels used in the trace
              output to identify each activity.

              Table_11-3_Activities_That_You_Can_Trace___________________

              Activity______Label__Description___________________________

              File access   IO     Opening and closing files.

              Calls to the  API    Each call to the AIDA application
              server               programming interface, together with
                                   the parameters passed.

              Connections   CON    Each connection to, and disconnection
              to the               from, the server.
              server_____________________________________________________

              For each server, you can trace any or all of the types of
              activity shown in Table 11-3.

              When you switch tracing on for a server, you can trace
              activity in individual sessions, or in all sessions with
              the server. If you trace activity in more than one session,
              the same types of activity are traced in each session. You
              cannot trace different activities in different sessions
              with the same server.

        11.3.2 AIDA Server Trace Files

              Trace output is written to a file that you can read, print,
              delete, or send by mail. Table 11-4 shows information about
              AIDA Server trace files.










        11-4 Tools for Troubleshooting

 



                                                Tools for Troubleshooting
                                                 11.3 AIDA Server Tracing


        Table_11-4_Questions_and_Answers_about_AIDA_Server_Trace_Files___

        Question______________Answer_____________________________________

        How can I access the  At the Manage AIDA Servers menu or the
        trace files for an    Index of Servers menu, select the server,
        AIDA Server?          then use the Manage trace logs (MTL)
                              option. Options on the Manage Trace Logs
                              menu enable you to examine the logs, send
                              them as mail messages, or delete them.

        When is a trace file  When you switch tracing on for a server.
        created?

        When is a new         A new generation of the trace file is
        generation started?   created:

                              o  When 5000 lines have been written to the
                                 file

                              o  When the file is locked

        When are trace files  A server's trace files are deleted:
        deleted?              o  If the Delete trace files during

                                 server startup field in the server's
                                 configuration record contains a value of
                                 Y, when the server next starts

                              o  When the server is deleted

                              o  When you use the Delete (D) option or
                                 the Delete all selected (XD) option on
                                 the Manage Trace Logs index menu

        _________________________________________________________________

        11.3.3 Enabling AIDA Server Tracing

              Table 11-5 shows how to enable tracing for an AIDA Server.

        Table_11-5_How_to_Enable_Tracing_for_an_AIDA_Server______________

        Step_Action______________________________________________________

        1    Make sure that the server is Running or Disabled.

                                                 (continued on next page)

                                           Tools for Troubleshooting 11-5

 



        Tools for Troubleshooting
        11.3 AIDA Server Tracing


        Table_11-5_(Cont.)_How_to_Enable_Tracing_for_an_AIDA_Server______

        Step_Action______________________________________________________

        2    Use the Manage server tracing (MST) option on the Manage
             AIDA Servers menu or on the Index of Servers menu.

             This displays the Manage Server Tracing form.

        3    In the Trace all server connections field, indicate whether
             you want to trace activity in all sessions with the server,
             or in a particular session or sessions only.
             ____________________________________________________________
             To_do_this:___________Enter_this_value______________________

             Trace all sessions    Y
             on the server

             Trace selected        N
             sessions_only_______________________________________________

        4    Set the trace options that you require. Enter a value of Y
             to turn an option on, or a value of N to turn it off. You
             must set at least one of the trace options to Y for tracing
             to work.

        5    Set the Tracing on/off field to ON.

        6    Press RETURN to leave the form.
             ____________________________________________________________
             If:________________________Then:____________________________

             You set tracing for all    Tracing starts when you leave
             server connections         the form. You do not have to do
                                        anything else.

             You set tracing to trace   Go to step 7.
             selected_sessions_only______________________________________

        7    Use the ISC option to display an index of current client
             sessions.

        8    Use the Set tracing on (TON) option to switch tracing on for
             a single client session, or, to trace more than one client
             session, select the sessions you want to trace, then use the
        _____Tracing_on_for_all_selected_(XTON)_option.__________________

        11-6 Tools for Troubleshooting

 



                                                Tools for Troubleshooting
                                                 11.3 AIDA Server Tracing


        11.3.4 Switching AIDA Server Tracing Off

              To switch tracing off for an individual session or for
              selected sessions, use the Set tracing off (TOF) option or
              the Tracing off for all selected (XTOF) option on the Index
              of Server Connections menu.

              If you switch tracing off for all individual sessions that
              are being traced, the server details continue to indicate
              that tracing is on until you switch tracing off for the
              server.

              To switch tracing off for a server, use the Manage server
              tracing (MST) option on the Manage AIDA Servers menu or
              on the Index of Servers menu, then set the Tracing on/off
              field to OFF. If you do this when you have set tracing on
              for individual client sessions, tracing is stopped for all
              these sessions.

              When a server stops while tracing is enabled, tracing
              is automatically switched off. To resume tracing, after
              you restart the server, enable tracing as described in
              Section 11.3.3.

        11.4 File Cabinet Server Log Files

              You can use the following log files to help you diagnose
              problems with the File Cabinet Server:

              o  OA$LOG:OAFC$SERVER.LOG

                 This is the main server log, and is used by all File
                 Cabinet servers running on your system. It contains all
                 server information messages, and messages resulting from
                 error conditions handled by the server. All logs within
                 this file are timestamped and identified with the DECnet
                 object number of the server.

              o  OA$LOG:OAFC$SERVER_ERROR.LOG

                 This contains all messages resulting from fatal errors
                 and error conditions that are not handled by the File
                 Cabinet Server.

              o  OA$LOG:OAFC$SERVER_STARTUP.LOG

                 This is the server startup log.

                                           Tools for Troubleshooting 11-7

 



        Tools for Troubleshooting
        11.4 File Cabinet Server Log Files


              On ALL-IN-1 Version 3.1 systems, access File Cabinet Server
              log files as follows:

              1. At the ALL-IN-1 Management menu, use the Manage ALL-IN-1
                 system (MSY) option

              2. At the Manage ALL-IN-1 System menu, use the Manage
                 system log files (MSL) option

              3. Use the Index (I) option to build an index using the
                 following file specification:

                 OA$LOG:OAFC*.LOG;*

              The File Cabinet Server log and error log can become very
              large, and consequently difficult to search for particular
              problems. To prevent the log files from becoming too
              large, create new log files from time to time. Do this by
              renaming the existing log files when all the File Cabinet
              Servers on the system are stopped. The File Cabinet Server
              automatically creates new log files when necessary.

        11.5 File Cabinet Server Tracing

              The File Cabinet Server tracing facility allows you to
              keep records of server activity and of connections to
              the server. This helps you to diagnose problems with the
              server.

              To display information about client and server tracing and
              about the trace files, use the Show tracing information
              (STI) option on the Manage Servers menu.

        11.5.1 Tracing File Cabinet Server Activity

              Use the Enable server tracing (EST) option on the Manage
              Servers menu to turn tracing on for the selected server.

              When you enable tracing for a File Cabinet Server, all
              actions of the server are recorded, for all connections.
              The creation of new connections is also recorded.

              To turn tracing off, use the Disable server tracing (DST)
              option.

        11-8 Tools for Troubleshooting

 



                                                Tools for Troubleshooting
                                         11.5 File Cabinet Server Tracing


        11.5.2 Tracing Client Connections

              To trace File Cabinet Server activity for a particular
              client or clients:

              1. Use the Manage server clients (MSC) option on the Manage
                 Servers menu to display an index of clients connected to
                 the server (see Section 9.10).

              2. Enter TON or XTON to turn tracing on for the selected
                 client or clients.

              To turn tracing off for clients, do one of the following:

              o  Use the Set tracing off (TOF) option (or the the
                 equivalent XTOF option for more than one client) at
                 the index of clients.

              o  Use the Disable server tracing (DST) option on the
                 Manage Servers menu. This stops tracing for all clients.

        11.6 PC Broadcast Server Log Files

              Table 11-6 shows information about PC Broadcast Server log
              files.

        Table 11-6 Questions and Answers about PC Broadcast Server Log
        ___________Files_________________________________________________

        Question______________Answer_____________________________________

        Where can I find the  The files are in OA$LOG, and are named
        log files for the PC  OA$PCBDCST_SRV_node.LOG.
        Broadcast Server?

        When is a log file    When the PC Broadcast Server starts.
        created?

                                                 (continued on next page)






                                           Tools for Troubleshooting 11-9

 



        Tools for Troubleshooting
        11.6 PC Broadcast Server Log Files


        Table 11-6 (Cont.) Questions and Answers about PC Broadcast
        ___________________Server_Log_Files______________________________

        Question______________Answer_____________________________________

        When is a new         A new generation of the log file is
        generation started?   created:

                              o  The first time an error occurs while the
                                 server is running

                              o  When 1000 lines have been written to the
                                 file

                              o  When the file is locked

        What do log files     The first generation records:
        record?               o  All stages in the startup process

                              o  Any failures in the startup process,
                                 and subsequent retries of the startup
                                 process

                              o  Occasions when the server's internal
                                 queue is full

                              Subsequent generations record all errors
                              and events that occur while the server
                              is active, and notification of broadcast
        ______________________failures.__________________________________

              The PC Broadcast Server keeps six versions of its log file.
              These files require no maintenance.

        11.7 The PC Broadcast Test Program

              The PC broadcast test program, OA$LIB:OA$PC_BROADCAST_
              TEST.EXE, bypasses the PC Broadcast Server and tests
              whether broadcast messages can reach a specified PC.

              To run the PC broadcast test program:

              1. Enter:

                 $ RUN OA$LIB:OA$PC_BROADCAST_TEST

              2. Answer the prompts to specify:

                 o  The PC on which you want to test broadcast messaging

        11-10 Tools for Troubleshooting

 



                                                Tools for Troubleshooting
                                       11.7 The PC Broadcast Test Program


                 o  The text of a test message

                 o  The number of times to display the test message

        11.8 The PC Broadcast Server Test Program

              The PC Broadcast Server test program, OA$LIB:OA$PCBDCST_
              SRV_TEST.EXE, tests whether the PC Broadcast Server is
              working correctly.

              To run the PC Broadcast Server test program:

              1. Enter:

                 $ RUN OA$LIB:OA$PCBDCST_SRV_TEST

              2. Answer the prompts as with the PC broadcast test program

        11.9 Testing Transport Mechanisms for Broadcast Messages

              The logical name OA$PC_BROADCAST_TRANSPORTS enables you to
              disallow the use of any particular transport mechanism for
              broadcast messages and so investigate whether a problem is
              related to the use of a particular transport mechanism.

              When you install the TLC, provided the appropriate software
              is installed (see Table 7-4), each of the supported
              transport mechanisms is enabled for broadcast messages.
              To disable a transport mechanism, define the logical name
              OA$PC_BROADCAST_TRANSPORTS. The value of this logical name
              contains values from the TRANSPORT field of the OA$PC_
              NOTIFY data set (see Table 10-2). If this logical name
              is defined, only those transport mechanisms whose value
              is included in the logical name definition are enabled.
              Thus, to disable a particular transport mechanism, define
              OA$PC_BROADCAST_TRANSPORTS and omit the TRANSPORT value
              that corresponds to the transport mechanism to be disabled.
              Include, in any order, the TRANSPORT values of all the
              transport mechanisms you want enabled.

              For example, use the following command to disable AppleTalk
              transport:

              $ DEFINE OA$PC_BROADCAST_TRANSPORTS NUDT

              If the logical name OA$PC_BROADCAST_TRANSPORTS is not
              defined, all types of transport mechanism are enabled for
              broadcast messages.

                                          Tools for Troubleshooting 11-11

 










                                                                       12
        _________________________________________________________________

                                                         Solving Problems


              This chapter gives information to help you investigate the
              following types of problem:

              o  Failure to address mail messages (see Section 12.1)

              o  Problems with the File Cabinet Server (see Section 12.2)

              o  Failure of broadcast messages and notification of new
                 mail (see Section 12.3)

              o  DSL errors (see Section 12.4)

        12.1 Problems with Addressing Mail

              If client users cannot address mail messages, make sure
              that the maximum number of concurrent users of the AIDA
              Server, as set in the server's configuration details, has
              not been reached. Use the ISC option on the Manage AIDA
              Servers menu to see how many users are connected to the
              server.

        12.2 Problems with the File Cabinet Server

              The following sections describe how to investigate and
              solve problems with the File Cabinet Server.

        12.2.1 Failure to Connect to the File Cabinet Server

              If a client user is unable to connect to the File Cabinet
              Server, check the following:

              o  That the ALL-IN-1 system is running and the File Cabinet
                 Server is running.

                 To check that the File Cabinet Server is running, at
                 the Manage Servers menu, select the server and check
                 that the status shown in the context block is Running
                 /Enabled.

                                                    Solving Problems 12-1

 



        Solving Problems
        12.2 Problems with the File Cabinet Server


              o  That the number of connections to the File Cabinet
                 Server is less than the maximum number of client
                 connections, as set in the server's attributes.

              In addition, for TeamLinks clients:

              o  Check that the node name of the server system is
                 correctly specified in the client's NCP database.

              o  If your ALL-IN-1 license permits, check that the client
                 user is able to log in to his or her OpenVMS account
                 from a VT terminal or from a terminal emulation session.
                 In the case of a login failure, solve the problem
                 reported in the error message.

              o  Check whether the OpenVMS intrusion database contains
                 any record for the client user. Use the following
                 command:

                 $ SHOW INTRUSION

              o  If the client user is trying to connect to a server
                 other than the default server, check that details of
                 the server are specified correctly in the initialization
                 procedure of the client application. See Section 9.6.

              o  Check whether the client user specifies a cluster alias
                 when trying to connect to the ALL-IN-1 File Cabinet.

                 If a user specifies a cluster alias when attempting
                 to connect to the ALL-IN-1 File Cabinet, the node to
                 connect to is selected at random. If ALL-IN-1 is not
                 running on the selected node, the connection fails.

              For VT clients:

              o  If the user is trying to connect to a server other
                 than the default server, check that the logical name,
                 OAFC$SRV_OBJ, is defined in the user's process, and that
                 its value is the DECnet object number of the server to
                 which the user is trying to connect. See Section 9.6.




        12-2 Solving Problems

 



                                                         Solving Problems
                               12.2 Problems with the File Cabinet Server


        12.2.2 File Cabinet Server Fails to Start

              If the File Cabinet Server fails to start:

              1. Check the
                 server startup log, OA$LOG:OAFC$SERVER_STARTUP.LOG,
                 for errors.

              2. If the log does not show the startup failure, start the
                 server as a foreground job so you can check for errors
                 as the job processes. Do this as follows:

                 a. Define a command to run the startup procedure. For
                    example:

                    $ start_server :=="$SYS$SYSTEM:OAFC$SERVER.EXE"

                 b. Run the startup procedure, giving the configuration
                    file name as a parameter. For example, for a server
                    on node BLUE using the DECnet object number 73, you
                    would enter:

                    $ start_server OA$DATA_SHARE:BLUE$SERVER73.DAT

              3. Check that the SYSGEN parameters, SCSSYSTEMID and
                 SCSNODE, are set, as described in Section 7.2.

              4. If the File Cabinet Server uses TCP/IP transport, make
                 sure that, on the system on which the server runs, the
                 DECnet node name is the same as the TCP/IP host name.

              5. Check the server log file for DASL errors (see
                 Section 12.4). If the server is attempting to start over
                 TCP/IP, make sure that TCP/IP software is installed.
                 Alternatively, if you do not want the server to use TCP
                 /IP, set the server's TCP/IP port number to zero (0).

        12.2.3 Invalid Authentication Information

              Access to a remote drawer or document may be denied, with
              the following error:

              Invalid authentication information received by the
              File Cabinet Server

              This happens when:

              o  A client is trying to access a drawer or document on
                 a remote system, but does not have a proxy account
                 correctly set up on the remote system.

                                                    Solving Problems 12-3

 



        Solving Problems
        12.2 Problems with the File Cabinet Server


                 Make sure that the client has a default proxy account on
                 the remote system, and that the account:

                 -  Has suitable access to the drawer or document

                 -  Has the DEFAULT qualifier associated with it

                 See  ALL-IN-1 Management Guide for details of how to set
                 up distributed sharing.

              o  You try to manage a server, using an account that does
                 not have the rights identifier OAFC$SYSMAN.

        12.2.4 Thread Access Violation or Internal Error

              If the File Cabinet Server log, OA$LOG:OAFC$SERVER.LOG,
              records a thread access violation or an internal error,
              troubleshooting information is recorded in the server
              error log, OA$LOG:OAFC$SERVER_ERROR.LOG. This information
              helps Digital engineers to investigate the problem. If you
              experience these problems with the File Cabinet Server,
              submit an SPR and attach a copy of the server error log.

              If there are any File Cabinet servers running on the
              system, the error log is locked. To create a copy of
              the error log, use the DCL TYPE command with the /OUTPUT
              qualifier to write the contents of the log to a new file.
              If this new file is large, edit it to remove information
              that is not related to the problem. Find the relevant
              information by searching the file for information that
              matches the information about the error that is shown in
              the server log, OA$LOG:OAFC$SERVER.LOG. For example, use
              the date stamp (omitting the seconds) associated with the
              error.

        12.3 Problems with Broadcast Messages

              Table 12-1 shows what to do if, after enabling notification
              from the client application, a client user does not receive
              broadcast messages or notification of the receipt of new
              mail.




        12-4 Solving Problems

 



                                                         Solving Problems
                                    12.3 Problems with Broadcast Messages


        Table_12-1_How_to_Solve_Problems_with_Broadcast_Messages_________

        Step_Action______________________________________________________

        1    Check that the conditions shown in Table 10-1 are met.
             For details of how to check and set the RSVD_FOR_TCS flag
             in the user's ALL-IN-1 profile entry, see Section 12.3.1.
             For details of how to check the OA$PC_NOTIFY data set, see
             Section 12.3.2.

        2    Run the PC broadcast test program (see Section 11.7).

             If the test fails, fix the problem reported in the error
             message, then rerun the test program.

        3    If the PC broadcast test succeeds, and the problem still
             exists, run the PC Broadcast Server test program (see
             Section 11.8).

             If the test message does not reach the PC, the PC Broadcast
             Server is not working correctly. Examine the PC Broadcast
             Server log file (see Section 11.6), and if necessary,
             restart the PC Broadcast Server (see Table 12-2). Always
             restart the PC Broadcast Server if the log file shows
             NETBIOS errors or that the mailbox is full.

             The log file may show that the server's internal queue is
             full. This happens when the OA$PC_NOTIFY data set contains
             records for a large number of PCs which are either not
             connected or not running the broadcast receiver. Ask
             TeamLinks users to set up their new mail notification so
             that notification is disabled when they disconnect from the
             mail service.

        4    If the PC broadcast test and the PC Broadcast Server test
             are both successful, the problem is in ALL-IN-1 IOS. Turn on
             mail tracing and send local mail to the user, then examine
             the trace for errors. For information about mail tracing,
             see the  ALL-IN-1 Mail Management Guide.

        5    Make sure that the appropriate networking software is
             running on the PC, as described in the documentation for
             the client application. Also make sure that the appropriate
             networking software is running on every node on which the
        _____ALL-IN-1_Sender_and_Fetcher_run.____________________________

                                                    Solving Problems 12-5

 



        Solving Problems
        12.3 Problems with Broadcast Messages


        12.3.1 Checking the RSVD_FOR_TCS Flag

              For a client user to receive broadcast messages and
              notification of new mail, the RSVD_FOR_TCS flag in user's
              ALL-IN-1 profile entry must have a value of 1. To check the
              value of this flag, at any ALL-IN-1 menu, enter:

              <GET PROFIL.RSVD_FOR_TCS["user"]

              user is the client user's ALL-IN-1 user name.

              If the RSVD_FOR_TCS flag does not have a value of 1, enter
              the following to set the flag:

              <WRITE CHANGE PROFIL USER="user", RSVD_FOR_TCS="1"

              user is the client user's ALL-IN-1 user name, entered in
              uppercase letters.

        12.3.2 Checking an Entry in the OA$PC_NOTIFY Data Set

              To see a user's entry in the OA$PC_NOTIFY data set, do the
              following:

              1. At any ALL-IN-1 menu, enter the following:

                 <FORM OA$PC_NOTIFY

              2. Enter the user's ALL-IN-1 user name in the ALL-IN-1 user
                 field.

              To modify the value of any fields in the data set, use the
              /MODE=CHANGE qualifier with the FORM function, as follows:

              <FORM OA$PC_NOTIFY/MODE=CHANGE

        12.3.3 Starting and Stopping the PC Broadcast Server

              To start or stop the PC Broadcast Server manually, use the
              commands shown in Table 12-2 from a privileged account.

              Table_12-2_Starting_and_Stopping_the_PC_Broadcast_Server___

              To_do_this:_______Use_this_command:________________________

              Start the server  $ @OA$LIB:OA$PCBDCST_SRV_START

                                                 (continued on next page)

        12-6 Solving Problems

 



                                                         Solving Problems
                                    12.3 Problems with Broadcast Messages


              Table 12-2 (Cont.) Starting and Stopping the PC Broadcast
              ___________________Server__________________________________

              To_do_this:_______Use_this_command:________________________

              Stop the server   $ STOP /ID=id_number

                                id_number is the identification number of
              __________________the_process._____________________________

        12.4 DASL Errors

              The Distributed Access Service Layer (DASL) is a component
              of the TLC that provides networking facilities for the
              servers. Errors in the DASL process are reported in the
              server log files. This section describes these errors.

              %DSL-E-DUPOBJ, Duplicate network object

              Description: A server with the same DECnet object name or
                           TCP/IP port number is already running on the
                           system.

              Action:      Change the DECnet object name or TCP/IP port
                           number of the server so that it is unique.

              %DSL-E-INSFMEM, Insufficient virtual memory

              Description: There is not enough virtual memory for the
                           server to operate.

              Action:      Change the server's configuration details to
                           increase the page file quota (PGFLQUOTA).

              %DSL-E-INVOBJNUM, Invalid object number

              Description: The DECnet object name or TCP/IP port number
                           specified in the server's configuration
                           details is not valid.

              Action:      Change the DECnet object name or TCP/IP port
                           number of the server.

                           DECnet object numbers must be in the range
                           1 to 255. Digital recommends that, when
                           specifying a DECnet object number, you avoid
                           using numbers below 128, because these are
                           reserved by Digital.

                                                    Solving Problems 12-7

 



        Solving Problems
        12.4 DASL Errors



                           TCP/IP port numbers must be in the range 1024
                           to 65535.

              %DSL-E-NOPRIV, Insufficient privilege

              Description: The process in which the server is running
                           must have SYSNAM, TMPMBX, and NETMBX
                           privileges for sessions to be able to connect
                           to the server.

              Action:      Check that the server image is installed with
                           these privileges, then restart the server.

              %DSL-W-SHUT, Network shutdown

              Description: DECnet or TCP/IP is not available.

              Action:      Restart DECnet or TCP/IP.

                           Check that the value of the NCP parameter,
                           Maximum Declared Objects, is sufficient for
                           all the objects on your system.

              %DSL-E-INVNET, Invalid network

              Description: The server has a TCP/IP address specified,
                           but TCP/IP networking is not available on the
                           system.

              Action:      Install TCP/IP software, or clear the TCP/IP
                           port number field in the server's details.

              %DSL-E-INVTSKNAM, Invalid task name string

              Description: The server has an invalid DECnet address.

              Action:      Check that the DECnet object name contains
                           only alphanumeric characters, and is no longer
                           than 12 characters.

              %DSL-W-NOTSKNAM, OBJNUM or OBJLOG or OBJTSKADR must be
              specified

              Description: No DECnet address or TCP/IP address is
                           specified for the server.

              Action:      Specify a valid DECnet address or TCP/IP
                           address, or both, for the server.

        12-8 Solving Problems

 














     _________________________________________________________________

                                                                 Index



     A______________________________   B______________________________

     Access                            Batch queue,  8-4
       to AIDA Server, 8-15            Broadcast message
       to File Cabinet object, 9-2       enabling,  7-8
     Access violation,  12-4             receiving on a PC,  8-17,
     Additional language                    10-1, 12-4
        installation, 4-4                testing,  11-10
     AIDA Server
       access for users, 8-2, 8-15     C
       configuration file, 8-3         _______________________________
       connections, 8-1, 8-17          Cache
       creating, 8-3, 8-18               drawer,  9-3, 9-9, 9-17, 9-21
       deleting, 8-18                  Capacity license,  7-2
       disabling, 8-16                 Captive ALL-IN-1 accounts
       editing, 8-3                      making asynchronous
       enabling, 8-16                       connections from, 3-3
       logging activity of, 11-2       Client
       starting, 8-16, 8-18              disconnect from File Cabinet
       state, 8-15                          Server, 9-16
       stopping, 8-16                    maximum connections to AIDA
       TCP/IP port number, 7-7              Server, 8-7, 8-8, 8-9
       tracing activity of, 11-5         maximum connections to File
     AppleTalk Gateway,  7-8, 10-2          Cabinet Server, 9-10,
     Asynchronous connection,  7-8          9-20, 9-22
       from captive account, 3-3       Cluster alias,  12-2
     Attributes                        Common Transport Interface
       of File Cabinet Server, 9-4,       (CTI),  7-8
         9-9, 9-13                     Concurrent tasks
     Audit information                   AIDA Server,  8-10
       about a File Cabinet Server,    Concurrent use license,  7-2
         9-18                          Configuration

                                         of AIDA Server,  8-3

                                                               Index-1

 







        Configuration (cont'd)            Delete (cont'd)

         of File Cabinet Server,  9-4,      AIDA Server, 8-18
            9-8, 9-13                       AIDA Server log files, 8-6,
        Connections to AIDA Server,           11-3
          8-1                               AIDA Server session, 8-17
         enabling new,  8-16                AIDA Server trace files,
         index of,  8-17                      8-6, 11-5
         maximum,  8-7, 8-8, 8-9, 12-1    Disable
         preventing new,  8-16              a File Cabinet Server, 9-15
         tracing,  11-4                     AIDA Server, 8-16
        Connections to File Cabinet         File Cabinet Server, 9-5
          Server,  9-1                    Disconnect
         enabling,  9-14                    AIDA Server session, 8-17
         failure,  12-1                     File Cabinet Server client,
         index of,  9-15                      9-16
         maximum,  9-10, 9-20, 9-22       Disk quota
         monitoring,  9-5, 9-16             checking, 2-1, 9-16
         preventing,  9-15                  warning, 9-5
         terminating,  9-16               Disk space,  4-5
         tracing,  11-9                     and AIDA server log files,
        Create                                11-3
         a File Cabinet Server,  9-4,     Drawer
            9-11                            cache, 9-3, 9-9, 9-17, 9-21
         an AIDA Server,  8-18              closing, 9-2, 9-10
         remote File Cabinet Server         open, 9-2, 9-3, 9-9, 9-10,
            entry,  9-6                       9-16, 9-20, 9-21

        D______________________________   E______________________________

        Data file                         Enable
         system,  8-11                      AIDA Server, 8-16
        Data set                            File Cabinet Server, 9-5,
         OA$PC_NOTIFY,  10-2, 10-3,           9-14
            12-5, 12-6                    Error
        DECnet                              internal, 12-4
         node name,  9-2, 12-3
         object name,  8-5, 12-7, 12-8    F______________________________
         object number,  8-5, 9-8,        File
            9-12, 12-2                      locked, 3-3, 8-17
         transport,  7-6, 10-2            File Cabinet Server
        DEC TCP/IP Services for             attributes, 9-9, 9-13
          OpenVMS,  7-6                     clients, 9-15
        Delete                              configuration, 9-8, 9-13
         a File Cabinet Server,  9-4,       connections, 9-15
            9-13

        Index-2

 







        File Cabinet Server (cont'd)      Installation Verification
         controlling cross-drawer            Procedure (IVP)
            operations,  9-1                running, 5-6, 11-1
         creating,  9-4, 9-11             Internal error,  12-4
         default,  9-12                   Internal queue
         deleting,  9-4, 9-13               PC Broadcast Server, 12-5

         disabling,  9-5, 9-15
         enabling,  9-5, 9-14             K______________________________

         failure to connect to,  12-1     Kit
         log file,  2-2, 11-7               contents, 4-1
         managing,  9-3
         remote,  9-6                     L______________________________
         reserving documents,  9-1        Language
         starting,  9-4, 9-14, 12-3         additional, 4-4
         status,  9-13                    Library search order,  8-12
         stopping,  9-4, 9-14             License
         TCP/IP port number,  7-7           capacity, 7-1, 7-2
         tracing,  11-8                     concurrent use, 7-2
        Flush                               personal, 7-1, 7-2
         data files,  8-11                Locked file,  3-3
        Form library                      Log file
         accessing,  8-12                   AIDA Server, 8-6, 11-2, 11-3
         search order,  8-12                deleting, 8-6, 8-19, 11-3
        Full installation, 4-3              File Cabinet Server, 2-2,

        I______________________________       11-7
        Index                               PC Broadcast Server, 11-9
         AIDA Server log files,  11-2     Logical name
         AIDA Server trace logs,  11-5      OA$AIDA_DDS_MIN_SURNAME,
         connections to AIDA Server,          8-10
            8-17                            OA$AIDA_DDS_TIMEOUT_SECONDS,
         connections to File Cabinet          8-11
            Server,  9-15                   OA$AIDA_LSO_FILE, 8-12
         File Cabinet Server log files      OA$DDS_PRIME, 8-9, 8-10
                                            OA$PC_ATK$GATEWAY, 7-8, 10-2
            ,  11-8                         OA$PC_BROADCAST_TRANSPORTS,
        Installation                          11-11
         aborting,  5-1                     OAFC$DISKQUOTALIMIT, 9-16
         restarting,  5-2, 6-1              OAFC$SERVER_PRIORITY, 9-22
         stopping,  5-2                     OAFC$SRV_OBJ, 9-12, 12-2
         time required,  5-1
         type,  4-3

                                                                  Index-3

 







                                          Notification data set
        M______________________________     OA$PC_NOTIFY, 10-3
        Mailbox, 12-5                     Notification of new mail,
         OA$PCBDCST_MBX,  10-1               10-1, 12-4

        Mail directory inquiry
         and AIDA Server performance,     O______________________________

            8-10                          OA$AIDA_DDS_MIN_SURNAME
         limiting the waiting time,          logical name, 8-10
            8-11                          OA$AIDA_DDS_TIMEOUT_SECONDS
         restricting the breadth of          logical name, 8-11
            search,  8-10                 OA$AIDA_LSO_FILE logical name,
        Manage AIDA Servers menu, 8-1        8-12
        Manage Servers menu, 9-5          OA$DDS_PRIME logical name,
        Maximum                              8-9, 8-10
         concurrent tasks,  8-11          OA$PCBDCST_MBX mailbox,  10-1
         connections to AIDA Server,      OA$PC_ATK$GATEWAY logical
            8-7, 8-8, 8-9, 12-1              name, 7-8, 10-2
         connections to File Cabinet      OA$PC_BROADCAST_TRANSPORTS
            Server,  9-10, 9-20, 9-22        logical name, 11-11
         open drawers,  9-10, 9-21        OA$PC_NOTIFY data set,  10-2,
        Menu                                 10-3, 12-5
         Index of Server Connections,       checking, 12-6
            8-17                          OAFC$SERVER_PRIORITY logical
         Manage AIDA Servers,  8-1           name, 9-22
         Manage Server Clients Index,     OAFC$SRV_OBJ logical name,
            9-16                             9-12, 12-2
         Manage Servers,  9-5             Object
         Manage Trace Logs,  11-5           DECnet, 8-5, 9-8, 12-2,
        Modem                                 12-7, 12-8
         accessing TeamLinks through,     Object library,  6-1
            7-8                           Open

        N                                   data file, 8-11
        _______________________________     drawer, 9-2, 9-10, 9-16,
        NETBIOS error, 12-5                   9-20, 9-21
        NETWORK.DAT data file, 8-11       OpenVMS account details
        New mail                            BYTLM, 7-9
         notification,  10-1, 12-4
        Node name                         P______________________________
         AIDA Server,  8-4                Partition file,  9-2
         File Cabinet Server,  9-8        PC Broadcast Server,  10-1
        Node Specific Batch Queues          and TCP/IP network protocol,
          data set,  8-4                      2-2

                                            internal queue, 11-10, 12-5
                                            log file, 11-9

        Index-4

 







        PC Broadcast Server (cont'd)      Quota
         starting,  10-1, 12-6              checking, 2-1, 9-16

         stopping,  12-7
        PC notification data set,         R______________________________

          10-2, 10-3                      Relinking ALL-IN-1,  4-6, 7-9
        Personal license, 7-2             Remote
        Port number                         access to ALL-IN-1 services,
         TCP/IP,  7-7, 8-6, 9-11,             7-8
            9-12, 12-3, 12-7                client, 9-16
        Postinstallation procedures         drawer, 3-2, 12-3
         running,  6-2                      File Cabinet Server, 9-6
        Priority                          Remote Connection Manager
         of AIDA server process,  8-8       modifying script for captive
         of File Cabinet Server               accounts,  3-3
            Process,  9-22                Resources
        Privileges                          used by a File Cabinet Server
         required for installing TLC,         ,  9-18
            5-2                           Rights identifier
         required for setting process       OAFC$SYSMAN, 9-6
            priority,  9-22
        Process                           S______________________________
         name of File Cabinet Server,     SCSNODE SYSGEN parameter,  7-5
            9-8                           SCSSYSTEMID SYSGEN parameter,
         priority of AIDA Server,            7-5
            8-7, 8-8                      Service name,  7-7, 8-6
         priority of File Cabinet         Session on AIDA Server
            Server,  9-22                   as means of accessing
         quota for AIDA Server,  8-9,         ALL-IN-1 data,  8-1
            8-10                            disconnecting, 8-17
         quota for asynchronous             enabling new, 8-16
            connection,  7-9                preventing new, 8-16
         quota for File Cabinet Server    Show audit information (SAI),
            ,  9-19                          9-18
        Profile entry                     Show resource information
         RSVD_FOR_TCS flag,  12-6            (SRI), 9-18

        Q                                 Show server status (SSS),  9-13
        _______________________________   Shut down ALL-IN-1,  4-3
        Queue                             Site link file,  4-6
         for AIDA Server startup,  8-4    Start
         for File Cabinet Server            AIDA Server, 8-6, 8-16, 8-18
            startup,  9-9, 9-14             File Cabinet Server, 9-4,
         PC Broadcast Server,  12-5           9-14, 12-3
                                            PC Broadcast Server, 10-1,
                                              12-6

                                                                  Index-5

 







        Startup procedure                 Transport mechanism,  7-5
         AIDA Server,  8-4                  AppleTalk, 7-6
         ALL-IN-1,  4-1, 8-6, 10-1          DECnet, 7-6
         File Cabinet Server,  9-9          disabling for broadcast
        State                                 notification,  11-11
         of AIDA Server,  8-15              TCP/IP, 7-6
         of servers in UCX,  7-6
        Status                            U______________________________
         of File Cabinet Server,  9-13    UCX,  7-6
        Stop                                state of servers, 7-6
         AIDA Server,  8-16               Update installation,  4-3
         File Cabinet Server,  9-4,       User profile
            9-14                            RSVD_FOR_TCS flag, 10-2,
         installation,  5-2                   12-6
         PC Broadcast Server,  12-7
        Subprocess
         for using the Mail directory,
            8-10
        SYSGEN parameter
         SCSNODE,  7-5
         SCSSYSTEMID,  7-5
         TTY_TYPAHDSZ,  7-9
        System data file
         accessing,  8-11

        T______________________________

        TCP/IP
         host name,  12-3
         network,  7-6
         port number,  7-7, 8-6, 9-11,
            9-12, 12-3, 12-7
         service name,  7-8, 8-6
        Thread access violation, 12-4
        Time required for installation
          ,  5-1
        Trace file
         AIDA Server,  8-6, 11-5
         deleting,  8-6, 8-19, 11-5
        Tracing
         AIDA Server,  11-3
         and performance,  8-8
         File Cabinet Server,  2-2,
            11-8

        Index-6