Understanding LASTCP Utility Functions

If both a Table of Contents and Search form are not displayed in separate frames along with this one, you may wish to redisplay this book in a frameset, beginning with the first page.

HP OpenVMS System Manager's Manual, Volume 2:...

Managing InfoServer Systems

Understanding InfoServer Client for OpenVMS Functions

Understanding LADCP Utility Functions

Understanding LASTCP Utility Functions

InfoServer Client for OpenVMS software uses the LASTport protocol to communicate with InfoServer systems on an extended LAN. The protocol is implemented in the OpenVMS device driver ESS$LASTDRIVER.

The LASTport Control Program (LASTCP) utility is the management interface that allows you to control and diagnose ESS$LASTDRIVER. You can use LASTCP to perform the following tasks:

Start and stop ESS$LASTDRIVER

Display counters for circuits, lines, nodes, and ESS$LASTDRIVER

Display node characteristics

Display known clients and servers

Display LASTport status

Reset counters

The description of the LASTCP utility covers the following topics:

Invoking and exiting the utility

LASTCP command summary

Starting InfoServer Client for OpenVMS software automatically

Invoking and Exiting the LASTCP Utility

Use of LASTCP requires normal privileges, except where noted. To invoke LASTCP, enter the following command:

$ RUN SYS$SYSTEM:ESS$LASTCP
%LASTCP-I-VERSION, ESS$LASTDRIVER V1.5 is running
LASTCP>

At the LASTCP> prompt, you can enter LASTCP commands. To exit the utility, enter EXIT or press Ctrl/Z at the LASTCP> prompt.

You can also execute a single LASTCP command by using a DCL string assignment statement, as shown in the following example:

$ LASTCP :== $ESS$LASTCP
$ LASTCP SHOW CLIENTS

LASTCP executes the SHOW CLIENTS command and returns control to DCL command level.

LASTCP Command Summary

Summary of LASTCP Commands summarizes LASTCP commands and their functions.

Table 2 Summary of LASTCP Commands
Command Function

EXIT
Returns the user to DCL command level

HELP
Displays HELP text for LASTCP commands

SHOW CIRCUIT COUNTERS
Displays circuit counters

SHOW CLIENTS
Displays known clients

SHOW LINE COUNTERS
Displays line counters

SHOW NODE CHARACTERISTICS
Displays node characteristics

SHOW NODE COUNTERS
Displays node counters

SHOW SERVERS
Displays known servers

SHOW STATUS
Displays local status

SHOW TRANSPORT COUNTERS
Displays transport counters

START TRANSPORT
Starts LASTDRIVER

STOP TRANSPORT
Stops LASTDRIVER

ZERO COUNTERS
Resets counters

**Table 2** **Summary of LASTCP Commands**
Command	Function
`EXIT`	Returns the user to DCL command level
`HELP`	Displays HELP text for LASTCP commands
`SHOW CIRCUIT COUNTERS`	Displays circuit counters
`SHOW CLIENTS`	Displays known clients
`SHOW LINE COUNTERS`	Displays line counters
`SHOW NODE CHARACTERISTICS`	Displays node characteristics
`SHOW NODE COUNTERS`	Displays node counters
`SHOW SERVERS`	Displays known servers
`SHOW STATUS`	Displays local status
`SHOW TRANSPORT COUNTERS`	Displays transport counters
`START TRANSPORT`	Starts LASTDRIVER
`STOP TRANSPORT`	Stops LASTDRIVER
`ZERO COUNTERS`	Resets counters

You can abbreviate LASTCP commands to the first unique characters of the command verb. For example, you can abbreviate the command SHOW SERVERS to SH SE.

LASTCP provides a Help facility that contains information about each command and its parameters and qualifiers, as well as examples of its use. For a complete description of LASTCP commands, refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.

Starting InfoServer Client for OpenVMS Software Automatically

You must start InfoServer Client for OpenVMS software using the ESS$STARTUP command procedure. To make sure the software is started automatically each time the system reboots, execute the startup procedure from within SYSTARTUP_VMS.COM.

How to Perform This Task

Determine the value of SCSNODE, your system's node name parameter. If the parameter is defined as the null string (the default value), InfoServer Client for OpenVMS software does not start.

If you are running or plan to run DECnet for OpenVMS, SCSNODE must be defined as the system's DECnet node name. If you do not plan to run DECnet, and if the system is an OpenVMS cluster member, SCSNODE must be defined as the SCS system name, a 1- to 6-character node name that is unique in the cluster.

