|
Leif, >wouldn't that same argument not also apply to Joe Pluta's method of >"re-engineering programs to remove the 5250 I/O" and get the same >interactive capability but without 5250? I differentiate them because the workload is indeed different, and now falls under the unrestricted category. It doesn't allow you to continue to use 5250 data streams at dumb workstations and exceed the licensed limits. >Presumably true "interactive" capability is measured in service >given to users interacting directly with the system. The interactive >tax should really be called a 5250 tax. Agreed that 5250 tax is more accurate, and that is precisely why Joe's method is acceptable -- nay, encouraged -- from a licensing viewpoint. Existing programs are in essence converted to client/server, and the 400 is allowed unfettered usage as the server. Joe is offloading the client UI presentation from the 400, which is what the 5250 tax is all about. Fast400 does no such thing, based on your analysis of its operation. Doug
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.