|
I don't use iSeries Access file transfer (so why am I replying to this?
not sure.)
But, that error usually crops up when you have a date like 0001-01-01
(the year 1) and you try to convert it to a 2-digit year. Since the
system doesn't want it to convert to 01-01-01 (since that would be
perceived as 2001) it throws the error message.
Is it possible to set your transfer options to include a 4-digit year?
James Rich wrote:
Hi list,
We're trying to use data transfer in iSeries Access to transfer a file
from the i to the PC. The file includes date fields. Some of the dates
are *LOVAL and when transferring we get error SQL0181 "Value in date,
time, or timestamp field not valid". Any solution to getting the file
transferred?
James Rich
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-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.