To determine the value of SCSNODE, enter the following commands to invoke SYSMAN and display the parameter:
```
$ RUN SYS$SYSTEM:SYSMAN
SYSMAN> PARAMETERS USE CURRENT
SYSMAN> PARAMETERS SHOW SCSNODE
```

If SCSNODE is defined as the null string, perform these steps:

Enter a command in the following format, where node-name is the system's DECnet node name or (if you do not plan to run DECnet for OpenVMS) the SCS system name: PARAMETERS SET SCSNODE "node-name"For example:
```
SYSMAN> PARAMETERS SET SCSNODE "MYNODE"
```

Enter the following commands to write the new value to the parameter file and exit from SYSMAN:
```
SYSMAN> PARAMETERS WRITE CURRENT
SYSMAN> EXIT
```

Add a line in the following format to the AUTOGEN parameter file SYS$SYSTEM:MODPARAMS.DAT to define the SCSNODE parameter: SCSNODE = "node-name"For example:

SCSNODE = "MYNODE"

The documented 6-character maximum size for SCSNODE is strictly enforced. The value of SCSNODE will be truncated by SYSBOOT if the size is set to anything over six characters in the system parameter file.

Invoke any editor to edit SYS$MANAGER:SYSTARTUP_VMS.COM and find the command that starts InfoServer Client software. For example:
```
$ @SYS$STARTUP:ESS$STARTUP DISK
```
Note that the parameters CLIENT and DISK are synonymous. If the command is preceded by the DCL comment delimiter (!), remove the delimiter. To enable tape functions, add the TAPE parameter to the command line:
```
$ @SYS$STARTUP:ESS$STARTUP DISK TAPE
```

If SYSTARTUP_VMS.COM invokes the DECnet for OpenVMS startup procedure (SYS$MANAGER:STARTNET.COM), make sure SYSTARTUP_VMS.COM executes the InfoServer Client for OpenVMS startup procedure after invoking STARTNET.COM.

The following example shows the network startup command line followed by the InfoServer Client for OpenVMS startup command line. Note that if you omit the TAPE parameter, only the disk function is started.
```
$ @SYS$MANAGER:STARTNET
.
.
.
$ @SYS$STARTUP:ESS$STARTUP DISK TAPE 
```

Optionally, edit the file SYS$STARTUP:ESS$LAST_STARTUP.DAT to specify desired startup qualifiers for the LASTport transport. (Refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.)

InfoServer Client Can Fail to Start If DECnet Is Started or Stopped

The InfoServer client software fails to start on a system where DECnet has been started and subsequently stopped. The following message will be found in the file SYS$MANAGER:ESS$STARTUP.LOG:

 
%ESS-I-NONET ESS started before DECnet.  4-MAR-2000 16:36:39.29

If the InfoServer client must be started at this point, the LASTport transport can be started with the Last Control Program using the following command:

 
$ MCR ESS$LASTCP
LASTCP> START

This command will start the transport. You can now execute the InfoServer client startup:

$ @SYS$STARTUP:ESS$STARTUP DISK

Because the transport is already started, the startup will run successfully.

Multiple Controllers Configured But Not All Attached to Media (Alpha Only)

If you have multiple Ethernet and FDDI controllers configured on your OpenVMS Alpha system, you might experience problems with the InfoServer client transport (LASTport) under either of the following conditions:

Not all of the Ethernet and FDDI controllers are connected to network cabling.

An FDDI controller is connected to the network cabling, but the FDDI ring is not functional; for example, some FDDI hardware may be powered down or broken.

Problems can range from not being able to access all the services available on the network, if you have four or more controllers configured, to a system crash.

To avoid these problems, specify only the controllers that are attached to media. HP recommends that you do this by first editing your SYS$STARTUP:ESS$LAST_STARTUP.DAT data file to specify only the controllers that are attached and then restarting your system.

With certain controller configurations, if you specify controllers that are not attached, your system might crash when you issue the following command sequence:

$ MC ESS$LASTCP
LASTCP> STOP

An example of how to edit the SYS$STARTUP:ESS$LAST_STARTUP.DAT file follows. The unedited file is shown first, followed by an edited file.

