Previous Topic: 1.3 Reporting and Inquiry FacilitiesNext Topic: 1.5 Product Prerequisites


1.4 Files Overview

The use and contents of each CA MICS file in the IMS
Information Area is described below.  Figure 1-2 illustrates
the IMS Information Area's data sources and files.


o  System Activity File (IMSISY)

   This file quantifies total activity for the entire IMS
   system for all users and includes resource consumption,
   service, availability, and performance measures and is
   derived from the interval system activity records found in
   the IMS log.

o  User Activity File - Full Function (IMSISU)

   This file quantifies the resources consumed by each user
   executing each different IMS transaction type.  It
   provides service, load, access, and performance measures
   and is derived from the detailed transaction records found
   in the IMS log.  Where BMC MAINVIEW for IMS Online is
   used, this file contains records for both full function
   and Fastpath transactions.

o  User Activity File - Fastpath (IMS_IS)

   This file quantifies the resources consumed by Fastpath
   users.  It provides service, load, access, and performance
   measures and is derived from the detailed transaction
   records found in the IMS log.

o  Application Unit Activity File - Full Function (IMSIAU)

   This file quantifies the resources consumed by each
   application unit within IMS.  It provides service, load,
   access, and performance measures and is derived from the
   detailed transaction records found in the IMS log.  Where
   BMC MAINVIEW for IMS Online is used, this file contains
   records for both full function and Fastpath transactions.

o  Application Unit Activity File - Fastpath (IMS_IA)

   This file quantifies the resources consumed by each
   application unit within IMS.  It provides service, load,
   access, and performance measures and is derived from the
   detailed transaction records found in the IMS log.

o  User Application Unit Count File (IMSIAC)

   This file quantifies frequency of use, by IMS user, for a
   specific application unit in the days, months, and years
   timespans.

o  Incident File (IMSINC)

   This file quantifies interesting incidents that relate to
   the operation, performance, and integrity of the IMS
   system.  It is derived from the detailed transaction
   records found in the IMS log or BMC MAINVIEW for IMS
   Online.

o  BMC MAINVIEW for IMS Online Database Activity File
   (IMSIDB)

   This file quantifies the activity that happens on
   databases used by IMS transactions that are monitored by
   the BMC MAINVIEW for IMS Online Event Collector.  Because
   it contains a large volume of data, it is typically used
   only for special studies.

                                                 +--------------+--------------+
                                                 |      CA MICS IMS ANALYZER   |
                                                 +-----------------------------+
                      +-------------+-------------+-------------+-------------+-------------+-------------+------------+
                      |             |             |             |             |             |             |            |
            +---------+---------+   |   +---------+---------+   |   +---------+---------+   |   +---------+-------+    |
            |      System       |   |   |   User Activity   |   |   |   User Activity   |   |   | User Application|    |
            |      Activity     |   |   |       File        |   |   |       File        |   |   |      Counts     |    |
            |       File        |   |   |   Full Function   |   |   |     Fast Path     |   |   |       File      |    |
            |     (IMSISY)      |   |   |     (IMSISU)      |   |   |     (IMS_IS)      |   |   |     (IMSIAC)    |    |
            | Types 40 and 45   |   |   | Types 01, 03, 07, |   |   | Types 5901, 5903, |   |   | Types 01, 03,   |    |
            |                   |   |   | 08, 31, 35, 36,   |   |   | 5936, 5937, 5938, |   |   | 07, 08, 31, 35, |    |
            |                   |   |   | 5937, 5950, F900, |   |   | 5950, 5953, 5955  |   |   | 36, 5937, 5950, |    |
            |                   |   |   | FAF1              |   |   |                   |   |   | F900, FAF1      |    |
            +-------------------+   |   +-------------------+   |   +-------------------+   |   +-----------------+    |
                                    |                           |                           |                          |
                          +---------+---------+       +---------+---------+       +---------+---------+       +--------+--------+
                          |  Application Unit |       |  Application Unit |       |     Incident      |       |       IMF       |
                          |   Activity File   |       |   Activity File   |       |       File        |       |    Data Base    |
                          |   Full Function   |       |     Fastpath      |       |                   |       |  Activity File  |
                          |     (IMSIAU)      |       |     (IMS_IA)      |       |     (IMSINC)      |       |     (IMSIDB)    |
                          | Types 01, 03, 07, |       | Types 5901, 5903, |       | Types 06, 10, 14, |       | Type FAF1       |
                          | 08, 31, 35, 36,   |       | 5936, 5937, 5938, |       | 15, 16, 20, 21,   |       |                 |
                          | 5937, 5950, F900, |       | 5950, 5953, 5955  |       | 24, 40, 41, 42,   |       |                 |
                          | FAF1              |       |                   |       | 45, 4C, 69        |       |                 |
                          +-------------------+       +-------------------+       +-------------------+       +-----------------+

 Figure 1-2. IMS Information Area Structure