|
Brad, all, Since we're all thinking out loud about this.... I've never done this sort of thing, but if the I/O routines necessary to support a SPECIAL device would interface with the existing EXFMT, READC, etc. opcodes then a change in the F spec from WORKSTN to SPECIAL would be the ultimate transition tool. Since the compiler folks periodically ask what we would like to have added, I'd vote my whole $100 on something along the lines of a new device code to handle data messaging in a client/server environment where the client could be anything that could handle the task. It wouldn't matter if the client was a VB program, a Java applet, a sockets program, whatever. If IBM can't/won't do this, possibly some really clever bunch of people could come up with a compiler patch so that any program with a WORKSTN device would use this patch to communicate with a WORKSTN controller emulator. just a thought... Brad Jensen wrote: > The conversation about this on this list has got me thinking also. > Why not have a tool the replaces the 5250 screen processing with a > web interface? They are both transaction oriented. > <<SNIP>>
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.