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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Monitor group not working on MOVE to date field???
From: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
Date: Thu, 08 Nov 2007 17:16:39 -0600
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I tried it on both V5R3 and V5R4, both of them trapped the error and turned *IN63 on. (no "hard halt")

Wilt, Charles wrote:

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Monitor group not working on MOVE to date field??? , Wilt, Charles

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