× 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.



Yes, as I mentioned in another reply. A test program I wrote worked as expected also.

In addition, the program was rerun with the same data and no error occurred.

Lastly, there were a number of records processed where OZDPDX = 0 that didn't hard halt. I saw the
messages in the job log.

Here's part of the dump:
ILE RPG/400 FORMATTED DUMP
Program Status Area:
Procedure Name . . . . . . . . . . . . : PM1720R
Program Name . . . . . . . . . . . . . : PM1720R
Library . . . . . . . . . . . . . . : COREPRDPGM
Module Name. . . . . . . . . . . . . . : PM1720R
Program Status . . . . . . . . . . . . : 00112
Date, Time or Timestamp value is not valid (C G D F).
Previous Status . . . . . . . . . . . : 00112
Date, Time or Timestamp value is not valid (C G D F).
Statement in Error . . . . . . . . . . : 00043400
RPG Routine . . . . . . . . . . . . . : *DETC
Number of Parameters . . . . . . . . . :
Message Type . . . . . . . . . . . . . : RNX
Additional Message Info . . . . . . . : 0112
Message Data . . . . . . . . . . . . . :
Date, Time or Timestamp value is not valid.
Status that caused RNX9001 . . . . . . :

here's the *MSGW part of the job log:

RNX0112 Escape 50 11/08/07 15:08:36.503952 QRNXUTIL QSYS *STMT PM1720R COREPRDPGM *STMT
From module . . . . . . . . : QRNXDATE
From procedure . . . . . . : SigExc
Statement . . . . . . . . . : 4
To module . . . . . . . . . : PM1720R
To procedure . . . . . . . : PM1720R
Statement . . . . . . . . . : 43400
Message . . . . : Date, Time or Timestamp value is not valid.

RNQ0112 Sender copy 99 11/08/07 15:08:36.504832 QRNXIE QSYS *STMT QRNXIE QSYS *STMT
From module . . . . . . . . : QRNXMSG
From procedure . . . . . . : InqMsg
Statement . . . . . . . . . : 3
To module . . . . . . . . . : QRNXMSG
To procedure . . . . . . . : InqMsg
Statement . . . . . . . . . : 3
Message . . . . : Date, Time or Timestamp value is not valid (C G D F).

*NONE Reply 11/08/07 15:12:08.025888 QMHSCLVL QSYS 0640 QRNXIE QSYS *STMT
To module . . . . . . . . . : QRNXMSG
To procedure . . . . . . . : InqMsg
Statement . . . . . . . . . : 5
Message . . . . : D

And here's earlier in the job log where the monitor worked as expected:

RNX0112 Escape 50 11/08/07 14:26:36.444960 QRNXUTIL QSYS *STMT PM1720R COREPRDPGM *STMT
From module . . . . . . . . : QRNXDATE
From procedure . . . . . . : SigExc
Statement . . . . . . . . . : 4
To module . . . . . . . . . : PM1720R
To procedure . . . . . . . : PM1720R
Statement . . . . . . . . . : 43400
Message . . . . : Date, Time or Timestamp value is not valid.

RNX0112 Escape 50 11/08/07 14:26:36.445208 QRNXUTIL QSYS *STMT PM1720R COREPRDPGM *STMT
From module . . . . . . . . : QRNXDATE
From procedure . . . . . . : SigExc
Statement . . . . . . . . . : 4
To module . . . . . . . . . : PM1720R
To procedure . . . . . . . : PM1720R
Statement . . . . . . . . . : 44700
Message . . . . : Date, Time or Timestamp value is not valid.

RNX0112 Escape 50 11/08/07 14:26:36.445760 QRNXUTIL QSYS *STMT PM1720R COREPRDPGM *STMT
From module . . . . . . . . : QRNXDATE
From procedure . . . . . . : SigExc
Statement . . . . . . . . . : 4
To module . . . . . . . . . : PM1720R
To procedure . . . . . . . : PM1720R
Statement . . . . . . . . . : 43400
Message . . . . : Date, Time or Timestamp value is not valid.

Doesn't make any sense to me.

It certainly appears that the monitor around statement #434 quit working.

Guess I'll look for PTFs.


Charles



-----Original Message-----
From: rpg400-l-bounces+wiltc=cintas.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+wiltc=cintas.com@xxxxxxxxxxxx] On
Behalf Of Scott Klement
Sent: Thursday, November 08, 2007 6:17 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Monitor group not working on MOVE to date field???

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


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




This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.