RE: Help with Test for a date and Monitor

Well, I didn't find anything in the manual that directly addresses the issue
at hand, nor have I ever used a TEST within a MONITOR group. But it would
seem that, at the least, that putting TEST(E) in a MONITOR group would be
redundant (i.e., if it worked, which it doesn't seem to do). After the
TEST(E), %Error() will either be '0' (good date) or '1' (bad date). So why
not eliminate the MONITOR code and just use %Error, such as:

TEST(e) RtDate;
IF %error;
(error code)
ENDIF;

Jerry C. Adams
IBM i Programmer/Analyst
When tempted to fight fire with fire, remember that the Fire Department
usually uses water.
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Cyndi Bradberry
Sent: Friday, January 06, 2012 11:09 AM
To: RPG400-L@xxxxxxxxxxxx
Subject: Help with Test for a date and Monitor

I can't seem to get my monitor opcode to work. I defined the error code for
an invalid date in the 'D' specs as BadDate.

I have the date field, *ISO standard. I put the user's entry into this field
and I want to verify it is a valid date. I know I must be missing something,
but the Monitor does not catch the error, instead I get a program error.

I cannot seem to locate a example, can someone please RTM me ?
Code snips:
D RtDate D DatFmt(*ISO)
D BadDate C 112


C Monitor
C Test (E) RtDate
C On-Error BadDate
C Eval SError = 'Invalid Date'
C GoTo ReDisplay
C EndMon


Thank you,
Cyndi B.
Boise, ID