The name of the spool volume must match your spooldef parm. You can clip any volume to the 4 or 5 character prefix and place a spool volume on it. You can add volumes on the fly so long as the meet the criteria. My preference is for 4 character volume name in the JES2 Deck.
SPOOLDEF VOLUME=SPLXP then you can create volumes with the name of SPLXP0 - SPLXPZ (36 volumes). Or if your VOLUME=SPLX then SPLX00 - SPLXZZ could be created. JES2 today is very fast at formatting a new JES2 Spool space. And very fast at formatting a JES2 CKPT Dataset that you can walk your current environment, from-to. The JES2 manuals have good details on the care and feeding of JES2 CKPT and SPOOL Spaces. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Tuesday, March 21, 2017 8:20 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Spool file > > The best practice for JES2 Spool file is standalone. Never put anything on > the same volume as either the SPOOL Space or the CKPT datasets. > > That can lead to unintentional issues. > > Many shops in the past have tended towards multi-use volumes with JES2. This > is not recommended. > > With storage arrays, you can code a volume as a MOD9 (9GB, 10,017 Cylinders) > and only place the ckpt or the spool space (not both) on it. The array will > typically only hold the amount of storage on the mod9 as is allocated. It > does not hold the entire 10,017 cylinders when you only have a 60 cylinder > dataset on it. As the volume is grown - the array will allocate more space to > that device until it reaches its maximum size. > > So, in my shop we have the ckpt on MOD3s and the Spool space on MOD54s. The > MOD3s only use a small portion for the ckpt as the ckpt is under 1000 > cylinders. > The MOD54s are maxed out as I have allocated the entire amount to the Spool > space. > > So even though there could be 3339 cylinders allocated for the MOD3, I am > using barely 15% of that. So the volume is not very large even though it > could be. > > Or your shop could elect to create MOD1s - which is any size you wish to > define > - for your ckpt and spool space to be considered stand alone. > > When you start to mix files on volumes that should be dedicated - CA1 TMS, JES > Spool or JES ckpt - you can enq that volume and cause issues to those > products. > > > Worst case scenario you might encounter is the need to cold start jes2. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Joseph Reichman > > Sent: Tuesday, March 21, 2017 5:47 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Spool file > > > > Hi > > > > I'm having problems with my spool file > > > > SYS1.HASPACE > > > > > > It happens to be in the same pack as my parmlib And other important > > files > > > > I'm wondering can the spool file be on any pack ? > > > > Thanks > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
