5. FILES › 5.2 IMS Information Area Files › 5.2.1 IMS System Activity File (IMSISY) › 5.2.1.3 Usage Considerations

5.2.1.3 Usage Considerations

This section identifies any special considerations or
techniques related to using the IMSISY 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 only have meaning when using
    the IMSISY file in the DETAIL timespan as they lose
    significance once summarization has been performed.
    Reference these data elements only when using the IMSISY
    file in the DETAIL timespan.

      ISYCIPSZ - Size of CIO Pool
      ISYCIPUS - Current Amount Allocated From CIO Pool
      ISYDLCKP - Checkpoints Since System Start
      ISYDMBSZ - Size Of Dmb Pool
      ISYDMBUS - Current Amount Allocated From DMB Pool
      ISYPSBSZ - Size of PSB Pool
      ISYPSBUS - Current Amount Allocated From PSB Pool
      ISYDPSSZ - Size Of DPSB Pool
      ISYDPSUS - Current Amount Allocated From DPSB Pool
      ISYWPSSZ - Size of PSBW Pool
      ISYWPSUS - Current Amount Allocated From PSBW Pool


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

      ISYPETTM - Pseudo Elapsed Time
      ISYSRU   - System Resource Units
      ISYCOST  - Processing Charges

3.  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:

      ISYCPUNI - Instructions Executed

4.  Be careful using the special date and time data elements
    contained in each CA MICS file. As the IMSISY 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 and YEARS.
      o  DAY and DAYNAME should not be used in WEEKS,
         MONTHS, or YEARS.
      o  WEEK should not be used in MONTHS or YEARS.
      o  MONTH should not be used in YEARS.

5.  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.

6.  The data elements STARTTS and ENDTS have special meanings
    when used in the DETAIL timespan.  Their purpose in the
    DETAIL timespan is described below:

      o  STARTTS represents the start time of the interval of
         time that the IMS checkpoint covers.  This time
         stamp comes from either the end time stamp of the
         previous checkpoint, if there was one, or from the
         first recognized event for the system being
         processed, if there was no previous checkpoint for
         that system.  Such an event is typically an IMS
         start or IMS log switch.

      o  ENDTS represents the time stamp on the last IMS log
         checkpoint record processed for the interval, in IMS
         log record type '40', subtype '98'.

7.  Response time statistics, distributions, and their
    percentages are not maintained in the DETAIL timespan of
    the IMSISY file.


Retrieval Examples

1.  Create a pie chart that shows the relative
    occurrences of various reasons for scheduling
    conflicts.  Use month-to-date data.

    DATA TEMP (KEEP= REASON COUNT);
    SET &PIMSM..IMSISY00 END=EOF;
    LENGTH REASON $8;
      REASON = 'PROGRAM '; COUNT = ISYSIPGM; OUTPUT;
      REASON = 'DATABASE'; COUNT = ISYSIDBI; OUTPUT;
      REASON = 'PRIORITY'; COUNT = ISYSICUT; OUTPUT;
      REASON = 'OTHER   '; COUNT = ISYSIOTH; OUTPUT;
    RUN;
    PROC CHART DATA=TEMP;
    PIE REASON / SUMVAR = COUNT;
    TITLE IMS TRANSACTION SCHEDULING CONFLICTS;

2.  Generate a vertical bar graph of the transaction
    scheduling rate by hour for yesterday.

    PROC CHART DATA=&PIMSD..IMSISY01;
    VBAR HOUR / SUMVAR = ISYPSSCD DISCRETE NOSPACE;
    TITLE IMS SCHEDULING RATE BY HOUR;