× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

What you can do is the following:
Send an escape message in the called program with a specified message id.
In the caller program pick that message id from the program status data
structure and handle it:

D PGMSDS        SDS
D   SDSMsgId                             40     46A
D   SDSMsgTxt                            91    170A  

Monitor;
  CallP MyPGM(Parm1: Parm2: ... ParmN);
On-Error;
  Select;
  When SDSMsgId = 'ERR1234';
       //Do something
  When SDSMsgId = 'ERR1111';
       //Do something else
  Other;
       //What ever you want ot do
  EndSL;
EndMon;

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them?  Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Holden Tommy
Gesendet: Monday, January 22, 2007 22:19
An: rpg400-l@xxxxxxxxxxxx
Betreff: Monitor/on-error


Simple question (I think)  when using a monitor block you can specify
specific errors on the on-error statement:

Monitor;
  CallP MyPgm();
On-Error 0202;
EndMon;

Are the only messages available for use on the on-error statement limited to
messages in the QRNXMSG message file?

Thanks,
Tommy Holden



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.