|
It's got nothing to do with sweat, Brad, but with architecture. PSC400 rewrites your programs to remove the 5250 I/O and replace it with a browser interface, the same as if you rewrote your program to use e-RPG or any other client/server technique. My tool actually goes in and modifies the source code, replacing 5250 I/O with calls to a browser API. This is the direction IBM seems to want us to move: to a client/server architecture where batch programs use the browser as the primary interface. Let's be VERY clear on this: revitalization is an architectural approach, not a hack. PSC400 doesn't trick the operating system into thinking that 5250 I/O is not 5250 I/O; it actually rewrites your programs to use true client/server techniques. The only way that my technique could be penalized by the interactive tax is if IBM changed the definition of either batch programs or servlets to be interactive programs. It is in no way the same as a CFINT buster. It is instead a stepping stone to a true client/server architecture. It's actually very straightforward to do what I did manually. Go in and replace each I/O opcode with a call to an API: I detailed that approach in my book over a year ago. Since then, I've designed and written a tool that will do it automatically. Absolutely not the same thing as a CFINT buster. Joe Pluta www.plutabrothers.com > -----Original Message----- > From: Brad Jensen > > I do find it funny that one person on this list says that its > okay to beat the IBM governor by using his product to > rewrite/reconfigure your resource use, while just setting a flag > is cheating. I guess it's okay if you sweat a little to get your > results - until IBM decides to rewrite the OS to remove HIS > advantage also.
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.