There has been no need for this walk-on-fire ritual for over ten years. If you want to make changes to your spool configuration, there are less traumatic and perilous methods available. For 1.7, you will first need to $ACTIVATE to the 'z/OS 1.2' level if you have not already done so. $D ACTIVATE will tell you straight out.
. . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] Francois Paré <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List <[email protected]> 08/22/2006 08:55 AM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject JES2 migration (z/OS 1.4 to z/OS 1.7) Hello, Soon, we're going to migrate from z/OS 1.4 to z/OS 1.7. At the very precise moment that we do the z/OS migration, we've always done a spool offload on the current system and a spool reload on the new system. I think that it is probably a task that we do from an old tradition. Since z/OS 1.4 and z/OS 1.7 are in the compatibility range for a migration, I would like to eliminate this task. Do you think it's OK? ---------------------------------------------------------------------- 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
