5. FILES › 5.3 IDMS Information Area Files › 5.3.2 IDMS Application Unit Activity File (IDMSAU) › 5.3.2.3 Usage Considerations
5.3.2.3 Usage Considerations
This section identifies usage considerations and techniques
for accessing the IDMS Application Unit Activity File
(IDMSAU).
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 IDMSAU file is supplemental. It is identical in
structure to the IDMS User Activity (IDMSUA) file with two
exceptions:
o The IDMSAU file contains one additional level of
granularity provided by the user-defined IDMS Application
Unit Code (IDMAPU) data element.
o The IDMSAU file does not have the granularity provided by
the IDMACTn account code data elements. The absence of the
@@ACCT (IDMACT1-n) data elements reduces its granularity
when compared to the IDMSUA file.
This table shows the default summarization keys for the
IDMSAU and IDMSUA files:
IDMSAU File IDMSUA File
------------------------ ------------------------
SYSID 1 SYSID 1
IDMSID 2 IDMSID 2
IDMAPU 3 @@ACCT 3
IDMTYPE 4 IDMTYPE 4
YEAR 5 YEAR 5
... other time-related keys ... other time-related keys
Note that the @@ACCT placeholder represents the user-defined
IDMACT1 to IDMACTn account code data elements.
Deactivation of the IDMSAU supplemental file can save
significant DASD space. If the IDMSAU 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 supplemental IDMSAU file can be captured by using the
IDMS account code derivation routine to customize the IDMSUA
file. To accomplish this, update the IDMS account code
derivation routine to populate an 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 IDMSAU 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.
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.
For reports or analysis requiring the level of summarization
provided by the supplemental IDMSAU file, you can resummarize
the IDMSUA file to remove the influence of the IDMACTn
account code data elements (except the one that contains the
IDMAPU value). To resummarize, use the %SUASUM macro with a
SAS BY statement that contains all of the summarization keys
appropriate for the timespan, except the IDMACTn data
elements that serve as account codes. You do want to include
the IDMACTn data element that contains the IDMAPU value.
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 IDMSAU 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.
