Saving V5R3 libs to V4R5
I currently have a V4R5, and V5R3 systems. I would like to discontinue use of the V4R5, but I have several customers on that version, or lower, and they don't plan to upgrade. I'd like to move all the code/objects to the new system, but have found no way to do a savlib on the new system, and be able to restore to a system with V4R5 or lower. I have tried it, but no go. Any ideas on this would be appreciated.
Software/Hardware used:
Software/Hardware used:
ASKED:
August 17, 2005 1:29 PM
UPDATED:
November 1, 2009 9:40 AM
Answer Wiki:
When carring out a SAVLIB have you changed the Target release parameter from *CURRENT TO V4R5MO?
==========================================================
AFAIK, if you go to V5R3 and your customers stay at V4R3, you have two choices.
<ol>
<li>Drop support for V4R5 and earlier. Objects that you create on V5R3 cannot be saved to earlier than V5R1 no matter what new features you use, even if you use none.</li><li>Drop the idea of sending compiled/created objects to earlier customers. Send source code and create the objects on the customer system. For data, send flat files and use a proc that you pre-install to read the flat file and convert the data into the formats appropriate for the customer.</li>
</ol>
I don't think any other choices exist.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
Titch, version V5R3 does not support V4R5.
Huskers, if you have (by one of your customer) V5R2 or V5R1 system, you could send your data to that system and there save it to V4R5. After save, send your data to V4R5 system. Maybe it’s possible to transfer your data through FTP directly from V5R3 to V4R5. From one system you do FTP connection directly to other and then start transfer with FTP GET or PUT commands.
I’m not sure that this second idea will work…