5. FILES › 5.3 IDMS Information Area Files › 5.3.1 IDMS Application Unit Counts File (IDMSAC) › 5.3.1.3 Usage Considerations

5.3.1.3 Usage Considerations

This section identifies usage considerations and techniques
for accessing the IDMS Application Unit Counts File (IDMSAC).

Using the special date and time data elements requires
special care.  As the file's granularity increases in higher
timespans, certain fields lose significance and should not
be used, namely:

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

The IDMSAC file is supplemental.  It is identical in
structure and content to the IDMS User Activity File (IDMSUA)
with one exception.  The IDMSAC file contains an additional
level of granularity provided by the user defined IDMS
Application Unit Code (IDMAPU) data element.

As you can see in the following table of default
summarization keys for the IDMSAC and IDMSUA files, the
IDMAPU data element adds granularity to the IDMSAC file.

        IDMSAC File                    IDMSUA File
----------------------------     ---------------------------
SYSID       1                    SYSID         1
IDMSID      2                    IDMSID        2
@@ACCT      3                    @@ACCT        3
IDMAPU      4                    IDMTYPE       4
IDMTYPE     5                    YEAR          5
YEAR        6                    ... other time related keys
... other time related keys

Note that the @@ACCT placeholder represents the user-defined
IDMACT1-IDMACTn account code data elements.

Deactivation of the IDMSAC supplemental file can save
significant DASD space.  If the IDMSAC file is active, and
DASD space is a concern at your site, you should consider
deactivation of this file.  The same information contained in
the IDMSAC file can be represented in the IDMSUA file by
using the IDMS account code derivation routine.  To
accomplish this, enhance your IDMS account code derivation
routine to populate an additional IDMACTn summarization key
data element with the value of the IDMS Application Unit Code
(IDMAPU) data element.  Refer to Section 7.2.2 of this guide
for information on defining IDMS account codes.

If you make this modification (deactivating the IDMSAC file
and adding an IDMACTn data element that contains the value of
the IDMAPU data element), your IDMSUA file will increase in
the number of observations at the DAYS and higher timespans.
It will, in fact, become as granular as the deactivated
IDMSAC file.  For reports and analysis that depend on the
summarization granularity of the IDMSUA file without the
influence of IDMAPU, you can simply resummarize the IDMSUA
file.  Use the %SUASUM macro with a SAS BY statement that
contains all of the summarization keys except the IDMACTn
data element containing the value of IDMAPU.  Refer to
Section 6.3.2.3 of the CA MICS System Modification Guide for
information on resummarizing files using the %fffSUM macros.

The DURATION data element represents the elapsed time of the
individual transaction records in the IDMSAC file.  In
summarized timespans, DURATION represents the sum of DURATION
of the individual transaction records that contributed to the
summarized observation.  DURATION is calculated as the
difference between the End Time (PMHETIME) and the Start Time
(PMHSTIME) fields from the CA-IDMS Performance Monitor header
record.

In all IDMS Analyzer files except the IDMSIN file, the
STARTTS and ENDTS data elements do not reflect the Start Time
and End Time of the individual transactions.  Instead,
STARTTS and ENDTS are adjusted to represent the start and end
of the time interval within which the transactions executed.