If you are running a second-level guest to do your maintenance in, then t he best way is to shutdown the SECOND-LEVEL guest and dump it using DDR from
the first level MAINT userid. Then bring up your second-level guest, appl y and test the maintenance (shutting down and restoring as necessary). Then migrate the good maintenance to your first-level production system. If you are applying your maintenance to minidisks on a first-level system , then you need to backup the individual minidisks used in the maintenance process. Then if something goes wrong in your VMSES processing, you can restore the affected minidisks. This will keep you from stomping on SPOOL or user minidisks. /Tom Kern /301-903-2211 On Thu, 8 Feb 2007 11:10:50 -0500, Anne Crabtree <[EMAIL PROTECTED]> wrote: >I would like to know what the recommended procedure is for backing up th e system prior to applying maintenance (and how to restore if there is a problem!!). The last time I did maintenance, I backed up 510RES with DDR XA and when PUT2PROD had errors, restored 510RES from that tape. To make a long story short, it really messed up the spool and I ended up on the pho ne for hours with IBM. I need to put maintenance on again and want to make sure and do it right this time. >======================== ========================= =======================
