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