Document revision date: 30 March 2001

## OpenVMS System Manager's Manual

Previous | Contents | Index

## 25.4 Understanding InfoServer Client for OpenVMS Functions

InfoServer Client for OpenVMS software enables clients running the OpenVMS operating system to access virtual device services offered by InfoServer systems on a LAN. Software components include the following ones:

- LASTport driver
  The LASTport driver provides reliable data transfer services for its clients. It interacts with the Data Link driver and the LASTport/Disk driver as an efficient transport for a virtual device service. The LASTport driver can support other applications, such as a primitive data queueing service.
- LASTport/Disk client driver
  The LASTport/Disk client driver presents a standard block device interface to the system. The OpenVMS file system interacts with the LASTport/Disk client as if the LASTport/Disk client were a local disk driver. The LASTport/Disk client driver supports both raw and buffered interfaces.
- LASTport/Tape client driver
  The LASTport/Tape client driver enables OpenVMS clients to access and use as local devices SCSI tapes attached to InfoServer systems.
- LASTCP and LADCP utilities
  These utilities allow you to start InfoServer Client software on your system, monitor transport status, and configure and maintain InfoServer device services. Section 25.5 and Section 25.6 introduce the utilities. For complete information about the utilities, refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.

## 25.5 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

### 25.5.1 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.

### 25.5.2 LASTCP Command Summary

Table 25-2 summarizes LASTCP commands and their functions.

Table 25-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.

### 25.5.3 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

1. 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 8-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

2. If SCSNODE is defined as the null string, perform these steps:
   1. 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"

   2. Enter the following commands to write the new value to the parameter file and exit from SYSMAN:

          SYSMAN> PARAMETERS WRITE CURRENT
          SYSMAN> EXIT

   3. 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"

3. 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

4. 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

5. 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.)

### 25.5.4 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 may now execute the InfoServer client startup:

    $ @SYS$STARTUP:ESS$STARTUP DISK

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

### 25.5.5 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. Compaq 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)

Note 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.

### 25.5.6 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.

### 25.5.7 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.

### 25.5.8 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 OpenVMS System Management Utilities Reference Manual for an explanation of how to verify and change account privileges and quotas.

### 25.5.9 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.

## 25.6 Understanding LADCP Utility Functions

Use the LAD Control Program (LADCP) utility to configure and control the LASTport/Disk and LASTport/Tape protocols on OpenVMS systems. OpenVMS systems that use LASTport/Disk and LASTport/Tape services are called client systems. You can use LADCP to perform the following tasks:

- Establish bindings to services. A binding creates a new DADn: virtual disk unit or a new MADn: virtual tape unit on the local OpenVMS system.
- Remove bindings to services.

You can control service access by using a service access password. You can also write-protect services. In this case, local OpenVMS users of a DADn: or MADn: device unit receive an error if they attempt a write operation to the unit.

The protocols allow you to access storage devices that reside on an InfoServer system as though they are locally connected to your OpenVMS system. Thus, several OpenVMS client systems can share the same read-only media, eliminating the need for duplicate drives and media.

DADn: and MADn: device units are also referred to as virtual device units. They represent the local OpenVMS context for a volume that resides on a remote server. The OpenVMS driver that controls the DADn: units is called ESS$DADDRIVER. The OpenVMS driver that controls the MADn: units is called ESS$MADDRIVER.

The LASTport/Disk and LASTport/Tape protocols depend on the LASTport transport. The ESS$STARTUP.COM command procedure in SYS$STARTUP automatically loads ESS$DADDRIVER and ESS$MADDRIVER as well as ESS$LASTDRIVER, the LASTport transport driver.

Note Your site-specific startup command procedure must include a call to ESS$STARTUP.COM. If you are using DECnet software, you must place the call after the @SYS$MANAGER:STARTNET.COM command that starts DECnet software. See Section 25.5.3.

### 25.6.1 Invoking and Exiting the LADCP Utility

To invoke LADCP, enter the following command:

    $ RUN SYS$SYSTEM:ESS$LADCP
    LADCP>

You can enter LADCP commands at the LADCP> prompt.

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

    $ LADCP :== $ESS$LADCP
    $ LADCP BIND CD_DOC_00661 /NOWRITE

LADCP executes the BIND command and returns control to DCL command level.

To exit LADCP, enter EXIT or press Ctrl/Z after the LADCP> prompt.

### 25.6.2 LADCP Command Summary

Table 25-3 summarizes LADCP commands and their functions.

Table 25-3 Summary of LADCP Commands
Command | Function
--- | ---
BIND | Establishes a service binding and creates a device unit
DEALLOCATE | Terminates any active connection to a service without deleting the unit control block (UCB)
EXIT | Returns the user to DCL command level
HELP | Displays help text for LADCP commands
SHOW SERVICES | Displays services offered by InfoServer systems on the LAN
UNBIND | Terminates an established service binding

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

### 25.6.3 Making InfoServer Devices Available Automatically

You can make remote InfoServer devices available on your system each time the system boots. To do so, add to SYSTARTUP_VMS.COM a series of LADCP BIND commands. For more information about the BIND command, refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.

How to Perform This Task

1. Edit SYSTARTUP_VMS.COM and find the command that starts InfoServer Client software. For example:

       @SYS$STARTUP:ESS$STARTUP DISK TAPE

   This command starts the software with disk and tape functions.
2. Add the following command to invoke LADCP:

       $ RUN SYS$SYSTEM:ESS$LADCP

3. Immediately after this command, add BIND commands in the following format to make InfoServer compact discs or read/write disks available as virtual device units:

   `BIND [/QUALIFIER,...] service-name`

   To make tape devices available, you must specify the /TAPE qualifier in addition to any other desired qualifiers:

   `BIND/TAPE [/QUALIFIER,...] service-name`

   For service-name, specify the name of the InfoServer device service. Usually a service name is the label of the volume to which the InfoServer system is providing access. For more information about the BIND command, refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.

4. Add an EXIT command to exit LADCP.
5. Add MOUNT commands in the following format to make available as public devices the virtual device units created in the previous step:

   `MOUNT/SYSTEM/NOASSIST device-name volume-label`

   For device-name, specify the name of the device. For volume-label, specify a volume label to assign to the device. For more information about the MOUNT command, refer to the MOUNT section in the OpenVMS System Management Utilities Reference Manual.

Example

The following commands, executed in SYSTARTUP_VMS.COM, start the InfoServer Client software and make available to client systems the InfoServer device DAD$OPENVMSV72.

       .
       .
       .
    $ @SYS$STARTUP:ESS$STARTUP DISK
    $ RUN SYS$SYSTEM:ESS$LADCP
      BIND OPENVMSV72
      EXIT
    $ MOUNT/SYSTEM/NOASSIST DAD$VMS055 VMS055
       .
       .
       .

In this example, the OpenVMS Version 7.2 consolidated distribution (CONdist) compact disc loaded in a compact disc drive connected to an InfoServer system, is made available on the server as a virtual device unit and mounted as a public device.

Previous | Next | Contents | Index

| privacy and legal statement |
6017PRO_098.HTML