• Subject: Re: Restoring to V4R1
  • From: DAsmussen <DAsmussen@xxxxxxx>
  • Date: Fri, 16 Jan 1998 21:53:42 EST
  • Organization: AOL (http://www.aol.com)

Gary,

In a message dated 98-01-12 11:11:13 EST, you write:

> 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? 

I imagine that you've already gotten an answer (probably several), but AOL is
again holding my mail hostage further than three notes from here so I'll say
-- _up_ is easy, _down_ is hard.  V3R7 to V4R1 should be no problem, but going
the other way could cause problems if you've implemented new V4R1 features in
your code.  If you want to go the other way, be sure to specify a target
release (TGTRLS under F10 on the SAVxxx command) during the save -- any
objects utilizing new features will be excluded from the save (with a
message), thus alerting you to compatibility problems...

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"I can't imagine why anyone would _need_ more than 640Kb of memory or 30Mb of
hard drive on a personal computer."  -- Bill Gates, author, "The Road Ahead"
+---
| 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 ...


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.