Verifies the integrity of a UNIX container file, including the
    following checks:

    o  Superblock validation

    o  Inode validation

    o  Directory validation

    o  Internal allocation validation

    o  Directory hierarchy validation

    Reports, and optionally corrects, problems within the structure
    of the container directory. Applies to the NFS server.

    Related commands: DIRECTORY, MAP, UNMAP

    Format

      ANALYZE CONTAINER  device:path.name

                         [ /[NO]CONFIRM ]

                         [ /[NO]REPAIR ]

1  –  Restrictions and Tips

    o  Before you enter the ANALYZE CONTAINER command, you must map
       the OpenVMS volume on which the container directory resides,
       using the MAP command.

    o  Before you enter the ANALYZE CONTAINER command, unmap the
       container file system to prevent users from attempting to
       access to it while you analyze it.

    o  This command requires the BYPASS privilege.

2  –  Parameters

 device:path.name

    Required.

    Device and container directory to analyze.

3  –  Qualifiers

3.1    /CONFIRM

       /CONFIRM
       /NOCONFIRM

    Optional. Default: /NOCONFIRM.

    Use only with the /REPAIR qualifier.

    When the software encounters a problem with the services
    database, it displays a description and solution and then
    requests confirmation before making each correction. For example:

 %TCPIP-E-ANA_SUP_BADIICGSIZE, Problem: Bad initial inode cell group
 size:bad_value
 Solution: Will be replaced by default size: good_value
       CONFIRM [Y/N/G]:

    Respond to the CONFIRM: prompt by entering one of the following:

    o  Y to repair the problem

    o  N to ignore the problem

    o  G to change to NO CONFIRMATION mode

3.2    /REPAIR

       /REPAIR
       /NOREPAIR

    Optional. Default: /NOREPAIR.

    Any errors will be repaired.

4  –  Examples

    1.TCPIP> UNMAP "/wren20"
      TCPIP> ANALYZE CONTAINER DUA0:[WREN20]

      Verifies the integrity of container DUA0:[WREN20].