|
Interesting - where I WAS, can recount HORROR stories dealing with them. Not to say that they were ALWAYS bad - if you could get to the GOOD people (HOPEFULLY they are still there after the "purge"...) Rob Berendt wrote: > I am not sure if we got the official blessing. I don't know what > hoops we had to jump through to get things working. I was not on > the team that actually did this. SSA has always been good to us. > They've had to rush rewrites out to us in the past. We were their > first customer that put their software on a model with a character > in the model - SSA had to modify BPCS security patch. At Dekko we > tend to stay on the bleeding edge in some respects. We are running > many versions. We are in a holding pattern on 4.05CD. We tend not > to upgrade to stuff that we know will need modifications and they > won't let us use the tools. > > CLEWIS@IQUEST.NET on 10/14/98 11:07:01 AM > Please respond to MIDRANGE-L@midrange.com@Internet > To: MIDRANGE-L@midrange.com@Internet > cc: > > Subject: Re: AS/400 V4R2-R1 "downgrade" > > Did you folks just go ahead and try this or did SSA give you their blessing ? > > My previous employer has been told different stories. The last being that >they would NOT support our current version of BPCS on > V4R2 or V4R3 (I think depening on which day you spoke to them). I ran into >the SAME thing when we moved from CISC to RISC several > years back. APPARENTLY we were one of the early ones to do this and I can't >BELIEVE the rigamaroll (sp ?) that we had to go > through. We EVENTUALLY got what we needed but the "alliance partners" seemed >to be more on the ball than SSA... > > Rob Berendt wrote: > > > We have a V4R3 machine as our development machine. We are running multiple >versions of BPCS on it just fine. > > > > CLEWIS@IQUEST.NET on 10/14/98 12:12:41 AM > > Please respond to MIDRANGE-L@midrange.com@Internet > > To: MIDRANGE-L@midrange.com@Internet > > cc: > > > > Subject: Re: AS/400 V4R2-R1 "downgrade" > > > > There s/w vendor wouldn't be Some Stupid A%#wipe, would it ;-) > > > > grnhornt@ix.netcom.com wrote: > > > > > Has anybody tried de-upgrading an AS/400 OS release lately? We have a >customer that wants to move a system from V4R2 back to > > > V4R1 so their secondary system matches that OS/400 release of their >production system which can't be upgraded right now. > > > (Their s/w vendor doesn't support V4R3, and they don't want to upgrade >twice in rapid succession). > > > > > > This process isn't documented anywhere that I can find (no surprise), so >right now I'm planning a relatively manual approach > > > of scratching the system, loading the OS and licensed programs, then >restoring the configuration and user libraries and > > > manually updating things like TCP/IP configuration and system values. > > > > > > Is there a better way that I can feel comfortable with? > > > > > > Erik Knudson > > > Symatrix Technology > > > Portland, OR > > > > > > +--- > > > | 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 > +--- > > +--- > | 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.
midrange.com
