× 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.


  • Subject: Re: Restoring to V4R1
  • From: "Jeffrey M. Carey" <jeffreycarey@xxxxxxx>
  • Date: Wed, 14 Jan 1998 15:23:37 -0600
  • Organization: Trase Miller Solutions

Mike Smith wrote:
> 
> If your programs still have observability saved (and they don't use anything
> that isn't supported on RISC, which isn't likely), you should be able to
> restore them directly.  If observability has been deleted, you'll have to
> re-compile.
> 
> Mike Smith
> ERP Development, IBM

That's not true for V3R7 to V4R1 - you only need observatbility going
from CISC to RISC - not RISC to RISC

> 
> -----Original Message-----
> From: Gary Feinstein <gfeinste@planethollywood.com>
> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
> Date: Monday, January 12, 1998 10:08 AM
> Subject: Restoring to V4R1
> 
> >Does anyone know what the process is for restoring an application from
> >my current V3R7 system to a separate V4R1 AS/400.  Can I simply do a
> >SAVLIB and corresponding RSTLIB or do  I need to worry about recompiling
> >my program objects?  What are some pitfalls that I should look out for?
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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 thread ...

Replies:

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.