HELPLIB.HLB  —  CMS  DELETE  CLASS
    Deletes one or more classes from a CMS library.

       Format:

           DELETE CLASS  class-expression "remark"

1  –  Restrictions 

    o  You cannot delete a class that contains any element
       generations unless you specify the /REMOVE_CONTENTS
       qualifier.

    o  You cannot delete a class that has read-only access. (Use the
       MODIFY CLASS/NOREAD_ONLY command to change the access to the
       class.)

2  –  Command Parameters 

 class-expression

    Specifies the class or classes to be deleted from the CMS library.
    A class expression can be a class name, a wildcard expression, or
    a list of these separated by commas.

 remark

    Specifies a character string to be logged in the history file
    with this command, usually used to explain why the command was
    entered. The remark is enclosed in quotation marks. If no remark
    was entered, a null remark ("") is logged.

3  –  Description 

    The DELETE CLASS command deletes one or more classes from a CMS
    library. The class must exist and must not contain any element
    generations unless the /REMOVE_CONTENTS qualifier is specified.
    If the /REMOVE_CONTENTS qualifier is not specified and any
    generations belong to the class, CMS issues an error message and
    does not delete the class. If the /REMOVE_CONTENTS qualifier is
    not specified, use the REMOVE GENERATION command to remove element
    generations from a class before issuing the DELETE CLASS command.

    Even though a class is deleted, records of transactions that
    created and used the class are retained in the library history.
    You can reuse the deleted class name to create a new class.
    However, there is no distinction between the two classes in the
    project history, except that their transactions are separated by
    entries for DELETE CLASS and CREATE CLASS commands.

    To determine which generations belong to a class, use the SHOW
    CLASS command with the /CONTENTS qualifier.

4  –  Qualifiers

4.1    /CONFIRM 

    Controls whether CMS prompts you for confirmation before each
    transaction.

    When you specify /CONFIRM and run CMS in interactive mode, CMS
    prompts you for confirmation. If you type YES, ALL, TRUE, or 1,
    CMS executes the transaction.  If you type NO, QUIT, FALSE, 0,
    or press RETURN or CTRL/Z, no action is performed. If you type
    any other character, CMS continues to prompt until you type an
    acceptable response.

    CMS does not prompt for confirmation in batch mode.

4.2    /LOG (D) 

    Controls whether CMS displays success and informational messages
    on the default output device. By default, if the command executes
    successfully, CMS displays a success message. If you specify
    /NOLOG, success and informational messages are suppressed. Any
    warning, error, or fatal error messages are displayed regardless
    of whether /LOG or /NOLOG is specified.

4.3    /OCCLUDE[=option,...] 

    Controls whether CMS selects the first instance of the specified
    object, or all instances of the specified object in the library
    search list. The options field contains one or more keywords
    associated with the name of the object. The options field can
    contain the following keywords:

       ALL--equivalent to CLASS
       CLASS (D)
       NOCLASS
       NONE--equivalent to NOCLASS

    You can specify either ALL, NONE, or the [NO]CLASS keyword.

    By default, CMS performs occlusion for all objects; that is, CMS
    selects only the first occurrence of a specified object.

4.4    /REMOVE_CONTENTS 

    Controls whether CMS removes generations of elements from the
    specified class prior to deleting the class. When /REMOVE_CONTENTS
    is specified CMS displays an informational message for each element
    generation that is removed from the class.

5  –  Examples 

    (1) CMS> DELETE CLASS PRE_RELEASE "no longer necessary"
        %CMS-S-DELETED, class DISKX:[PROJECT.CMSLIB]PRE_RELEASE deleted

      This command deletes the class named PRE_RELEASE.

    (2) CMS> REMOVE GENERATION *.* BETA*
        _Remark: beta sites converted to released product
        %CMS-I-GENREMOVED, generation 3 of element
        DISKX:[PROJECT.CMSLIB]INI.FOR removed from class
        DISKX:[PROJECT.CMSLIB]BETAFEB
        %CMS-I-GENREMOVED, generation 4 of element
        DISKX:[PROJECT.CMSLIB]SRC.FOR removed from class
        DISKX:[PROJECT.CMSLIB]BETAFEB
        %CMS-I-GENREMOVED, generation 3 of element
        DISKX:[PROJECT.CMSLIB]INI.FOR removed from class
        DISKX:[PROJECT.CMSLIB]BETAJAN
        %CMS-I-GENREMOVED, generation 2 of element
        DISKX:[PROJECT.CMSLIB]SRC.FOR removed from class
        DISKX:[PROJECT.CMSLIB]BETAJAN
        %CMS-S-REMOVALS, 4 removals completed

        CMS> DELETE CLASS BETA* "beta sites converted to released product"
        %CMS-I-DELETED, class DISKX:[PROJECT.CMSLIB]BETAFEB deleted
        %CMS-I-DELETED, class DISKX:[PROJECT.CMSLIB]BETAJAN deleted
        %CMS-S-DELETIONS, 2 classes deleted

      This example removes all element generations from all classes
      whose names begin with the string BETA, then deletes all of
      the empty classes. CMS does not prompt for confirmation during
      deletion unless you specify the /CONFIRM qualifier.
Close Help