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








1. I need to discern between a zero date (which should be interpreted as a
valid null date), and other invalid dates.
2.  Readability.  Since i am coding in free format I want something that
will maintain continuity.
It seems what I coded below is not bad, but since it's a common requirement
I'll encapsulate it into a service program procedure.
-Dave




why not use  TEST?
_____________________________________________________
El Tuesday 23 November 2004 14:49, David Keck escribió:
>
> 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;





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.

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.