Re: Monitor group not working on MOVE to date field???

On 09/11/2007, at 7:50 AM, Wilt, Charles wrote:

Another developer sent me this question:

Why would this still throw a hard halt when OZDPDX = 0?

433.00 c Monitor
434.00 c *ISO Move OZDPDX CVDate1
435.00 c *ISO Move OZERDX CVDate2
436.00 c On-Error
437.00 c Eval *in63 = *on
438.00 c EndMon


The program went into a MSGW, error message said Date, Time, Timestamp, not valid on statement# 434.

A dump of the program showed OZDPDX did indeed contain all zeros.
OZDPDX PACKED(8,0) 00000000. '000000000F'X



I don't have an answer. Anybody else seen this?

Monitor should catch errors during MOVE right?

Yes. The code as shown is correct and will work. The MONITOR statement will catch the error and control will branch to the ON- ERROR clause.

Unless the code also contains
H OPTION(*SRCSTMT)

the statement number in the exception message will not match the source statement number. So ... are you looking at the correct part of the source?

If that is the correct source statement then I suggest you start looking for PTFs.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------