Am I understanding this correctly? BUFSIZE is 3992 at your sites, so a TGSIZE of 30 says that JES2 will build each track group big enough to hold 30 buffers of 3992 bytes or 119760 bytes. How many 3390 tracks are required to hold this? I just checked ours, and we're set at a TGSIZE of 33 which I think happened before my time. Looking at the 3390 reference summary, my guess is that whoever set it figured that since the JES2 BUFSIZE is 3992, that the actual blocks are 3992 bytes, therefore 11 can fit on a track, so 3 tracks would equate to a TGSIZE of 33 for best utilization. I'm thinking that is probably an incorrect calculation and my setting is wasting space. Thoughts?
Thanks, Rex -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jousma, David Sent: Wednesday, April 22, 2020 6:27 AM To: [email protected] Subject: [External] Re: JES2 SPOOLDEF TGSIZE recommendation sought Yea, just getting my coffee too... Looks like TGSIZE is easy enough to make larger, no so much to make smaller....I guess if you are going to change, then make the change before you add the new volumes. Once formatted, it doesn't change? TGSIZE=nnn|30 Specifies the number (1-255) of JES2 buffers to be contained in a track group. JES2 uses this value to determine the number of tracks in a track group on each spool device. This is the default value for the number of track groups for each new spool volume added to the complex. Because the number of tracks in a track group will vary based on the track capacity of the device, the resultant value is rounded to the minimum integral number of tracks that can contain the specified number of buffers. If you specify TGSIZE=, it must contain a value from 1 to 255. Regardless of the value specified, the minimum resulting track group size is one track and the maximum is the smaller of 255 and the number of tracks in the first extent of the SYS1.HASPACE data set with the least number of tracks. Note: If you do not specify TGSIZE= as the same value on all members of the complex, JES2 might not use the value specified here for a new spool volume. Performance Considerations: Attempt to tailor the value of TGSIZE to fit the majority of the jobs in your system. SMF type 26 records can be used to assist your choice of a value for this parameter. Small values for TGSIZE= can cause an excessive number of track group allocations per job thus increasing processor overhead. For example, an IEFBR14 job requires 13 spool buffers for control blocks and JCL data sets; therefore, set the value of TGSIZE= greater than 13. Large values for TGSIZE= can waste spool space and unnecessarily increase seek time. Modification: Minimum action to modify is $T SPOOLDEF to increase and a JES2 cold start to decrease. _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Richards, Robert B. Sent: Wednesday, April 22, 2020 7:00 AM To: [email protected] Subject: Re: JES2 SPOOLDEF TGSIZE recommendation sought **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Dave, At your request! I should have provided it before...now where is that 2nd cup of coffee? Bob SPOOLDEF BUFSIZE=3992,DSNAME=SYS1.HASPACE,DSNMASK=, FENCE=(ACTIVE=NO,VOLUMES=1),GCRATE=NORMAL, LASTSVAL=(2007.287,19:42:13),LARGEDS=ALLOWED, SPOOLNUM=64,TGSIZE=24,TGSPACE=(MAX=2443200, DEFINED=1900575,ACTIVE=1900575, PERCENT=32.1218,FREE=1290076,WARN=80), TRKCELL=3,VOLUME=JESS -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jousma, David Sent: Wednesday, April 22, 2020 6:56 AM To: [email protected] Subject: Re: JES2 SPOOLDEF TGSIZE recommendation sought It would be helpful if you could post the output of a $DSPOOLDEF command. We run with mod-54's with no issues. Just make sure you code LARGEDS=ALLOWED $SPOOLDEF SPOOLDEF BUFSIZE=3992,DSNAME=SYS1.HASPACE,DSNMASK=, FENCE=(ACTIVE=NO,VOLUMES=1),GCRATE=NORMAL, LASTSVAL=(2007.294,12:08:34),LARGEDS=ALLOWED, SPOOLNUM=96,TGSIZE=30,TGSPACE=(MAX=2524640, DEFINED=1202032,ACTIVE=1202032, PERCENT=49.1162,FREE=611639,WARN=80), TRKCELL=3,VOLUME=JESD _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Richards, Robert B. Sent: Wednesday, April 22, 2020 6:49 AM To: [email protected] Subject: JES2 SPOOLDEF TGSIZE recommendation sought **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** For years, we have run with 3390-3 spool volumes and a TGSIZE=24. I am not sure when or why the default became 30 and why it was not changed in my shop. Probably the wisdom of it is not broke, do not fix it. Okay, so much for history. Shortly, there will be a push to go to all higher capacity spool volumes. At the moment, it looks like we are going to MOD-27s. What I am trying to determine is a better value for TGSIZE given the migration to the MOD-27s. TGSPACE has recently been tripled (still relatively small at 2.4 million). The rest of the numbers associated with SPOOLDEF are defaults. Any suggestions would be appreciated. If it matters, DS8886 DASD. Thanks in advance! Bob ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
