Peter,
I have found plenty of places where the discussion is about DB2's DBM1 and
IRLM address spaces. Those ignore any MEMLIMIT setting and set this limit to
values defined in DB2.
I could not find anything related to the utility program DSNX9WLM regarding
MEMLIMIT. Waiting for an
Barbara Nitz wrote:
I don't think that this is written down anywhere.
Except for modify command for IRLM - F IRLM,MLT = valueunit
I also don't see anything for other DB2 address spaces.
Just look at the memlimit column in SDSF DA, you'll see exactly which address
spaces have adopted this
Check the archives, I seem to have a dim memory that we discussed this here
and I got bashed when I objected to such a practise.
Thanks Barbara. I've got that hint yesterday, and was then checking the
archives. I have indeed found the threads you're talking about (and this is
what I
I'm with you Barbara: authorized code can be as impolite as it wants, but that
doesn't make it right.
Scott
On Thu, 30 Oct 2014 07:40:02 +0100, nitz-...@gmx.net nitz-...@gmx.net wrote:
Peter,
I have found plenty of places where the discussion is about DB2's DBM1 and
IRLM address spaces.
...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker
From: Peter Hunkeler p...@gmx.ch
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 29/10/2014 14:47
Subject:AW: Re: MEMLIMIT not honoured by DB2 utility job
Sent
://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker
From: nitz-...@gmx.net nitz-...@gmx.net
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 30/10/2014 06:40
Subject:Re: AW: Re: MEMLIMIT not honoured by DB2 utility job
Sent by:IBM Mainframe Discussion List IBM-MAIN
Isn't DSNX9WLM the program for DB2 Stored Procedures server address spaces?
And not a DB2 Utility program?
Yep, I wrote that in the initial post.
--Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access
Some hints:
REGION=0 means ignore MEMLIMIT.
I understand that specifying REGION=0K/M and *not* specifying MEMLIMIT (and not
having IEFUSI limiting it) implies MEMLIMIT=NOLIMIT. But if MEMLIMIT *is*
explicitly specified, it will be honoured and REGION=0K/M does not have any
influence in
Pretty sure that I read somewhere that DB2 has been written to ignore
memlimit.
Thanks. Will try to find this in DB2 docs.
--Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
W dniu 2014-10-29 o 15:10, Peter Hunkeler pisze:
Some hints:
REGION=0 means ignore MEMLIMIT.
I understand that specifying REGION=0K/M and *not* specifying MEMLIMIT (and not
having IEFUSI limiting it) implies MEMLIMIT=NOLIMIT. But if MEMLIMIT *is*
explicitly specified, it will be honoured and
Pretty sure that I read somewhere that DB2 has been written to ignore
memlimit. Thanks. Will try to find this in DB2 docs.
I have found plenty of places where the discussion is about DB2's DBM1 and IRLM
address spaces. Those ignore any MEMLIMIT setting and set this limit to values
defined in
Do you say that DFSORT will ignore MEMLIMIT?
Yes, and no.
I had problems with some DB2 ulitity (reorg) which use DFSORT under the
cover. It consumed to much virtual memory causing paging.
I set MEMLIMIT in the jobcard. After that the problem still occured, but
DFSORT, instead of using 64-bit
12 matches
Mail list logo
