I've been following the saga of draining/halting spool volumes. That was our preferred method in the past. In this go-around we're short on time (no opportunity to migrate a software change), and R13 is already in place. I figured that $MSPL might actually be less risky here than bumping up against a known problem with an ancient process. Wanted broader confirmation. Thanks to all who replied.
. . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: "Vernooij, CP - SPLXM" <[email protected]> To: [email protected] Date: 07/10/2012 11:27 PM Subject: Re: Moving JES2 spool volumes Sent by: IBM Mainframe Discussion List <[email protected]> Before doing any actions against spoolvolumes, have a look at this Red Alert: http://www14.software.ibm.com/support/customercare/sas/f/redAlerts/20120 629.html Kees. "Skip Robinson" <[email protected]> wrote in message news:<ofd4cb9123.73e94e6d-on88257a37.007852a3-88257a37.00791...@sce.com> ... > We need to move an R13 JES2 MAS onto new spool volumes. R13 introduced the > $MSPL command to migrate/move spool dynamically. We have not used $MSPL. > Any advice? > > . > . > JO.Skip Robinson > SCE Infrastructure Technology Services > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
