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
