Indeed this is not an unlimited resource, but it's controllable. The limit is specified in JES2 parmlib INTRDR RDINUM=. I've never seen TSO SUBMIT cause an internal reader shortage, but we have had problems in the past with CICS applications, which would allocate internal readers in order to submit jobs. This occurred in so many regions that we would hit the defined limit. Solution: increase the limit.
I'm pretty sure that SUBMIT allocates and releases an internal reader for each execution. If a lot of tasks--TSO users, batch jobs, regions, whatever--are bogarting internal readers, then either increase the limit or have a chat with the hogsters. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ed Gould Sent: Saturday, August 29, 2015 8:02 AM To: [email protected] Subject: Re: Submit job without messages On Aug 29, 2015, at 1:12 AM, Tim Hare wrote: > Did not see this caveat, and I had some big troubles from this, so I > have to mention this: > > IF you allocate an INTRDR under TSO, you need to find a way to limit > how many concurrent users use it. Unless things have changed since I > retired, internal readers are _not_ an unlimited resource, there are > only so many defined in the system. If you have a lot of concurrent > users of your submit process and they use up _all_ of the internal > readers, then regular SUBMIT commands can start failing . Try using free+close on the allocate. Ed ---------------------------------------------------------------------- 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
