Software Product Description.

              PRODUCT NAME: Monitoring Performance History (MPH)

              DESCRIPTION

              Monitoring Performance History software (MPH) is
              distributed with the OpenVMS Version 7.0 Associated
              Products CD_Rom and is installed separately. This software
              should be installed after installing or upgrading the
              system to OpenVMS Version 7.0.

              MPH is a tool that collects information (such as error
              logs, crash dump summaries, configuration, and performance
              data) from the system on which it is installed. This data
              is transmitted back to Digital and is used to set standard
              requirements for future releases of OpenVMS, such as
              MeanTime Between Crash (MTBCr) and MeanTime Between System
              Interruption (MTBSi). The disk size requirement for MPH
              installation is approximately 1200 blocks. MPH requires
              300 blocks of disk space per node after installation.

              MPH performs three main functions:

              o  Captures updates to the error log.

              o  Captures the crash dump profile after the system
                 reboots (if the crash dump is enabled and present).

              o  Captures changes to the hardware configuration of a
                 cluster/node.

              All data is stored in the MPH copy area (MPH$COPY) and is
              transported to DPP on a weekly or daily basis.

              MPH can use one of three transport mechanisms to copy data
              from the MPH$COPY area:

              o  DSNLink: MPH data is transferred via DSNLink to the
                 CSC. The files are then copied from the CSC to the
                 Digital processing site via Digitals internal network.

              o  Internet: MPH data is mailed via Internet directly to
                 the Digital processing site.











                                                                       1

 






           o  DECnet: Customer systems that are not running DSNLink
              or Internet must be connected via DECnet to another
              cluster which is running MPH and has DSNlink installed.
              The MPH data is copied to the other cluster and from
              there is copied to the CSC via DSNLink.

           The MPH error log files are compressed before being
           transferred via the chosen transport mechanism.

           For more information, please refer to the OpenVMS Version
           7.0 Release Notes. External customers can request
           additional information on MPH by sending Internet mail
           to mph_admin@dppsys.enet.dec.com. (Digital internal sites
           should send mail to mph_admin@dppsys.ayo.dec.com). Using
           the keyword INFO anywhere in the subject header of your
           message will expedite the routing of your request.







































                                                                       2