8. CA MICS NSM Integration (MTI) › 8.5 Integration Checklists › 8.5.4 Recovering the MTI Dictionary

8.5.4 Recovering the MTI Dictionary

This section addresses recovery in the unlikely event of
a catastrophic failure resulting in the total destruction of
the MTI Dictionary through the use of the MTIDUTIL utility
(discussed in detail in Section 8.8).  Although chances of
such a loss occurring are slim, the MTI Dictionary was
constructed so that it can be rebuilt with minimal impact to
existing MTI components.

Note that the MTI Dictionary is stored in the
sharedprefix.MICS.TABLES data set and is backed up with the
Primary CA MICS database unit.  This checklist should be used
ONLY if the Primary database backup is unavailable.

___1. Reinitialize the MTI Dictionary.

      Edit sharedprefix.MICS.CNTL(MTIDUTIL) and delete all
      lines following the MTISYSIN DD.  Add the following
      after the MTISYSIN DD:

      %DICINIT(FORCE=YES)

      *******************************************************
      *                                                     *
      *      !  !  !   C  A  U  T  I  O  N   !  !  !        *
      *                                                     *
      *  Running a DICINIT with the FORCE=YES option will   *
      *  completely destroy the existing MTI Dictionary!    *
      *  All existing MTI configuration information will    *
      *  be lost!                                           *
      *                                                     *
      *******************************************************

      Submit the job in prefix.MICS.CNTL(MTIDUTIL).

      Ensure that there are no error messages in the MICSLOG;
      that the MICSLOG contains the normal termination
      message, MTI02399I; and that the job completes with a
      condition code of zero.

___2. Reload the METRICS / MTI Dictionary.

      Edit sharedprefix.MICS.CNTL(DICLOAD).

      CA MICS shipped an HFS CSV file representing certain
      pre-packaged Metrics data that were created for certain
      machine types.  This file is called the "Standardized
      Metrics Update File".

      All Standardized Metrics Update File data previously
      loaded by way of the INPUTMTX DD will also have to be
      reloaded.  The Metrics file will need to be specified
      as a data set name on the INPUTMTX DD.

      On the INPUTMTX DD, add the data set name of the
      Standardized Metrics Update file.

      On the INPUTCSV DD, add the data set names of all the
      input data sets for ALL MTI components.  Concatenated
      data sets are allowed.  You should manually check the
      daily jobs, cccCGEN, cccUPDAT, DICLOAD, and DICSCAN in
      order to locate all data sets.

      In order to properly rebuild the MTI Dictionary, all
      data sets previously used to build the dictionary must
      be reloaded.

      Failure to do so can give unpredictable results.

      Submit the job in sharedprefix.MICS.CNTL(DICLOAD).

      Ensure that there are no error messages in the MICSLOG;
      that the MICSLOG contains the normal termination
      message, MTI02399I; and that the job completes with a
      condition code of zero.

___4. Delete all existing MTI CA MICS Data Dictionary
      entries.

      Using the ISPF Library utility (Options 3.1),
      delete all members starting with an underscore(_) in
      sharedprefix.MICS.DIC.TEXT.

___5. Compress sharedprefix.MICS.DIC.TEXT.

      In order to make room for the new MTI Data Dictionary
      members, you should compress
      sharedprefix.MICS.DIC.TEXT.  You can use ISPF Library
      Utilities (option 3.1), or IEBCOPY.

___6. Rebuild the MTI CA MICS Data Dictionary entries.

      Edit sharedprefix.MICS.CNTL(DICDSHEL).  Make sure the
      COMMIT=YES parameter is specified on the DICSHELL
      statement.

      Submit the job in sharedprefix.MICS.CNTL(DICDSHEL).

      Ensure that there are no error messages in the MICSLOG;
      that the MICSLOG contains the normal termination
      message, MTI02399I; and that the job completes with a
      condition code of zero.

___7. Regenerate each MTI Component.

      *******************************************************
      *                                                     *
      *  Repeat this step for each MTI component. To        *
      *  identify MTI components, run the MICF Shared       *
      *  Inquiry MTILD5 (Defined MTI Components).           *
      *                                                     *
      *******************************************************

      Edit sharedprefix.MICS.CNTL(cccCGEN).  Make sure that
      the INPUTCSV DD contains the proper data sets.  Verify
      with the daily jobs in all units containing MTI
      component ccc.

      Submit the job in sharedprefix.MICS.CNTL(cccCGEN).

      Ensure that there are no error messages in ISPLOG and
      MICSLOG; that MICSLOG contains the normal termination
      messages, BAS20999I; and that the job completes with a
      condition code of zero.