ESS$INFOSERVER.HLB  —  DELETE

1  –  SERVICE 

    Deletes one or more services.

    Privileges Required

       LOG_IO

    Format

      DELETE SERVICE  serviceName [device-or-partitionName]

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

1.2  –  Qualifiers

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

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.

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.

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