It says REGION=512M to scan up to 100 modules.  How many modules are you 
scanning?  Does it work with 10 modules, or 1?

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Wayne Bickerdike
Sent: Tuesday, January 08, 2019 1:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Generic query on Region allocation failure

We keep seeing S106 abends trying to run DFHEISUP utility.

It's been discussed a few times on various fora but no definitive solution yet.

At CICS 5.2 it ran fine.5.3 it's hit and miss and 5.4 just plain doesn't  work.

All permutations of region size, MEMLIMIT=NOLIMIT, no IEFUSI have worked.
Tried on 4 different systems. No joy. PMR time..


On Wed, Jan 9, 2019 at 6:19 AM Carmen Vitullo <cvitu...@hughes.net> wrote:

> A good point, I myself have overlooked STC's region size because it's
> never been a problem, I see some tasks never updated for 10+ years and
> still have very small regions sizes.
>
>
>
>
> Carmen Vitullo
>
> ----- Original Message -----
>
> From: "Jesse 1 Robinson" <jesse1.robin...@sce.com>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Sent: Tuesday, January 8, 2019 1:13:14 PM
> Subject: Re: Generic query on Region allocation failure
>
> This post is not intended to be enlightening; it's merely corroborative.
> We recently went from z12EC to z14. We had already upgraded to z/OS
> 2.3 with hardware support service. In the week or so afterwards, we
> experienced a handful of 'storage shortage abends' in tasks that had
> been running unchanged for years. AFAIK no technical explanations ever
> came forth. In the few PMRs we opened, the advice was to increase region 
> size. We did.
> Problems went away. Move on.
>
> I do have one piece of advice. Never specify a smallish region size.
> If it's worth your time and effort to type in any region size at all,
> go for some number >16M. It generally costs nothing and may save some
> debugging grief down the road. I've seen cases where 0M may be
> required for a particular product. Again, the cost of doing so is minimal. 
> Why quibble?
> Someone needs to refresh the communal coffee pot.
>
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-543-6132 Office ⇐=== NEW
> robin...@sce.com
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Tom Marchant
> Sent: Tuesday, January 08, 2019 7:49 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: Generic query on Region allocation failure
>
> On Tue, 8 Jan 2019 10:16:00 +0400, Jake Anderson wrote:
>
> >IEF085I REGION NOT AVAILABLE ERROR CODE = 20 IEF187I NNNNNJJJ FAILED
> >- SYSTEM ERROR IN INITIATOR IEF472I NNNNNJJJ
>
> That means that the region that was specified is not available.
>
> Most likely, the region specified is less than 16M and that much
> storage is not available below the line. It is certainly possible that
> the available region size below the line is smaller on your old system
> than is available on your new system.
>
> --
> Tom Marchant
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


--
Wayne V. Bickerdike

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DISCLAIMER: This email and any attachments may contain confidential information 
that is intended solely for use by the intended recipient(s). If you are not 
the intended recipient, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the communication. If 
you received this email in error, please contact the sender by reply email and 
immediately delete the communication.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to