Check MAXASSIZE in BPXPRMxx
Check Check ASSIZEMAX and MEMLIMT in the OMVS segment for the UID in question

HTH,

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Carmen Vitullo
Sent: Monday, November 19, 2018 8:03 AM
To: [email protected]
Subject: Re: Region size for OMVS tasks

do you have a MEMLIMIT in the SMFPRMxx member ?



Carmen Vitullo

----- Original Message -----

From: "Sean Gleann" <[email protected]>
To: [email protected]
Sent: Monday, November 19, 2018 7:51:04 AM
Subject: Region size for OMVS tasks

We have a problem here that is proving to be … um... "resistant to analysis" & 
I wonder if anyone on this list might be able to help.

Most of our developers submit work to the system from a PuTTY session, that 
will result in multiple OMVS tasks being fork()ed or spawn()ed. Of late, such 
work has been failing with messages:
IEW4000I FETCH FOR MODULE xxxxxxxx FROM DDNAME SYS00061 FAILED BECAUSE 
INSUFFICIENT STORAGE WAS AVAILABLE.
- and -
CSV031I LIBRARY ACCESS FAILED FOR MODULE xxxxxxxx, RETURN CODE 14, REASON CODE 
26110021, DDNAME SYS00061 which basically, as far as I can make out, mean that 
my region size is too small.

But these are OMVS tasks, where a REGION size specification isn't allowed for.
If I look at the type-30 records for the failing tasks, I see that the 'region 
requested' value is 54M in each case.
We don 't have any SMFLIMxx member defined, so there's nothing coming from 
there, since that PARMLIB member *must* be defined if it is to be used - there 
are no defaults.
Our IEFUSI is the default 'stub' supplied with the BCP i.e. all it does is the 
equivalent of a 'BR 14', so that isn't limiting anything either.
So where is that 54M value coming from? How can I modify it?

Regards
Sean

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN
::DISCLAIMER::
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to