 















          LAT Version 5.4-2 Installation and
          Release Notes




          February 1991

          This document contains information about installing
          and using LAT Version 5.4-2 software on the VMS
          operating system.




          Operating System Version:     VMS Version 5.4-2 or
                                        higher

          Software Version:             LAT Version 5.4-2










          digital equipment corporation
          maynard, massachusetts

 





          ________________________
          February 1991

          __________
          The information in this document is subject to change
          without notice and should not be construed as a
          commitment by Digital Equipment Corporation. Digital
          Equipment Corporation assumes no responsibility for
          any errors that may appear in this document.

          The software described in this document is furnished
          under a license and may be used or copied only in
          accordance with the terms of such license.

          No responsibility is assumed for the use or
          reliability of software on equipment that is not
          supplied by Digital Equipment Corporation or its
          affiliated companies.

          Restricted Rights: Use, duplication, or disclosure
          by the U.S. Government is subject to restrictions as
          set forth in subparagraph (c)(1)(ii)  of the Rights in
          Technical Data and Computer Software clause at DFARS
          252.227-7013.

          __________
          © Digital Equipment Corporation 1991.

          All Rights Reserved.
          Printed in U.S.A.

          __________
          The postpaid Reader's Comments forms at the end of
          this document request your critical evaluation to
          assist in preparing future documentation.

          The following are trademarks of Digital Equipment
          Corporation:

          CDA           DEQNA         MASSBUS         VAXcluster
          DDIF          Desktop-VMS   MicroVAX        VAX RMS
          DEC           DIGITAL       PrintServer 40  VAXserver
          DECdtm        GIGI          Q-bus           VAXstation
          DECnet        HSC           ReGIS           VMS
          DECUS         LAT           ULTRIX          VT
          DECwindows    LiveLink      UNIBUS          XUI
          DECwriter     LN03          VAX             DIGITAL

          The following is a third-party trademark:

          PostScript is a registered trademark of Adobe Systems
          Incorporated.

 





          __________________________________________________________________

          Production Note

          This book was produced with the VAX DOCUMENT
          electronic publishing system, a software tool
          developed and sold by Digital. In this system, writers
          use an ASCII text editor to create source files
          containing text and English-like code; this code
          labels the structural elements of the document, such
          as chapters, paragraphs, and tables. The VAX DOCUMENT
          software, which runs on the VMS operating system,
          interprets the code to format the text, generate a
          table of contents and index, and paginate the entire
          document. Writers can print the document on the
          terminal or line printer, or they can use Digital-
          supported devices, such as the LN03 laser printer
          and PostScript printers (PrintServer 40 or LN03R
          ScriptPrinter), to produce a typeset-quality copy
          containing integrated graphics.

 






          _______________________________________________________

          Contents

                _________________________________________________
                PREFACE                                      viii

          _______________________________________________________
          CHAPTER 1  LAT INSTALLATION PROCEDURES              1-1

                _________________________________________________
                1.1      BEFORE INSTALLING THE LAT VERSION 5.4-2
                         SOFTWARE                             1-1

                _________________________________________________
                1.2      INSTALLING THE LAT VERSION 5.4-2
                         SOFTWARE                             1-4

                _________________________________________________
                1.3      POSTINSTALLATION PROCEDURES         1-10

                _________________________________________________
                1.4      REINSTALLING LTDRIVER               1-11


          _______________________________________________________
          CHAPTER 2  LAT VERSION 5.4-2 RELEASE NOTES          2-1

                _________________________________________________
                2.1      LAT GENERAL USER RELEASE NOTES       2-1

                2.1.1       Outbound LAT Connections
                            Support                           2-1

                _________________________________________________
                2.2      LAT SYSTEM MANAGER RELEASE NOTES     2-3

                2.2.1       LATCP Commands Replaced           2-3

                2.2.2       Modifications to LATCP Command SET
                            NODE                              2-4

                2.2.3       LATCP offering Services over
                            Specific Links Removed            2-6

                                                                v

 


          Contents



                2.2.4       Other LATCP Commands and Qualifiers
                            Ignored                           2-6

                2.2.5       New LATCP Display Commands        2-7

                2.2.6       Other New LATCP Commands and
                            Qualifiers                        2-7

                2.2.7       New LATCP Help Library            2-8

                2.2.8       New Startup Method                2-8

                2.2.9       Do not INSTALL LATCP              2-9

                2.2.10      Using the LATCP Command
                            SET NODE/STATE=OFF or
                            /STATE=SHUT                      2-10

                2.2.11      LAT Print Symbiont (LATSYM)      2-10

                2.2.12      LATCP enabling of group
                            codes                            2-11

                2.2.13      New TTY_ALTYPAHD Setting for Forward
                            Ports                            2-12

                2.2.14      Expanding the LATACP Database
                            Size                             2-12

                2.2.15      Setting LTA MAX Units through
                            LATCP                            2-12

                2.2.16      Creating LAT application
                            ports                            2-12

                2.2.16.1   Using LATCP SET
                           NODE/DEVICE_SEED          2-13

                2.2.16.2   LATCP SET NODE/STATE=ON
                           to precede creating LTA
                           application ports         2-14

                2.2.17      LATCP SET NODE/STATE=ON to save
                            non-paged pool memory            2-15

                2.2.18      Using Dedicated Ports            2-15

                2.2.19      MUXserver 300 Terminal Server
                            Problem                          2-15

                2.2.20      DECserver 200 Multisessions
                            Problem                          2-16

                2.2.21      LATCP SET SERVICE/IDENTIFICATION
                            Command: Known Problem           2-16

          vi

 


                                                         Contents



                _________________________________________________
                2.3      LAT PROGRAMMER RELEASE NOTES        2-16

                2.3.1       Changes to QIO interface         2-16

                2.3.2       New SETMODE and SENSEMODE QIO
                            Functions                        2-17

                2.3.3       Forward Port Connections and
                            Disconnections                   2-17

                2.3.4       QIO Functions Superseded         2-17

                2.3.5       Port Modifier QIO Functions
                            Ignored                          2-18

                2.3.6       Change to Disconnect
                            Processing                       2-19

                2.3.7       LTA0 Now a Template Device       2-19

                2.3.8       QIO Completion Status            2-20

                2.3.9       LAT QIO Programming
                            Examples                         2-20

          _______________________________________________________
          APPENDIX A  MODIFICATIONS SINCE LAT VERSION
                      5.4-1                                   A-1

                _________________________________________________
                A.1      PROBLEMS AND SOLUTIONS               A-1

                _________________________________________________
                A.2      ADDITIONAL CHANGES                   A-8






                                                              vii

 





          _______________________________________________________

          Preface


          This document contains information about installing
          and using LAT Version 5.4-2 software on Version 5.4-2
          or higher of the VMS operating system.

          __________________________________________________________________

          Intended Audience

          This document is intended primarily for system
          managers and programmers.

          __________________________________________________________________

          Associated Documents

          You might need to refer to the following documents:

          o  VMS LAT Control Program (LATCP) Manual (A
             revised version of this manual is copied to
             SYS$COMMON:[SYSHLP] during the LAT installation
             and is available in PostScript (LATCP_MANUAL.PS)
             and ASCII text (LATCP_MANUAL.TXT) formats for this
             release.)

          o  VMS I/O User's Reference Manual: Part I

          __________________________________________________________________

          Conventions

          The following conventions are used in this document:

          Ctrl/x                A sequence such as Ctrl/x
                                indicates that you must hold
                                down the key labeled Ctrl while
                                you press another key or a
                                pointing device button.

          viii

 


                                                          Preface




          UPPERCASE TEXT        Uppercase letters indicate that
                                you must enter a command (for
                                example, enter OPEN/READ), or
                                they indicate the name of a
                                routine, the name of a file, the
                                name of a file protection code,
                                or the abbreviation for a system
                                privilege.

          numbers               Unless otherwise noted, all
                                numbers in the text are assumed
                                to be decimal. Nondecimal
                                radixes-binary, octal, or
                                hexadecimal-are explicitly
                                indicated.

          []                    In format descriptions, brackets
                                indicate that whatever is
                                enclosed within the brackets is
                                optional; you can select none,
                                one, or all of the choices.
                                (Brackets are not, however,
                                optional in the syntax of
                                a directory name in a file
                                specification or in the syntax
                                of a substring specification in
                                an assignment statement.)













                                                               ix

 






          _______________________________________________________

   1      LAT Installation Procedures




          This chapter provides installation procedures and
          related information that you should review before you
          install the LAT Version 5.4-2 software.

          __________________________________________________________________

   1.1    Before Installing the LAT Version 5.4-2 Software

          IMPORTANT: If you are presently running LAT Version
          5.4-1 software and you have installed VMS Version
          5.4-2, then you must install the LAT Version 5.4-2
          software.

          Installation of the LAT Version 5.4-2 software takes
          approximately five minutes, depending on the type of
          media and your system configuration. Before installing
          this software, note the following:

          1  Make sure you review all the information in this
             document.

          2  You can install LAT Version 5.4-2 software only
             on Version 5.4-2 or higher of the VMS operating
             system.

          3  Although you can reinstall your original LTDRIVER
             (as described in Section 1.4), that reinstallation
             procedure does not return your system exactly
             to its pre-LAT Version 5.4-2 LTDRIVER setup.
             Therefore, Digital recommends that you back up your
             VMS Version 5.4-2 system disk before you install
             the LAT Version 5.4-2 software in case you want to
             restore the disk fully to its pre-LAT Version 5.4-2
             state.

                                                              1-1

 


          LAT Installation Procedures
          1.1 Before Installing the LAT Version 5.4-2 Software


          4  You must have the following privileges and
             resources:

             o  SETPRV privilege, or all privileges except
                BYPASS

             o  A minimum of 3000 blocks of free disk space
                available before the installation

          5  The LAT Version 5.4-2 startup files included in
             your kit are organized as follows:

                             SYS$SYSDEVICE:
                                   |
                     --------------------------------------------------
                     |                              |
                  SYS$COMMON:[SYSMGR]         SYS$COMMON:[SYS$STARTUP]
                    LTLOAD.COM                    LAT$STARTUP.COM
                    LAT$SYSTARTUP.COM             LAT$CONFIG.COM
                    LAT$SYSTARTUP.TEMPLATE

             During the installation, these files will be moved
             to the following target directories:

          _______________________________________________________
          File_Name_______________Target_Directory_______________

          LTDRIVER.EXE            SYS$COMMON:[SYS$LDR]

          LATACP.EXE              SYS$COMMON:[SYSEXE]

          LAT$SHR.EXE             SYS$COMMON:[SYSLIB]

          LATCP.EXE               SYS$COMMON:[SYSEXE]

          LATSYM.EXE              SYS$COMMON:[SYSEXE]

          LTPAD.EXE               SYS$COMMON:[SYSEXE]

          LATCP$HELP.HLB          SYS$COMMON:[SYSHLP]

          1-2

 


                                       LAT Installation Procedures
               1.1 Before Installing the LAT Version 5.4-2 Software

          _______________________________________________________
          File_Name_______________Target_Directory_______________

          LATCP_MANUAL.TXT        SYS$COMMON:[SYSHLP]

          LATCP_MANUAL.PS         SYS$COMMON:[SYSHLP]

          LTLOAD.COM              SYS$COMMON:[SYSMGR]

          LAT$CONFIG.COM          SYS$COMMON:[SYS$STARTUP]

          LAT$STARTUP.COM         SYS$COMMON:[SYS$STARTUP]

          LAT$SYSTARTUP.COM       SYS$COMMON:[SYSMGR]

          LAT$SYSTARTUP.TEMPLATE  SYS$COMMON:[SYSMGR]

          REINSTALL_LTDRIVER.COM  SYS$COMMON:[SYSMGR]


          _______________________________________________________


             NOTE:

              o  Do NOT modify the following files:

                 -  SYS$MANAGER:LTLOAD.COM (only a placeholder
                   for this release)

                 -  SYS$STARTUP:LAT$STARTUP.COM (calls
                   LAT$CONFIG.COM and LAT$SYSTARTUP.COM)

                 -  SYS$STARTUP:LAT$CONFIG.COM (loads driver and
                   starts LATACP)

              o  You can modify SYS$MANAGER:LAT$SYSTARTUP.COM to
                start up LAT site-specific commands that suit
                your environment.



                                                              1-3

 


          LAT Installation Procedures
          1.1 Before Installing the LAT Version 5.4-2 Software


              o  Version 5.4 of the LAT host software, which is
                bundled with the VMS operating system, already
                contains the files LTLOAD.COM, LTDRIVER.EXE,
                and LATCP.EXE. After you install the LAT Version
                5.4-2 software, multiple versions of these files
                will exist in the target SYS$COMMON directories.
                Files with the higher version numbers are the
                LAT Version 5.4-2 files.

              o  If you have [SYSMGR]LTLOAD.COM,
                [SYS$LDR]LTDRIVER.EXE, or [SYSEXE]LATCP.EXE
                located in the SYS$SPECIFIC: directory instead
                of SYS$COMMON: (particularly in a VAXcluster
                environment), the LAT Version 5.4-2 software
                will not function after you reboot the system.
                Digital recommends that you move these files to
                the corresponding SYS$COMMON: directories before
                you install the LAT Version 5.4-2 software.
                This will ensure that you can successfully
                reinstall your pre-LAT Version 5.4-2 LTDRIVER
                (as described in Section 1.4 if you choose to do
                so at a later date.

          6  During the LAT Version 5.4-2 installation,
             XTERMINAL Host Services software is upgraded on
             your system as well. This software supports the
             VT1000 and VT1200 terminals as X display devices
             connected to the host system using LAT as the X
             Transport Protocol.

          __________________________________________________________________

   1.2    Installing the LAT Version 5.4-2 Software

          Install the LAT Version 5.4-2 software as follows:

          1  Log in to a privileged account and invoke VMSINSTAL
             by entering the following command:

                  $ @SYS$UPDATE:VMSINSTAL LATU2054 ddcu:

          1-4

 


                                       LAT Installation Procedures
                     1.2 Installing the LAT Version 5.4-2 Software


             where:

             o  dd is the device code for the drive that holds
                the distribution media

             o  c is the controller designation code

             o  u is the unit number, which along with the
                controller designation code identifies the
                location of the device

          2  When you invoke VMSINSTAL, the procedure does the
             following and asks you to respond to the prompts as
             necessary:

             o  Checks whether you are logged in to a privileged
                account

             o  Checks whether you have adequate quota for
                installation

             o  Checks whether SYS$SYSDEVICE has at least 3000
                free blocks

             o  Displays a list of active processes

             o  Asks whether you want to continue

             o  Asks whether you are satisfied with the backup
                of your system disk

          3  The procedure then generates a number of
             informational messages similar to the following:

          %LAT-I-NOINQUIRE, No more questions will be asked

          %LAT-I-BEGIN,  Beginning installation of LAT V5.4-2 ...

          %LAT-I-INSTALL,  Installing LAT

             The following message indicates that the
             installation is successful:

          %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

                                                              1-5

 


          LAT Installation Procedures
          1.2 Installing the LAT Version 5.4-2 Software


          4  The procedure creates the following LAT Version
             5.4-2 files:

          _______________________________________________________
                                    Destination
                                    in
          File_Name_________________SYS$COMMON:____Function______

          LATU2054.RELEASE_NOTES    [SYSHLP]       LAT Version
          (168 blocks)                             5.4-2 release
                                                   notes

          LTDRIVER.EXE              [SYS$LDR]      LAT driver
          (96 blocks)

          LATACP.EXE                [SYSEXE]       ACP for LAT
          (106 blocks)                             driver

          LAT$SHR.EXE               [SYSLIB]       Shareable
          (169 blocks)                             image for
                                                   LAT Control
                                                   Program
                                                   (LATCP)

          LATCP.EXE                 [SYSEXE]       LAT Control
          (10 blocks)                              Program

          LATSYM.EXE                [SYSEXE]       LAT printer
          (103 blocks)                             symbiont

          LTPAD.EXE                 [SYSEXE]       SET HOST/LAT
          (41 blocks)

          LATCP$HELP.HLB            [SYSHLP]       LATCP help
          (203 blocks)                             library

          LTLOAD.COM                [SYSMGR]       LAT site-
          (3 blocks)                               independent
                                                   placeholder


          1-6

 


                                       LAT Installation Procedures
                     1.2 Installing the LAT Version 5.4-2 Software

          _______________________________________________________
                                    Destination
                                    in
          File_Name_________________SYS$COMMON:____Function______

          LAT$STARTUP.COM           [SYS$STARTUP]  LAT site-
          (7 blocks)                               independent
                                                   startup com-
                                                   mand proce-
                                                   dure; calls
                                                   LAT$CONFIG.COM
                                                   and LAT$SYSTARTUP.COM

          LAT$CONFIG.COM            [SYS$STARTUP]  LAT site-
          (7 blocks)                               independent
                                                   startup
                                                   command
                                                   procedure;
                                                   loads driver
                                                   and starts
                                                   LATACP

          LAT$SYSTARTUP.COM         [SYSMGR]       LAT site-
          (8 blocks)                               specific
                                                   startup
                                                   command
                                                   procedure

          LAT$SYSTARTUP.TEMPLATE    [SYSMGR]       LAT site-
          (8 blocks)                               specific
                                                   startup
                                                   template

          REINSTALL_LTDRIVER.COM    [SYSMGR]       LTDRIVER re-
          (15 blocks)                              installation







                                                              1-7

 


          LAT Installation Procedures
          1.2 Installing the LAT Version 5.4-2 Software

          _______________________________________________________
                                    Destination
                                    in
          File_Name_________________SYS$COMMON:____Function______

          LATCP_MANUAL.TXT          [SYSHLP]       LATCP manual
          (444 blocks)                             in ASCII text
                                                   format

          LATCP_MANUAL.PS           [SYSHLP]       LATCP manual
          (845 blocks)                             in PostScript
                                                   format
          text format)


          _______________________________________________________

             The installation procedure also creates the
             following XTERMINAL files:

          _______________________________________________________
                                    Destination
                                    in
          File_Name_________________SYS$COMMON:____Function______

          XTDRIVER.EXE              [SYS$LDR]      XTERMINAL
          (13 blocks)                              driver

          DECW$TRANSPORT_LAT.EXE    [SYSLIB]       X Transport
          (13 blocks)

          DECW$DWT_DECNET.EXE       [SYSEXE]       DECnet
          (20 blocks)                              component

          DECW$DWT_FONT_DAEMON.EXE  [SYSEXE]       Font daemon
          (24 blocks)

          DECW$STARTXTERMINAL.COM   [SYSMGR]       XTERMINAL
          (14 blocks)                              startup



          1-8

 


                                       LAT Installation Procedures
                     1.2 Installing the LAT Version 5.4-2 Software

          _______________________________________________________
                                    Destination
                                    in
          File_Name_________________SYS$COMMON:____Function______

          REINSTALL_XTERMINAL.COM   [SYSUPD]       XTERMINAL re-
          (7 blocks)                               installation


          _______________________________________________________
































                                                              1-9

 


          LAT Installation Procedures
          1.2 Installing the LAT Version 5.4-2 Software


          5  The following display signals the completion of the
             LAT Version 5.4-2 installation procedure:

                 Installation of LAT V5.4-2 completed at hh:mm

           Enter the products to be processed from the next distribution volume set.
          * Products:

                 VMSINSTAL procedure done at hh:mm


          NOTE: If the installation procedure fails, a message
          similar to the following will be displayed:

               The installation of LAT V5.4-2 has failed.

           One or more of the following conditions can cause the
          installation to fail:

           o  Wrong version of the VMS operating system (must be
             5.4-2 or higher)

           o  Insufficient quotas

           o  Premature termination of VMSINSTAL (for example, by
             pressing CTRL/Y or by experiencing a system power
             failure)

           If the installation fails and you have corrected the
          condition that caused the failure, you must restart
          the installation, beginning with the procedures
          described in Section 1.2.

          __________________________________________________________________

   1.3    Postinstallation Procedures

          After you have successfully installed the LAT Version
          5.4-2 software, follow these procedures:

          CAUTION: Do NOT delete any files in
          SYS$COMMON:[SYSUPD.OLD_LAT]. Files in this directory
          are required if you want to reinstall pre-LAT Version

          1-10

 


                                       LAT Installation Procedures
                                   1.3 Postinstallation Procedures


          5.4-2 LTDRIVER and XTERMINAL files. For information
          about the reinstallation procedure, see Section 1.4.

          1  Modify LAT$SYSTARTUP.COM by moving all your
             LAT site-specific commands from your original
             LTLOAD.COM file to SYS$MANAGER:LAT$SYSTARTUP.COM.
             Use LAT$SYSTARTUP.TEMPLATE as a guide.

             Make sure your LAT$SYSTARTUP.COM has only LATCP
             commands. The SYSGEN command to load the LTDRIVER
             in your original LTLOAD.COM must not be included
             (LAT$CONFIG.COM performs that task).

             NOTE: Do NOT modify LTLOAD.COM, LAT$STARTUP.COM,
             or LAT$CONFIG.COM. Those files contain contain LAT
             site-independent LAT commands.

          2  Make sure that your SYSTARTUP_V5.COM file does NOT
             install LATCP.

             CAUTION: LAT Version 5.4-2 software does not require
             and will NOT work with the LAT Control Program
             (LATCP) if LATCP has been installed using CMKRNL
             privilege.

          3  To start the LAT Version 5.4-2 software, reboot
             your system. Note that the XTERMINAL host services
             software is started automatically when you reboot
             the system.

          4  After the system is up, reboot all VT1000 and
             VT1200 X terminals that are connected to this
             system (using LAT as the X Transport Protocol).

          __________________________________________________________________

   1.4    Reinstalling LTDRIVER

          This section describes how to reinstall the version of
          LTDRIVER that was on your system before you installed
          the LAT Version 5.4-2 software.

          Note: If your system was running LAT V5.4-1 and you
          have installed LAT V5.4-2 and now want to reinstall

                                                             1-11

 


          LAT Installation Procedures
          1.4 Reinstalling LTDRIVER


          LTDRIVER, this reinstallation procedure will reinstall
          the version of LTDRIVER that was on your system prior
          to the installation of the LAT V5.4-1 software. That
          is, the reinstallation procedure is not intended to
          reinstall LAT V5.4-1.

          NOTE: This reinstallation procedure does not return
          your system exactly to its pre-LAT Version 5.4-2
          LTDRIVER setup. To achieve that, you must use the
          VMS Backup Utility to save the system disk before you
          install the LAT Version 5.4-2 software. You can then
          use the Backup Utility to restore the disk fully to
          its pre-LAT Version 5.4-2 state.

          1  During the LAT Version 5.4-2 installation
             procedure, the following files are copied
             to SYS$COMMON:[SYSUPD.OLD_LAT] (file type
             .PRE_V54_UP:)

             o  LAT files:

                   SYS$LOADABLE_IMAGES:LTDRIVER.EXE
                   SYS$SYSTEM:LATCP.EXE
                   SYS$MANAGER:LTLOAD.COM

             o  XTERMINAL host services files:

                   SYS$LOADABLE_IMAGES:XTDRIVER.EXE
                   SYS$LIBRARY:DECW$TRANSPORT_LAT.EXE
                   SYS$SYSTEM:DECW$DWT_DECNET.EXE
                   SYS$SYSTEM:DECW$DWT_FONT_DAEMON.EXE
                   SYS$MANAGER:DECW$STARTXTERMINAL.COM

             If you want to reinstall the version of LTDRIVER
             that was on your system prior to the installation
             of the LAT Version 5.4-2 software, enter the
             following command:

                  $ @SYS$MANAGER:REINSTALL_LTDRIVER


          1-12

 


                                       LAT Installation Procedures
                                         1.4 Reinstalling LTDRIVER


          2  The procedure will copy the files listed in step 1
             from SYS$COMMON:[SYSUPD.OLD_LAT] to the designated
             SYS$COMMON directories. These files will supersede
             existing files of the same name. Files of the same
             name will not be purged.

          3  The following LAT Version 5.4-2 files, not present
             in LTDRIVER Version 5.4 or earlier, will be removed
             from your system disk:

                SYS$COMMON:[SYSLIB]LAT$SHR.EXE;*
                SYS$COMMON:[SYSEXE]LTPAD.EXE;*
                SYS$COMMON:[SYSEXE]LATACP.EXE;*
                SYS$COMMON:[SYSHLP]LATCP$HELP.HLB;*
                SYS$COMMON:[SYS$STARTUP]LAT$CONFIG.COM;*
                SYS$COMMON:[SYS$STARTUP]LAT$STARTUP.COM;*
                SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.TEMPLATE;*

          4  SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COM will not be
             deleted, in case you want to examine this file
             for additional LAT site-specific commands that
             may have been added since the LAT Version 5.4-2
             installation.


















                                                             1-13

 






          _______________________________________________________

   2      LAT Version 5.4-2 Release Notes




          This chapter includes LAT Version 5.4-2 information
          of interest to general users, system managers, and
          programmers.

          __________________________________________________________________

   2.1    LAT General User Release Notes

          This section contains LAT-specific information for
          general users of the VMS operating system.

          ___________________________

   2.1.1  Outbound LAT Connections Support

          The LAT Version 5.4-2 software provides support for
          outbound (forward) LAT connections by means of the
          SET HOST/LAT command. (Note, however, that you cannot
          use SET HOST/LAT to connect to the local node.) After
          the LAT Version 5.4-2 software has been installed on
          your system, you can use this feature by entering the
          following command:

               $ SET HOST/LAT [service-name]

          The SET HOST/LAT command accepts the following
          qualifiers:

          o  /NODE=node-name

             Specifies the node that offers the service to which
             you want to connect. Failover will not be performed
             if the connection fails.

          o  /DESTINATION_PORT=port-name

             Specifies the port on a node to which you want to
             connect. You must specify the /NODE qualifier along
             with the /DESTINATION_PORT qualifier.

                                                              2-1

 


          LAT Version 5.4-2 Release Notes
          2.1 LAT General User Release Notes


          o  /PASSWORD=password

             Service password (if required).

          o  /LOG[=log-file]

             Logs the session to the specified file. SETHOST_
             LAT.LOG is the default file name.

          o  /DISCONNECT=disconnect-character

             Defines the character that you can use to
             disconnect from a remote session, which you do by
             pressing CTRL/disconnect-character. You can select
             any ASCII character from @ through z, except C,
             M, Q, S, Y, and the left bracket ([). For example,
             if you specify /DISCONNECT=A, CTRL/A will be the
             disconnect character. You cannot select a character
             that is already defined as the break character.

          o  /BREAK=break-character

             Defines a character that you can use to generate
             a break on lines that expect a break rather than
             a carriage return. To generate a break, press
             CTRL/break-character. You can select any ASCII
             character between @ and z, except C, M, Q, S,
             Y, and the left bracket ([). You cannot select a
             character that is already defined as the disconnect
             character.

          o  /[NO]AUTOCONNECT

             Specifies whether connection attempts should be
             retried automatically when a connection fails
             because a service is unknown or unavailable, or
             because a node is unknown or unreachable. Also
             specifies that reconnects should be attempted
             automatically if a service has disconnected
             abnormally. The default is /NOAUTOCONNECT.

          2-2

 


                                   LAT Version 5.4-2 Release Notes
                              2.2 LAT System Manager Release Notes

          __________________________________________________________________

   2.2    LAT System Manager Release Notes

          This section contains LAT-specific information for
          system managers.

          For Version 5.4-2 of the LAT software, the LAT port
          driver (LTDRIVER) and the LAT Control Program (LATCP)
          have been rewritten. In addition, the LAT Ancillary
          Control Process (LATACP) is new. LATACP assists
          LTDRIVER by maintaining information about the local
          node and about nodes and services to which you can
          connect. LAT terminal emulation (invoked with the SET
          HOST/LAT command) is provided by the new LTPAD image.

          ___________________________

   2.2.1  LATCP Commands Replaced

          Several LATCP commands have been replaced. Although
          existing command procedures that use the pre-Version
          5.4-2 LATCP commands are still supported in this
          release, Digital recommends that you modify those
          existing command procedures accordingly and begin
          using the new LATCP commands whenever you create a new
          command procedure.

          The new commands and the old commands they replace are
          shown in the following table. See the LATCP help and
          the revised VMS LAT Control Program (LATCP) Manual for
          more information about the new commands. (The revised
          VMS LAT Control Program (LATCP) Manual is copied to
          SYS$COMMON:[SYSHLP] during the LAT installation and
          is available in PostScript (LATCP_MANUAL.PS) and ASCII
          text (LATCP_MANUAL.TXT) formats for this release.)






                                                              2-3

 


          LAT Version 5.4-2 Release Notes
          2.2 LAT System Manager Release Notes

          _______________________________________________________
          Old_Command_____________________New_Command____________

          START NODE                      SET NODE/STATE=ON

          STOP NODE                       SET NODE/STATE=OFF

          SET PORT/LINK[=link-name]       SET PORT (ignoring
                                          qualifier)

          SET COUNTERS/ZERO               ZERO COUNTERS/NODE

          SHOW CHARACTERISTICS            SHOW NODE

          SHOW COUNTERS/LINK[=link-name]  SHOW LINK/COUNTERS
                                          [link-name]

          SHOW COUNTERS/NODE              SHOW NODE/COUNTERS

          _______________________________________________________

          ___________________________

   2.2.2  Modifications to LATCP Command SET NODE

          Two qualifiers to the LATCP command SET NODE have
          been replaced. Although existing command procedures
          that use the pre-Version 5.4-2 qualifiers are still
          supported in this release, Digital recommends that you
          modify those existing command procedures accordingly
          and begin using the new LATCP commands whenever you
          create a new command procedure.

          The new qualifiers and the qualifiers they replace are
          shown in the following table:







          2-4

 


                                   LAT Version 5.4-2 Release Notes
                              2.2 LAT System Manager Release Notes

          _______________________________________________________
          Old_Qualifier_________________New_Qualifier____________

          /DISABLE=group-code           /GROUPS=DISABLE=group-
                                        code

          /ENABLE=group-code            /GROUPS=ENABLE=group-
                                        code

          _______________________________________________________

          The following new qualifiers have also been added
          to the SET NODE command to support new features,
          which include the ability to specify outbound
          LAT connections and the ability to create service
          responder nodes:

          o  /CIRCUIT_TIMER=msecs

          o  /CONNECTIONS=option

          o  /[NO]CPU_RATING=power

          o  /KEEPALIVE_TIMER=secs

          o  /[NO]NODE_LIMIT=value

          o  /RETRANSMIT_LIMIT=count

          o  /[NO]SERVICE_RESPONDER

          o  /SESSION_LIMIT=option

          o  /STATE=option

          o  /USER_GROUPS=option

          See the LATCP help and the revised VMS LAT Control
          Program (LATCP) Manual for a description of each
          new qualifier to the SET NODE command. (The revised
          VMS LAT Control Program (LATCP) Manual is copied to
          SYS$COMMON:[SYSHLP] during the LAT installation and
          is available in PostScript (LATCP_MANUAL.PS) and ASCII
          text (LATCP_MANUAL.TXT) formats for this release.)

                                                              2-5

 


          LAT Version 5.4-2 Release Notes
          2.2 LAT System Manager Release Notes

          ___________________________

   2.2.3  LATCP offering Services over Specific Links Removed

          With Version 5.4-2 of the VMS operating system, the
          ability to offer services selectively over specific
          links (by enabling different group codes) has been
          removed, because all services offered by a VMS node
          will now be offered over all available links. Group
          codes are now an attribute of the VMS node rather than
          of a specific link. Because of this change, the VMS
          Version 5.4-2 operating system now ignores qualifiers
          to certain LATCP commands, as follows:

          _______________________________________________________
          LATCP_Command____Qualifiers_Ignored____________________

          CREATE LINK      /DISABLE
                           /ENABLE

          CREATE SERVICE   /LINK

          SET LINK         /DISABLE
                           /ENABLE

          SET SERVICE      /LINK

          START NODE       /LINK

          STOP NODE        /LINK

          _______________________________________________________

          ___________________________

   2.2.4  Other LATCP Commands and Qualifiers Ignored

          The following LATCP command and qualifiers are also
          accepted but ignored:

          o  SHOW SERVERS command

          o  SHOW COUNTERS command qualifiers:

                /DEVICE

          2-6

 


                                   LAT Version 5.4-2 Release Notes
                              2.2 LAT System Manager Release Notes


                /INACTIVE
                /SERVERS

          ___________________________

   2.2.5  New LATCP Display Commands

          The following new commands are now available for
          displaying information about particular LAT entities:

          o  SHOW LINK

          o  SHOW NODE

          o  SHOW SERVICE

          See the LATCP help and the revised VMS LAT Control
          Program (LATCP) Manual for more information about
          these commands. (The revised VMS LAT Control Program
          (LATCP) Manual is copied to SYS$COMMON:[SYSHLP] during
          the LAT installation and is available in PostScript
          (LATCP_MANUAL.PS) and ASCII text (LATCP_MANUAL.TXT)
          formats for this release.)

          ___________________________

   2.2.6  Other New LATCP Commands and Qualifiers

          With Version 5.4-2 of the VMS operating system, you
          can associate a logical name with the name of a port
          at the time of its creation by using the /LOGICAL
          qualifier to the CREATE PORT command.

          New LATCP commands are as follows:

          o  ATTACH

          o  DEFINE/KEY

          o  DELETE LINK

          o  RECALL

          o  REFRESH

          o  SPAWN

                                                              2-7

 


          LAT Version 5.4-2 Release Notes
          2.2 LAT System Manager Release Notes


          o  ZERO COUNTERS

          See the LATCP help and the revised VMS LAT Control
          Program (LATCP) Manual for more information about
          each new command. (The revised VMS LAT Control Program
          (LATCP) Manual is copied to SYS$COMMON:[SYSHLP] during
          the LAT installation and is available in PostScript
          (LATCP_MANUAL.PS) and ASCII text (LATCP_MANUAL.TXT)
          formats for this release.)

          ___________________________

   2.2.7  New LATCP Help Library

          The old LATCP help library, LATCP.HLB, has been
          replaced by LATCP$HELP.HLB.

          ___________________________

   2.2.8  New Startup Method

          Changes to the LAT port driver (LTDRIVER) and the
          LAT Control Program (LATCP), along with the addition
          of the LAT Ancillary Control Process (LATACP),
          necessitate a new method for starting LAT software
          on the VMS operating system.

          The method now consists of executing the following
          three command procedures:

          1  SYS$STARTUP:LAT$STARTUP.COM

          2  SYS$STARTUP:LAT$CONFIG.COM

          3  SYS$MANAGER:LAT$SYSTARTUP.COM
             (LAT$SYSTARTUP.TEMPLATE is also provided in the
             SYS$MANAGER directory)

          LAT$STARTUP.COM controls the startup of the LAT
          terminal software. To start the LAT software
          automatically with each system boot, insert the
          following command in SYS$MANAGER:SYSTARTUP_V5.COM:

               @SYS$STARTUP:LAT$STARTUP

          2-8

 


                                   LAT Version 5.4-2 Release Notes
                              2.2 LAT System Manager Release Notes


          LAT$STARTUP.COM invokes LAT$CONFIG.COM to load the LAT
          terminal driver and create LATACP. LAT$STARTUP.COM
          then invokes LAT$SYSTARTUP.COM to define LAT
          characteristics specific to your site.

          NOTE: Do NOT edit LAT$STARTUP.COM or LAT$CONFIG.COM.
          Instead, edit LAT$SYSTARTUP.COM to include LATCP
          commands that define LAT characteristics specific for
          your site.

          A new LTLOAD.COM file is also included for
          this release only; it serves as a placeholder
          and simply executes the LAT startup procedure
          LAT$STARTUP. LTLOAD.COM will be obsolete in a
          future VMS release, when it will be permanently
          replaced by LAT$STARTUP.COM, LAT$CONFIG.COM,
          and LAT$SYSTARTUP.COM. You should replace any
          references you make to SYS$MANAGER:LTLOAD.COM with
          SYS$STARTUP:LAT$STARTUP.COM.

          You can execute these files from the system manager's
          account only (SYSTEM).

          ___________________________

   2.2.9  Do not INSTALL LATCP

          Do NOT use the VMS Install Utility to install LATCP.
          Version 5.4-2 of LATCP does not require CMKRNL
          privilege and must not be installed with that
          privilege. Note as well that while LATCP does not
          require any privilege to display information, it
          does require the OPER privilege to do SET and CREATE
          functions. Other privileges may be required to perform
          special management functions. See the LATCP help and
          the revised VMS LAT Control Program (LATCP) Manual for
          more information. (The revised VMS LAT Control Program
          (LATCP) Manual is copied to SYS$COMMON:[SYSHLP] during
          the LAT installation and is available in PostScript
          (LATCP_MANUAL.PS) and ASCII text (LATCP_MANUAL.TXT)
          formats for this release.)

                                                              2-9

 


          LAT Version 5.4-2 Release Notes
          2.2 LAT System Manager Release Notes

          ___________________________

   2.2.10 Using the LATCP Command SET NODE/STATE=OFF or
          /STATE=SHUT

          The LATCP command SET NODE/STATE=OFF stops the LAT
          port driver (and LAT protocol software) on your
          node. Any existing LAT connections are aborted. Any
          characteristics that you changed or set with LATCP are
          lost.

          The LATCP command SET NODE/STATE=SHUT will cause your
          VMS system to reject further incoming and outgoing LAT
          connection requests. It will not disconnect current
          sessions. When all sessions become disconnected,
          LTDRIVER will stop. This command also stops the
          LATACP (indicated by an OPCOM message) preventing
          you from performing any LAT management functions. (See
          Section 2.2.11 for information about this command's
          affect on LAT print queues.)

          To restart the LAT software on your node again,
          invoke LAT$STARTUP.COM. LATACP starts (indicated by
          an OPCOM message). The LAT characteristics defined in
          LAT$SYSTARTUP.COM will then take effect.

          ___________________________

   2.2.11 LAT Print Symbiont (LATSYM)

          Because of the change to disconnect processing (see
          Section 2.3.6), LATSYM no longer imposes a 5-second
          delay at the start of a print job.

          CAUTION: If the LAT software is stopped (by the LATCP
          command SET NODE/STATE=OFF or SET NODE/STATE=SHUT),
          LATSYM will shut down all print queues that it is
          processing. The system will then generate an OPCOM
          message indicating that the print queues are stopped.
          You must manually restart those print queues.


          2-10

 


                                   LAT Version 5.4-2 Release Notes
                              2.2 LAT System Manager Release Notes

          ___________________________

   2.2.12 LATCP enabling of group codes

          In LAT Version 5.4-2, there are two types of group
          codes that can be selectively enabled or disabled via
          LATCP.

          The first type, as it has always existed in previous
          versions of the LAT software, allows or disallows the
          listed groups access to services offered on your local
          node. For example, the LATCP command:

               $LCP SET NODE /ENAB=(12,40,43,73)

          allows group codes 12,40,43,73 access to your local
          node. An equivalent, and recommended way of the
          achieving the same result via LATCP, in LAT Version
          5.4-2, is:

               $LCP SET NODE/GROUPS=ENABLE=(12,40,43,73)/CONNECTIONS=INCOMING

          The second type of group codes restricts the access of
          outbound connections from your local node to service
          nodes in the network which belong to the specified
          groups. For example, the LATCP command:

               $LCP SET NODE /USER_GROUPS=ENABLE=(42,77)/CONNECTIONS=OUTGOING

          restricts outbound connections from your node to
          services on the network that have groups codes 42 or
          77 enabled. For more details of outbound connections,
          see Section 2.1.1. The /USER_GROUPS qualifier also
          serves to limit the number of nodes stored in your
          node's LATACP database (refer to Section 2.2.14).

          The following is an example of a LATCP command which
          enables groups codes for both incoming and outgoing
          connections for the local node:

               $LCP SET NODE/GROUP=ENA=(12,40,43,73)/USER=ENA=(42,77)/CONN=BOTH

                                                             2-11

 


          LAT Version 5.4-2 Release Notes
          2.2 LAT System Manager Release Notes

          ___________________________

   2.2.13 New TTY_ALTYPAHD Setting for Forward Ports

          To attain optimal SET HOST/LAT performance and
          forward port performance, set the SYSGEN parameter
          TTY_ALTYPAHD to 1500.

          ___________________________

   2.2.14 Expanding the LATACP Database Size

          You can expand the capacity of the LATACP's service
          and node database by increasing the setting for the
          SYSGEN parameter CTLPAGES. However, you should fill
          the database with services and nodes that you are
          interested in through proper management of group
          codes.

          ___________________________

   2.2.15 Setting LTA MAX Units through LATCP

          You can set MAX units for LTA devices with the LATCP
          command SET NODE/UNIT_NUMBER_MAXIMUM. You cannot set
          this value through SYSGEN. See the LATCP help and
          the revised VMS LAT Control Program (LATCP) Manual
          for more information about the SET NODE/UNIT_NUMBER_
          MAXIMUM command. (The revised VMS LAT Control Program
          (LATCP) Manual is copied to SYS$COMMON:[SYSHLP] during
          the LAT installation and is available in PostScript
          (LATCP_MANUAL.PS) and ASCII text (LATCP_MANUAL.TXT)
          formats for this release.)

          ___________________________

   2.2.16 Creating LAT application ports

          If you are attempting to create an application port,
          you may encounter this error:

                   $LCP CREATE PORT LTA5001:/APPLICATION
                   %LAT-W-CMDERROR, error reported by command executor
                   -SYSTEM-F-DUPLNAM, duplicate name

          2-12

 


                                   LAT Version 5.4-2 Release Notes
                              2.2 LAT System Manager Release Notes


          This error results because the LAT application port
          that you are trying to create is already created by
          some other application. This application could very
          well be LATCP itself (LATCP's port - LATCP$MGMT_PORT -
          is used to communicate with LTDRIVER).

          The following sections describe two ways to avoid
          this "collision" between LATCP$MGMT_PORT devices and
          applications LTA devices.
                 _____________________
                 2.2.16.1  Using LATCP SET NODE/DEVICE_SEED
          By default, LTA device units that originate from the
          $ASSIGN system service to LTA0: (for example, LATCP
          management ports or forward ports) have unit numbers
          that fall in the following range (starting at the low
          boundary):

               ( MAX unit /2 - 1 ) < N < ( MAX unit )
                 where:
                   N        = Device unit number of LTA device (LTAN:)
                   MAX unit = Maximum LTA device unit number.
                              Default and absolute maximum is 9999.
                              This is a settable parameter.
                              Refer to Section 2.2.15 for more information.

          The lower boundary can be overridden by the LATCP
          command SET NODE/DEVICE_SEED[=N], where N < 9999
          (Default MAX unit). By default, N = 0.

          For example in the case where you encounter the
          following:

                   $LCP CREATE PORT LTA5001:/APPLICATION
                   %LAT-W-CMDERROR, error reported by command executor
                   -SYSTEM-F-DUPLNAM, duplicate name
                           :
                           :
                   $LCP CREATE PORT LTA5010:/APPLICATION
                   %LAT-W-CMDERROR, error reported by command executor
                   -SYSTEM-F-DUPLNAM, duplicate name

                                                             2-13

 


          LAT Version 5.4-2 Release Notes
          2.2 LAT System Manager Release Notes


          You can move the lower boundary beyond the LTA devices
          that you are intending to use as applications ports.
          For example, if you know that all LTA devices from
          LTA7000: onward are not used as application ports, you
          could then enter the following commands:

                   $LCP SET NODE/DEVICE_SEED=7000
                   $LCP CREATE PORT LTA5001:/APPLICATION
                           :
                           :
                   $LCP CREATE PORT LTA5010:/APPLICATION
                 _____________________
                 2.2.16.2  LATCP SET NODE/STATE=ON to precede
                           creating LTA application ports
          Digital strongly recommends that the LATCP command
          SET NODE/STATE=ON be executed before any LTA
          application or dedicated ports are created. In other
          words, you should conform to the format given in
          SYS$MANAGER:LAT$SYSTARTUP.TEMPLATE.

          By executing this command before any LAT application
          or dedicated ports are created, LTDRIVER is triggered
          to delete any leftover LTA devices that have a
          reference count of 0 and are explicitly marked for
          deletion (by means of the $DASSGN system service or
          the LATCP DELETE PORT command, for example).

          Consequently, every LATCP Management port (LATCP$MGMT_
          PORT) that was created by the previous LATCP
          invocation is deleted. As a result, there will be
          no "collision" with LAT application or dedicated ports
          that are to be created. You would enter the following
          commands:

                   $LCP SET NODE/STATE=ON
                   $LCP CREATE PORT LTA5001:/APPLICATION
                           :
                           :
                   $LCP CREATE PORT LTA5010:/APPLICATION


          2-14

 


                                   LAT Version 5.4-2 Release Notes
                              2.2 LAT System Manager Release Notes


          In addition to avoiding LTA device "collisions," the
          deletion of zero-referenced LTA devices minimizes
          usage of non-paged pool memory. For this reason alone,
          users are urged to follow this recommendation.

          ___________________________

   2.2.17 LATCP SET NODE/STATE=ON to save non-paged pool memory

          Digital strongly recommends that the LATCP command SET
          NODE/STATE=ON be executed before any LTA application
          or dedicated ports are created. This allows LTDRIVER
          to delete all zero-referenced LTA devices that
          are also explicitly marked for deletion. This
          minimizes non-paged pool memory usage. Please refer
          to Section 2.2.16.2 for a more detailed discussion.

          ___________________________

   2.2.18 Using Dedicated Ports

          LTDRIVER no longer creates services needed for
          dedicated ports. To use a dedicated port with an
          application service, you must create the service
          and explicitly tell LTDRIVER that the service is an
          application service to be used by a dedicated port.
          See the CREATE PORT and CREATE SERVICE commands in
          LATCP help for more information.

          ___________________________

   2.2.19 MUXserver 300 Terminal Server Problem

          The MUXserver 300 server may not accept print jobs
          from systems running pre-LAT Version 5.4-2 software.
          To avoid this problem, you should install post-Version
          1.1 MUXserver software.




                                                             2-15

 


          LAT Version 5.4-2 Release Notes
          2.2 LAT System Manager Release Notes

          ___________________________

   2.2.20 DECserver 200 Multisessions Problem

          There is a known problem using multisessions on
          DECserver 200 systems running the early BL33 software.
          Contact your Digital Customer Services support center
          to obtain a patch that will solve the problem.

          ___________________________

   2.2.21 LATCP SET SERVICE/IDENTIFICATION Command: Known
          Problem

          Using this command to set a new identification
          string for a particular service is not successful,
          even though you do not receive an error message.
          This will be fixed in a future release. However,
          Digital recommends in the interim that you specify
          /IDENTIFICATION when you enter the CREATE SERVICE
          command.

          __________________________________________________________________

   2.3    LAT Programmer Release Notes

          This section contains LAT-specific information for
          programmers.

          ___________________________

   2.3.1  Changes to QIO interface

          The following changes have been made to the QIO
          interface:

          o  LAT SETMODE and SENSEMODE QIO functions have been
             added.

          o  Forward connects and disconnects have been added.

          o  Some QIO functions have been superseded.

          o  Some Port Modifier QIO Function items no longer
             have meaning, but are they accepted by the driver
             and ignored.

          The following sections describe these changes.

          2-16

 


                                   LAT Version 5.4-2 Release Notes
                                  2.3 LAT Programmer Release Notes

          ___________________________

   2.3.2  New SETMODE and SENSEMODE QIO Functions

          These new QIO functions are documented in a separate
          ASCII file that is located in the directory for LAT
          V5.4-1 and higher:

          SYS$COMMON:[SYSHLP.EXAMPLES.LATV541]IO_USER_RELEASE_NOTES.TXT

          View or print this document for more information about
          the SENSEMODE and SETMODE functions.

          ___________________________

   2.3.3  Forward Port Connections and Disconnections

          Connections and disconnections on forward ports
          (outbound LAT) are now possible. You can get a forward
          port by assigning a channel to the LAT template device
          LTA0. You can map the port to a remote service (remote
          node and remote port are optional) by using the LAT
          SETMODE QIO function on a port and specifying the
          following items:

             LAT$_ITM_TARGET_SERVICE_NAME
             LAT$_ITM_TARGET_NODE_NAME
             LAT$_ITM_TARGET_PORT_NAME

          The IO$M_LT_CONNECT function modifier is supplied
          with the IO$_TTY_PORT QIO function to perform the LAT
          CONNECT function.

          The IO$M_LT_DISCON function modifier is supplied
          with the IO$_TTY_PORT QIO function to perform the LAT
          DISCONNECT function.

          ___________________________

   2.3.4  QIO Functions Superseded

          Two QIO functions have been replaced. Although
          existing programs that use the pre-Version 5.4-2
          functions are still supported in this release, Digital
          recommends that you modify those existing programs
          accordingly and begin using the new QIO functions
          whenever you create a new program.

                                                             2-17

 


          LAT Version 5.4-2 Release Notes
          2.3 LAT Programmer Release Notes


          The functions which have been superseded are as
          follows:

          o  Map Port Function

             Instead of using the Map Port function code and
             modifier (FUNC=#IO$_TTY_PORT!IO$M_LT_MAP_PORT) to
             associate a specific port on a terminal server with
             a local LTA device, you can now accomplish that
             task by using the LAT SETMODE QIO function on a
             port and specifying the following items:

                LAT$_ITM_TARGET_NODE_NAME
                LAT$_ITM_TARGET_PORT_NAME
                LAT$_ITM_TARGET_SERVICE_NAME

          o  Set Rating Function

             Instead of using the Set Rating function code and
             modifier, (FUNC=#IO$_TTY_PORT!IO$M_LT_RATING) to
             set a static rating for a VMS service, you can
             now accomplish that task by using the LAT SETMODE
             QIO function on a service and specifying the item,
             LAT$_ITM_RATING.

          (Both functions are documented in Section 8.4.4.1 of
          the VMS I/O User's Reference Manual: Part I.)

          ___________________________

   2.3.5  Port Modifier QIO Functions Ignored

          With Version 5.4-2 of the VMS operating system, two
          Port Modifier (IO$M_LT_MAP_PORT) QIO function items
          no longer have meaning. Although existing programs
          that use these pre-Version 5.4-2 function items will
          still run on the VMS Version 5.4-2 operating system,
          the functions will be ignored by LTDRIVER. Therefore,
          Digital recommends that you modify existing programs
          accordingly, since these two function items may not be
          supported in future releases.

          o  IO$V_LT_MAP_LNKNAM

          2-18

 


                                   LAT Version 5.4-2 Release Notes
                                  2.3 LAT Programmer Release Notes


             You can no longer map an application port onto
             a specific link because of the changes to link
             processing.

          o  IO$V_LT_MAP_NETADR

             This function item was originally implemented as
             a temporary debug item code when host-initiated
             connects were first being prototyped. Now, the
             LAT protocol calls for the node address to be
             solicited, thus overwriting whatever is specified
             with this item code.

          (Both function items are documented in Section 8.4.4.1
          of the VMS I/O User's Reference Manual: Part I.)

          ___________________________

   2.3.6  Change to Disconnect Processing

          In past versions of the VMS operating system, an LTA
          device was unavailable for a second or two after a
          disconnect. With Version 5.4-2 of the VMS operating
          system, the LTA device is available immediately.

          You can now set the DISCONNECT QIO flush flag so data
          is flushed at disconnect time to prevent sessions from
          hanging in the "Disconnecting" state. The flush flag
          is the LAT$M_FLUSH_DATA bit of the P2 argument of the
          DISCONNECT QIO.

          ___________________________

   2.3.7  LTA0 Now a Template Device

          LTA0 is now a template device. Assigning a channel to
          it returns a cloned LT device.




                                                             2-19

 


          LAT Version 5.4-2 Release Notes
          2.3 LAT Programmer Release Notes

          ___________________________

   2.3.8  QIO Completion Status

          The R0 QIO completion status now indicates only the
          success or failure of the execution of the QIO itself
          (VMS-specific checks, such as BYTLM). To check the
          completion status of the LAT function for which the
          QIO LAT function was purported, the first word of the
          IOSB must be checked.

          ___________________________

   2.3.9  LAT QIO Programming Examples

          The directory SYS$COMMON:[SYSHLP.EXAMPLES.LATV541]
          contains the following LAT QIO programming examples
          for LAT V5.4-1 and higher.

          o  TEST_APPLIC.MAR - LAT QIO to an application port

          o  TEST_DEDIC.MAR - LAT QIO to a dedicated port

          o  TEST_FORWARD.MAR - LAT QIO to a forward port (to do
             outbound connects to a service from a VMS node)

          o  TEST_SENSE.MAR - LAT QIO SENSEMODE to a port

          To compile and link a program, use COMPILE_LINK.COM,
          which is located in the same directory.












          2-20

 






          _______________________________________________________

   A      Modifications Since LAT Version 5.4-1





          __________________________________________________________________

   A.1    Problems and Solutions

          Problem:      A VAX 4000 class machine may crash with
                        an INCONSTATE bugcheck at LTDRIVER+7D68.

          Solution:     LTDRIVER was modified to toggle one
                        multicast address that could be
                        conditionally on or off. The other 2
                        multicast addresses are turned on at
                        datalink creation and remain on for the
                        life of the logical link.



          Problem:      When LAT was started, a DECnet event
                        message 0.7, "aborted service request,
                        receive error", may occur for a few
                        minutes. The condition would self
                        correct, and didn't cause any actual
                        problems.

          Solution:     By changing the manner in which LTDRIVER
                        initialized the datalink, this message
                        is no longer generated.







                                                              A-1

 


          Modifications Since LAT Version 5.4-1
          A.1 Problems and Solutions



          Problem:      An INVEXCEPTN system crash can occur at
                        location LTDRIVER+64CD.

          Solution:     An incorrect memory location reference
                        was found and corrected.



          Problem:      An INVEXCEPTN system crash can occur at
                        location LTDRIVER+6DA8.

          Solution:     The faulty code path has been found and
                        corrected.



          Problem:      An INVEXCEPTN system crash can occur at
                        location LTDRIVER+53AF.

          Solution:     There was an incorrect logic flow
                        preceeding this location. The logic has
                        been corrected.



          Problem:      A system crash, a SSRVEXCEPTN
                        bugcheck, can occur if a LAT service
                        identification string obtained
                        from SYS$ANNOUNCE is longer than 64
                        characters.

          Solution:     LATACP now truncates the translation
                        of SYS$ANNOUNCE to 64 characters
                        when creating a default service
                        identification string.





          A-2

 


                             Modifications Since LAT Version 5.4-1
                                        A.1 Problems and Solutions



          Problem:      A system crash may occur during SET
                        NODE /STATE=OFF and the subsequent link
                        shutdown processing.

          Solution:     When a LINK is prepared for destruction,
                        its reference count is increased each
                        time a message is sent and when the
                        service annoucement message is queued
                        to LATACP for final processing. Then,
                        when the ACP has finished processing the
                        final multicast message, the reference
                        count for the link is decremented.



          Problem:      A system crash with an INVEXCEPTN
                        bugcheck may occur at location
                        LTDRIVER+1ECC.

          Solution:     The pointer value is reset to correctly
                        indicate the UCB location.



          Problem:      A system crash may occur during the
                        cancellation of a solicit request
                        when the ACP is attempting to look up
                        the target node's ethernet address.
                        The crash is an INVEXCEPTN bugcheck,
                        generally at LTDRIVER+63D0, but the
                        location may vary.

          Solution:     In LTDRIVER, stop processing the
                        connect request if the request has been
                        cancelled.





                                                              A-3

 


          Modifications Since LAT Version 5.4-1
          A.1 Problems and Solutions



          Problem:      An INVEXCEPTN bugcheck can occur
                        at LTDRIVER+42AF, when the system
                        is connecting to a non-Digital LAT
                        implementation, because of a badly
                        formatted LAT message.

          Solution:     If a run message is received and a bad
                        slot identifier is included for one of
                        the slots of that message, then ignore
                        the slot.



          Problem:      An INVEXCEPTN bugcheck can occur at
                        LTDRIVER+724F.

          Solution:     There was an extraneous consistency
                        check in LTDRIVER for dedicated LTA
                        devices. This check has been removed.



          Problem:      An INVEXCEPTN bugcheck can occur at
                        LTDRIVER+20AF. This crash will occur
                        when an application program attempts to
                        do a LAT sensemode operation to an LTA
                        device, and the LTA device is associated
                        with a virtual terminal (VTA device).
                        The same crash can occur by doing the
                        LT_SENSEMODE to the VTA device.

          Solution:     The FDT routines have been changed so
                        an IO$M_LT_SENSEMODE operation against a
                        virtual device or virtual-associated
                        device will return the status SS$_
                        ILLIOFUNC (illegal I/O function code),
                        instead of causing a system crash.



          A-4

 


                             Modifications Since LAT Version 5.4-1
                                        A.1 Problems and Solutions



          Workaround:   If LAT information must be sensed
                        from an LTA device that has a virtual
                        terminal associated with it, use the
                        following technique instead:

                        1  Assign a channel to LTA0: to obtain a
                           new LTA device.

                        2  Use the channel from above for the
                           LAT sensemode operation, but also
                           include (in P4) the "entity name"
                           parameter.

                        3  In this "entity name" parameter,
                           specify the actual LTA device for
                           which you want information.

          Problem:      LATCP may give SMG$ "bad escape
                        sequence" errors.

          Solution:     LATCP now uses the $FAO !AF (format
                        string) directive for all identification
                        strings. A "." will be inserted for
                        "special" characters and it prevents
                        SMG$ from reporting bad escape sequence
                        errors.

          Problem:      Using LATCP may give "exceeded quota"
                        errors when run from an account with
                        BYTLM smaller than the SYSGEN parameter
                        MAXBUF, or a factor of this value.

          Solution:     Before issuing the LT_SENSEMODE $QIO,
                        LATCP will take the minimum of MAXBUF
                        and the user's remaining BYTCNT as the
                        size of the item list for the driver to
                        write into.



                                                              A-5

 


          Modifications Since LAT Version 5.4-1
          A.1 Problems and Solutions





          Problem:      More "invalid structure level" errors
                        can occur in LATSYM.

          Solution:     LATSYM has been changed so that if the
                        queue name is already known, then it
                        doesn't call the PSM routine to obtain
                        it.



          Problem:      When LATCP is used, it obtains an LTA
                        device for use in communicating with
                        LTDRIVER. The device chosen would be
                        a sequential number, starting at LTA1:
                        However, during system startups, LTA1
                        may have been chosen already by the
                        system manager for use with remote
                        print queues and the like. The LATCP
                        commands to create and modify the system
                        manager's LTA1: device would then get
                        "duplicate device" errors. LATCP may
                        also create LTA2:, LTA3:, and so on, as
                        necessary, compounding the problem even
                        further.














          A-6

 


                             Modifications Since LAT Version 5.4-1
                                        A.1 Problems and Solutions



          Solution:     LTDRIVER has been modified to
                        arbitrarily choose a device seed
                        for cloning of LTA0. In addition,
                        LATCP has the added SET NODE /DEVICE_
                        SEED=x qualifier, to allow setting
                        and resetting the starting value for
                        devices.

                        When LTA0: is set up, the device seed
                        for cloning is initialized to ((maximum
                        unit number / 2) - 1) instead of 0.
                        Also, SETMODE support was added to allow
                        this parameter to be tweaked.

                        This change will affect LATCP's
                        management ports, the physical devices
                        obtained with CREATE PORT/LOGICAL, and
                        the device obtained by an application
                        program from assigning a channel to
                        LTA0:.


          Problem:      It is possible for "ghost" LAT links
                        to be created. If this problem is
                        encountered, then LAT will be non-
                        functional on the system. All appears
                        to be normal from LATCP, but the service
                        ratings for the node are all 0. A "SHOW
                        LINK" command shows that no datalink
                        communcations exist. However, a SHOW
                        DEVICE command shows that a device did
                        get created by LATACP for use with the
                        Ethernet datalink layer. LAT is now
                        stalled and the system must be rebooted
                        to rectify the problem.





                                                              A-7

 


          Modifications Since LAT Version 5.4-1
          A.1 Problems and Solutions



          Solution:     When the default link is created, the
                        data structure's field is initialized to
                        the correct value.

          __________________________________________________________________

   A.2    Additional Changes

          o  LATCP will now automatically start LATACP.

             LATCP creates the detached process to run LATACP
             the first time it executes (usually at system
             startup). This permits a wider variety of startup
             paths for the LAT ACP.

          o  The name provided for the "remote port name" of
             connections initiated from a VMS LATmaster node had
             been the LTA device name in use.

             The provided remote port name is now 'PORT_
             uicnum', where uicnum is the UIC of the user who is
             attempting the outbound connection. For example, if
             the user's UIC is [305,23] then the string becomes
             "PORT_305023".) The primary reason for this change
             is to prevent the bypass of VMS breakin evasion
             running on the target system.

          o  Some of the LATCP help frames were incomplete.
             These frames have been completed.

          o  When outgoing connections were not enabled, and a
             user attempted to do a SET HOST/LAT to a service,
             the error "server mode disabled" was returned.

             This error message has been changed to read
             "Outgoing connections disabled".

          o  The maximum number of forward, outgoing connections
             from a single VMS node to another LAT node has been
             increased from 16 per remote node to 255 per remote
             node.

          A-8
