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
- Recover or reset QSECOFR passwords
- AS400 Job Scheduler
- List Job (QUSLJOB) API
- UDATE and *DATE in AS400 RPG
- Using QCLRDTAQ to clear data queues in CL and RPG
- What is LANSA
- IBM System i APIs at Work
- as400 api - Process Commands (QCAPCMD) API
- What is RPGsp (RPG Smart Pages)
- Slow Running Batch Jobs on as400 Iseries
No comments:
Post a Comment