Ironically, one of the problems with iSeries Access for Windows is also one of its strengths: its longevity. Starting out as a product called PC Support/400 in the late 1980s and progressing through at least three different name changes, this software has a history so long that it's almost geology. However, sometimes that history works against it, particularly when administrators who are not familiar with i5/OS and OS/400 are in charge of installing and maintaining iSeries Access for Windows desktops.
To alleviate potential problems when Windows administrators handle IBM's connectivity package to AS/400, iSeries, and i5 servers, here are four tips to help Microsoft Windows professionals create better iSeries Access software installations on the Windows desktops under their control
Wednesday, August 30, 2006
Subscribe to:
Post Comments (Atom)
Popular Posts
- Spam king Adam Vitale busted by Secret Service
- Build Your Own PBX
- Make del.icio.us bookmarks
- Three Languages For Java Programmers to Learn
- 10 Really as400 Helpful APIs
- Common Gateway Interface (CGI) on the as400 / iSeries
- as400 commands and APIs you'll use for handling messages
- Four Hundred Guru--Admin Alert: Moving Libraries Between i5/OS Partitions, Part 1
- 5250 Emulators
- Recommended PHP reading list
No comments:
Post a Comment