Will vista and Windows 7 be compatible with old Client Access?

65 pts.
Tags:
AS/400 Client Access
AS/400 upgrades
AS/400 upgrading
OS/400
V4R5
Windows 7
My questions is from the time machine. We have an AS/400 installed in the last century(1999)  for Y2K software upgrade. The hardware and os400 is unbeatable. The ERP application is still very good. We have a lot of archival data and 7 users so there is little upgrade reasoning. My question is a concern for the OLD CLIENT ACCESS. Will vista and Windows 7 be compatible with this old client access. Thank you,  SHS

Software/Hardware used:
AS400 v4r5
ASKED: November 28, 2009  6:22 PM
UPDATED: June 27, 2013  7:55 PM

Answer Wiki

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

If your client Access is also at v4R5, the short answer id NO. Note that client access is not always at the same level as the OS. However, some people have got old versions to work with Vista. i don’t know anyone who has tried that old a version with Windows 7

Discuss This Question: 7  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
  • Shs
    Can I use a newer level of Client access with v4r5
    65 pointsBadges:
    report
  • TomLiotta
    Can I use a newer level of Client access with v4r5 Maybe. It probably depends on what you do with System i Access. If you only use it for terminal emulation, you probably shouldn't be using it at all. Use a different product such as Mocha TN5250. If you're using more complex features such as System i Access File Transfer, then you might have difficulties. At the moment, the most recent release of System i Access is having its bugs in Windows 7 being reported by customers and fixed by IBM. Previous releases...? I haven't heard much, though 'compatibility mode' to run under WinXP seems to work for some. I have no way to check anything relating to V4R5. I'd expect a variety of problems, particularly in how Windows authentication has changed over the years. Aspects of integrating into a Windows network may be tricky. Your V4R5 will be wanting to work more like Windows 2000 than like any later Windows connectivity. Not much can be done about that. Tom
    125,585 pointsBadges:
    report
  • graybeard52
    Generally, newer version of Client Access will work with older versions of the OS. There may be some new functions might not work, but otherwise you should be ok. Its not the v4r5 that will get you, its the Windows 7
    3,115 pointsBadges:
    report
  • TomLiotta
    Its not the v4r5 that will get you, its the Windows 7 Without knowing what 'new version' of iSeries (or System i) Access might be installed and without testing it, that's difficult to know. There have been numerous changes in NetServer, for example, that might cause issues with V4R5. The newer Windows authentication protocols for mapped shares are physically not present in V4R5 nor were they ever PTFed in. As long as the replacement iSeries Access functions can still negotiate back to Windows 2000 protocols, that should be okay. (I haven't checked.) E.g., if iSeries Access V5R3 is used to replace whatever is currently being used now for Client Access, things should still work as far as iSeries Access is concerned. Whether V4R5 can handle anything outside of iSeries Access from Windows 7, I can't guess. Library lists were changed with V5R1 to allow many more libraries. Any iSeries Access component that resolves library lists (iSeries Navigator) would still have to account for both old and new library list formats. I'm almost certain that this was done at least up through iA V5R3. I don't know about later releases. Streamfile handling relating to the migration from 'code page' to 'CCSID' reliance began in earnest in V5R1. If server functions all still handle the old API formats correctly when the new format attributes are passed in or if negotiation in newer protocols still drops back to an appropriate 'lowest common denominator' to handle V4R5, then IFS manipulation should still work okay from Windows 7. (Whether iSeries Navigator after V5R3 can do everything correctly is unknown.) Long-password support in V5R1 brought changes to clients connecting to DRDA/DDM. As long as recent clients can still negotiate back to 'lowest common denominator' protocols, then all remote SQL access should still work. Similarly, connecting to any other host server will require clients to handle back-level negotiation. Not a problem if releases are close enough. Perhaps the most difficult issues would arise in iNav or OpsConsole access to DST/SST types of functions. V5R1 brought some big differences. And again, as long as releases are close enough, there probably won't be any problem. Likewise, all host and TCP/IP server startup options changed in V5R1, particularly relating to how TCP/IP startup changed but also in how server jobs related to QSERVER, QSYSWRK and QUSRWRK, and a couple less important areas. Maintenance via iNav might or might not work if release differences are too great. Numerous host and TCP/IP server attributes were handled by creating special data areas prior to V5R1. The SMTP server, for example, would use the QTMSCBNDIP and QTMSSBNDIP data areas to determine IP addresses to bind to. Support for those was dropped in V5R1, was moved into a new file and is now handled by new commands. If iNav attempts to use the new commands, it won't work. Other servers have had similar changes since V4R5. Perhaps the worst problem will be iSeries Access license key enforcement. Prior to V5R1, license keys weren't actually "required". You could work your Client Access functions even without valid license keys. That was no longer allowed as of V5R1. Any install of iSeries Access later than V4R5 is going to want to find a host license server. IIRC, V4R5 is long out of support. If license keys for iSeries Access for any release from V5R1 on up are requested from IBM, it's going to be tricky getting them issued for the V4R5 serial number. So far up to that point, everything is about potential V5R1 iSeries Access issues in a Windows 7 environment where V4R5 is the host. Maybe those issues would all work cleanly; there weren't a lot of things that wouldn't work in Win2K or WinXP once proper iA service packs were installed. Or maybe they'd work in WinXP compatibility mode. There would be other potential issues if the chosen iA version/release was V5R2, V5R3 or later. The later the choice is, the less likelihood that V4R5 server protocols would be accepted. But those would still be just potential. I have no direct knowledge given the proposed mix of host/client releases. I can only think of areas that I would verify in my own environment. (And there's no point in listing the additional things to check if any release later than V5R1 is chosen; there are too many possibilities.) I haven't seen a release of Client Access, iSeries Access or System i access that had any problem going two releases back. Service packs were always available eventually for minor parts that didn't work out of the box. Service packs that work on Windows 7 for any release before V5R4 might not be predictable. V5R4 is a 'four releases' difference from V4R5, and some of the differences are major. But the licensing...? That would be the element that needs some certainty anyway. I have no idea how to to handle that area. Tom
    125,585 pointsBadges:
    report
  • Shs
    I saw a memo about WINDOWS 7 having an XP MODE. Do you know anything about this?
    65 pointsBadges:
    report
  • Teandy
    According to IBM the only versions of client access that are compatible with vista are versions V5R4 and later. For Win 7 the only version is V6R1 provided you have the correct service pack. See the link below for more information. http://www-03.ibm.com/systems/i/software/access/windows/supportedos.html#windows
    5,860 pointsBadges:
    report
  • jinteik
    maybe you can even run the compatibility with windows xp when you are running windows 7...
    16,930 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