Transferring from V4R5 to V6

1,395 pts.
Tags:
AS/400 data transfer
iSeries Data Transfer
V4R5
we need to transfer all the lib's,obj's, everthing from v4 to v6 now?
which is the best method to do it? i'm expecting guidence through FTP method?


Software/Hardware used:
FTP
ASKED: August 25, 2011  9:51 AM
UPDATED: March 31, 2012  5:44 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Is sounds like you are moving to a different machine.
The fastest way would be to save the libraries to tape and restore them on the targat system.
Is that option available for you?

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Rajasekhar15
    no charlie we dont have tape option here, that's why i asking for FTP option....thanks in advance
    1,395 pointsBadges:
    report
  • CharlieBrowne
    1. Create a *SAVF (what ever you want to call it) 2. SAVLIB xxx *SAVF (the above *SAVF you just created) 3. FTP it to the target box 4. On the target box do RSTLIB xxx *SAVF * I do not remember if you need to create the *SAVF on the target box and use (Replace on the FTP command. Depending on how much you have to do, repeat this process for each library or write a program to do it. You can also create a new library and your *SAVFs in it, then SAV that LIB and FTP a single time
    39,780 pointsBadges:
    report
  • TomLiotta
    To FTP a savefile between two AS/400s, it's not necessary to create the savefile first on the target system as long as NAMEFMT 1 is used. After opening a connection and logging on, the command sequence might look like:
    bin
    na 1
    put mysavefile.savf
    Savefiles are always transferred in binary mode, so the {bin} command is necessary. Switching to NAMEFMT 1 with the {na 1} command lets the target system recognize the .SAVF file extension. Then {put mysavefile.savf} is understood by the target system as a special kind of file -- a savefile. The automatic handling of a savefile also eliminates the use of {(REPLACE}, so be aware that there will be no warning if a savefile is overwritten. If the default is set for NAMEFMT 1 or if previous commands have already caused NAMEFMT 1 to be enabled, then it's not necessary to ask for it. However, I always ask explicitly for a NAMEFMT setting. Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    If the two systems can communicate via FTP, then it could be feasible to use ObjectConnect. I haven't seen it used between systems separated by that many releases, though. Also, APPN configuration would need to be done enough for at least those two systems to communicate through it. Using ObjectConnect would mostly eliminate creating and populating savefiles on either side. Depending on space restrictions, that might be useful. It could also cut a significant amount of network time (perhaps especially if multiple libraries were processed concurrently). Tom
    125,585 pointsBadges:
    report
  • Rajasekhar15
    [...] 8. Check out CharlieBrowne’s approved answer on transferring from V4R5 to V6. [...]
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following