You should have the PTFs for z/OS APAR OA17114 installed if you are
using paged fixed buffers in DB2 V8.   Not having it was one of the
causes of a z/OS outage here when a DB2 DBA accidently overcommitted
storage to DB2.

APAR Identifier ...... OA17114      Last Changed ........ 07/07/03
  IRA400E 04,PAGEABLE STORAGE SHORTAGE  HIGH VIRTUAL STORAGE
  FIXED IN "ABOVE" FRAMES INSTEAD OF "HIGH" FRAMES
 
  Symptom ...... MS MSGIRA400E        Status ........... CLOSED  PER
  Severity ................... 2      Date Closed ......... 07/05/31
  Component .......... 5752SC1CR      Duplicate of ........
  Reported Release ......... 720      Fixed Release ............ 999
  Component Name 5752 REAL STOR       Special Notice           HIPER
  Current Target Date ..07/06/15      Flags  RESTART/BOOT/IPL
  SCP ...................
  Platform ............
 
  Status Detail: SHIPMENT - Packaged solution is available for
                            shipment.
 
  PE PTF List:
 
  PTF List:
  Release 709   : UA34631 available 07/06/13 (F706 )
  Release 720   : UA34632 available 07/06/13 (F706 )
  Release 730   : UA34633 available 07/06/13 (F706 )
  Release 740   : UA34634 available 07/06/13 (F706 )


You should also need to educate your DBA's that they must confirm all
increases in DB2 bufferpool storage.  If they get any error they should
immediately back out whatever they did.

A DBA transposed some numbers in job and got DSNB542I but did not
immediately back out the changes. 

DSNB542I  -DB2P DSNB1ABP THE TOTAL ACTIVE PGFIX YES BUFFER POOL
STORAGE
           EXCEEDS THE DB2 ALLOWED REAL STORAGE CAPACITY
           WHEN EXPANDING STORAGE FOR BUFFER POOL BP24
           CURRENT VPSIZE = 400000
           NEW     VPSIZE = 2000000
           REAL STORAGE CAPACITY = 73728 MB.
DSN9022I  -DB2P DSNB1CMD '-ALT BPOOL' NORMAL COMPLETION


It would be useful if DB2 allowed an installation to set the percentage
to decline to allow buffer pools increases beyond rather than hard
coding 80%.

DSNB542I csect-name THE TOTAL ACTIVE PGFIX YES BUFFER POOL STORAGE
EXCEEDS
        THE DB2 ALLOWED REAL STORAGE CAPACITY WHEN EXPANDING STORAGE FOR

        BUFFER POOL bpname CURRENT VPSIZE = cbpsize NEW     VPSIZE =

        nbpsize REAL STORAGE CAPACITY = rsc MB.

 

 Explanation:  When expanding the VPSIZE for an active PGFIX YES buffer

 pool, DB2 detects that the total storage allocated for all active PGFIX

 YES buffer pools will exceed 80% of the real storage capacity on this
z/OS
 image. The ALTER BUFFERPOOL command fails and the buffer pool will

 continue to be active with the current VPSIZE value.

 

 The buffer pool attributes and real storage capacity are:

 

 bpname    The buffer pool name.

 

 cbpsize   The current VPSIZE for the buffer pool.

 

 nbpsize   The new VPSIZE that was specified on the ALTER BUFFERPOOL

           command.

 

 rsc       The real storage capacity of this z/OS image in units of

           megabytes (1 MB = 2**20 bytes).

 System Action:  The ALTER BUFFERPOOL command fails. The buffer pool

 continues to be active with the current VPSIZE.

 

 System Programmer Response:  Either allocate more real storage to this

 z/OS image, reduce the requested size of the buffer pool or use the
PGFIX 
 NO attribute.


        Best Regards, 

                Sam Knutson, GEICO 
                System z Performance and Availability 
                mailto:[EMAIL PROTECTED] 
                (office)  301.986.3574 
             
"Think big, act bold, start simple, grow fast..."

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Roland Schiradin
Sent: Wednesday, November 07, 2007 1:19 PM
To: [email protected]
Subject: Re: Real storage usage - a quick question

Hi Max, 

if you're going to V8 make sure the bufferpools are "pagefixed"
otherwise
DB2 have to do it for each I/O.  


Roland
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to