Re: DDS Time vs. DDL Time

Considering that C# DateTime also requires a valid date and time,
invalid data is unlikely. The output of my line is "15.21.47" which is
a valid ISO time.

--
Mike Wills
http://mikewills.me



On Thu, Oct 20, 2011 at 2:10 PM, Raul A. Jager W. <raul@xxxxxxxxxx> wrote:

There is a difference, in DDL (SQL) defined files, the data is validated
when writing the record, in DDS files it is validated at read time. It
is very likely that your application is trying to write a "wrong time".

Mike Wills wrote:

I am working through an issue here. I have a C#.NET application that
is uploading data to the i. In one application, I have the file
defined as DDS (old habits don't die) with a time field. In this new
application, I am using DDL to create the file and it also has a time
field. I have basically copied and pasted the line from the working
application to the new application and still doesn't work. The only
difference I can see is DDS vs. DDL. Is anyone able to confirm there
is some sort of difference (even though I don't know why there wold
be)?

Working line:
cmd.Parameters.Add("@SUPERVISOR_SIGNED_TIME",
iDB2DbType.iDB2Time).Value =
leaveRequest.SupervisorSignedDateTime.ToString("HH.mm.ss");

Non-working line:
cmd.Parameters.Add("@PAYMENTTIME", iDB2DbType.iDB2Time).Value =
transactions.Transaction.TransactionTimestamp.ToString("HH.mm.ss");

Both leaveRequest.SupervisorSignedDateTime and
transactions.Transaction.TransactionTimestamp are of the same C# type
(DateTime).

The error is:
IBM.Data.DB2.iSeries.iDB2ConversionException was unhandled
Message=A conversion error occurred.
Source=IBM.Data.DB2.iSeries
MessageCode=111
MessageDetails=Parameter: 13.

I am first posting to MIDRANGE-L to eliminate the table out of the issue.

--
Mike Wills
http://mikewills.me

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