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

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

For one I would get away from MOVE and use %Date instead - what a MOVE does is just non-intuitive.

The easiest way to catch errors of this kind is to place them in a MONITOR group.


Jon Paris
Jon.Paris@xxxxxxxxxxxxxx



> On Mar 13, 2025, at 1:33 PM, James H. H. Lampert via RPG400-L <rpg400-l@xxxxxxxxxxxxxxxxxx> 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.