![[OpenVMS documentation]](../../images/openvms_doc_banner_top.gif)
|
![[Site home]](../../images/buttons/bn_site_home_off.gif)
![[Send comments]](../../images/buttons/bn_comments_off.gif)
![[Help with this site]](../../images/buttons/bn_site_help_off.gif)
![[How to order documentation]](../../images/buttons/bn_order_docs_off.gif)
![[OpenVMS site]](../../images/buttons/bn_openvms_off.gif)
![[Compaq site]](../../images/buttons/bn_compaq_off.gif)
|
| Updated: 11 December 1998 |
|
|
|
|
| Updated: 11 December 1998 |
OpenVMS System Management Utilities Reference
Manual
| Previous | Contents | Index |
This qualifier affects your local node when outgoing connections are enabled (/CONNECTIONS=OUTGOING_ONLY or /CONNECTIONS=BOTH).
Use the SHOW NODE command for a list of the user groups (service groups) enabled for your node.
The /USER_GROUPS qualifier has several options. For each option described here, you can use two ways to specify more than one group:
The available options are as follows:
| ENABLE= group-code[,...] | Gives your node access to the listed user groups. |
| DISABLE= group-code[,...] | Prevents your node from accessing the listed groups. The listed groups were enabled previously. |
|
ENABLE=
group-code[,...],
DISABLE=group-code[,...] |
This option lets you enable certain groups and disable other groups in
one command line: gives your node access to the groups listed with the
ENABLE option and prevents your node from accessing the groups listed
with the DISABLE option. Enclose both ENABLE and DISABLE in
parentheses; for example, /GROUP=(ENABLE=(10,12),
DISABLE=(1-30)). |
The SET NODE command, which is typically executed in the site-specific LAT configuration command procedure, LAT$SYSTARTUP.COM, allows you to specify such characteristics as:
- Node name
- Node identification
- Service and user groups
- Timing of service announcements
- The maximum number of LAT sessions allowed simultaneously on the node
- The maximum number of outgoing sessions and incoming interactive sessions
Because LATCP commands change characteristics dynamically (that is, the commands take effect immediately), you can use the SET NODE command any time the LAT port driver is active. These changes remain in effect until the LAT port driver stops. To make sure the changes take effect when you start the LAT port driver again, edit LAT$SYSTARTUP.COM to include these changes. Start the LAT port driver by invoking LAT$SYSTARTUP.COM. (Refer to the OpenVMS System Manager's Manual.) The OpenVMS System Manager's Manual contains additional information about the LAT network in general and service nodes in particular.
Note
The SET NODE command must be executed first (after LTDRIVER is loaded and the LATACP is started) to ensure that other management commands execute properly thereafter.
| #1 |
|---|
LATCP> SET NODE DUKE /IDENT="NODE DUKE, SALES VMSCLUSTER"
|
This command specifies node name DUKE for your local node. The identification string "NODE DUKE, SALES VMSCLUSTER" is multicast from node DUKE.
| #2 |
|---|
LATCP> SET NODE /MULTICAST_TIMER=50 /GROUPS=(ENABLE=(1-3,8,11),DISABLE=5)
|
This command causes your local node to send multicast messages every 50 seconds to announce DUKE's services to terminal servers. The command also enables groups 1, 2, 3, 8, and 11 for access to the local node, and it disables group 5 from accessing the local node. Group 5 had been previously enabled.
| #3 |
|---|
LATCP> SET NODE /CONNECTIONS=BOTH /USER_GROUPS=(ENABLE=(24,121-127),DISABLE=0)
|
This command sets up your local node to allow both incoming and outgoing connections. Users on your local node can access those service nodes belonging to user groups 24 and 121 through 127. Users cannot access service nodes in user group 0.
| #4 |
|---|
LATCP> SET NODE /CIRCUIT_TIMER=80 /KEEPALIVE_TIMER=20 -
_LATCP> /RETRANSMIT_LIMIT=20 /CONNECTIONS=BOTH /MULTICAST_TIMER=60-
_LATCP> /GROUPS=(DISABLE=0,ENABLE=73) /SESSION_LIMIT=(OUTGOING=10,INCOMING=0)
|
This command sets many characteristics at once for node DUKE.
Associates a logical port on the local node with a remote port on a terminal server that supports a device. Alternatively, it associates a logical port on the local node with a specific service. The service can be offered by a terminal server or associated with one or more dedicated ports on a remote LAT service node.You must have OPER privilege to use this command.
SET PORT port-name
port-name
Specifies the name of the port. A port name must be in the form LTAn:, where n is a unique number from 1 to 9999.
/APPLICATION
Specifies that a port on the local node is an application port, logically associated with a port on a terminal server or a dedicated port on another LAT service node. The terminal server port supports a device (for example, a printer). If the port is used to support a printer, the print queue is established in a startup command procedure. Refer to the OpenVMS System Manager's Manual for a description of configuring remote printers on a terminal server.If you do not specify a port type, the default port type is APPLICATION.
/DEDICATED
Specifies that a logical port on your local node is dedicated to an application service. The /DEDICATED qualifier requires the /SERVICE qualifier.To set up an application service for a logical port on a LAT service node:
- Create the service by specifying the CREATE SERVICE/APPLICATION command and then define the dedicated port by specifying the CREATE PORT/DEDICATED command. You can include these commands in LAT$SYSTARTUP.COM.
- Associate the dedicated ports with the service by specifying the SET PORT/DEDICATED/SERVICE command.
- Start the application program. Within the program, allocate dedicated ports with the same name as those defined in LAT$SYSTARTUP.COM.
/LIMITED
Specifies that a logical port on your local node is limited to a service in the same way a port created using the /DEDICATED qualifier is dedicated to an application service. The difference is that ports created using the /LIMITED qualifier are under the control of the system login image (LOGINOUT.EXE) instead of an application program (a user who connects to a limited service and is assigned to a limited port receives the Username: prompt).Using the /LIMITED qualifier, you can create a limited number of ports and map them to a specific service offered by the host system. If users are logged in to all of the limited ports for the service, no more connections are allowed to that service (terminal server users receive a "service in use" message).
/LOG
/NOLOG (default)
Specifies whether LATCP displays a message confirming that the port's characteristics were modified. If you do not specify the /LOG or /NOLOG qualifier, the default is that no message will be displayed./NODE=remote-node-name
Specifies the name of a terminal server (or a remote node that supports outgoing connections) to be logically associated with the specified application port on your node. The server supports a remote device. Note that you can set up an application port on your local node and associate the port with a dedicated port on a remote LAT service node. The remote port is dedicated to an application service./PASSWORD=remote-password
Specifies the password required to access a remote service that is logically associated with the specified application port./PORT=remote-port-name
Specifies the name of the remote port on a terminal server that supports a remote device, or specifies the name of a remote port dedicated to an application service on a remote LAT service node. In either case, the remote port is logically associated with the specified application port on your local node./QUEUED
/NOQUEUED
Specifies queued or nonqueued access to the server port. A queued or nonqueued request is accepted by a terminal server if a remote port is free. If the remote port is busy and queuing is enabled on the terminal server, then the server queues the remote request. If you do not want your remote requests to be queued on the server, specify /NOQUEUED.Not specifying either the /QUEUED or /NOQUEUED qualifier results in queued access to the server port. This is the default.
/SERVICE=service-name
Specifies either of the following names:
- The name of the remote service offered at a terminal server port that will be associated with the specified application port (/APPLICATION) on the local node
- A service name for an application program being offered on a dedicated port (/DEDICATED) on a LAT service node
To specify the name of a remote service offered at a terminal server port, use the /NODE and /SERVICE qualifiers. To specify a particular port for a service, use the /NODE, /PORT, and /SERVICE qualifiers. Ask the terminal server manager for these names.
To name a service for a particular application program to be offered locally on a dedicated port, use the /DEDICATED and /SERVICE qualifiers. (The service must have been created with the CREATE SERVICE command.) Assign only one service to a dedicated port, but note that several ports can have the same service assigned.
The SET PORT command associates an application port on your local node with a port or service on a terminal server.To create a port, use one of the following methods:
- Interactively enter the CREATE PORT command.
- Run a program that creates ports.
When you associate an application port with a service on a terminal server, you allow access to any of the ports (printers) represented by that service (see Examples 1 and 2). Note that the application port must have been created with the CREATE PORT/APPLICATION command.
The SET PORT command can also associate a dedicated port on the local node with an application service offered locally. The service must already exist (see Example 3). Note that you must use the /DEDICATED and /SERVICE qualifiers.
The SET PORT command can also associate an application port on your local node with an application service associated with one or more dedicated ports on a remote LAT service node. This service is offered to users on terminal servers or on nodes that support outgoing connections (see Example 4). Note that the dedicated port must have been created with the CREATE PORT/DEDICATED command.
You can also set up the port as a limited port, using the /LIMITED qualifier.
See the examples for the SHOW PORT command for displays that reflect the changes made by the following SET PORT command examples.
| #1 |
|---|
LATCP> SET PORT LTA22: /APPLICATION /NODE=TS33EW /PORT=LN02
|
This command sets up port LTA22: as an application port to be associated with the port named LN02 on the terminal server named TS33EW. This command associates port LTA22: with a specific printer on the server. In the next example, the SET PORT command associates a port with a set of printers (designated by the service name PRINTER) on a terminal server.
| #2 |
|---|
LATCP> SET PORT LTA19: /APPLICATION /NODE=TLAT1 /SERVICE=PRINTER /QUEUED
|
This command shows how to associate a local logical port with a service (several printers) on a terminal server. The command associates the application port LTA19: with the service PRINTER on terminal server TLAT1. The service PRINTER can be associated with one or more ports on TLAT1. The /QUEUED qualifier specifies that the server offering the service PRINTER can queue the remote connection request if all ports offering the service are in use. Refer to the description of print operations in the OpenVMS System Manager's Manual for information about setting up print queues.
| #3 |
|---|
LATCP> SET PORT LTA21: /DEDICATED /SERVICE=GRAPHICS
|
This command specifies that the application port LTA21: on the local service node offers the service GRAPHICS to users on terminal servers or on nodes that support outgoing connections. GRAPHICS is a particular utility or application program.
| #4 |
|---|
LATCP> SET PORT MAIL_PORT /SERVICE=MAIL/NODE=RMNODE
|
This command associates the port whose logical name is MAIL_PORT with the dedicated service MAIL on remote node RMNODE. The port logically named MAIL_PORT was created with the CREATE PORT command (see Example 3 in the discussion of the CREATE PORT command). The logical name could also have been created with the DCL command ASSIGN or DEFINE. On node RMNODE, a port must be dedicated to the service MAIL by using the SET PORT port-name /DEDICATED/SERVICE=MAIL command.
| #5 |
|---|
$ LCP :== $LATCP
$ LCP CREATE SERVICE/LIMITED ONLY_ONE
$ (U>(LCP CREATE PORT/LIMITED LTA1234:)
$ (U>(LCP SET PORT LTA1234: /SERVICE=ONLY_ONE)
|
This series of commands, which includes the SET PORT command, creates a limited service that allows only one user to log in to the system through that service. When a user connects to service ONLY_ONE by responding to the terminal server prompt (Local>), the user is assigned port LTA1234 and then prompted for the user name. Any user who attempts to connect to the same service while LTA1234 has a user logged in receives the "service in use" message.
Dynamically changes the characteristics of a locally offered service. You must have OPER privilege to use this command.
SET SERVICE [service-name]
service-name
Specifies the service whose characteristics are to be modified. If a service name is omitted, the default service name is the name of the local node you defined by using the SET NODE command.
/APPLICATION
Sets up the service as an application service. An application service offers a specific application on the service node rather than all of the resources on the service node. Define a dedicated port for the service by using the CREATE PORT and SET PORT commands./CONNECTIONS
/NOCONNECTIONS
Specifies whether a service offered by an OpenVMS system accepts incoming connections. If you use the /NOCONNECTIONS qualifier to disable incoming connections, users cannot connect to that service and receive instead the error message "service is disabled."By default, a service accepts incoming connections (/CONNECTIONS).
/IDENTIFICATION[="identification-string"]
Describes and identifies a service. Service nodes include the identification string in service announcements. A service node announces its services at regular intervals established with the SET NODE command. Entering the LATCP command SHOW NODE or the DECserver command SHOW NODE generates a display that includes this identification string.By default, the identification string is the translation of SYS$ANNOUNCE. A service node announces its services at regular intervals established with the SET NODE command.
You cannot specify more than 64 ASCII characters in an identification string (a SYS$ANNOUNCE longer than that will be truncated to the first 64 characters). Enclose the string in quotation marks (" ").
/LIMITED
Specifies that the service is a limited service, using devices assigned the limited characteristic and associated with (mapped to) this limited service. This qualifier is used in conjunction with the SET PORT /LIMITED command (see Example 2)./LOG
/NOLOG (default)
Specifies whether or not LATCP displays a message confirming that the command was executed. If you do not specify the /LOG or /NOLOG qualifier, the default is that no message will be displayed./QUEUED
/NOQUEUED
Specifies whether a locally offered limited (/LIMITED) or application (/DEDICATED) service is allowed to have queued connections when all ports are busy (the default). If you specify /NOQUEUED, incoming connections will be rejected if all ports are busy./STATIC_RATING=rating
/NOSTATIC_RATING
Enables or disables dynamic service ratings. A dynamic service rating means that a LAT algorithm calculates the availability of a service dynamically, based on the overall level of activity of the node that offers the service and the amount of memory. When a terminal server or node requests a connection to a service that is offered on two or more service nodes, the requesting node selects the service node with the highest (most favorable) service rating. This selection process is called load balancing.The dynamic service rating, which is the default, is usually adequate for efficient load balancing on the LAT network. However, when necessary, you can use the /STATIC_RATING qualifier to disable dynamic service ratings so that you can specify a static (fixed) rating. That static rating value does not change until the dynamic service rating is reenabled.
Use the static rating to direct users away from or toward your node temporarily. Static ratings range from 0 to 255. Specify a low value to make the local service node less likely to be used; specify a high value to make the local service node more likely to be used.
If you do not specify either the /STATIC_RATING or /NOSTATIC_RATING qualifier, the default is that the LAT software uses the dynamic service rating.
Limited and application services do not rely exclusively on the dynamically calculated service rating. Instead, they use a portion of the dynamic rating based on how many ports are available for the service. For example, if a limited service has 50 percent of its ports available, the dynamic service rating will be scaled, halved, and then added to 105. When ports are available, the rating will always be above the value 105.
When all ports for a limited or application service are in use, the rating will be based on the scaled dynamic rating and the number of free queue slots on the local node. The rating will always be less then 90.
This rating procedure for limited and application services follows the terminal server rating algorithm for services and available ports that the service offers, while at the same time taking into account the availability of the node (which is the factor used to calculate the dynamic rating).
If your system is licensed for a specific number of units (where only a fixed number of users can log in to the system regardless of how the login limit is set), then all dynamic ratings become 0 when all OpenVMS license units have been consumed. (This forces all node service ratings to the lowest possible value when logins are not possible because all OpenVMS license units have been consumed.)
Note that the LAT software transmits a service announcement message when a user logs in to or out of the system. This allows the system to more quickly provide information about service rating changes that result from a login or logout operation.
The SET SERVICE command dynamically changes the characteristics of a service that you created previously (by interactively entering the CREATE SERVICE command or by running a program that created services).
| #1 |
|---|
LATCP> SET SERVICE SALES /IDENT="SALES FORCE TIMESHARING SERVICES"
|
This command specifies a new identification string, "SALES FORCE TIMESHARING SERVICES", for the service SALES. This string is announced with the service SALES in the multicast messages sent by a service node.
| #2 |
|---|
$ LCP :== $LATCP
$ LCP SET SERVICE/LIMITED ONLY_ONE
$ LCP CREATE PORT/LIMITED LTA1234:
$ LCP SET PORT LTA1234: /SERVICE=ONLY_ONE
|
This series of commands changes an existing service to a limited service that allows only one user to log in to the system through that service. When a user connects to service ONLY_ONE by responding to the terminal server prompt (Local>), the user is assigned port LTA1234 and then prompted for the user name. Any user who attempts to connect to the same service while LTA1234 has a user logged in receives the "service in use" message.
Displays the status and LAT characteristics of links on the local node.
SHOW LINK [link-name]
link-name
Specifies the name for a LAT data link. A link name can have up to 16 ASCII characters.If you do not specify a link name, LATCP displays information about all links currently defined for the node.
/BRIEF
Displays the device name and state of the link. This is the default display./COUNTERS
Displays the device counters kept for the link. The numbers displayed represent the values recorded since the last time the counters were reset (when the node first started or when the ZERO COUNTERS command was used).Do not use the /BRIEF or /FULL qualifier with this qualifier.
The following table lists and describes counters common to both CSMA/CD (carrier sense, multiple access with collision detect) and FDDI (Fiber Distributed Data Interface) links.
Counter Description Messages received The total number of messages received over the link. Multicast messages received The total number of multicast messages received over the link. Bytes received The total number of bytes of information received over the link. Multicast bytes received The total number of multicast bytes received over the link. System buffer unavailable The total number of times no system buffer was available for an incoming frame. Unrecognized destination The total number of times a frame was discarded because there was no portal with the protocol enabled. This count includes frames received for the physical address only. Messages sent The total number of messages sent over the link. Multicast messages sent The total number of multicast messages sent over the link. Bytes sent The total number of bytes of information sent over the link. Multicast bytes sent The total number of bytes of multicast messages sent over the link. User buffer unavailable The total number of times no user buffer was available for an incoming frame that passed all filtering. Data overrun The total number of bytes lost on the link's device because the local node's input buffers were full. A nonzero value can indicate noisy lines, a bad device, a busy or poorly tuned system (not enough resources allocated), or a hardware problem with another device on the LAN connection. The following table lists and describes receive errors common to both CSMA/CD and FDDI links. These errors, which are included in the display generated by the SHOW LINK/COUNTERS command, are represented by flags that indicate the error has occurred.
Flag Description Block check error CRC error in packets received. Framing error Received frames ended incorrectly. Frame too long Frames received longer than length limits. Frame status error CRC error on ring noticed by local FDDI station (FDDI only). Frame length error Frame length too short (FDDI only). The following table lists and describes transmit errors common to both CSMA/CD and FDDI links. These errors, which are included in the display generated by the SHOW LINK/COUNTERS command, are represented by flags that indicate the error has occurred.
Flag Description Excessive collisions Frames failed to transmit because the collision limit of 16 was reached (CSMA/CD only). Carrier check failures Indicates transceiver problem or short circuit in cable. Short circuit Short circuit in cable. Open circuit Open circuit in cable. Frame too long Frames too long. Indicates a transmission problem in one of the portals using the link. Remote failure to defer A remote station failed to defer frames transmission. Could indicate a misconfigured network. Transmit underrun Transmission of a frame was too slow. Indicates a hardware controller error. Transmit failure Frames failed to transmit.
Previous Next Contents Index
![[OpenVMS documentation]](../../images/openvms_doc_banner_bottom.gif)
Copyright © Compaq Computer Corporation 1998. All rights reserved.
Legal6048PRO_036.HTML