Previous Topic: 5.3.3.2 Elements List

Next Topic: 5.3.4 IDMS System Incident File (IDMSIN)

5.3.3.3 Usage Considerations


This section identifies usage considerations and techniques
for accessing the IDMS System Calendar File (IDMSCL).

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.

This file is designed to contain the most important data
elements for quickly evaluating IDMS general performance
tuning.  Reports produced from these data are best viewed in
the format provided, the SAS Calendar procedure.  Although
you can perform some of your own reporting by accessing this
file, note that the DAYS timespan contains only one cycle.
The DAYS level cycle is updated with each database update run
so that the IDMSCL01 file will eventually contain an entire
month's information.

This file is delivered with only the DAYS timespan turned on.
If you attempt to turn on any timespan higher than DAYS, the
IDMCGEN will automatically turn that timespan off.  This was
done because this file does not contain valuable information
at any timespan higher than DAYS.

If this file is turned on in the DAYS timespan and you have
the DAYS timespan of the IDMSSY file turned off, your IDMCGEN
will fail.  This will occur because this file is dependent
upon the DAYS timespan of the IDMSSY file.  In order to
correct the problem, you must either turn this file off in
the DAYS timespan or turn on the IDMSSY file in the DAYS
timespan.  If changes were made, you must rerun the IDMCGEN
job.

The DURATION data element represents the elapsed time of the
individual transaction records in the IDMSCL 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.