Re: Quick question: catching exceptions in MOVE statements on time/date data

OOOOpppppppsssss

Forget the last post - of course, TEST(E) can do it.

The only downside is that you are effectively validating the value twice.

For me I would only use TEST(E) if I anticipated a fairly high error rate (for example when validating user input) but would use MONITOR when I only expect 1 in a few thousand to fail.

But that's just me and clearly I have already demonstrated that my brain is not working well today!


Jon Paris
Jon.Paris@xxxxxxxxxxxxxx

On Mar 13, 2025, at 1:49 PM, Brian Parkins <goodprophet.bp@xxxxxxxxx> wrote:

You could use the TEST opcode to check for validity before the MOVE operations.

Brian.

On 13/03/2025 17:33, James H. H. Lampert via RPG400-L wrote:

Fellow programmers:

I've got MOVE statements of the form:

C *ISO MOVE XXXDAT DATE

and

C *HMS MOVE XXXTIM TIME

where XXXDAT and XXXTIM are zoned decimal fields.

And occasionally, I will get bad data for one or both of those fields, crashing the program.

What are my options for catching the exceptions before the program crashes? Obviously an error indicator isn't an option, since MOVE doesn't have one. And it's been a while since I've had to deal with this sort of thing, so forgive me if I'm a bit rusty.

--
JHHL

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.