You can do a cold start on new volumes without touching your current volumes, so you do not have to lose any data, which should make it fairly easy to get approvals.
Depending on how much down time you can tolerate, there are a few different ways to do this. The easiest way is to use spool offload to extract all of the data from the current spools, and then reload the data after you have changed JES2 to point to the new spool set. The down side of this approach is that the spool offload/reload can take a lot of time with a large number of spool volumes. Another approach is to define a second JES2 subsystem pointing the current spool set, and change the primary JES2 to point to the new spool set. From there you can either transfer jobs on demand or just pass everything across. The second JES2 system can either be a secondary JES2 subsystem running on the same image as the primary, or it can be the primary JES2 on a sandbox MVS image, whichever is easier for you to configure. Check the archives or google for "secondary JES2" or poly-JES for more details. Good luck, /jack ----- Original Message ----- From: "Dorota Sorokulska" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Friday, July 07, 2006 2:23 PM Subject: Re: [IBM-MAIN] problem with spool volume serial > No, I've just gave up. Now I'm thinking, how to convince people to cold > start, in order to completely change the spool's volumes prefix (that > would be better for our naming conventions). And if they won't agree, I > will just cut the last letter from the prefix. > D. > ---------------------------------------------------------------------- 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
