|
midrange.com
Thanks, I will look into that.
Denis Robitaille
Directeur services technique TI
819 363 5187
SUPPORT
Jour (EST) Daytime : 819-363-5087
En-dehors des heures (EST) After hour : 819-363-5095
Network Status : 819-363-5096
>>> bvining@xxxxxxxxxx 08/14/03 01:35pm >>>
In V5R2 a new exit point was added to the system for Reply Handling. The
exit point can be found in the Information Center under Programming; APIs;
APIs by category; Message Handling; and then Reply Handling. This exit
does not exactly answer your question (how to prevent a user from
answering) but does allow your program to either reject their response or
change their response. Obviously the program could also notify your
support personnel in addition to changing the Cancel response to Dump (or
whatever).
I should point out that there is one consideration when running the exit
program that we are in the process of updating the Information Center
about. And that is the debug breakpoints won't work when the exit program
is running.
Bruce
"Denis Robitaille"
<denis_robitaille@xx To:
<midrange-l@xxxxxxxxxxxx>
scades.com> cc:
Sent by: Subject: How to prevent a
user from answering a message error
midrange-l-bounces@x
idrange.com
08/14/2003 10:39 AM
Please respond to
Midrange Systems
Technical Discussion
Hello all,
One of our programmers asked me the following:
Can we prevent a user from answering an error message. Example: the user
calls PGMA that call PGMB but there is a level check error. We want the
user to be unable to cancel the program so that the IT support personel can
do theire job better (like look at the call stack, list of open files ...).
If someone can point me in the right direction (like where in the
information center or IBM manual information regarding this might be
found), I would apreciate.
Thanks
Denis Robitaille
Directeur services technique TI
819 363 5187
SUPPORT
Jour (EST) Daytime : 819-363-5087
En-dehors des heures (EST) After hour : 819-363-5095
Network Status : 819-363-5096
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.
