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?
JES3 does not have any such limit. In JES3 the file is written to
the spool as output, then queued to a process that reads it and
processes it as an input file.
In HASP (I have not run JES2) if I remember correctly you defined
a number of INTRDR's and when you wrote to one the file was directly
processed as an input file. Since there were a limited number, they
could all be allocated in which case you couldn't get one.
I have no idea what is being done now.
Note that the JES3 scheme did have some problems. When we first
converted (mid 70's) we had a large number of students using the
system, and they were able to submit jobs very fast. The original
design locked the queue while it was being updated, and because of
the rate of submission the INTRDR had problems getting the lock.
We filled up the spool with jobs waiting for the INTRDR (of course
when the student didn't see his job he would just submit it again).
We ended up writing a dedicated reader that worked more like JES2's
and tied the system students used to submit jobs (WYLBUR) to it.
The JES3 team later redesigned this, and we were able to go back
to standard INTRDR's for WYLBUR.
--
Richard
----------------------------------------------------------------------
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
