Hi Matt, Lim,
Sorry for taking so long to reply to you guys - busy, busy times.
Lim said:
You can probably use alarm() and sigaction() to accomplish that also. I
learned that from Scott Klement when dealing with socket programming.
Not sure why you do not want to use INVITE. I think that is the easier
of all.
Larry says:
The architecture we currently use involves alarm() and sigaction(), or are
you saying it would be possible to set the alarm to interrupt a program
which is sitting on an EXFMT? Currently I have to send a *ESCAPE message to
the program to accomplish this. Could you expand on that?
Matt said:
Have a read on this thread topic. I know it has INVITE, which
you say you do not like but not why. It uses the DTAQ parameter of the
display file.
<
http://archive.midrange.com/rpg400-l/199911/msg00419.html>
http://archive.midrange.com/rpg400-l/199911/msg00419.html
Larry says:
I don't think this gives me anything I haven't already got with our current
architecture. The beauty of using the alarm() technique is that I can add it
to a current program/display file without touching the DDS. It also allows
me to specify a "handler" sub-procedure that exists in a service program -
totally abstracted from the display program. This also means I can "switch"
it off at any point if necessary. We have screens that you can toggle to
auto-refresh if you want it to, but you can switch that off too. Not sure
how flexible INVITE and/or WAITRCD and/or DTAQs are with that. The only
downside of our current code is the fact that I have to use a *ESCAPE
message to interrupt the display program when an event occurs that forces a
refresh of the screen.
Thanks for your thoughts.
Cheers
Larry Ducie
midrange.com
