RE: Hmmmm.....$1 Billion (Booth Martin)

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

We had used the Data Queue approach in an old HR system.  If the data queue
timed out, the screen was blanked but your work was saved.  You had to enter
your password to get back into the screens.  Really easy to do by attaching
a data queue to a display file.  I wish that the vender of our imaging
system would use a better approach at tying the 5250 screen to the imaging
display.  To select a record to display and through up the image is great,
but going back to the green screen and changing records or closing does not
close the imaging.  In fact they really are not tied together except through
the DDE/EHLLAPI which only launches the Windoz command.

Chris Bipes

-----Original Message-----
I have no reason to think it _can't_ be done, but I'm trying to picture the
kinds of useful multi-threaded apps that would be reached by telnetting to a
Windows system. Or an app that communicates only within the CMD.EXE window.

As it is, I can have a 5250 app that communicates through multiple iSeries
Access session windows on my PC. It's interesting to ACQUIRE the other
devices, but not too challenging. And DSPFs that signal via data queues have
been around for ages though pretty much nobody cares about them.

I suppose virtual terminal APIs could allow some interesting stuff to be
done if there's a restriction due to physical terminals rather than
emulation.