!++
! This file will be used to set the appropriate LASTCP qualifiers. The following
! LASTCP qualifiers: ALL_CONTROLLERS, CHECKSUM, TRANSMIT_QUOTA, or SLOW_MODE
! can be set by using the following statement format:
! LASTCP qualifier = 1 to enable   e.g. SLOW_MODE = 1 enables  SLOW_MODE
! LASTCP qualifier = 0 to disable  e.g. SLOW_MODE = 0 disables SLOW_MODE
! The remaining LASTCP qualifiers will require the appropriate value settings.
! DEVICE          = (list-of-devices)
! TIMEOUT 	  = n				     minimum interval in seconds
! CIRCUIT_MAXIMUM = n				maximum number of nodes		
! GROUP           = n				Group number
! NODE_NAME       = name			Node name
! CONTROLLERS     = ([{controller letter,}...]) Controller list
! TRANSMIT_QUOTA  = n				Number of transmit buffers
!--
ALL_CONTROLLERS = ON

The edited SYS$STARTUP:ESS$LAST_STARTUP.DAT file follows. This example assumes you have ESA, ETA, EXA, EZA controllers configured on your system and that only the ESA controller is attached to the Ethernet wire.

!++
! This file will be used to set the appropriate LASTCP qualifiers. The following
! LASTCP qualifiers: ALL_CONTROLLERS, CHECKSUM, TRANSMIT_QUOTA, or SLOW_MODE
! can be set by using the following statement format:
! LASTCP qualifier = 1 to enable   e.g. SLOW_MODE = 1 enables  SLOW_MODE
! LASTCP qualifier = 0 to disable  e.g. SLOW_MODE = 0 disables SLOW_MODE
! The remaining LASTCP qualifiers will require the appropriate value settings.
! DEVICE          = (list-of-devices)
! TIMEOUT 	  = n				     minimum interval in seconds
! CIRCUIT_MAXIMUM = n				maximum number of nodes		
! GROUP           = n				Group number
! NODE_NAME       = name			Node name
! CONTROLLERS     = ([{controller letter,}...]) Controller list
! TRANSMIT_QUOTA  = n				    Number of transmit buffers
!--
ALL_CONTROLLERS = OFF
DEVICE = (ESA)

The default ESS$LAST_STARTUP.DAT file is stored in SYS$COMMON:[SYS$STARTUP]. You might want to put the edited file in SYS$SPECIFIC:[SYS$STARTUP]. Otherwise, other system roots might be affected.

Startup Restrictions: PATHWORKS and RSM

If PATHWORKS or Remote System Manager (RSM) or both are installed, the InfoServer Client for OpenVMS startup must be run before the startup for PATHWORKS or RSM, or both. For example:

$ @SYS$MANAGER:STARTNET
.
.
.
$ @SYS$STARTUP:ESS$STARTUP DISK TAPE
$ @SYS$STARTUP:PCFS_STARTUP
$ @SYS$STARTUP:RSM$SERVER_STARTUP

InfoServer Client for OpenVMS software provides device drivers and control programs that are shared by both the PATHWORKS and RSM products. All InfoServer Client for OpenVMS components are prefixed with ESS$. The drivers and control programs supplied with InfoServer Client for OpenVMS software provide all necessary support for both PATHWORKS and RSM in addition to InfoServer Client support. You must execute the InfoServer Client for OpenVMS startup in the site-specific startup before executing either the PATHWORKS or RSM startup procedure.

Startup Restrictions: SYSMAN

You cannot start InfoServer Client for OpenVMS from a subprocess. Because the OpenVMS System Management utility (SYSMAN) uses subprocesses to complete its tasks on remote nodes, SYSMAN cannot be used to execute the SYS$STARTUP:ESS$STARTUP procedure.

User Account Requirements

To work with InfoServer Client for OpenVMS software, user accounts on your system must have the following privileges and quotas:

GRPNAM privilege to use the /GROUP qualifier of the LADCP command BIND; SYSNAM privilege to use the command's /SYSTEM qualifier.

At a minimum, default UAF account quotas.

Refer to the AUTHORIZE section in the HP OpenVMS System Management Utilities Reference Manual for an explanation of how to verify and change account privileges and quotas.

System Parameter MAXBUF Requirement

To use all the LASTport Control Program (LASTCP) utility's SHOW functions, you must set the value of the system parameter MAXBUF to 32000 or greater.

Understanding InfoServer Client for OpenVMS Functions

Understanding LADCP Utility Functions