× 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: date type field test
  • From: "Art Tostaine, Jr." <atostain@xxxxxxxxxxx>
  • Date: Tue, 06 Jan 1998 09:20:56 -0500
  • Organization: Creative Computer Associates, Inc.

I have a physical file with an L date type.  The field is received from
a custom "EDI" transaction.  A customer sent me a date of 1920/01/01 for
order date, obviously an incorrect date for an order, but a valid date,
and it went in fine to my database.

Now I must send this date back out using another custom "EDI'
application, and my RPGLE program tries to move this date to a *YMD
field, but my program bombs because it is an invalid 6 digit date.
AS/400 thinks 01-39 years are 21st century.

How can I test that this *ISO type date field is also a valid *YMD
field.  If I use the test operation, it won't let me use factor 1 as
*YMD.  If i use TEST(D), the compiler fails because (D) is not needed
because this is already a date field.

I guess I have to move this date to an alpha or numeric field first,
then do TEST(D).

Any other ideas?

--
Art Tostaine, Jr.
Creative Computer Associates, Inc.
Parlin, NJ
atostaine_at_crecomp_dot_com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.