In some cases, the amount real storage occupied by an application can be influenced by the app itself. When we were rolling out DB2 V10, one smallish LPAR ran so short of real storage that it crashed. I even added some real storage to no avail. IBM finally recommended changes to DB2 run-time parms, and the problem went away.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Doug Henry Sent: Tuesday, August 04, 2015 8:56 AM To: [email protected] Subject: Re: Limit number of frames of real storage per job On Tue, 4 Aug 2015 14:13:57 +0000, Vlcek, Vitezslav Vit <[email protected]> wrote: >Hi > >I would like to ask more experienced sysprogs regarding real storage manager. > >Is it possible to limit number of frames of real storage on job level? The >MEMLIMIT/REGION parameters limit virtual memory of whole address space however >I would like to limit the only real memory while the virtual memory remain as >it is. > As others have told you it is at the system level. One way to this is to use a program to pagefix a large amount of frames to a utility job and then you can cause paging for your test job. Of course this should be done on a sandbox lpar. Check out CBT Tape file 19 PAGEFIX This utility allows an installation to * FILE 019 //* effectively dynamically remove storage * FILE 019 //* from the system. This can be either to * FILE 019 //* reserve it for some future use or to * FILE 019 //* determine the effects that a major new * FILE 019 //* application may have on paging. * FILE 019 //* * FILE 019 Doug ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
