Yes, 1.7, the same one that caused me to redo several JES2 exits. I think we
both heard about that at the same Share session.
I can't imagine a system-wide limitation; I'd think address space limitations
would be either DYNAMNBR or TIOT size.
Bob
On 9/4/2015 11:43 AM, J O Skip Robinson wrote:
Wow. I was bowled over by the 'left us' comment. We still specify it even in
z/OS 2.1, but it seems indeed to have disappeared from the doc. Was that in 1.7
with the JES2 redesign? If there is no longer a defined limit, why would anyone
still have a system-wide problem?
.
.
.
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 Bob Rutledge
Sent: Friday, September 04, 2015 7:41 AM
To: [email protected]
Subject: Re: Submit job without messages
I believe RDINUM left us at the same time that internal reader processing left
the JES2 address space and moved to the address space of the requester.
Bob
On 8/29/2015 7:48 PM, J O Skip Robinson wrote:
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
