skip book previous and next navigation links
go up to top of book: HP OpenVMS System Manager's Manual, Volume 2:... HP OpenVMS System Manager's Manual, Volume 2:...
go to beginning of chapter: Managing the LAT Software Managing the LAT Software
go to previous page: Understanding the LATCP Utility Understanding the LATCP Utility
go to next page: Customizing LAT CharacteristicsCustomizing LAT Characteristics
end of book navigation links

Starting Up the LAT Protocol  



As system manager, you start up the LAT protocol and configure your node as a service node by executing the command procedure SYS$STARTUP:LAT$STARTUP. This procedure executes the following two procedures:
  1. LAT$CONFIG.COM, to load the LAT terminal driver LTDRIVER and create the LATACP process
  2. LAT$SYSTARTUP.COM, to execute LATCP commands that define LAT characteristics

How to Perform This Task

To make sure the LAT protocol is started each time the system boots, add a command to execute this procedure in the general-purpose, site-specific startup command procedure, described as follows. (See the HP OpenVMS System Manager's Manual, Volume 1: Essentials for more detailed information about this command procedure, including the file specification used to identify it in your operating system.)

To set up your node as a LAT service node and start the LAT protocol software on your system each time the system boots, edit the general-purpose, site-specific startup command procedure to add the following line:

$ @SYS$STARTUP:LAT$STARTUP.COM
When the general-purpose, site-specific startup command procedure executes this command, it invokes LAT$STARTUP.COM, which in turn invokes the LAT$CONFIG and LAT$SYSTARTUP command procedures.

You can append any of the following arguments to the command line that invokes LAT$STARTUP to specify unique LAT characteristics for your node. The procedure will pass these arguments to LAT$SYSTARTUP.COM to define the LAT characteristics you specify.

$ @SYS$STARTUP:LAT$STARTUP "P1" "P2" "P3" "P4" "P5"
HP recommends that you modify LAT$SYSTARTUP.COM directly, rather than passing parameters in P1 through P5. However, if you choose to use P1 through P5, the arguments have the following meanings:

Argument Format Meaning
P1
Service-name
Name of the service. For clustered service nodes, use the cluster alias as the service name. For independent service nodes, use the DECnet node name. LAT$SYSTARTUP.COM uses the argument P1 to assign a service name to the node (with the LATCP CREATE SERVICE command).
P2--P4
Any of the following names:
LAT$SYSTARTUP.COM uses the arguments to assign LAT node characteristics (with the LATCP SET NODE command).

/IDENTIFICATION= "string"
Description of the node and its services that is advertised over the local area network (LAN). The default is the string defined by the logical name SYS$ANNOUNCE. Make sure you include five sets of quotation marks around the identification string. For example:
"/IDENTIFICATION=" - 
"""""Official system center"""""


/GROUPS=(ENABLE=group-list )
Terminal server groups qualified to establish connections with the service node. By default, group 0 is enabled.

/GROUPS=(DISABLE=group-list )
Removes previously enabled terminal server groups. If you are specifying the preceding qualifier to enable groups, you can combine the qualifiers into one, as shown in the example that follows this table.
P5
Any qualifiers valid with the CREATE SERVICE command
LAT$SYSTARTUP.COM uses this argument to assign service characteristics with the LATCP CREATE SERVICE command. You can specify the /IDENTIFICATION, /LOG, and /STATIC_RATING qualifiers. Specify several qualifiers as shown in the following example:
"/IDENTIFICATION=" - 
"""""Official system node""""" - 
/STATIC_RATING=250"


Note that if you want to do any of the following LAT network tasks, you must edit LAT$SYSTARTUP.COM (described in Customizing LAT Characteristics):

For a full description of LATCP commands and qualifiers, refer to the HP OpenVMS System Management Utilities Reference Manual.

Example

The following command creates the service OFFICE on the service node MOE, which is part of the OFFICE cluster (refer to Components of a LAT Network):

$ @SYS$STARTUP:LAT$STARTUP OFFICE

go to previous page: Understanding the LATCP Utility Understanding the LATCP Utility
go to next page: Customizing LAT CharacteristicsCustomizing LAT Characteristics