4. EXCEPTIONS › 4.3 Detailed Exception Descriptions › 02005: Detected Wait Swap Rate Exceeds Max

02005: Detected Wait Swap Rate Exceeds Max

FILE: Paging Activity File
SAS FILE NAME: DAYS.SCPPAG01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYRMFEXC)

SEVERITY: Critical             (SEVERITY='C')
MANAGEMENT AREA: Performance   (MGMTAREA='PERFORMANCE')

PURPOSE:  A high detected wait swap rate results from
unexpected delays and thus identifies performance degradation
periods.

RATIONALE:  A detected wait occurs when the System Resource
Manager (SRM) finds that a task that is already in memory
has been in wait state for several seconds.  The SRM usually
does not know why the task is waiting so it swaps out the
task rather than clearing the wait.  Thus, detected wait
swaps are undesired and should be investigated.  Some common
causes of detected wait swaps are reserves, locks, and
enqueues.

DEFINITION:  This exception is detected when the detected
wait swap rate exceeds the installation-defined maximum.

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:

**  02005 DETECTED WAIT SWAP RATE EXCEEDS MAX
*;
RATE=PAGDWS / DURATION;
IF RATE GT rate
 THEN DO;
  EXCCODE='02005'; SEVERITY='C'; MGMTAREA='PERFORMANCE';
  EXCDESC1='DETECTED WAIT SWAP RATE EXCEEDS MAX';
  EXCDESC2='SWAP RATE=' !! PUT(RATE,5.1) !! '/SEC';
  LINK HIT;
END;

THRESHOLD MODIFICATION:  The user should modify the rate
value according to the following convention:

rate - The maximum rate of detected wait swaps per second is
specified.  A rate threshold of 2 would appear as:

RATE GT 2