|
Hi Ya'll, We have an S10 eserver that we have been using as an OS/400 beta test machine. The machine was at V4R4 and when we tried to install the beta of V4R5, it gave a SRC B1014507 and now and then, a SRC B1014505. Both indicate that the installable device is not ready or reading properly. In any case, IBM service came out and replaced the CD drive after which we were able to install the beta with little problem. A few months ago, we restored the system back to V4R4 from tape, again with no apparent issue. In the meantime, the CD drive has only been used a few times to install PTF's and such, and now I would like to install the new beta OS and it will not read the CD, giving exactly the same symptoms and SRC's as before. It was less than a year ago the CD was replaced and it has really had little use and works just fine to install PTF's or other applications, just not bootable ones. It will allow a WRKOPTDIR with no problem, just not any form of installation. This is also the case on the base V4R5 and V4R4 CD's so it's not a problem with the CD itself. We called software service for any ideas on the SRC that we are getting and they couldn't come up with anything but the suggestion that perhaps it could be an IOP conflict of some sort. Looking back at the system's logbook, we did install a new token ring and IOP right before we started having these problems. Aha! So we removed these, did a full restart, deleted all remnants of them and no luck. We even went so far as to unplug both the optical and the tape drives from the SCSI chain, do a full IPL, plug just the OPT drive back in and let it reconfigure (which it did fine and would again read/install just fine on other CD's) but still no luck with the installation CD's. I came across something that suggested that if you installed the OS from a different installable device you may get problems using a different one. The suggested fix for this was some (we went through so many by now!) combination of IPL and deleting references, but again, no luck. Does anyone have any thoughts? I really don't think the CD needs to be replaced and certainly don't want to have to go through this everytime I install a new beta! Argh. Thanks for any ideas! Jessica (: -----Original Message----- From: Leif Svalgaard [mailto:leif@leif.org] Sent: Monday, March 26, 2001 1:26 PM To: MIDRANGE-L@midrange.com Subject: Re: New Machine, QSECOFR not authorized Bob, Its not the point and click that is important it is moving the stuff around. ----- Original Message ----- From: <rob@dekko.com> To: <MIDRANGE-L@midrange.com> Sent: Monday, March 26, 2001 2:47 PM Subject: Re: New Machine, QSECOFR not authorized > > How does a one line command point and click? > > > Rob Berendt > > ================== > Remember the Cole! > > > > "Leif Svalgaard" > <leif@leif.org> To: <MIDRANGE-L@midrange.com> > Sent by: cc: > owner-midrange-l@mi Subject: Re: New Machine, QSECOFR not authorized > drange.com > > > 03/24/01 06:42 PM > Please respond to > MIDRANGE-L > > > > > > > > ----- Original Message ----- > From: Joe Pluta <joepluta@PlutaBrothers.com> > To: <MIDRANGE-L@midrange.com> > Sent: Saturday, March 24, 2001 5:09 PM > Subject: RE: New Machine, QSECOFR not authorized > > > > After getting around the problems with the logon, I have to admit that > > OpsNav makes some things a LOT easier... for example, moving 30 libraries > > from one machine to another is simply point and click. That's pretty > darned > > impressive. > > Unix has had a one-line command that could do this for 30 years. > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.