Not wanting to actually touch the source member, I recompiled with "*SRCSTMT" as a compiler option in the command.

The exception showed up today, and this time, the statement number was 21 lines down from what it was telling me yesterday (I'm guessing that somebody changed an include member).

Now, it's a statement that can actually throw the exception, and yet it still puzzles me.

We have a variable, EnterpriseID, defined thusly:

EnterpriseID s 9 0

and then the exception is thrown here

monitor;
EnterpriseID = %dec(xRecordID21:9:0);
on-error;
endmon;

The fact that it's /FREE code tells me that it's not mine, and the monitor/on-error/endmon certainly explains why the exception is not crashing the program.

It's looking more and more like it's completely harmless; nobody catches exceptions and ignores them unless they're harmless.

xRecordId21 is a 21-character field in a data structure. So what's throwing the exception? the call to %dec(), or the assignment of the result to EnterpriseID?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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