RE: Monitor Date Conversion Fills Job Log

IMHO,

The way you are doing is best since it prevents the exception from being
thrown.  Thus, improving performance.

However, I've seen example code that used the Receive Message API to clean
up expected exception messages.  

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: David Keck [mailto:DavidKeck@xxxxxxxx]
> Sent: Tuesday, November 23, 2004 12:50 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Monitor Date Conversion Fills Job Log
> 
> 
> 
> 
> 
> 
> 
> In populating a file with true date fields from another large 
> file with
> YYMMDD signed numeric date fields I find that my job log fills up with
> RNX0112 messages (Date Not Valid) due to numerous Zero YYMMDD 
> date values.
> The severity on this message is 50 so I can't reasonably 
> solve the problem
> by changing the job's logging level.  A sample is a 
> transaction void date
> which usually contains zero.  I am getting around the problem by
> specifically testing for a zero date in an IF statement, 
> before checking
> for generic date errors via the monitor clause as shown below.
>       Is there a more elegant solution ?
> 
> Message ID . . . . . . :   RNX0112       Severity . . . . . . . :   50
> Message type . . . . . :   Escape
> Message . . . . :   Date, Time or Timestamp value is not valid.
> 
> if hdr_VoidDate = *zero;
>    hdr2_vDateISO = d'0001-01-01';
> else;
>    monitor;
>       hdr2_vDateISO = %date(hdr_VoidDate : *YMD);   // 
> Transaction Date
> *ISO
>    on-error;
>       hdr2_vDateISO = d'0001-01-01';       // default date
>    endmon;
> endif;
> 
> Thanks, Dave
>