Hi Joe,

How about doing a RCVMSG (or, the API equivalent, QMHRCVPM) within your on-error block? If your source is compiled with *SRCSTMT, it should be possible to get the line number that way.

Disclaimer: This isn't something I normally do, so I might be wrong. I think I tried it once and it worked, though. It might be worth looking into...

On 4/5/2012 12:25 PM, Joe Pluta wrote:
I've run into a little hitch when attempting to use the program status
data structure in conjuction with a monitor block.

Here's the skeleton of a standard mainline for me:

iRC = 0;

iRC = process();


iRC = 999;
PSDSInfo =
' (' + %char(PSDS_Status) + ')@' + PSDS_Line;


if iRC<> 0;
ExceptionInfo =
'** Internal error ' + %char(iRC) + PSDSInfo;
dsply (ExceptionInfo);

*inlr = *on;

Pretty straightforward. Set error code to zero. Execute process()
which returns zero or an error. On error, set iRC to 999 and get the
status and failing line from the program status data structure. After
the monitor block, check the return code. If it's non-zero, display
the error.

The problem? By the time I hit the on-error block, the line number for
the PSDS is the call to process, not the line that actually failed.
Let's assume this is a normal program with H specs and a prototype and
so on. In that case, the line iRC = process() would be, say, line 18.
So every time I get an error, the line number would be 18.00.

So evidently any entry in the call stack causes the PSDS to be changed.
Is there a way to identify the actual failing line?


This thread ...


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

This mailing list archive is Copyright 1997-2020 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].