I doubt the likelihood of transient "insufficient storage" fetch
failures after linklst activation, both because I have never seen an
instance and because it doesn't make logical sense that this should be
so unless there is an APARable bug in the linklist activate code.
Previously running address spaces should continue to use the old
linklist and activating a new linklist should be invisible to them.
Newly started address spaces should see the new linklist if they are
started after the new linklist is active, but this shouldn't happen
until after all the new linklist libraries have been allocated by the
system and appropriate LLA data has been built. If things are still in
transition and this process is not complete the new address space should
still get the old linklist.
If you dynamically force a running address space to use a newly
activated linklist, then IBM has repeatedly warned that there are some
cases where this could be detrimental to the health of the address space
or even to the health of the system, so if you do this you take your
chances and all bets are off; but on the rare occasions where this was
the lessor of two evils I have never seen a fetch failure much less
"insufficient storage" failures.
JC Ewing
On 10/22/2010 06:55 AM, Veilleux, Jon L wrote:
I am trying to find the specific reference, but I saw IBM entries stating that
there is a span of time after a second
linklist set is activated that there can be this type of fetch errors and yes
it does say that they are due to
insufficient storage.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Scott Rowe
Sent: Thursday, October 21, 2010 5:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Storage usage in a job
Yes, you may get load failures in that case, but the failure wouldn't say:
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABLE
On Thu, Oct 21, 2010 at 5:03 PM, Schumacher, Otto<otto.schumac...@hp.com>wrote:
If someone added a module into a library that is in the linklist and
by doing so caused the library to go into extents. You could start
getting load failures on modules.
Regards
Otto Schumacher
HP Enterprise Services
Infrastructure Specialist
Ahold Account
CICS& Capacity Technical Support
P.O. Box 6462
2000 Wade Hampton Blvd.
LC1-302
Greenville, South Carolina, 29606
Cell: 864 569--5338
Tel: 864 987-1417
Fax: 864 987-4500
E-mail: otto.schumac...@hp.com
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Tom Marchant
Sent: Thursday, October 21, 2010 3:30 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Storage usage in a job
On Wed, 20 Oct 2010 07:21:58 -0400, Veilleux, Jon L wrote:
By any chance did someone change the LINKLIST set recently without an
IPL? That can cause this error,
Can it? What kind of LinkList change are you thinking of? I've never
seen an error as a result of a proper linklist change, though you can
get I/O errors if you do things that you shouldn't. And an IPL should
not be necessary after a LinkList change. This is a failure to load a
module because of insufficient virtual storage.
--
Tom Marchant
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf
Of Phil Smith
Sent: Tuesday, October 19, 2010 10:11 PM
To: IBM-MAIN@bama.ua.edu
Subject: Storage usage in a job
We're doing some load testing, and running out of storage, but we
can't
figure out how to tell WHAT storage. Shortly before it blew off, the
REAL column in SDSF showed "120T". We're pretty sure that wasn't 120
terabytes; it seems to be T for Thousand. But that isn't a lot of memory?!
Here's the job output when it failed - does this offer any clues? Any
hints, or pointers to doc, are gratefully accepted!
EW4000I FETCH FOR MODULE EDCUZZZZ FROM DDNAME -LNKLST- FAILED BECAUSE
INSUFFICIENT STORAGE WAS AVAILABLE.
SV031I LIBRARY ACCESS FAILED FOR MODULE EDCUZZZZ, RETURN CODE 24,
REASON
CODE 26080021, DDNAME *LNKLST*
...
--
Joel C. Ewing, Fort Smith, AR jcew...@acm.org
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
