This screen provides information about AIJ journal performance.

    The following information is examined:

    o  AIJ journaling status

    o  Database configuration

    o  Reserved journals

    o  AIJ log server (ALS) status

    o  Journal overwrite

    o  Default allocation

    o  AIJ backup server (ABS) and backup file names

    You can use the information in this screen to ensure that AIJ
    journals are on their own device. You can also examine the
    AIJ request block to I/O ratio, blocks per I/O ratio, and the
    formatting of the AIJ request block.

    Information in the AIJ Analysis screen is displayed only if it
    exceeds established threshold values or normal expectations. Note
    that the items identified in this screen are not necessarily
    indications of performance problems. The items may be an
    indication of a performance problem, but in most cases, further
    research is necessary.

    The AIJ Analysis screen has a configuration submenu that allows
    you to set thresholds for the following:

    o  Seconds to AIJ extend/switch

       The default threshold is 60. You can override the default
       value with the RDM$BIND_STATS_AIJ_SEC_TO_EXTEND logical name.

    o  ARBs per AIJ I/O

       The default threshold is 2. You can override the default value
       with the RDM$BIND_STATS_AIJ_ARBS_PER_IO logical name.

    o  Blocks per AIJ I/O

       The default threshold is 2. You can override the default value
       with the RDM$BIND_STATS_AIJ_BLKS_PER_IO logical name.

    o  Background ARB threshold

       The default threshold is 50. You can override the default
       value with the RDM$BIND_STATS_AIJ_BKGRD_ARB_RATIO logical
       name.

    o  Cache overflow threshold

       The default threshold is 10. You can override the default
       value with the RDM$BIND_STATS_CACHE_OVF_RATIO logical name.

    o  Network bandwidth threshold

       The default threshold is 60 seconds. You can override the
       default value with the RDM$BIND_STATS_AIJ_NETWORK_BPS logical
       name.

    Note that the Online Analysis facility uses the actual database
    parameters and attributes specified using interactive SQL. The
    Online Analysis facility does not use the Dashboard facility
    because the Database Dashboard attributes are temporary settings.
    Therefore, online changes made using the Dashboard facility are
    not reflected in the analysis output. Yet, using the Dashboard
    facility is the recommended method for testing potential database
    attribute settings. You must use interactive SQL in order to make
    the attribute settings persistent.

    Also note that the Online Analysis facility is invoked at the
    designated screen refresh interval. As the Online Analysis
    facility is fairly CPU intensive, and the analysis results seldom
    vary greatly over a miniscule period of time, it is recommended
    that the screen refresh interval be set to 3 seconds or more.

    The AIJ Analysis screen is not recorded in the binary output file
    produced using the Output qualifier. Consequently, this screen
    is not available when you replay a binary file using the Input
    qualifier.