Using the Interval Monitor › Program Pool Detail (PF15)

Program Pool Detail (PF15)

 PM-Rnn.n SYSTEM71         CA, Inc.                  V71      08.348 16:10:53.25
 CMD-->                                                             Window : 02

   02 15:30 PPDT Program Pool Detail                                          >
 Pool Type           Pool     In   High    Pool   Pages Overlay Overlay Overlay
                     Size    Use  Water   Loads  Loaded  No_Use Pgm_Use  In_Use
 PROGRAM            53248  16384  16384       1       4       1       0       0
 REENTRANT         2936kB  390kB  390kB      36     779      36       0       0
 XA PROGRAM        204800      0      0       0       0       0       0       0
 XA REENTRANT      2680kB 1223kB 1223kB      93    2446      93       0       0

 PM-Rnn.n SYSTEM71         CA, Inc.                  V71      08.348 16:10:53.25
 CMD-->                                                             Window : 02

   02 15:30 PPDT Program Pool Detail                                       <
    Pool Type        Overlay Overlay Overlay    Load    Load    Pool    Pool
                      No_Use Pgm_Use  In_Use   Waits    Time   Waits    Time
    PROGRAM                1       0       0       0  .0000S       0  .0000S
    REENTRANT             36       0       0       0  .0000S       0  .0000S
    XA PROGRAM             0       0       0       0  .0000S       0  .0000S
    XA REENTRANT          93       0       0       0  .0000S       0  .0000S

Screen Description

The Program Pool Detail screen displays statistics related to the use of program pools for the current interval. The screen includes one line for each program pool defined to the DC/UCF system. For each program pool, the screen identifies the pool size and provides access statistics.

Using This Screen

To request the Program Pool History screen, press [PF9].

What To Look For

• Look for non-zero values in the Overlay In Use field or the Pool Waits field. A non-zero number indicates the pool was very fragmented, and tasks had to wait until enough contiguous space became available to load a program. When these conditions occur, try these tuning options:
  • Expand the pool size. If you don't have enough space, try reducing the size of another program pool or try reducing the MAX TASK and MAX ERUS parameters.
  • Make heavily used reentrant or quasi-reentrant programs resident.
  • Reduce the size of modules in your programs to reduce concurrent demand on the program pools. For example, don't use large subschemas for your application programs; use tailored subschemas instead.
• Compare the number of pages loaded (Pages Loaded) to the total number of loads (Pool Loads). If there are many pages loaded for only a few program loads, consider increasing the block size for the program load libraries and load areas. For example, a block size of 10Kb requires 20 I/Os to load a 200Kb program; a block size of 1Kb requires 200 I/Os to load the same program.