× 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.



I've found that same thing to be true, you get the line# of the call to the procedure.

I've wound up putting these in every procedures where I need to know the procedure
Name and the line# - (I suppose it could/should be 'monitor', but it works)

Hth,

John


//********************************
begsr @exit;
//********************************

if gErrMsg <> *blanks;
log_Add(gErrMsg);
msg_User(gAlertUser:gErrMsg);
clear gErrMsg;
endif;

exsr @return;

endsr;

//********************************
begsr @return;
//********************************
return;
endsr;

//********************************
begsr *pssr;
//********************************

if gPssrSw = *on;
exsr @return;
endif;
gPssrSw = *on;

gErrMsg =
msg_BldErr(
%trimr(psds.Pgm)
:'Uncaught *pssr exception, ' +
psds.Msg + ':' + %trimr(psds.ExcDta)
:utlty_ProcName()
:''
:psds.LineNbr
);
exsr @exit;

endsr;




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.