1    /BRANCH

    Format options:

       /BRANCH=branchname
       /NOBRANCH (default)

    Specifies whether CDO creates a version on a new branch line or
    on an existing line of descent. The element must be controlled to
    use the /BRANCH qualifier.

2    /CLOSURE

    Format options:

       /CLOSURE=keyword
       /NOCLOSURE (default)

    Specifies whether CDO reserves additional elements. A CLOSURE
    operation fails if any element is a child of an element outside
    the area defined by the CLOSURE keyword.

    CLOSURE takes one of the following keywords:

    CLOSURE
    Keyword      Behavior

    TO_BOTH      Reserves the element specified and all owners and
                 members.

    TO_BOTTOM    Reserves the element specified and all members.

    TO_CLOSURE   Reserves the element specified, all owners, and any
                 element under the top collection that depends on the
                 element specified.

    TO_TOP       Reserves the element specified and all owners.

    In most cases, you can specify the TO_BOTH, TO_TOP, or TO_BOTTOM
    keywords. The TO_CLOSURE keyword is useful when you are working
    with the source and derived files common in system building
    applications.

    If you specify TO_BOTH, TO_CLOSURE, or TO_TOP, CDO ignores owners
    of the top collection.

3    /LOG

    Format options:

       /LOG
       /NOLOG (default)

    Specifies whether CDO displays text identifying each element as
    the element is reserved.

4    /OUTPUT

    Format options:

       /OUTPUT (default)
       /NOOUTPUT

    The /NOOUTPUT qualifier lets you reserve a FILE_ELEMENT of type
    MCS_BINARY without copying the file into the current context
    directory. This capability is useful for using the repository
    to manage binary files that are superseded each time they are
    reserved. It lets you reserve the file element without incurrring
    the processing time to create the binary file in the context
    directory.

    If you use the /NOOUTPUT qualifier in a RESERVE command, you
    must update the context directory with the latest binary file to
    be replaced. If you do not update the current context directory
    with a new file, the REPLACE command will fail. When the REPLACE
    command fails, CDO displays an error message containing the
    full directory specification of the reserved file that CDO was
    attempting to replace. Refer to this error message and place a
    new copy of the specified file in the context directory.

    If you reserve a file with the /NOOUTPUT qualifier, CDO does not
    create the file in the context directory. If you manually place
    a file in the context directory and then issue the UNRESERVE
    command, the reserved file is unreserved and any copies of the
    file in the context directory are deleted. This occurs even if
    you manually superseded any files in the context directory.

                                   NOTE

       If you use the VERIFY/FIX command on a repository, any
       files reserved with the /NOOUTPUT qualifier are created
       in the context directory, because the VERIFY command cannot
       find reserved files. This performance cost has always been
       associated with the VERIFY/FIX command when it cannot find
       reserved files.