Saving on V5R4 and restoring on V5R1?

23730 pts.
Backup and Recovery
IBM iSeries
Hi, I have a customer that runs an AS/400 on V5R1 and is unable to upgrade to V5R4 (they have an old software package without the source and the objects have had the observability removed). I need to get some software installed on their machine, but I've recently upgraded my machine to V5R4 and now the target release V5R1M0 is no longer available on the save commands. I thought maybe I could send them a save file and use FTP, but I can't even save to the save file with V5R1 as a target release. Is there a way around this ? Thanks in advance, Martin Gilbert.

Answer Wiki

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

Off hand I don’t recall any requirement for recompilation or re-encapsulation when moving from V5R1 through V5R4 (though V6R1 is a different story) so I don’t think the lack of source code and/or observability is a problem.

As TGTRLS support only goes back two releases I believe you do have a problem if you need to send them actual objects (as opposed to flat files, source code for recompilation on their system, etc). I only have a V5R4 system myself, but I have an agreement with another company (at V5R2) that I can do compiles, testing, etc on their system remotely. In that way I can support the distribution of objects to back level releases. Any chance you can do something similiar?

Bruce Vining

Another way is Hardware does not permit your client to go to V5R4 have them go to V5R3. Also if you have the source you can save the source to PC and then ftp to Client and recompile…..Rick

Discuss This Question: 3  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.
  • Gilly400
    Hi Bruce, Thanks for the reply. If I can save and restore source that would solve my problem, as I am able to compile on their machine. I don't need to send objects as such (although that would save me some time). I will try and send them a save file of the sources and see how that goes. Maybe I should try saving with several different release levels, to see how it goes. Thanks again, Martin Gilbert.
    23,730 pointsBadges:
  • bvining
    No need for save/restore in that case. Just use FTP for the source members. Here's a script that I use to move all of the source for a given application to another system:
    USRPRF PASSWORD                   
    quote cwd /qsys.lib/dc1lib.lib    
    quote site namefmt 0              
    quote namefmt 0                   
    mput dc1lib/qclsrc.*              
    mput dc1lib/qcmdsrc.*             
    mput dc1lib/qddssrc.*             
    mput dc1lib/qpnlsrc.*             
    mput dc1lib/qrpglesrc.*           
    mput dc1lib/qsrvsrc.*             
    quote cwd vptshared               
    mput vptshared/prototypes.*       
    mput vptshared/qrpglesrc.*        
    I have the above in a member DC1LIB of source file VINING/FTPSCRIPT. To run this I: OVRDBF input vining/ftpscript mbr(dc1lib) FTP system_name DLTOVR *all You may need to fine tune the first few statements depending on how the remote system defaults the namefmt and directory. The source files in the remote library have been created previously. One of the members in DC1LIB/QCLSRC that is sent is the build stream to then recompile everything needed for the product. In my case DC1LIB is the development library for a product and VPTSHARED a source library used for my development that contains programmer tools shared across products -- basically the source to build *SRVPGMs exporting functions that I use all the time. Bruce Vining
    7,070 pointsBadges:
  • Gilly400
    Thanks Bruce, I think my problem is now solved. Martin Gilbert.
    23,730 pointsBadges:

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.

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


Share this item with your network: