Re: PL/1 Storage Control Issue
- From: ukr@xxxxxxxxxxx (Ulrich Krueger)
- Date: 10 Dec 2007 09:06:16 -0800
Rick,
I'm sorry, I can't give you the PL/1 - internal info you asked for, but I
can perhaps give you a quick fix for your problem:
Years ago, in the early days of LE, I also had a memory-hungry program that
liked to abend S878 during CLOSE after hours of run time. The quick and
dirty solution was to add a runtime PARM LE - override to "force" working
storage into 31-bit territory:
PARM='/HEAP(16M,1M)'
LE defaults call for small memory allocation amounts which typically end up
in 24-bit storage and don't continue above the line when 24-bit region runs
out.
To see your LE options in effect, use
PARM='/RPTSTG(ON),RPTOPTS(ON)'
Try it with and without the HEAP parm added to see the difference. The
storage and options reports go to //SYSOUT DD, which you may have to add to
your JCL.
HTH
Regards,
Ulrich Krueger
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@xxxxxxxxxxx] On Behalf
Of Rick Fochtman
Sent: Monday, December 10, 2007 08:37
To: IBM-MAIN@xxxxxxxxxxx
Subject: PL/1 Storage Control Issue
Can anyone point me to a reference that describes in detail the various
storage control blocks used by PL/1 in managing BASED storage entities?
I have an application that's running out of storage, supposedly, far too
soon, even with REGION=0M. The number of entities that lead to failure
leads me to believe that the BASED elements are all being held in 24-bit
addressable storage. This is NOT a UNIX-style application, if that makes
any difference. The compiler is IEL00.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- References:
- PL/1 Storage Control Issue
- From: Rick Fochtman
- PL/1 Storage Control Issue
- Prev by Date: Re: PL/1 Storage Control Issue
- Next by Date: Re: Problems with checks IXGLOGR_*
- Previous by thread: Re: PL/1 Storage Control Issue
- Next by thread: Re: PL/1 Storage Control Issue
- Index(es):
Relevant Pages
|
|