4. EXCEPTIONS › 4.3 Detailed Exception Descriptions › 00305: Supervisor Trace Table Too Small

00305: Supervisor Trace Table Too Small

FILE              TSO System Activity
SAS FILE NAME     DETAIL.TSOTSO01
SOURCE LOCATION   sharedprefix.MICS.SOURCE(DYTSOEXC)

SEVERITY          Impacting    (SEVERITY='I')
MANAGEMENT AREA   Performance  (MGMTAREA='PERFORMANCE')

PURPOSE      Indicates that the supervisor trace is not
             serving its purpose.

RATIONALE    Keeping a "trace table" within the MVS nucleus
             with entries that record supervisor events is
             very useful for system problem-shooting.  MVS
             system dumps can be difficult or impossible to
             analyze without the information available in the
             trace table.  Also, since so many different
             events are traced, a table smaller than a
             certain size can result in seeing only events
             which happened after the events of interest
             (e.g., RTM processing).

DEFINITION   Code is provided to note this exception when the
             following data element is found with a nonzero
             value:

            TSOXSTRX - Intvls When Supervisor Trace Too Small

             See Appendix B for more information on this
             data element.


EXCEPTION    The SAS statements identifying the exception
STATEMENTS   situation and describing the condition are
             stored in the source member named in SOURCE
             LOCATION and are described below:

************************************************************;
*
** 00305
** SUPERVISOR TRACE TABLE TOO SMALL
*;
IF TSOXSTRX > 0
 THEN DO;
  EXCCODE='00305'; SEVERITY='I'; MGMTAREA='PERFORMANCE';
  EXCDESC1='SUPERVISOR TRACE TABLE TOO SMALL';
   EXCDESC2=' ENDTS=' || PUT(ENDTS,DATETIME19.2);
  LINK HIT;
END;

THRESHOLD     Most likely, you will want to modify this
MODIFICATION  exception to only signal an exception for the
              opposite of how you usually run your systems.
              For example, if it is installation policy to
              run with trace on, you will want to generate an
              exception if trace is off.

              You may want to generate this kind of exception
              selectively based on SYSID.  However, for all
              your systems, you will probably want to keep
              the exception approximately the size of the
              trace table.