[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

Content starts here

HP OpenVMS Version 8.3 New Features and Documentation Overview


Previous Contents Index

EXIT

Terminates the program. Alternatively, you can press Ctrl/Z to exit from the program.

Format

EXIT

HELP

Online InfoServer help.

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.


Format

HELP [topic]


Parameters

topic

The topic for which help is requested.

Example


$ INFOSERVER HELP SHOW SESSIONS
      

This command displays help about the InfoServer command SHOW SESSIONS.

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


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 you do not specify a file type, the type defaults to .COM.

The default procedure name is ESS$LAD_SERVICES.COM.


Example


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


$ SAVE BASELEVELS








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

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 pseudodisk 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 re-created for the device.
  6. The experimental baselevel services are password protected. For security, the password is stored in the command procedure in prehashed 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 explanation #6.

SET SERVICE

Modifies the attributes of an existing service.

Format

SET SERVICE serviceName [device-or-partitionName]


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.

  • 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 percent (%) character matches exactly one character. The asterisk (*) character matches zero or more characters.
    A disk specification must end with a colon.
  • 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. HP strongly suggests that you use LD devices to support partitioned hard drives. See the DCL command LD HELP for more information.

Qualifiers

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

For example, you can 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

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

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

/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 the /READAHEAD and the /READBEHIND qualifiers are specified, any block requested within a cache bucket causes the entire bucket range of blocks to be read into the cache.

/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 the /READAHEAD and the /READBEHIND qualifiers are specified, any block requested within a cache bucket causes the entire bucket range of blocks to be read into the cache.

/READERS=number

Specifies the maximum number of client connections allowed for read access.

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, showing that the use of a password has been disabled. (In the second example, notice that the use of a password is enabled for the FUNDY service.)

SHOW SERVER

Displays information about the server (that is, the system that provides services).

Format

SHOW SERVER


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


      

This command displays information about the server that provides services to the client. The information displayed includes the following:

  • The maximum number of services this server can offer simultaneously
  • The current size of the cache
  • Cache effectiveness statistics
  • Current and maximum historical number of clients connected simultaneously
  • I/O statistics

SHOW SERVICES

The SHOW SERVICES command displays service-specific information for one or all services offered by the server. This information includes the device number associated with the service 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 percent (%) character matches exactly one character. The asterisk (*) character matches zero or more characters.


Format

SHOW SERVICES [serviceName] [options...]


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 the same as those used in OpenVMS. The percent (%) character matches exactly one character. The asterisk (*) character matches zero or more characters.


Qualifiers

/BRIEF (default)

The BRIEF option provides an abbreviated one-line summary of information for each service selected. BRIEF is the default.

/FULL

The FULL option provides all the service-specific information for the services selected.

Examples

#1

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.


      

This command displays the one-line default BRIEF summary of all the services that are connected.

#2

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.


      

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

SHOW SESSIONS

Displays information about client nodes that are connected to services.

Format

SHOW SESSIONS [serviceName] [device-or-partitionName]]


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 percent (%) character matches exactly one character. The asterisk (*) 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.

  • 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 the same as those used in OpenVMS. The percent (%) character matches exactly one character. The asterisk (*) character matches zero or more characters.
    A disk specification must end with a colon.
  • 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.

Qualifiers

/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 are displayed.

Examples

#1

$ INFOSERVER SHOW SESSIONS
HUDSON               [ODS-2]         _MOVERS$LDA1: [ 1 Connection]
1 service found.

      

#2

$ INFOSERVER SHOW SESSIONS/ALL
HUDSON               [ODS-2]         _MOVERS$LDA1: [ 1 Connection]

BAFFIN               [ODS-2]         _MOVERS$LDA1:

FUNDY                [ODS-2]         _MOVERS$LDA1:
3 services found.

      

In the first example, this command displays only the session that has a client connection, HUDSON. In the second example, this command displays all sessions, even those with no client connections.

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]


Example


InfoServer> SPAWN DIRECTORY
   .
   .
   .
(output)
   .
   .
   .
InfoServer>
      

This command spawns a process to execute a DCL command DIRECTORY. Following execution of the command, control returns to the InfoServer process.


Previous Next Contents Index