LAT Version 5.4-3 Installation and
Release Notes
May 1991
This document contains information about installing
and using LAT Version 5.4-3 software on the VMS
operating system.
Operating System Version: VMS Version 5.4-3 or
higher
Software Version: LAT Version 5.4-3
digital equipment corporation
maynard, massachusetts
________________________
May 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 Ethernim 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-3
SOFTWARE 1-1
_________________________________________________
1.2 INSTALLING THE LAT VERSION 5.4-3
SOFTWARE 1-5
_________________________________________________
1.3 POSTINSTALLATION PROCEDURES 1-10
_________________________________________________
1.4 REINSTALLING LTDRIVER 1-12
_______________________________________________________
CHAPTER 2 LAT VERSION 5.4-3 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
v
Contents
2.2.3 LATCP Qualifiers Ignored (Offering
Services Over Specific Links
Removed) 2-6
2.2.4 Additional LATCP Commands and
Qualifiers Ignored 2-6
2.2.5 New LATCP Display Commands 2-7
2.2.6 Additional 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 Installing and Setting Privileges
for 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 Managing the LATACP Database
Size 2-12
2.2.15 Setting LTA MAX Units through
LATCP 2-13
2.2.16 Creating LAT Application
Ports 2-13
2.2.16.1 Using LATCP SET
NODE/DEVICE_SEED 2-14
2.2.16.2 LATCP SET NODE/STATE=ON
to Precede Creating LTA
Application Ports 2-15
2.2.17 Saving Non-Paged Pool Memory with
LATCP SET NODE/STATE=ON 2-16
2.2.18 Using Dedicated Ports 2-16
2.2.19 LAT Support for FDDI
Controller 2-16
vi
Contents
2.2.20 MUXserver 300 Terminal Server
Problem 2-17
2.2.21 DECserver 200 Multisessions
Problem 2-17
2.2.22 Ethernim Top Talker Problem 2-17
2.2.23 LAT Startup with Xterminals 2-17
_________________________________________________
2.3 LAT PROGRAMMER RELEASE NOTES 2-18
2.3.1 Changes to QIO interface 2-18
2.3.2 New SETMODE and SENSEMODE QIO
Functions 2-18
2.3.3 Forward Port Connections and
Disconnections 2-19
2.3.4 QIO Functions Superseded 2-19
2.3.5 Port Modifier QIO Functions
Ignored 2-20
2.3.6 Change to Disconnect
Processing 2-21
2.3.7 LTA0 Now a Template Device 2-21
2.3.8 QIO Completion Status 2-21
2.3.9 LAT QIO Programming
Examples 2-22
_______________________________________________________
APPENDIX A SAMPLE LTLOAD.COM AND LAT$SYSTARTUP.COM
FILES A-1
_________________________________________________
A.1 SAMPLE LTLOAD.COM FILE A-1
_________________________________________________
A.2 SAMPLE LAT$SYSTARTUP.COM FILE A-2
vii
Contents
_______________________________________________________
APPENDIX B MODIFICATIONS SINCE LAT VERSION
5.4-2 B-1
_________________________________________________
B.1 PROBLEMS AND SOLUTIONS B-1
viii
_______________________________________________________
Preface
This document contains information about installing
and using LAT Version 5.4-3 software on Version 5.4-3
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-3 software.
__________________________________________________________________
1.1 Before Installing the LAT Version 5.4-3 Software
IMPORTANT: You should install LAT Version 5.4-3 only
after you have upgraded your system to VMS Version
5.4-3.
If you are presently running LAT Version 5.4-1 or
5.4-2 software and have upgraded your system to VMS
Version 5.4-3, Digital recommends that you install
the LAT Version 5.4-3 software that is included as an
optional saveset in your VMS Version 5.4-3 kit. If you
choose not to install the LAT Version 5.4-3 software,
your system will continue running the version of LAT
software that was on your system before you upgraded
to VMS Version V5.4-3.
LAT Version 5.4-3 does not install the file
SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COM if a version
of that file already exists in the same directory.
Installation of the LAT Version 5.4-3 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.
1-1
LAT Installation Procedures
1.1 Before Installing the LAT Version 5.4-3 Software
2 You can install LAT Version 5.4-3 software only
on Version 5.4-3 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-3 LTDRIVER setup.
Therefore, Digital recommends that you back up your
VMS Version 5.4-3 system disk before you install
the LAT Version 5.4-3 software in case you want to
restore the disk fully to its pre-LAT Version 5.4-3
state.
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-3 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:
1-2
LAT Installation Procedures
1.1 Before Installing the LAT Version 5.4-3 Software
_______________________________________________________
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]
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]
_______________________________________________________
1-3
LAT Installation Procedures
1.1 Before Installing the LAT Version 5.4-3 Software
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.
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-3 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-3 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-3 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-3 software.
This will ensure that you can successfully
reinstall your pre-LAT Version 5.4-3 LTDRIVER
(as described in Section 1.4 if you choose to do
so at a later date.
1-4
LAT Installation Procedures
1.1 Before Installing the LAT Version 5.4-3 Software
6 During the LAT Version 5.4-3 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-3 Software
Install the LAT Version 5.4-3 software as follows:
1 Log in to a privileged account and invoke VMSINSTAL
by entering the following command:
$ @SYS$UPDATE:VMSINSTAL LATU3054 ddcu:
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
1-5
LAT Installation Procedures
1.2 Installing the LAT Version 5.4-3 Software
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-3 ...
%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...
4 The procedure creates the following LAT Version
5.4-3 files:
_______________________________________________________
Destination
in
File_Name_________________SYS$COMMON:____Function______
LATU3054.RELEASE_NOTES [SYSHLP] LAT Version
(168 blocks) 5.4-3 release
notes
LTDRIVER.EXE [SYS$LDR] LAT driver
(99 blocks)
LATACP.EXE [SYSEXE] ACP for LAT
(109 blocks) driver
LAT$SHR.EXE [SYSLIB] Shareable
(174 blocks) image for
LAT Control
Program
(LATCP)
1-6
LAT Installation Procedures
1.2 Installing the LAT Version 5.4-3 Software
_______________________________________________________
Destination
in
File_Name_________________SYS$COMMON:____Function______
LATCP.EXE [SYSEXE] LAT Control
(10 blocks) Program
LATSYM.EXE [SYSEXE] LAT printer
(105 blocks) symbiont
LTPAD.EXE [SYSEXE] SET HOST/LAT
(42 blocks)
LATCP$HELP.HLB [SYSHLP] LATCP help
(203 blocks) library
LTLOAD.COM [SYSMGR] LAT site-
(3 blocks) independent
placeholder
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
1-7
LAT Installation Procedures
1.2 Installing the LAT Version 5.4-3 Software
_______________________________________________________
Destination
in
File_Name_________________SYS$COMMON:____Function______
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
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:
1-8
LAT Installation Procedures
1.2 Installing the LAT Version 5.4-3 Software
_______________________________________________________
Destination
in
File_Name_________________SYS$COMMON:____Function______
XTDRIVER.EXE [SYS$LDR] XTERMINAL
(14 blocks) driver
DECW$TRANSPORT_LAT.EXE [SYSLIB] X Transport
(14 blocks)
DECW$DWT_DECNET.EXE [SYSEXE] DECnet
(21 blocks) component
DECW$DWT_FONT_DAEMON.EXE [SYSEXE] Font daemon
(25 blocks)
DECW$STARTXTERMINAL.COM [SYSMGR] XTERMINAL
(14 blocks) startup
REINSTALL_XTERMINAL.COM [SYSUPD] XTERMINAL re-
(7 blocks) installation
_______________________________________________________
1-9
LAT Installation Procedures
1.2 Installing the LAT Version 5.4-3 Software
5 The following display signals the completion of the
LAT Version 5.4-3 installation procedure:
Installation of LAT V5.4-3 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-3 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-3 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-3 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-3 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). Appendix A
contains examples of an original LTLOAD.COM file
and how it should appear in LAT$SYSTARTUP.COM.
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-3 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-3 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-11
LAT Installation Procedures
1.4 Reinstalling LTDRIVER
__________________________________________________________________
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-3 software (or LAT Versions 5.4-1
or 5.4-2).
NOTE: This reinstallation procedure does not return
your system exactly to its pre-LAT Version 5.4-3
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-3 software. You can then
use the Backup Utility to restore the disk fully to
its pre-LAT Version 5.4-3 state.
1 During the LAT Version 5.4-3 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-3 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-3 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-3
installation.
1-13
_______________________________________________________
2 LAT Version 5.4-3 Release Notes
This chapter includes LAT Version 5.4-3 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-3 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-3 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-3 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-3 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-3 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.
NOTE: Note that The following sections contain examples
of how to invoke certain LATCP commands. Those
commands require that you first define the DCL symbol
LCP by entering the following:
$ LCP :== $LATCP
___________________________
2.2.1 LATCP Commands Replaced
Several LATCP commands have been replaced. Although
existing command procedures that use the pre-Version
5.4-3 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-3 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-3 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-3 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-3 Release Notes
2.2 LAT System Manager Release Notes
___________________________
2.2.3 LATCP Qualifiers Ignored (Offering Services Over
Specific Links Removed)
With LAT Version 5.4-3, 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 LAT Version 5.4-3 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 Additional 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-3 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 Additional New LATCP Commands and Qualifiers
With LAT Version 5.4-3, 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-3 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-3 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 Installing and Setting Privileges for LATCP
Do NOT use the VMS Install Utility to install LATCP.
With LAT Version 5.4-3, 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-3 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-3 Release Notes
2.2 LAT System Manager Release Notes
___________________________
2.2.12 LATCP Enabling of Group Codes
In LAT Version 5.4-3, there are two types of group
codes that can be selectively enabled or disabled
using 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 using LATCP, in LAT Version
5.4-3, 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-3 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 Managing the LATACP Database Size
LATACP maintains a database for nodes and services.
The nodes and services may be those that are
multicasted from remote LAT nodes, or they could
consist of the local node and one or more local
services that you create on your own system. The
maximum size of this database is dependent on the
SYSGEN parameter CTLPAGES.
After you enter a LATCP command, you might get the
following response:
%LAT-W-CMDERROR, error reported by command executor
-LAT-F-ACPNOCTL, insufficient resources - ACP CTL/P1 space limit reached
If so, this signifies that the database size has
reached the CTLPAGES limit. You can correct the
situation in one of three ways:
1 Reduce the size of the database by setting the node
limit. For example, you can reduce the absolute
number of nodes that are stored in the database by
entering the following command:
$ LCP SET NODE/NODE_LIMIT=10
Refer to the LATCP Help or the revised VMS LAT
Control Program (LATCP) Manual for additional
information about this command.
2 Reduce the size of the database by reducing the
user group codes that a user can do an outbound
connect to (using SET HOST/LAT).
2-12
LAT Version 5.4-3 Release Notes
2.2 LAT System Manager Release Notes
For example, suppose that you have user groups
0,45,77-88 enabled (enter $ LCP SHOW NODE, and look
at the "User Groups" field for user group codes
enabled on your system). You can then enter the
following command if you decide that user groups 0,
78-88 are not required for outbound connects:
$ LCP SET NODE /USER_GROUPS=DISABLE=(0,78-88)
See Section 2.2.12 for more information about user
group codes.
3 Extend the size of the database by increasing the
size of CTLPAGES using SYSGEN (and then rebooting
the system). As a general rule, note that every
unit of CTLPAGES that you increase is roughly
equivalent to six additional nodes or services that
will be stored in the database.
___________________________
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-13
LAT Version 5.4-3 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-14
LAT Version 5.4-3 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-15
LAT Version 5.4-3 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 Saving Non-Paged Pool Memory with LATCP SET
NODE/STATE=ON
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 more detailed information.
___________________________
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 LAT Support for FDDI Controller
This version of the LAT software supports the FDDI
controller. For example, to create a link on the FDDI
controller, enter the following command:
$ LCP CREATE LINK/DEVICE=FXA0:/STATE=ON FDDI$LINK
(For more information on creating links, refer to the
VMS LAT Control Program (LATCP) Manual.)
2-16
LAT Version 5.4-3 Release Notes
2.2 LAT System Manager Release Notes
___________________________
2.2.20 MUXserver 300 Terminal Server Problem
The MUXserver 300 server may not accept print jobs
from systems running pre-LAT Version 5.4-3 software.
To avoid this problem, you should install post-Version
1.1 MUXserver software.
___________________________
2.2.21 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.22 Ethernim Top Talker Problem
If you enter the Ethernim Top Talker command on
a system running the LAT Version 5.4-3 software,
the system may receive erroneous LAT messages not
intended for that system. The system will then send
a Stop message to the remote node that generated the
message, which, in turn, will cause the LAT software
to terminate the LAT circuit between that remote node
and some other remote node (the node that the message
was originally intended for).
___________________________
2.2.23 LAT Startup with Xterminals
If your system has Xterminal connections, do
not submit SYS$STARTUP:LAT$STARTUP.COM or the
corresponding SYS$MANAGER:LTLOAD.COM in a batch queue.
Instead, execute the LAT startup procedure in-line
from within your site-specific startup procedure.
2-17
LAT Version 5.4-3 Release Notes
2.3 LAT Programmer Release Notes
__________________________________________________________________
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.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-18
LAT Version 5.4-3 Release Notes
2.3 LAT Programmer Release Notes
___________________________
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-3
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.
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
2-19
LAT Version 5.4-3 Release Notes
2.3 LAT Programmer Release Notes
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 LAT Version 5.4-3, 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-3 function items will still run on LAT Version
5.4-3, 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
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
2-20
LAT Version 5.4-3 Release Notes
2.3 LAT Programmer Release Notes
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 LAT Version 5.4-3, 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.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-21
LAT Version 5.4-3 Release Notes
2.3 LAT Programmer Release Notes
___________________________
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-22
_______________________________________________________
A Sample LTLOAD.COM and LAT$SYSTARTUP.COM Files
The following examples illustrate how an original
LTLOAD.COM file should appear in LAT$SYSTARTUP.COM.
Note that both LTLOAD.COM and LAT$SYSTARTUP.COM are in
SYS$COMMON:[SYSMGR].
__________________________________________________________________
A.1 Sample LTLOAD.COM File
The following is an example of an LTLOAD.COM file:
$ ! Copyright (c) 1987 Digital Equipment Corporation. All rights reserved.
$ ! This command procedure starts up the LAT protocol
$ ! and configures applications devices for remote printer use.
$
$ RUN SYS$SYSTEM:SYSGEN
CONNECT LTA0/NOADAPTER
$
$! Invoke LATCP
$
$LCP := $LATCP
!
! The following commands will set up LAT service with the default name
! SYS$NODE and default ident SYS$ANNOUNCE. The LAT service name will
! will default to the node name SYS$NODE unless you specify the name as
! a the first parameter in the command line. Additional node characteristics
! such as group codes can also be supplied as parameters.
!
$LCP SET NODE /IDENT /MULTI=30 /ENAB=(12,40,43,73) /DISAB=0 /NOLOG
$LCP CREATE SERVICE /NOLOG
$IF P1 .NES. "" THEN $LCP CREATE SERVICE 'P1' /IDENT /NOLOG
$!
$RUN SYS$SYSTEM:LATCP
!
! Set up the applications devices that will support remote printer
A-1
Sample LTLOAD.COM and LAT$SYSTARTUP.COM Files
A.1 Sample LTLOAD.COM File
! access.
!
! Create the devices.
!
!CREATE PORT LTA1: /NOLOG
!CREATE PORT LTA2: /NOLOG
!
CREATE PORT LTA1: /NOLOG
CREATE PORT LTA20: /NOLOG
! Maps applications port(s) to a specific port(s) on the terminal
! server
!
!SET PORT LTA1: /APPLICATION /NODE=SERVER_1 /PORT=LN03
!SET PORT LTA2: /APPLICATION /NODE=SERVER-2 /PORT=PORT_3
!
SET PORT LTA1: /APPLICATION/NODE=TERM_SERVER_1 /PORT=PORT_6
SET PORT LTA20: /APPLICATION/NODE=TERM_SERVER_2 /PORT=PORT_6
! Start LAT Service
!
START NODE
EXIT
__________________________________________________________________
A.2 Sample LAT$SYSTARTUP.COM File
The following example illustrates how the
LAT$SYSTARTUP.COM file would appear after you have
moved the LAT node-specific commands in LTLOAD.COM
(illustrated previously in Section A.1).
A-2
Sample LTLOAD.COM and LAT$SYSTARTUP.COM Files
A.2 Sample LAT$SYSTARTUP.COM File
$! Copyright (c) 1990 Digital Equipment Corporation. All rights reserved.
$!
$! LAT$SYSTARTUP.COM -- LAT Startup Commands Specific to Site
$!
$! Use this command procedure to customize the LAT characteristics for
$! the local node. These commands, which should serve as examples,
$! will set up a LAT service name SYS$NODE and default identification
$! SYS$ANNOUNCE. The LAT service name and identification will default
$! to SYS$NODE and SYS$ANNOUNCE unless you specify a service name and
$! identification as arguments to the command line that invokes
$! LAT$STARTUP.COM:
$! $ @SYS$STARTUP:LAT$STARTUP
$!
$! You can specify other node and service characteristics (such as group
$! codes) as arguments to this command line, as shown below.
$!
$! Argument Function
$! --------- --------
$!
$! P1 Name of the service to be created. If not supplied, a
$! service will be created with the same name as the node.
$!
$! P2,P3,P4 Parameters and qualifiers to the SET NODE command.
$!
$! P5 Parameters and qualifiers to the SET SERVICE command.
$! P5 is only used if P1 is specified. More than one
$! argument may be supplied by enclosing the string in
$! quotes.
$!
$! Example: $ @SYS$STARTUP:LAT$STARTUP HAWK "/IDENTIFICATION=" -
$! """""Development node"""""
$!
$! Please review and edit this file for possible additions and deletions
$! that you wish to make. Future software updates will not overwrite the
$! changes made to this file.
$!
$ required_privileges = "OPER"
$ prev_privs = f$setprv(required_privileges)
$ if .not. f$privilege(required_privileges) then goto no_privileges
$ lcp := $latcp
A-3
Sample LTLOAD.COM and LAT$SYSTARTUP.COM Files
A.2 Sample LAT$SYSTARTUP.COM File
$!
$! --------------------- Modify Node Characteristics ------------------------
$!
$ lcp set node 'p2' 'p3' 'p4'
$!
$! Some examples:
$!
$! ** Allow incoming connections only
$!
$! lcp set node /connections=incoming /groups=(enable=(12,40,43,73),disable=0)
$! lcp set node /connections=incoming /groups=enable=(0-255)
$!
$ LCP SET NODE /CONNECTIONS=INCOMING /GROUPS=(ENABLE=(12,40,43,73),DISABLE=0)
$!
$! ** Allow outgoing connections only
$!
$! lcp set node /connections=outgoing /user_groups=enable=(24,121-127)
$! lcp set node /connections=outgoing /user_groups=(enable=0-255) /node_limit=50
$!
$! ** Enable incoming and outgoing connections
$!
$! lcp set node /connections=both /group=enable=(43,73) /user=enable=(44,56)
$! lcp set node /connections=both /group=enable=(0-255) /user=enable=(0-255)
$!
$!
$! -------------------- Modify Service Characteristics ----------------------
$!
$ if p1 .eqs. ""
$ then
$ lcp create service
$ else
$ lcp create service 'p1' 'p5'
$ endif
$! ------------------------- Start LAT Protocol -----------------------------
$!
$ lcp set node /state=on
$!
$!
$! ------------------------- Create and Map Ports ---------------------------
$!
A-4
Sample LTLOAD.COM and LAT$SYSTARTUP.COM Files
A.2 Sample LAT$SYSTARTUP.COM File
$! Some examples:
$!
$! lcp create port lta101: /dedicated
$! lcp create port lta102: /application
$! lcp create port lta103: /application
$! lcp create port /nolog/logical=(name=ln03$mgmt, table=system, mode=executive)
$
$ LCP CREATE PORT LTA1: /NOLOG
$ LCP CREATE PORT LTA20: /NOLOG
$
$! lcp set port lta101: /dedicated /service=graphics
$! lcp set port lta102: /node=server_1 /port=port_1
$! lcp set port lta103: /node=server_2 /service=laser
$! lcp set port ln03$mgmt: /node=server_3 /service=ln03_printers
$!
$ LCP SET PORT LTA1: /APPLICATION/NODE=TERM_SERVER_1 /PORT=PORT_6
$ LCP SET PORT LTA20: /APPLICATION/NODE=TERM_SERVER_2 /PORT=PORT_6
$!
$exit:
$ prev_privs = f$setprv(prev_privs)
$ exit
$!
$no_privileges:
$ write sys$output "Insufficient privileges to execute LATCP commands."
$ write sys$output "Requires ",required_privileges," privileges."
$ goto exit
A-5
_______________________________________________________
B Modifications Since LAT Version 5.4-2
__________________________________________________________________
B.1 Problems and Solutions
Problem: Host-initiated connects triggered by
writing to a LTA application device
without an explicit $QIO Connect request
would, in some instances, cause a system
crash on a Port Cancel Event.
Solution: LTDRIVER was modified so that a Port
Cancel Event is correctly processed.
Problem: The LATCP command, LCP SET SERVICE
/IDENTIFICATION, did not actually
set a new identification string for a
particular service successfully, even
though you did not receive an error
message.
Solution: LATCP was modified so that this command
will now work correctly.
B-1
Modifications Since LAT Version 5.4-2
B.1 Problems and Solutions
Problem: The LATCP command, LCP CREATE SERVICE
/IDENTIFICATION, did not actually set
the identification of service unless
the logical SYS$ANNOUNCE was already
defined.
Solution: LATCP was modified so that this command
will now work correctly.
B-2