|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] thanks, Also I am guess I will buy gallons not just fifths......... -----Original Message----- From: rob@dekko.com [mailto:rob@dekko.com] Sent: Thursday, March 14, 2002 12:30 PM To: midrange-l@midrange.com Subject: RE: Restoring a V5R1 machine back to V4R4 Do a complete option 21 save of your V5R1 machine. Then save all of your volatile data again. This time with a target release of V4R4. Fix anything that didn't save because it wasn't compiled down to that level and save them or redo this last save. Then following the Backup and Recovery guide for a system which has lost it's load source disk. Use your last save from when you were at V4R4 to restore. You will lose the contents of data queues and output queues. If you have SNADS you could do a SNDNETSPLF to a dummy user on the current V4R4 machine to store the spool files. Then send them back once you are restored. If you use *ALLDATA instead of *RECDTA on the SNDNETSPLF you should only lose the job name, user, number. May I recommend alcohol? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Beebe, Linda" <lbeebe@dlis.dla.mi To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> l> cc: Sent by: Fax to: midrange-l-admin@mi Subject: RE: Restoring a V5R1 machine back to V4R4 drange.com 03/14/2002 12:05 PM Please respond to midrange-l This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] no new hardware. "Should" have a full system backup, although the operator is not always on top of things.. And I have all ready thought of the resume, theres just not that many 400's in this area! :-) -----Original Message----- From: rob@dekko.com [mailto:rob@dekko.com] Sent: Thursday, March 14, 2002 11:59 AM To: midrange-l@midrange.com Subject: Re: Restoring a V5R1 machine back to V4R4 1) Was any hardware loaded on to the V5R1 machine since it last was on V4R4? If so then you need to ensure that the hardware is supported on that old release. 2) Do you have a complete system backup of the V5R1 machine from when it ran V4R4? If so, how old is it? I was going to reply send your resume' out and find someplace willing to stay current - but some people just don't appreciate humor. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Beebe, Linda" <lbeebe@dlis.dla.mi To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> l> cc: Sent by: Fax to: midrange-l-admin@mi Subject: Restoring a V5R1 machine back to V4R4 drange.com 03/14/2002 11:08 AM Please respond to midrange-l This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] We have 2 machines, one we are moving off site for disaster recovery. This machine is at V5R1. Because we have some issues with the other machine we can not upgrade it to V5R1 just yet. So They want to do a full restore on the V5R1 machine back to V4R4. Is this possible? and if so what needs to be done? TIA Linda _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
