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

Managing InfoServer Systems

Understanding LASTCP Utility Functions

Managing the LAT Software

Understanding LADCP Utility Functions  

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

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 Starting InfoServer Client for OpenVMS Software Automatically.

Invoking and Exiting the LADCP Utility  

To invoke LADCP, enter the following command:

$ RUN SYS$SYSTEM:ESS$LADCP
LADCP> 

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

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

LADCP Command Summary 

Summary of LADCP Commands summarizes LADCP commands and their functions.

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

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-nameTo make tape devices available, you must specify the /TAPE qualifier in addition to any other desired qualifiers: BIND/TAPE [/QUALIFIER,...] service-nameFor 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-labelFor 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 HP OpenVMS DCL Dictionary.

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

Understanding LASTCP Utility Functions

Managing the LAT Software