Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

service-name

example

/ASYNCHRONOUS

/GROUP

/PASSWORD

/SYSTEM

/WRITE_ENABLE

LADCP BIND — VMS 5.5-2H4

        Format: BIND service-name/qualifier

The BIND command creates a device associated with a virtual disk and
creates a logical name that points to the device. The BIND command
also displays the logical name that it created.

Additional information available:

service-nameexample

/ASYNCHRONOUS/GROUP/PASSWORD/SYSTEM/WRITE_ENABLE

service-name

The name associated with the virtual disk.


/ASYNCHRONOUS

        Format: /[NO]ANSYNCHRONOUS

Specifies whether write requests complete immediately.
If /ASYNCHROUNOUS is specified, write requests complete
immediately.  If /NOASYNCHRONOUS is specified, requests do not
complete until all network I/O to the physical disk is completed.

The default value is /NOASYNCHRONOUS.

/GROUP

        Format: /GROUP

Places the logical name created by the BIND command in the group
logical name table.

This qualifier requires GRPNAM privilege.

/PASSWORD

        Format: /PASSWORD="password-string"

Specifies a password associated with the
virtual disk. The password can be up to 39
alphanumeric ASCII characters in length.


/SYSTEM

        Format: /SYSTEM

Places the logical name created by the BIND command in the system
logical name table.

This qualifier requires SYSNAM privilege.

/WRITE_ENABLE

        Format: /[NO]WRITE_ENABLE

Specifies whether the service is to be write enabled.
The default value of /NOWRITE_ENABLED means that the service
is read-only.

The qualifier is negatable.

example

$ LADCP BIND CD_DOC_00661

This command creates a read-only logical disk pointed to by
the logical name DAD$CD_DOC_00661.

$ LADCP BIND VIRTUAL_DISK/WRITE/NOASYNC

This command creates a device for the service name
VIRTUAL_DISK and creates the logical name DAD$VIRTUAL_DISK,
which points to this device.  The command also specifies that
all data must be written to the remote physical device
before the write request completes.

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026