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
- List Job (QUSLJOB) API
- Using QCLRDTAQ to clear data queues in CL and RPG
- 80 Column Punched Cards and the History of RPG on the AS400
- What is QZHQSSRV job?
- Make a Home made, open source mp3 Player
- AS400 APIs
- Encrypt Data on as400 (QC3ENCDT, Qc3EncryptData)
- API Example - Deleting Old Spooled Files
- UDATE and *DATE in AS400 RPG
- Contact Us
No comments:
Post a Comment