2. Administrative Information Area Files › 2.1 Exception Activity File › 2.1.3 Usage Considerations

2.1.3 Usage Considerations

This section identifies any special considerations or
techniques related to using the ADMEXC file.  Additionally,
several sample retrieval examples are provided to facilitate
the use of 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 data element 'ID' contains the TSO userid or the
        batch jobname, for a TSO or batch based exception
        respectively.

    2.  The following data elements only have meaning when
        using the ADMEXCnn file in the DAYS timespan in that
        they lose significance once summarization has been
        performed.  These data elements should only be
        referenced when using the ADMEXCnn file in the DAYS
        timespan.

        EXCDESC2 - Exception Values Text

    3.  Care must be exercised in using the special date and
        time data elements contained in each CA MICS file. As
        the file's granularity increases in higher Timespans
        certain fields lose significance and should not be
        used in those cases.

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

    4.  The ENDTS and STARTTS, when appearing in the
        MONTHS Timespans, bounds the span of time
        over which the data has been summarized with STARTTS
        being the lowest date and time and ENDTS the highest
        date and time for the data summarized.  The data
        elements STARTTS and ENDTS have different meanings
        when used in the DAYS Timespan with their
        purpose described below:

        o  STARTTS is not supported in this File.
        o  ENDTS represents the ENDTS of the record from
           which the exception was detected.

    Retrieval Examples

    1.  Retrieve the detail exceptions identified yesterday:

        DATA;
        SET &PADMD..ADMEXC01;
        PROC PRINT; VAR SYSID ENDTS ID EXCCODE EXCDESC1;

    2.  Report the number of exceptions by user for the last
        two months.

        DATA;
        SET &PADMM..ADMEXC01 &PADMM..ADMEXC02;
        PROC FREQ; TABLES ID*EXCCODE;

    3.  Retrieve the detail exceptions processed yesterday:

        DATA;
        SET &PADMD..ADMEXC01;
        ENDDT=DATEPART(ENDTS);
        IF ENDDT=TODAY()-1;
        PROC PRINT; VAR SYSID ENDTS ID EXCCODE EXCDESC1;