Re: Microsoft OLE DB for DB2 driver issue -- MIDRANGE-L

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

What is the reason to convert to a different OLE?? Maybe this is a CCSID
setting.

On Mon, Nov 12, 2012 at 11:56 AM, J Franz <franz400@xxxxxxx> wrote:

Our network side is testing the DB2OLEDB (SQL Server 2008 R2) in place of
the
iSeries Access OLE DB driver
and one big issue...

The sql request is handled by QRWTSVR where the iSeries Access went through
QZDASOINIT.

In the result sets, all the character fields have the trailing blanks
(fixed
length, not trimmed) where as the iSeries Access OLE DB result sets were
trimmed.

Any idea how this is controlled? Too many apps to modify.
V6R1 w/cume 1256

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

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.