You might find it easier to create one new spool volume to juggle output around. When you're all done, you can drop that temporary volume.
In general, output on a spool volume that prevents it from being taken offline (drained) is, as others have said, output that is viewed as 'active'. This could be long running tasks or something as simple as syslog. If you put a volume in draining status and then IPL each JES member (one at a time), you will most likely end up with a volume that be taken offline. That process is a PITA in practice, which is why IBM invented the spool migration function. You might, as I said above, find it easier to add a temporary volume to migrate to, then migrate back at the end. I don't recall seeing your actual motivation and goal for doing all this. I might help us give better advice. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gerhard Adam Sent: Tuesday, January 24, 2017 2:53 PM To: [email protected] Subject: (External):Re: Draining JES2 SPOOL volume Also, if the objective is simply to free the data to drain the spool volume, have you tried Spool Offload? Adam -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pew, Curtis G Sent: Tuesday, January 24, 2017 2:34 PM To: [email protected] Subject: Re: Draining JES2 SPOOL volume On Jan 24, 2017, at 4:12 PM, Gerhard Adam <[email protected]> wrote: > > Have you looked at, or tried the $MSPL command? I looked at it, but it didn’t fit what I was trying to do. -- Pew, Curtis G [email protected] ITS Systems/Core/Administrative Services ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
