Finding where an escape message came from

[antoine.contal@xxxxxxx]

Hello,

I would like to know if there is a way to find where a monitored escape 
message came from?

I have a program with something along those lines.

monitor; 
     myProc();
on-error; 
     // Error logging logic.
endmon; 

The procedure 'myProc' calls other procedures and even other programs. 
Sometimes, one of the called procedures or programs will send an escape 
message.  I would like to write in my log file the origin of this escape 
message (program name, module name, procedure name, specification...).

I have searched the mailing list archive, and found some interesting 
threads (i.e., http://archive.midrange.com/rpg400-l/200307/msg00373.html 
), but I could not quite find what I am looking for.

Is what I am trying to do impossible with the monitor opcode?  Do I have 
to use the ILE Condition Handler API no matter what?

Thanks in advance.

--
Antoine Contal

Les informations contenues dans ce message et les pieces jointes (ci-apres 
denomme le message) sont confidentielles et peuvent etre couvertes par le 
secret professionnel. Si vous n'etes pas le destinataire de ce message, il vous 
est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser 
tout ou partie. Si vous avez recu ce message par erreur, nous vous remercions 
de le supprimer de votre systeme, ainsi que toutes ses copies, et d'en avertir 
immediatement l expediteur par message de retour. Il est impossible de garantir 
que les communications par messagerie electronique arrivent en temps utile, 
sont securisees ou denuees de toute erreur, alteration, falsification ou virus. 
En consequence, le Groupe decline toute responsabilite du fait des erreurs, 
alterations, falsifications ou omissions qui pourraient en resulter.
The information contained in this e-mail is confidential. It may also be 
legally privileged. If you are not the addressee you may not copy, forward, 
disclose or use any part of it. If you have received this message by error, 
please delete it and all copies from your system and notify the sender 
immediately by return e-mail. E-mail communications cannot be guaranteed to be 
timely secure, error or virus-free. The sender does not accept liability for 
any errors or omissions which arise as a result.