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
- Java Examples - JExamples.com
- iReport - OpenSource Java Reporting Tool
- as400 iSeries NetServer Disabled user profiles
- Create a Custom Live Linux CD - Leveraging BusyBox and OpenSSH
- Search for text in vi or vim
- IBM eServer iSeries - iSeries NetServer: Command Line Setup
- Reno County is preparing to move from an AS400 computer system to a personal-computer-based system
- Encode HTML Entities - Showing code in blogs
- Super $500 Myth Project
- HOW TO make a Powerbook in to a Wi-Fi access point!
No comments:
Post a Comment