5. FILES › 5.2 IMS Information Area Files › 5.2.7 IMS Application Unit Activity File-Fast Path (IMS_IA) › 5.2.7.3 IMS_IA Usage Considerations

5.2.7.3 IMS_IA Usage Considerations

This section identifies any special considerations or
techniques related to using the IMS_IA file.  Additionally,
sample retrieval examples are provided to help you use this
file.


In the examples, a SAS macro variable is used to specify the
DDname part of the CA MICS file name. These macro variables
are a standard part of CA MICS and are available for all
files. The macro variable name has the form &diiit, where d
is the database identifier, iii is the information area
name, and t is the timespan.  For the examples, a database
identifier of P is used.  The identifier is installation
dependent, so you should find out what the identifiers are at
your installation.

Special Considerations/Techniques

1.  The following data elements are reserved in this record
    for future use:

      IAUPETTM - Pseudo Elapsed Time
      IAUSRU   - System Resource Units
      IAUCOST  - Processing Charges

2.  Use of the following data element is dependent upon the
    MIPS rate parameter of prefix.MICS.PARMS(SYSID).  Its use
    should be within the frame of reference of the option's
    definition:

      ISUCPUNI - Instructions Executed

3.  Be careful using the special date and time data elements
    contained in each CA MICS file. As the IMS_IA file's
    granularity increases in higher timespans, the following
    fields lose significance and should not be used in the
    case described:

      o  HOUR should not be used in MONTHS.
      o  DAY and DAYNAME should not be used in MONTHS.
      o  WEEK should not be used in MONTHS.

4.  The STARTTS and ENDTS, when appearing in the DAYS, WEEKS,
    MONTHS, or YEARS timespans, mark the span of time over
    which the data has been summarized, with STARTTS being
    the lowest (earliest) date and time and ENDTS the highest
    (latest) date and time.


Retrieval Examples

1.  Produce a frequency distribution chart of application
    units executed last week showing the number of times each
    executed.

    DATA TEMP (KEEP= IMSAPU IAUTRANS);
    SET &PIMSW..IMS_IA01;
       IF IAUTRANS GT 0  THEN OUTPUT TEMP;
    RUN;
    PROC FREQ DATA=TEMP;
    TABLES IMSAPU / NOROW NOCOL; WEIGHT IAUTRANS;
    RUN;


2.  Generate a horizontal bar graph of total database
    access by HOUR of the day using yesterday's data.

    PROC CHART DATA=&PIMSD..IMS_IA01;
    HBAR HOUR / SUMVAR = IAUDBTOT DISCRETE; RUN;