4. EXCEPTIONS › 4.3 Detailed Exception Descriptions › 03059: Program Working Set Size Exceeded Limit

03059: Program Working Set Size Exceeded Limit

FILE:             Batch User Program Activity
SAS FILE NAME:    DETAIL.BATPGM01
SOURCE LOCATION:  prefix.MICS.USER.SOURCE.(DYSMFEXC)

SEVERITY:  Warning              (SEVERITY='W')
MANAGEMENT AREA:  Workload      (MGMTAREA='WORKLOAD')

PURPOSE:  Identifies programs which utilized a large working
set size.

RATIONALE:  Programs which utilize a large working set size
may have a serious impact on available real storage.
Depending on the mix of other tasks and also the availability
of real storage frames, such jobs could precipitate a
significant increase in demand paging and swapping activity.
Programs that specify V=R usually show up in this test.  They
should be examined to determine if the need for real storage
only is legitimate.

DEFINITION:  This exception is detected when a program's
working set size exceeds the installation-defined value.

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

*
** 03059
** PROGRAM WORKING SET SIZE EXCEEDED LIMIT
*;
IF PGMEXCTM > execution-time AND PGMMXWSS > working-set-size
 THEN DO;
  MGMTAREA='WORKLOAD'; EXCCODE='03059'; SEVERITY='W';
  EXCDESC1=
     'PROGRAM WORKING SET SIZE EXCEEDED LIMIT';
  EXCDESC2='WORKING SET SIZE=' || PUT(PGMMXWSS,5.);
  LINK HIT;
END;

THRESHOLD MODIFICATION:     Modify the values used for
execution-time and working-set-size as follows:

    execution-time - The target execution time.  A threshold
       of 5 minutes of execution time appears as:

          PGMEXCTM > HMS(00,05,00)

    working-set-size  -  The working set size in 4K frame
       units.  A threshold of 200 (representing 800K bytes)
       appears as:

          PGMMXWSS > 200