Re: iSeries Access for Web

trying to "buy" some time as they seem "h### bent" on picking
a "replacement" ASAP followed by at least an 18-24 month
conversion and thats IF we stick with the same SW vendor and
use their "new and improved" .NET version...

We hear the same complaint from our customers.  Department heads and casual 
users want a GUI point-and-click interface, while data-entry people want to 
hold on to the 5250 interface.

But iSeries Access for the Web has the same problem that all screen-scrapping 
and 5250 conversion programs have.  The user interface remains essentially the 
same, while performance goes down and hardware requirements to up.

Data entry people get mad because performance is worse.  Casual users get mad 
because their favorite GUI features weren't implemented.  The CFO gets mad 
because the IT department is asking for new equipment.  iSeries ISVs get mad 
because they keep loosing market share to Wintel platforms.

ISVs eventually "try" to migrate their products to .Net, only to learn after 
huge development efforts and costs that .Net has unanticipated architectural, 
security, performance, and other types of  issues, which hardly arise under a 
5250 paradigm.

But with a little smoke an mirrors they figure they can pass it on to their 
customers, until the customer begins seeing parallels between .Net and their 
experience with thick-client architectures of the 90's, which were a pain to 
manage.

Nathan.


 
____________________________________________________________________________________
Have a burning question?  
Go to www.Answers.yahoo.com and get answers from real people who know.