× 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.  Home
  2. MIDRANGE-L
  3. October 2011

Re: DDS Time vs. DDL Time

On Thu, 20 Oct 2011 12:21:03 -0500, Mike Wills wrote:

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 work in a shop where the default date format is *USA, and to make my
programs work I have to specify both DATFMT(*ISO) in my RPG H spec and
add EXEC SQL SET OPTION DATEFMT=*ISO at the top of the C specs in order
to get things to work correctly. Not the same as your issue, but possibly
similar.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.