HELPLIB.HLB  —  InfoServer  SET  SERVICE
    Modifies the attributes of an existing service.

    Format

      SET SERVICE  serviceName [device-or-partitionName]

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. VSI strongly recommends that you use
       LD devices to support partitioned hard drives. See the DCL
       command LD HELP for more information.

2  –  Qualifiers

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

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.

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.

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.

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.

2.6    /READERS

       /READERS=number

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

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