Re: Internal Reader Resources Jes 1.7
does anyone know how much storage is allocated per reader within the a/s ? I'm curious about CICS regions and user's running amuck with job submissions -- 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
Internal Reader Resources
I remember seeing cautions on this list that SYSOUT=(,INTRDR) be used with restraint because of resource constraints. So: o What resource(s)? o How many INTRDRs can (typically) be active concurrently? o Can an installation modify the limit? What are the costs of doing so? o Are the resource(s) occupied from ALLOCATE until FREE, or merely from OPEN until CLOSE? -- gil -- StorageTek INFORMATION made POWERFUL -- 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
Re: Internal Reader Resources
This answer is based on the last time I looked (it may be different for current versions of JES2 that I don't have) 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, although I think you can use FREE=CLOSE to make sure it's freed when closed. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 I remember seeing cautions on this list that SYSOUT=(,INTRDR) be used with restraint because of resource constraints. So: o What resource(s)? o How many INTRDRs can (typically) be active concurrently? o Can an installation modify the limit? What are the costs of doing so? o Are the resource(s) occupied from ALLOCATE until FREE, or merely from OPEN until CLOSE? -- 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
Re: Internal Reader Resources
Note that RDINUM is not supported at z/OS 1.7. Craig -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tim Hare Sent: Wednesday, November 29, 2006 10:13 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Internal Reader Resources This answer is based on the last time I looked (it may be different for current versions of JES2 that I don't have) 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, although I think you can use FREE=CLOSE to make sure it's freed when closed. Tim Hare -- 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
Re: Internal Reader Resources
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? -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? -- gil -- StorageTek INFORMATION made POWERFUL -- 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
Re: Internal Reader Resources
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
Re: Internal Reader Resources
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
Re: Internal Reader Resources
On Wed, 29 Nov 2006 18:44:50 -0500, Bob Rutledge wrote: It happened in z/OS JES2 1.7. Which we happen to have in production (such as production is in a development shop). 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. Excellent! It appears to be a move to a Right Design -- one more static limit removed. I know nothing useful about JES3. But you might even so know a great deal. -- gil -- StorageTek INFORMATION made POWERFUL -- 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
Re: Internal Reader Resources
The Init Ref manual says it was removed with 1.7. I hope someone else can explain the ramifications. Craig -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Wednesday, November 29, 2006 6:07 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Internal Reader Resources 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? -- gil -- -- 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
Re: Internal Reader Resources
On Nov 29, 2006, at 7:35 PM, Paul Gilmartin wrote: -SNIP- 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. Excellent! It appears to be a move to a Right Design -- one more static limit removed. SNIP-- Does anyone know why IBM did it this way? Was it a user requirement or was there some other reason. DON'T get me wrong I like it but it would be nice to know why. Call me curious. Ed -- 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
Re: Internal Reader Resources
While I don't know all the details, from what I have heard, this was done as part of the restructuring required to implement NJE over native TCP/IP. Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ed Gould Sent: Wednesday, November 29, 2006 10:08 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Internal Reader Resources On Nov 29, 2006, at 7:35 PM, Paul Gilmartin wrote: -SNIP- 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. Excellent! It appears to be a move to a Right Design -- one more static limit removed. SNIP-- Does anyone know why IBM did it this way? Was it a user requirement or was there some other reason. DON'T get me wrong I like it but it would be nice to know why. Call me curious. Ed -- 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 -- 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
