There is one event you are overlooking - a system event.
Your notification process could send an "escape" message to the user's program. The user's program would then handle the "error".
You might try putting a break handling program on the user's message queue. Your notification process sends a message to the message queue and the break handling program sends a message to the user's program. The user's program would monitor for the message and take appropriate action.
You could also look at using a combination of trigger program, data queue, start service job and the debugger APIs. Trigger writes to data queue. The data queue program starts a service job against the user in question, starts debug and changes the variable(s) in question.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Sunday, September 02, 2012 5:38 PM
To: Midrange Systems Technical Discussion
Subject: Event-based actions
This seems simple enough yet I am stumbling all over the school yard
This has to do with event-based actions versus waiting for the Enter key
to be pressed or for a timer to run out..
This is a fairly simplistic case, but it should serve to demonstrate the
problem I am trying to solve.
Lets say a desktop gadget displays the local temperature. When the
temperature changes, the gadget changes the display. As I understand
it, this is accomplished by a "listener" that "listens" for a
temperature change event from the mother ship. It is not a timer that
periodically checks to see what the temperature is. When the listener
hears that the temperature has changed, it alerts the desktop gadget and
my desktop display shows the new temperature. As I said, this is a
So, in midrange world, how do I mimic the behavior of a listener and of
This may not be well presented. For that I apologize. Of course, if I
understood the issue better I probably would also know the answer,
right? ;) If you have questions, please ask. That may help me
explain my issue better.