Re: Date conversion on chain

Remember *MDY has no room for year 9999 -- ans the two digit year is
assumed from some range that I forgot now. Read the database as it is
defined and convert in code. Data management will never be able to
represent that date as an *MDY date.



On Wed, Apr 16, 2014 at 1:05 PM, Horn, Jim <jim.horn@xxxxxxxxxxxxxx> wrote:

I have a file that contains a date field with a value of 9999-12-31. I
need to "chain" this record into a program that has an Hspec of
datefmt(*mdy). I am getting error RNQ0114, Date or timestamp value not in
correct range. If I change the program to datefmt(*usa) the chain works.
The program specs say I need to use datefmt(*MDY). Tried entering a D
spec with the field name with DATEFMT(*mdy). Didn't work. Any ideas?

Jim

--


***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.

--
This is the RPG programming on the IBM i (AS/400 and 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.