RE: RE: 5250 datastream & workstation I/O & WebFacing

>> Oh, and as another user of his product I can say that it does more than
>> aXes appears to.

First, thanks for the kind words from Crispin and Walden :-) Now if you tell my 
boss the same thing, maybe I'll get a bonus one day....

>> Why reinvent the wheel?

I'd have to say that this is a different wheel. My solution delivers pure 
(totally customizable) HTML + JavaScript + CSS using the standard HTTP server 
that is shipped with the AS/400. No need to change your programs or your 
display files or to install WebSphere Application Server or anything else 
similarly bulky, it has significantly better performance than WebFacing, 
integrates tightly with our development environment/toolset and it installs in 
less than 10 minutes. I'm not saying it's better than other solutions, just 
that it's different and may be closer to what my customers need... It's just 
the 5250 interactive tax that is causing me some heartache.

>> The demo program stack appears to go through QWT3REQIO and
>> "looks" like a normal interactive job, so I'd love to see more about
>> that option.

I'd only seen the call stack of a WebFacing job running once and couldn't see 
enough of the stack to see if it called QT3REQIO from QWSGET/QWSPUT. Obviously 
*somewhere* along the way it determines how the 'flag' is set, but I'm damned 
if I can find out where (unsurprisingly).
 
Obviously IBM don't publish details of the Workstation Management 'module' so I 
can't see where any flag might be set. Even if I got my hands on the 
information I suspect that I might be barred from using it anyway (assuming 
we'd have to sign an NDA).
 
My only hope is that I can simply discover this information and somehow make 
use of it in a legal way that IBM can't complain about...
 
Rory