Paul Gilmartin wrote:
In a recent note, Kittendorf, Craig said:
Date: Wed, 29 Nov 2006 17:10:27 -0500
Note that RDINUM is not supported at z/OS 1.7.
??? Before or after? And does this mean that for the release(s)
for which it's not supported that there's no limit, or that the
limit is hard-coded in JES2 (what about JES3?) and not subject
to configuration?
It happened in z/OS JES2 1.7.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Tim Hare
Sent: Wednesday, November 29, 2006 10:13 AM
The number of internal readers is set in JES2 by the RDINUM parameter on
the INTRDR statement. That's the limit. I don't see documentation
allowing RDINUM to be set by the $SET INTRDR command. As with any other
SYSOUT file, the resources are in use from ALLOCATE until FREE,
And now I'm puzzled again. If an INTRDR uses resources in a way
similar to any other SYSOUT file, why is (was/will be) there a
specific limit for INTRDRs, and not a limit for all SYSOUT files
in aggregate?
>
From the "z/OS Version 1 Release 7 Implementation" Redbook:
"The INTRDR RDINUM= initialization statement is no longer needed. Internal
Reader processing now occurs in the allocating address space, and there is no
need to pre-allocate data areas."
(Which is one of the reasons for the JES2 exit changes in that release.)
I know nothing useful about JES3.
Bob
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
