How to overcome the target release constraint?

15 pts.
Tags:
FTP
IBM iSeries
It is our intention to FTP objects between IBM iSeries v6r1 and IBM iSeries v3r2. But when we create the SAVE FILE in IBM iSeries v6r1, in specifying the target release, We can at most stepdown to v5r3. Does anybody know how to overcome this constraint? We want to stepdown to v3r2. Thanks

Software/Hardware used:
AS400 iSeries

Answer Wiki

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

Discuss This Question: 6  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
  • TomLiotta

    Stepping down to V3R2 from i 6.1 is like trying to step down to Windows 98 from Windows 7. It would be very difficult. Very few objects would make sense to such an older platform.

    There is no way to use savefiles for such a transfer. There are no objects that can be saved and restored between the two in that direction.

    If any such move is made, it has to be done as text files. Any objects would have be copied in source form and recreated. Of course, any source elements that were not available on the older system would have be removed. Any data would have to be exported to text files also, and then the data would need to be imported after the containers were recompiled.

    It's likely that the only way to transfer the text files would be with FTP. There won't be many other networking protocols that could be used. I'm not sure if there would be many ways to communicate with PCs, for example, though it might be possible to use Windows 2000. Better would be Windows 98. Networking protocols from 15 years ago are needed. If you can find ways to make them work, it might be possible.

    In any case, text files are the way to go for everything.

    Tom

    125,585 pointsBadges:
    report
  • CharlieBrowne
    Is there a reason you do not update the other machine to be on the same release? It would seem to be a step that would give you a good ROI.
    41,430 pointsBadges:
    report
  • TomLiotta
    No V3R2 machine can be updated beyond V3R2. V3R2 was the last CISC release. Machines after that were RISC. -- Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    ...although it's generally possible to purchase a used system for a cheap enough price that is reasonably current (e.g., i 6.1) and probably more powerful than any old V3R2 system. -- Tom
    125,585 pointsBadges:
    report
  • kennethc

    Thanks, guys.

    The v3r2 machine owner is not prepared, as of now, to migrate to another AS400 release yet, because of their internal schedules.

    We do not have the Source (so rule out possibility of recompiling) of the Objects, which we want to save from v6r1 to install in v3r2, as this is the COGNOS development tool in runtime version. 

    But the v3r2 machine owner needs this tool urgently !

    Appreciate all your help

     

    15 pointsBadges:
    report
  • TomLiotta

    Compiled objects from i 6.1 cannot be restored to a V3R2 system. Period.

    Not only are the objects likely to have many compiler attributes that cannot be processed by such an old release, but at least two different levels of changes to internal structures have happened. It's possible to go backwards through one level of such changes (from version 6 to version 5) if the objects were compiled to allow it. That's part of what the TGTRLS() attribute does. But version 6 of the OS has no information about internal structures used by version 4, much less version 3. Expecting to go back through at least 11 different releases over 4 versions of the OS makes no sense.

    And the underlying hardware adds a huge obstacle. A one-way upgrade going forward from CISC to RISC is to be expected. IBM even allowed backwards conversion from RISC back to CISC for a number of OS releases, but that was dropped late in version 4. The RISC systems not only had a radically different machine language, but there was also a change from 48-bit addressing to 64-bits when RISC was first introduced.

    For any practical thought, it cannot be done. It'd be cheaper, easier and faster simply to obtain a used system that runs i 6.1.

    Tom

    125,585 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