4. EXCEPTIONS › 4.3 Detailed Exception Descriptions › 04006: CICS Application Exceeds Max Memory Limit

04006: CICS Application Exceeds Max Memory Limit

FILE:             CICS Application Unit Activity File
SAS FILE NAME:    DAYS.CICCAU01
SOURCE LOCATION:  prefix.MICS.USER.SOURCE(DYCICEXC)

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

PURPOSE:  Identifies those CICS applications whose memory was
greater than the installation-defined memory limit.

RATIONALE:  An installation can set a limit for maximum
memory usage.  Setting the limit this way recognizes the
importance of conserving CICS dynamic storage, since
monopolizing large amounts of storage for long periods of
time can lead to overall system degradation from
fragmentation and short-on-storage conditions.

DEFINITION:  This exception is detected when an individual
transaction's memory high-water mark exceeds the
installation's memory objective.

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.

************************************************************;
*
**  04006
**  CICS APPLICATION EXCEEDS MAX MEMORY LIMIT
*;
COREMAX=number-of-bytes;
IF CAUMEMHI > COREMAX
THEN DO;
EXCCODE='04006'; SEVERITY='W'; MGMTAREA='WORKLOAD';
EXCDESC1=
'CICS APPLICATION EXCEEDS MAX MEMORY LIMIT';
EXCDESC2= 'APPL=' || CICAPU ||
        ', MAX MEMORY USAGE=' ||
        PUT(CAUMEMHI,7.);
LINK HIT;
END;

THRESHOLD MODIFICATION:  Modify the value number-of bytes to
define your installation's memory limit according to the
following convention:

    number-of-bytes = The number of bytes of main memory
       which a typical transaction should not exceed.  A
       40,000 byte limit appears as:

          COREMAX = 40000;