ESS$INFOSERVER is the user interface for the LASTport/Disk
server implemented as an application on OpenVMS. It is similar
in behavior to the hardware InfoServer product although not
identical to it.
You can use the InfoServer utility commands to do the following:
o Create and delete services for virtual disk devices on a local
area network
o Save a list of active InfoServer services
o Modify the attributes of existing services
o Display information about the server and the nodes connected
to services on the server
o Display service-specific information about one or more
services
o Start the LASTport/disk server and set various server and
cache characteristics
To run the Infoserver, you must enter the following command:
$ RUN SYS$SYSTEM:ESS$INFOSERVER
The system then displays the following prompt:
InfoServer>
If your system does not display the InfoServer prompt but
displays an error message instead, ask your system manager to
start the InfoServer server.
Another way to begin to use the InfoServer is to define it as a
foreign command. This method is explained in the Usage_Summary
subtopic.
Following the Infoserver prompt, you can enter any InfoServer
command; for example:
InfoServer> SHOW SERVER
You can also enter HELP to obtain help on InfoServer commands
within the utility:
InfoServer> HELP SHOW SERVER
1 – Parameter
command
Specifies an InfoServer command. This parameter is optional. If
you do not specify a command, the utility displays its prompt and
waits for command input until you exit from the utility.
2 – Usage Summary
You can invoke the InfoServer in the following ways:
o Using the RUN command
As explained in the introduction, you can invoke the
InfoServer using the RUN command by entering the following
at the DCL command prompt:
$ RUN SYS$SYSTEM:ESS$INFOSERVER
o Defining the InfoServer as a foreign command
You can also define the InfoServer as a foreign command by
entering the following at the DCL prompt, or in a startup or
login command file:
$ InfoServer :== $ESS$INFOSERVER
After you enter this definition, you can enter the InfoServer
command at the DCL prompt to invoke the utility:
$ InfoServer
If you use InfoServer as a foreign command:
- And also enter an InfoServer command, the utility
terminates after it executes the command and returns you
to the DCL command prompt; for example:
$ InfoServer SHOW SERVER
.
.
.
(output)
.
.
.
$
- Without specifying an InfoServer command, the utility
displays the InfoServer> prompt, at which point you can
enter commands; for example:
$ InfoServer
InfoServer> SHOW SERVER
.
.
.
(output)
.
.
.
When you are inside the InfoServer utility, you can enter HELP to
get help on InfoServer commands.
NOTE
All InfoServer commands require SYSPRV and OPER privileges.
To exit from the InfoServer utility, enter the EXIT command at
the InfoServer> prompt or press Ctrl/Z.
For information about the InfoServer utility, enter the HELP
command at the InfoServer> prompt.
3 – CREATE
3.1 – SERVICE
Creates a service for a specified device or partition.
Usage Rules:
o All devices must be mounted systemwide to prevent them from
being dismounted when a process logs out.
o A device that has read/write service must be mounted /FOREIGN
so that it is not visible to OpenVMS.
o A device that has read-only service must be mounted either
/NOWRITE or /FOREIGN to OpenVMS so that no one can change it
locally.
o A partition can be served off a disk mounted for either read-
only or read/write access to OpenVMS.
o Support for partitions is limited in this release.
Format
CREATE SERVICE serviceName device-or-partitionName
3.1.1 – Parameters
serviceName
The name by which the service is known to the local area network.
The service name can consist of alphanumeric characters and
dollar signs ($). It can be 255 characters or fewer in length.
device-or-partitionName
The device or partition name is the name of the OpenVMS disk
device or partition being served to the local area network.
The name of the device or partition must have been created
previously.
Explanations of device and partition names follow.
o Device names
Devices served to the local area network are OpenVMS disk
devices; use OpenVMS device names when you specify an
InfoServer device name.
A disk specification must end with a colon.
o Partition names
Partitions are container files that are served to the network.
As such, they have OpenVMS file names with a default file type
of ".ESS$PARTITION". Partition names, including the device,
directory, and file name, can be no more than 242 characters
in length.
Support for partitions is limited in this version. HP strongly
suggests that you use LD devices to support partitioned hard
drives. See the DCL command LD HELP for more information.
3.1.2 – Qualifiers
3.1.2.1 /CLASS
/CLASS=className
Specifies a subset of the complete LASTport Disk (LAD) name
space.
The purpose of class names is to subdivide name spaces so that
clients see only those names that are meaningful to them. The use
of class names also allows two services to have the same name and
not conflict with one another.
You can, for example, use different class names for different
on-disk structures that several client systems use. You
might use SERVICEA/CLASS=ODS-2 for some client systems and
SERVICEA/CLASS=ISO_9660 for other client systems. The service
has the same name, SERVICEA, but the class names are different.
The class name you use depends upon the client systems that will
connect to the service being created. The default class name
is ODS_2. For example, OpenVMS systems use the ODS_2 name space
when attempting to mount an InfoServer device. Note that OpenVMS
clients can solicit only those services that are in the ODS_2
service class.
Valid class names are the following:
V2.0 Names understood by PCSA MS-DOS Clients
Unformatted Virtual disk has no format
MSDOS MSDOS virtual disks
ODS_2 VMS virtual disks
UNIX UNIX virtual disks
ISO_9660 ISO 9660 CD format
HIGH_SIERRA MS-DOS CD format
APPLE Macintosh HFS format
SUN Sun format
3.1.2.2 /ENCODED_PASSWORD
/ENCODED_PASSWORD=hexstring
The SAVE command creates this qualifier. Because passwords are
not stored in plain text, the hashed password value is written
out as part of the SAVE operation so that the service can be
recreated without revealing the password.
Note that if you edit the command procedure that the SAVE command
creates and change the service name, the encoded password value
is no longer valid. You need to set another password on the
service using the /PASSWORD qualifer.
3.1.2.3 /PASSWORD
/PASSWORD=passwordString
/NOPASSWORD (default)
Specifies an optional access control password for the service.
The client system must specify the password to access the
service.
The password string can be up to and including 39 alphanumeric
ASCII characters in length. If no password is specified, the
client system is not required to provide a password to access the
service.
The text password is hashed and stored in encrypted form in
memory with the other service information.
3.1.2.4 /RATING
/RATING=DYNAMIC
/RATING=STATIC=value
Clients use the service rating to select a service in the case of
multiple matching services. The service with the highest service
rating is selected.
The system adjusts the dynamic service rating based on load. You
can also set a static rating between 0 and 65535. The system does
not adjust static ratings.
One use of static ratings is to migrate clients from one copy
of a service to another. If you set a static rating of 0 on
services you want to migrate clients away from, no new clients
will connect to a 0-rated service; instead, they will connect to
higher-rated services. When all current clients have disconnected
from a service, you can safely delete it.
3.1.2.5 /READAHEAD
/READAHEAD (Default)
/NOREADAHEAD
When a disk read is required to fill a cache block, /READAHEAD
specifies that the read is to be from the first block requested
to the end of the bucket boundary. Readahead can speed up
sequential operations by pre-loading disk blocks that are needed
into the cache.
If you specify both /READAHEAD and /READBEHIND, any block
requested within a cache bucket causes the entire bucket range
of blocks to be read into the cache.
3.1.2.6 /READBEHIND
/READBEHIND
/NOREADBEHIND (default)
When a disk read is required to fill a cache block, /READBEHIND
specifies that the read is to include all blocks from the
beginning of the cache bucket boundary up to and including the
requested blocks.
If you specify both /READAHEAD and /READBEHIND, any block
requested within a cache bucket causes the entire bucket range
of blocks to be read into the cache.
3.1.2.7 /READERS
/READERS=number (default READERS 1000)
/NOREADERS
Specifies the maximum number of simultaneous client connections
allowed for read access. The default is 1000 readers. A value of
0 indicates write-only access.
If a client requests read-only or read/write access to a service,
the system counts this as one reader.
3.1.2.8 /WRITERS
/WRITERS
/NOWRITERS (default)
Specifies that the service is to allow access to a single writer.
3.1.3 – Examples
1.$ SHOW DEVICE MOVMAN$DQA0:/full
Disk MOVMAN$DQA0:, device type Compaq CRD-8322B, is online, file-oriented
device, shareable, served to cluster via MSCP Server, error logging is
enabled.
Error count 0 Operations completed
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 0 Default buffer size 512
Total blocks 16515072 Sectors per track 63
Total cylinders 16384 Tracks per cylinder 16
$ MOUNT/SYSTEM dqa0 OVMSIPS11
Volume is write locked
OVMSIPS11 mounted on _MOVMAN$DQA0:
$ InfoServer
InfoServer> CREATE SERVICE VMS_SIPS_V11 _MOVMAN$DQA0:
%INFOSRVR-I-CRESERV, service VMS_SIPS_V11 [ODS-2] created for
_MOVMAN$DQA0:.
This example shows commands you might enter to create a service
for a CD device:
o The SHOW DEVICE . . . /FULL command displays a complete list
of information about the _MOVMAN$DQA0 CD.
o The MOUNT/SYSTEM mounts the OVMSIPS11 volume on the
_MOVMAN$DQA0: CD.
o The InfoServer CREATE SERVICE command creates the VMS_SIPS_
V11 service on the _MOVMAN$DQA0 CD.
2. $LD CREATE KIT1/SIZE-100000
$DIRECTORY KIT1
Directory DKB0:[DISKS]
KIT1.DSK;1 100000/100008 29-APR-2005 14:14:43.49
Total of 1 file, 100000/100008 blocks.
$LD CONNECT KIT1
%LD-I-UNIT, Allocated device is MOVMAN$LDA1:
$INITIALIZE/SYSTEM MOVMAN$LDA1: kit1
$MOUNT/SYSTEM/NOWRITE MOVMAN$LDA1: kit1
%MOUNT-I-MOUNTED, KIT1 mounted on _MOVMAN$LDA1:
$CREATE SERVICE TEST_KIT_1 MOVMAN$LDA1:
%INFOSRVR-I-CRESERV, service TEST_KIT_1 [ODS-2] created for
_MOVMAN$LDA1:
This example shows commands you might enter to create a service
for a logical disk (LD) device:
o The LD CREATE KIT1 command creates a contiguous file, KIT1,
that can be used as a logical disk.
o The DIRECTORY KIT1 command provides information about KIT1.
o The LD CONNECT KIT1 connects the logical disk file, KIT1, to
the logical disk device MOVMAN$LDA1:.
o The INITIALIZE command formats the MOVMAN$LDA1: LD device.
o The MOUNT command makes the LD device available for
processing.
o The CREATE SERVICE command creates the TEST_KIT_1 service on
the _MOVMAN$LDA1 LD device.
4 – DELETE
4.1 – SERVICE
Deletes one or more services.
Format
DELETE SERVICE serviceName [device-or-partitionName]
4.1.1 – Parameters
serviceName
The name by which the service is known to the local area network.
The service name can consists of alphanumeric characters and
dollar signs ($). It can be up to and include 255 characters.
Wildcards are permitted in this command.
device-or-partitionName
The device or partition name is the name of the OpenVMS disk
device or partition as it is to be known to the local area
network. The name of the device or partition that you enter must
have been created previously.
Explanations of device and partition names follow.
o Device names
Devices served to the local area network are OpenVMS disk
devices; use OpenVMS device names when you specify an
InfoServer device name. Note that the device name must either
match exactly the name that the SHOW SERVICES command displays
or must contain wildcards. (Wildcards are permitted in this
command.)
A disk specification must end with a colon.
o Partition names
Partitions are container files that are served to the network.
As such, they have OpenVMS file names with a default file type
of ".ESS$PARTITION". Partition names, including the device,
directory, and file name, can be no more than 242 characters
in length.
The partition name can be used to further identify the
specific service selected. Support for partitions is limited
in this version, however. HP strongly recommends that you use
LD devices to support partitioned hard drives. See the DCL
command LD HELP for more information.
4.1.2 – Qualifiers
4.1.2.1 /CLASS
/CLASS=className
Specifies a subset of the complete LASTport Disk (LAD) name
space.
The purpose of class names is to subdivide name spaces so that
clients see only those names that are meaningful to them. The use
of class names also allows two services to have the same name and
not conflict with one another.
You can, for example, use different class names for different
on-disk structures that several client systems use. You
might use SERVICEA/CLASS=ODS-2 for some client systems and
SERVICEA/CLASS=ISO_9660 for other client systems. The service
has the same name, SERVICEA, but the class names are different.
The class name you use depends upon the client systems that will
connect to the service being created. The default class name
is ODS_2. For example, OpenVMS systems use the ODS_2 name space
when attempting to mount an InfoServer device. Note that OpenVMS
clients can solicit only those services that are in the ODS_2
service class.
Valid class names are the following:
V2.0 Names understood by PCSA MS-DOS Clients
Unformatted Virtual disk has no format
MSDOS MSDOS virtual disks
ODS_2 VMS virtual disks
UNIX UNIX virtual disks
ISO_9660 ISO 9660 CD format
HIGH_SIERRA MS-DOS CD format
APPLE Macintosh HFS format
SUN Sun format
4.1.2.2 /CONFIRM
/CONFIRM (default)
/NOCONFIRM
Confirm the deletion of a service. If there are any connections,
even though /NOCONFIRM has been entered, the system forces a
confirmation.
Controls whether a request is issued before each delete operation
to confirm that the operation should be performed on that
service. The following responses are valid:
YES NO QUIT
TRUE FALSE Ctrl/Z
1 0 ALL
Return (key)
Usage Notes:
o You can use any combination of uppercase and lowercase letters
for word responses. Word responses can be abbreviated to
one or more letters (for example, T, TR, or TRU for TRUE);
however, these abbreviations must be unique.
o Affirmative answers are YES, TRUE, and 1. Negative answers
include NO, FALSE, 0, and pressing Return.
o Entering QUIT or pressing Ctrl/Z indicates that you want to
stop processing the command at that point.
o When you respond by entering ALL, the command continues to
process, but no further prompts are displayed.
4.1.2.3 /DISCONNECT
/DISCONNECT
/NODISCONNECT (default)
Overrides the default prompting for confirmation if you attempt
to delete a service that has sessions connected to it. If a
service has connected sessions and the /DISCONNECT qualifier
is not supplied, you are prompted to confirm service deletion.
To delete services without being prompted at all, specify both
the /NOCONFIRM and /DISCONNECT qualifiers.
4.1.3 – Example
$ InfoServer SHOW SERVICES
Service Name [Service Class] Device or File
-------------------- --------------- --------------
CURRENT_KIT [ODS-2] _MOVMAN$LDA2:
CURRENT_KIT [ODS-2] _MOVMAN$LDA42:
%INFOSRVR-I-FOUND, 2 services found.
$ DELETE SERVICE CURRENT_KIT _MOVMAN$LDA42:
Delete service CURRENT_KIT [ODS-2] for _MOVMAN$LDA42:? [N]:Y
%INFOSRVR-I-DELSERV, service CURRENT_KIT [ODS-2] deleted for
_MOVMAN$LDA42:.
The first command displays 2 services.
The second command deletes the CURRENT_KIT service on the
_MOVMAN$LDA42: device. The system prompts you to confirm
your deletion command. After you do so, the system displays
a messages indicating that the service has been deleted.
5 – EXIT
Terminates the program. Alternatively, you can press Ctrl/Z to
exit from the program.
Format
EXIT
6 – SAVE
Saves the current set of active services as a set of commands in
a command procedure. You can then invoke the command procedure to
reproduce the current services when you reboot the system.
Format
SAVE [procedureName]
6.1 – Parameters
procedureName
Creates a command procedure that restores the current server
state. The procedure name is the OpenVMS file name of the command
procedure to be created. If a file type is not supplied, the type
defaults to .COM.
The default procedure name is ESS$LAD_SERVICES.COM.
6.2 – Examples
1.$SHOW SERVICES
Service Name [Service Class] Device or File
-------------------- --------------- --------------
BASELEVEL_A [ODS-2] _INFOS$LDA1:
BASELEVEL_B [ODS-2] _INFOS$LDA2:
BASELEVEL_C [ODS-2] _INFOS$LDA3:
BASELEVEL_D [ODS-2] _INFOS$LDA4:
FIELD_TEST_BASELEVEL [ODS-2] _INFOS$LDA2:
CURRENT_BASELEVEL [ODS-2] _INFOS$LDA3:
EXPERIMENTAL_BASELEVEL
[ODS-2] _INFOS$LDA4:
%INFOSRVR-I-FOUND, 7 services found.
The SHOW SERVICES command in this example displays the services
that are currently offered by the server. There is a set of
software baselevels, each on its own logical disk and served
to the LAN. The baselevels are labeled a through d, but, in
addition, names help users so that they do not need to remember
the corresponding letters.
Note that devices LDA2, LDA3, and LDA4 have two services
assigned to each one.
2.$SAVE BASELEVELS
The following example has been annotated. The individual
numbers that appear in the example correspond to the
numbered explanations that follow the example.
$! Created by the OpenVMS InfoServer SAVE command on 22-APR-2005
14:34:02.48
$ Set NoOn
$ Infoserver := $ESS$INFOSERVER
$!
$! The comment for each service includes the current device name.
$!
$!***************************************************************
$! BASELEVEL_A [ODS_2] - _BILBO$LDA1: 1
$!***************************************************************
$ LD Connect/Symbol _BILBO$DKB0:[DISKS]BASELEVEL_A.DSK;1 2
$ LD_UNIT_1 := LDA'LD_UNIT': 3
$ If $STATUS Then Mount/System/NoWrite 'LD_UNIT_1' BASELEVELA 4
$ INFOSERVER Create Service BASELEVEL_A 'LD_UNIT_1' - 5
/Class=ODS_2/Readers=1000/NoWriters -
/Readahead/NoReadbehind -
/Rating=Dynamic
$!***************************************************************
$! BASELEVEL_B [ODS_2] - _BILBO$LDA2:
$!***************************************************************
$ LD Connect/Symbol _BILBO$DKB0:[DISKS]BASELEVEL_B.DSK;1
$ LD_UNIT_2 := LDA'LD_UNIT':
$ If $STATUS Then Mount/System/NoWrite 'LD_UNIT_2' BASELEVELB
$ INFOSERVER Create Service BASELEVEL_B 'LD_UNIT_2' -
/Class=ODS_2/Readers=1000/NoWriters -
/Readahead/NoReadbehind -
/Rating=Dynamic
$!***************************************************************
$! BASELEVEL_C [ODS_2] - _BILBO$LDA3:
$!***************************************************************
$ LD Connect/Symbol _BILBO$DKB0:[DISKS]BASELEVEL_C.DSK;1
$ LD_UNIT_3 := LDA'LD_UNIT':
$ If $STATUS Then Mount/System/NoWrite 'LD_UNIT_3' BASELEVELC
$ INFOSERVER Create Service BASELEVEL_C 'LD_UNIT_3' -
/Class=ODS_2/Readers=1000/NoWriters -
/Readahead/NoReadbehind -
/Rating=Dynamic
$!***************************************************************
$! BASELEVEL_D [ODS_2] - _BILBO$LDA4:
$!***************************************************************
$ LD Connect/Symbol _BILBO$DKB0:[DISKS]BASELEVEL_D.DSK;1
$ LD_UNIT_4 := LDA'LD_UNIT':
$ If $STATUS Then Mount/System/NoWrite 'LD_UNIT_4' BASELEVELD
$ INFOSERVER Create Service BASELEVEL_D 'LD_UNIT_4' -
/Class=ODS_2/Readers=1000/NoWriters -
/Readahead/NoReadbehind -
/Rating=Dynamic -
/Encoded_Password=481C6B9081E742C2
! Invalid if service name changes 6
$!***************************************************************
$! FIELD_TEST_BASELEVEL [ODS_2] - _BILBO$LDA2:
$!***************************************************************
$ INFOSERVER Create Service FIELD_TEST_BASELEVEL 'LD_UNIT_2' - 7
/Class=ODS_2/Readers=1000/NoWriters -
/Readahead/NoReadbehind -
/Rating=Dynamic
$!***************************************************************
$ INFOSERVER Create Service CURRENT_BASELEVEL 'LD_UNIT_3' -
/Class=ODS_2/Readers=1000/NoWriters -
/Readahead/NoReadbehind -
/Rating=Dynamic
$!***************************************************************
$! EXPERIMENTAL_BASELEVEL [ODS_2] - _BILBO$LDA4:
$!***************************************************************
$ INFOSERVER Create Service EXPERIMENTAL_BASELEVEL 'LD_UNIT_4' -
/Class=ODS_2/Readers=1000/NoWriters -
/Readahead/NoReadbehind -
/Rating=Dynamic -
/Encoded_Password=01F1D7374C0B81EC
! Invalid if service name changes 8
$ Exit
The numbers in the example correspond to the numbers of the
following explanations.
1 The comment for each device contains the name of the device
at the time the SAVE command was executed. LD devices are
pseudo disk devices and might change unit numbers every time
they are connected.
2 This command connects an LD device to the container file and
assigns the unit number to the DCL symbol LD_UNIT.
3 A unique symbol is created for each device assigned to a
container file.
4 This command mounts the device specifying the label of the
volume that the device had at the time of the SAVE command.
5 The InfoServer service is recreated for the device.
6 The experimental baselevel services are password-protected.
For security, the password is stored in the command
procedure in pre-hashed format. Note that both services
have the same password, but the hash is different.
7 Because FIELD_TEST_BASELEVEL and BASELEVEL_B point to the
same LD device, no attempt is made to create another device,
and the correct unit (symbol LD_UNIT_2) is used to refer to
the previously created unit.
8 See #6.
7 – SET
7.1 – SERVICE
Modifies the attributes of an existing service.
Format
SET SERVICE serviceName [device-or-partitionName]
7.1.1 – Parameters
serviceName
The name by which the service is known to the local area network.
The service name can consist of alphanumeric characters or dollar
signs ($). It can be up to 255 characters in length.
device-or-partitionName
The device or partition name is the name of the OpenVMS disk
device or partition as it is to be known to the local area
network. The name of the device or partition that you enter must
have been created previously.
Explanations of device and partitions names follow.
o Device names
Devices served to the local area network are OpenVMS disk
devices; use OpenVMS device names when you specify an
InfoServer device name. Note that the device name must either
match exactly the name that the SHOW SERVICES command displays
or must contain wildcards.
In the InfoServer utility, wildcards, where supported, are
those used in OpenVMS. The % character matches exactly one
character. The * character matches zero or more characters.
A disk specification must end with a colon.
o Partition names
Partitions are container files that are served to the network.
As such, they have OpenVMS file names with a default file type
of ".ESS$PARTITION". Partition names, including the device,
directory, and file name, can be no more than 242 characters
in length.
The partition name can be used to further identify the
specific service selected. Support for partitions is limited
in this version, however. HP strongly recommends that you use
LD devices to support partitioned hard drives. See the DCL
command LD HELP for more information.
7.1.2 – Qualifiers
7.1.2.1 /CLASS
/CLASS=className
Specifies a subset of the complete LASTport Disk (LAD) name
space.
The purpose of class names is to subdivide name spaces so that
clients see only those names that are meaningful to them. The use
of class names also allows two services to have the same name and
not conflict with one another.
You can, for example, use different class names for different
on-disk structures that several client systems use. You
might use SERVICEA/CLASS=ODS-2 for some client systems and
SERVICEA/CLASS=ISO_9660 for other client systems. The service
has the same name, SERVICEA, but the class names are different.
The class name you use depends upon the client systems that will
connect to the service being created. The default class name
is ODS_2. For example, OpenVMS systems use the ODS_2 name space
when attempting to mount an InfoServer device. Note that OpenVMS
clients can solicit only those services that are in the ODS_2
service class.
Valid class names are the following:
V2.0 Names understood by PCSA MS-DOS Clients
Unformatted Virtual disk has no format
MSDOS MSDOS virtual disks
ODS_2 VMS virtual disks
UNIX UNIX virtual disks
ISO_9660 ISO 9660 CD format
HIGH_SIERRA MS-DOS CD format
APPLE Macintosh HFS format
SUN Sun format
7.1.2.2 /PASSWORD
/PASSWORD=passwordString
/NOPASSWORD
Specifies an optional service access control password. The client
system must specify the password to access the service.
The password string can be up to 39 alphanumeric ASCII characters
in length. If no password is specified, the client is not
required to provide a password to access the service.
The text password is hashed and stored in encrypted form in
memory with the other service information.
7.1.2.3 /RATING
/RATING=DYNAMIC
/RATING=STATIC=value
Clients use service rating to select a service in the case of
multiple matching services. The service with the higher service
rating is selected.
The system adjusts the dynamic service rating based on load.
A static rating between 0 and 65535 can also be set. Static
ratings are not adjusted by the system.
7.1.2.4 /READAHEAD
/READAHEAD
/NOREADAHEAD
When a disk read is required to fill a cache lock, specifies that
the read should be from the first block requested to the end of
the bucket boundary. Readahead can speed up sequential operations
by pre-loading disk blocks that are needed into the cache.
If both /READAHEAD and /READBEHIND are specified, any block
requested within a cache bucket causes the entire bucket range
of blocks to be read into the cache.
7.1.2.5 /READBEHIND
/READBEHIND
/NOREADBEHIND
When a disk read is required to fill a cache block, specifies
that the read should include all blocks from the beginning of the
cache bucket boundary up to and including the requested block.
If both /READAHEAD and /READBEHIND are specified, any block
requested within a cache bucket causes the entire bucket range
of blocks to be read into the cache.
7.1.2.6 /READERS
/READERS=number
Specifies the maximum number of client connections allowed for
read access.
7.1.3 – Example
$ INFOSERVER SET SERVICE FUNDY/NOPASSWORD
Service FUNDY [ODS-2] modified.
$ INFOSERVER SHOW SERVICES FUNDY/FULL
FUNDY [ODS-2] Access: Read-only
File or device: _MOVERS$LDA1: [750000 blocks]
Flags: 00000000D2 {No Writers,Static Rating,Readbehind,
Readahead}
Rating: Static, 42 Password: Disabled
Max Readers: 1000 Max Writers: 0
Curr Readers: 0 Curr Writers: 0
Reads: 0 Writes: 0
Blocks Read: 0 Blocks Written: 0
The first command in this example modifies the FUNDY service so
that the client does not need to enter a password to access the
service. The second command displays the FUNDY service, which
indicates that the use of a password has been disabled.
8 – SHOW
8.1 – SERVER
Displays information about the server (that is, the system that
provides services).
Format
SHOW SERVER
8.1.1 – Example
$ INFOSERVER SHOW SERVER
Node MOVERS [COMPAQ Professional Workstation XP1000] running
OpenVMS XALD-BL2
LASTport/Disk Server Version 1.2
Max Services: 64 Write Quota: 0
Cache Buckets: 4096 Cache Bucket Size: 32 blocks
Cache Size: 67108864 bytes
Hits: 478 Hit Percentage: 59%
Misses: 328
Current Sessions: 0 Peak Sessions: 1
Read Write
Requests: 40 0
Blocks: 319 0
Errors: 0 0
Aborted: 0 0
Conflicts: 0 0
The command in this example displays information about the
server that provides services to the client. The information
displayed includes the following:
o The maximum number of services this server can offer
simultaneously
o The current size of the cache
o Cache effectiveness statistics
o Current and maximum historical number of clients connected
simultaneously
o I/O statistics
8.2 – SERVICES
The SHOW SERVICES command displays service-specific information
for one or all services offered by the server. This information
includes the device associated with the service, the service
class, and the number of connected sessions.
The SHOW SERVICES command supports wildcard expressions. In the
InfoServer utility, wildcards, where supported, are those used
in OpenVMS. The % character matches exactly one character. The *
character matches zero or more characters.
Format
SHOW SERVICES [serviceName] [options...]
8.2.1 – Parameters
serviceName
The name by which the service is known to the local area network.
The service name consists of alphanumeric characters or dollar
signs ($). It can be up to 255 characters in length. If omitted,
the service name defaults to all services.
In the InfoServer utility, wildcards, where supported, are those
used in OpenVMS. The % character matches exactly one character.
The * character matches zero or more characters.
8.2.2 – Qualifiers
8.2.2.1 /BRIEF
/BRIEF (default)
The BRIEF option provides an abbreviated one-line summary of
information for each service selected. BRIEF is the default.
8.2.2.2 /FULL
The FULL option provides all the service-specific information for
the services selected.
8.2.3 – Example
INFOSERVER> SHOW SERVICES
Service Name [Service Class] Device or File
-------------------- --------------- --------------
HUDSON [ODS-2] _MOVERS$LDA1:
BAFFIN [ODS-2] _MOVERS$LDA1:
FUNDY [ODS-2] _MOVERS$LDA1:
3 services found.
INFOSERVER> SHOW SERVICES/FULL
HUDSON [ODS-2] Access: Read-only
File or device: _MOVERS$LDA1: [750000 blocks]
Flags: 0000000082 {No Writers,Readahead}
Rating: Dynamic, 65535 Password: Disabled
Max Readers: 1000 Max Writers: 0
Curr Readers: 0 Curr Writers: 0
Reads: 0 Writes: 0
Blocks Read: 0 Blocks Written: 0
BAFFIN [ODS-2] Access: Read-only
File or device: _MOVERS$LDA1: [750000 blocks]
Flags: 0000000082 {No Writers,Readahead}
Rating: Dynamic, 65535 Password: Disabled
Max Readers: 1000 Max Writers: 0
Curr Readers: 0 Curr Writers: 0
Reads: 0 Writes: 0
Blocks Read: 0 Blocks Written: 0
FUNDY [ODS-2] Access: Read-only
File or device: _MOVERS$LDA1: [750000 blocks]
Flags: 00000000D2 {No Writers,Static Rating,Readbehind,
Readahead}
Rating: Static, 42 Password: Enabled
Max Readers: 1000 Max Writers: 0
Curr Readers: 0 Curr Writers: 0
Reads: 0 Writes: 0
Blocks Read: 0 Blocks Written: 0
3 services found.
The first command in this example displays the 1-line default
BRIEF summary of all the services that are connected.
The second command in this example displays all of the service-
specific information for all the services that are connected.
Notice that passwords are disabled on the HUDSON and BAFFIN
services and enabled on the FUNDY service.
8.3 – SESSIONS
Displays information about client nodes that are connected to
services.
Format
SHOW SESSIONS [serviceName] [device-or-partitionName]]
8.3.1 – Parameters
serviceName
The name by which the service is known to the local area network.
The service name can consist of alphanumeric characters, dollar
signs ($), and wildcards. It can be up to 255 characters in
length. If omitted, the service name defaults to all services.
In the InfoServer utility, wildcards, where supported, are those
used in OpenVMS. The % character matches exactly one character.
The * character matches zero or more characters.
device-or-partitionName
The device or partition name is the name of the OpenVMS disk
device or partition as it is to be known to the local area
network. The name of the device or partition that you enter must
have been created previously.
Explanations of device and partition names follow.
o Device names
Devices served to the local area network are OpenVMS disk
devices; use OpenVMS device names when you specify an
InfoServer device name. Note that the device name must either
match exactly the name that the SHOW SERVICES command displays
or must contain wildcards.
In the InfoServer utility, wildcards, where supported, are
those used in OpenVMS. The % character matches exactly one
character. The * character matches zero or more characters.
A disk specification must end with a colon.
o Partition names
Partitions are container files that are served to the network.
As such, they have OpenVMS file names with a default file type
of ".ESS$PARTITION". Partition names, including the device,
directory, and file name, can be no more than 242 characters
in length.
Support for partitions is limited in this version. HP strongly
suggests that you use LD devices to support partitioned hard
drives. See the DCL command LD HELP for more information.
8.3.2 – Qualifiers
8.3.2.1 /ALL
Display all services that match the selection criteria even if
no clients have connections. If this qualifier is omitted, only
those services with clients connected will be displayed.
8.3.3 – Example
$ INFOSERVER SHOW SESSIONS
HUDSON [ODS-2] _MOVERS$LDA1: [ 1 Connection]
1 service found.
$ INFOSERVER SHOW SESSIONS/ALL
HUDSON [ODS-2] _MOVERS$LDA1: [ 1 Connection]
BAFFIN [ODS-2] _MOVERS$LDA1:
FUNDY [ODS-2] _MOVERS$LDA1:
3 services found.
The command in the first example displays only the session
that has a client connection, HUDSON. The command in the
second example displays all sessions, even those with no client
connections.
9 – SPAWN
Spawns a process to execute a DCL command. If you do not enter a
command, the command terminal is attached to the spawned process.
If you do enter a command, that command is executed, and, upon
completion of the command, control returns to the parent process.
Format
SPAWN [DCL Command]
9.1 – Example
InfoServer> SPAWN DIRECTORY
.
.
.
(output)
.
.
.
InfoServer>
The command in this example spawns a process to execute a DCL
DIRECTORY command. Following execution of the command, control
returns to the InfoServer process.
10 – START
10.1 – SERVER
This command starts the LASTport/Disk server and sets various
server and cache characteristics.
Usually, this command is executed by SYS$STARTUP:ESS$LAD_
STARTUP.COM using data from SYS$STARTUP:ESS$LAD_STARTUP.DAT.
HP strongly recommends that you make all modifications in the
SYS$STARTUP:ESS$LAD_STARTUP.DAT file.
You can use the START SERVER command interactively to use its
qualifiers to change server settings so long as no services are
currently defined.
NOTE
If you enter the START SERVER command directly, you must
specify all four qualifiers, or the system will revert to
using default values.
Format
START SERVER
10.1.1 – Qualifiers
10.1.1.1 /BUFFER_SIZE
/BUFFER_SIZE=n
The InfoServer block cache is structured as an array of fixed-
size buffers (also called buckets.) The /BUFFER_SIZE qualifier
determines the size of each bucket. (The /CACHE qualifer
determines the number of buckets.)
The numeric value of this parameter is an integer between 3 and
8 inclusive, representing the bucket size in 512-byte blocks as
follows:
3 - 8 blocks (default)
4 - 16 blocks
5 - 32 blocks
6 - 64 blocks
7 - 128 blocks
8 - 256 blocks
The default value is 3.
Bucket sizes that are larger than 32 blocks are not appropriate
for most users. The OpenVMS client segments I/O requests that
are larger than 31 blocks into 31-block chunks, and the default
bucket readahead behavior might result in unnecessary I/O
activity to the disk.
10.1.1.2 /CACHE
/CACHE = number-of-buckets (default = 512)
The InfoServer block cache is structured as an array of
fixed-size buffers (also called buckets. The /CACHE qualifier
determines the number of buckets in the cache. The /BUFFER_SIZE
qualifier determines the size of each bucket.
Numbers larger than 16384 can adversely affect performance.
Consider increasing the /BUFFER_SIZE qualifier to reach the
desired cache size.
10.1.1.3 /MAXIMUM_SERVICES
/MAXIMUM_SERVICES = maxservice (default = 256)
Sets the maximum service count for the server. This is the
maximum number of services that can be defined at one time.
Each service descriptor consumes non-paged pool; however, unused
service slots consume only 4 bytes each.
The maximum value is 1024.
10.1.1.4 /WRITE_QUOTA
/WRITE_QUOTA = n (default = 0)
Number of simultaneous synchronous writes permitted within the
server. The default of zero means that all write operations are
performed synchronously.
10.1.2 – Example
$ InfoServer SHOW SERVER
Node BILBO [HP rx2600 (900MHz/1.5MB)] running OpenVMS XAR8-D2Y
LASTport/Disk Server Version 1.2
Max Services: 64 Write Quota: 0
Cache Buckets: 2048 Cache Bucket Size: 32 blocks
Cache Size: 33554432 bytes
Hits: 0 Hit Percentage: 0%
Misses: 0
Current Sessions: 0 Peak Sessions: 0
Read Write
Requests: 0 0
Blocks: 0 0
Errors: 0 0
Aborted: 0 0
Conflicts: 0 0
$ InfoServer START SERVER/MAXIMUM_SERVICES=128
/CACHE=2048/BUFF=5/WRITE=0
%INFOSRVR-I-STARTED, LASTport/Disk server started.
$ InfoServer SHOW SERVER
Node BILBO [HP rx2600 (900MHz/1.5MB)] running OpenVMS XAR8-D2Y
LASTport/Disk Server Version 1.2
Max Services: 128 Write Quota: 0
Cache Buckets: 2048 Cache Bucket Size: 32 blocks
Cache Size: 33554432 bytes
Hits: 0 Hit Percentage: 0%
Misses: 0
Current Sessions: 0 Peak Sessions: 0
Read Write
Requests: 0 0
Blocks: 0 0
Errors: 0 0
Aborted: 0 0
Conflicts: 0 0
The first command in this example displays the current
information about the server. The second command starts the
server and increases the maximum number of services for the
server. The third command displays the new information about
the server, showing the increases maximum number of services.