On Mon, 5 Feb 2007 21:56:48 +0000, Ted MacNEIL <[EMAIL PROTECTED]> wrote:
>>I'd like to set SPOOLDEF DSNAME=SYS1.&SYSNAME..HASPACE as well as >CKPTDEF CKPT1=(DSNAME=SYS1.&SYSNAME..HASPCKPT > >If you're using shared SPOOL, then why would you? >If you're not sharing SPOOL, then who cares? > >- >Too busy driving to stop for gas! I'm looking for consistency. I don't mind the idea of the same VOLSER prefix for the different systems, but the idea of the same dataset name scares me! With SYS1.&SYSNAME..HASPACE, I *know* that I won't muck with Production. I read this: "The second time it happened, we were working on creating a one-pack system and tried to IPL it. The JES2 spool volume prefix was the same as the production system, so we created a new spool volume with SYS1.HASPACE for the new test system. However, we had a CHPID going from that system to most of our production DASD; at IPL time all those disks were brought online, and when JES2 did a cold start it formatted the spool on all the volumes which matched the prefix, including one of our production spool volumes. It took us a few hours to realize what was wrong with our production JES2, and then a few more hours doing the offload/reload. Most of the jobs were gone, though - and I had a lot of explaining to do the next day... " and thought that *not* using SYS1.HASPACE would be a good idea! ---------------------------------------------------------------------- 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
