× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Update.  Depsite APAR MA37764 showing closed PER there will be a fixing PTF for V5R3.  It's not closed yet, or searchable, but it will be MF46700.
PS - it seems to be almost identical to the problem reported, & fixed, in V5R1 & V5R2 on APAR MA27962
Neil Palmer, Cambridge, Ontario, Canada



(This account not monitored for personal mail,

remove the last two letters before @ for that)

--- On Wed, 4/22/09, Neil Palmer <neilpalmer400mr@xxxxxxxx> wrote:

From: Neil Palmer <neilpalmer400mr@xxxxxxxx>
Subject: V5R3 RSTSTG warning if moving to larger disks
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Received: Wednesday, April 22, 2009, 12:13 PM

If you were thinking of using SAVSTG/RSTSTG on V5R3, to move to larger disks (swap out 8.5GB drives, swap in 17.5GB or larger, to allow installation of V5R4 - probably something quite a few people may think of doing), then a word of advice.  DON'T.You will go through the entire process of SAVSTG, restoring LIC to the new load source, running the RSTSTG from DST, and all will appear successful through the end of the LIC IPL, UNTIL it hits the very last piece "Start the Operating System".  At which point it will crash with:B6000417 0DB00060 And no, trying to SLIP install the Operating System from a SAVSYS tape will not resolve the problem, merely change the SRC code when you hit "Start the Operating System" to:B9003440 0DB00080  Apparently I was only the 2nd person to hit this problem when I found it last weekend, less than seven days after the first poor sucker, so when I searched for open APAR's to check this was safe to use before running I didn't
find any as at the time APAR MA37764 was not publicly viewable (it is now).
Apparently IBM thinks closing the APAR as a Permanent Restriction without issuing a fixing PTF for V5R3 is acceptable.  I don't.http://www-912.ibm.com/n_dir/nas4apar.nsf/c79815e083182fec862564c00079d117/0464abaf5c4aae678625759f003c6fc7
Neil Palmer, Cambridge, Ontario, Canada



(This account not monitored for personal mail,

remove the last two letters before @ for that)




      __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now
http://ca.toolbar.yahoo.com.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.