In two of our JES2 environments we use MOD-27s and in one other we use MOD-54s.
All three environments use TGSIZE=36. I don't recall when it changed to
TGSIZE=36, but it has been that way for years. We have not seen any issues
with either size volumes. As Dave mentioned don't forget to set
LARGEDS=ALLOWED.
$DSPOOLDEF
$HASP844 SPOOLDEF
$HASP844 SPOOLDEF BUFSIZE=3992,DSNAME=SYS1.CRS1.HASPACE,
$HASP844 DSNMASK=,FENCE=(ACTIVE=NO,VOLUMES=1),
$HASP844 GCRATE=NORMAL,LASTSVAL=(1999.164,06:34:51),
$HASP844 LARGEDS=ALLOWED,SPOOLNUM=64,CYL_MANAGED=FAIL,
$HASP844 TGSIZE=36,TGSPACE=(MAX=3339040,
$HASP844 DEFINED=1801635,ACTIVE=1637850,
$HASP844 PERCENT=41.9087,FREE=951447,WARN=80),
$HASP844 TRKCELL=3,VOLUME=OSSP
Thanks..
Paul Feller
AGT Mainframe Technical Support
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Richards, Robert B.
Sent: Wednesday, April 22, 2020 6:00 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 SPOOLDEF TGSIZE recommendation sought [EXTERNAL]
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 <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Jousma, David
Sent: Wednesday, April 22, 2020 6:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Richards, Robert B.
Sent: Wednesday, April 22, 2020 6:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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
lists...@listserv.ua.edu 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
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
Please note: This message originated outside your organization. Please use
caution when opening links or attachments.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
