|
Using a default date is one idea. An alternative is to use null values. Requires the use of a "null indicator" (No, I am NOT talking about a *INxx field). A search of the reference for null indicator should do the trick for you. Actually, your IF is extraneous. The monitor should catch that also. If a vast majority of your dates are valid, and just a small percentage are zeros, you may even get better performance by removing the IF and rely solely on the monitor. That way you don't waste cycles checking valid dates. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com David Keck <DavidKeck@xxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 11/23/2004 12:49 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To rpg400-l@xxxxxxxxxxxx cc 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 David Keck NBTY, Inc Phone (631) 200-5809 DavidKeck@xxxxxxxx Confidentiality Notice: This communication and attachments are intended for the personal and confidential use of the designated recipient(s) named above. This communication and attachments are intended for the recipient only. If the reader of this message is not an intended recipient(s) or agent of the intended recipient(s), you are hereby notified that you have received this document in error, and that any use, review, distribution, or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to sender and deleting all copies of the communication and attachments. Although this E-mail and attachments are believed to be virus and defect free, it is the responsibility of the recipient to ensure that the same are virus and defect free. The sender disclaims all responsibility for any loss or damage arising from the use of this communication or attachment.Thank you.-- 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.
As an Amazon Associate we earn from qualifying purchases.
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.