Re: .NET Data Provider and CPE3426

Thanks for your insight.

From your post I get that the QZDASOINIT jobs on the I are simply pgms that serve up data for either ODBC and/or OLE/db.

Our pgmr contends that the .NET provider (OLD/db) is much faster than ODBC. Wondering why that would be the case if, in fact, it is true.

Also wondering if the db connectors in 5733OPS (Python and node.js) would serve up data faster than the lugubrious ODBC.

As for making this "visible" it is a request on my part to be able to respond to Q's from the .NET folks as to why we are crashing with the CPE3426 msg.

Jerry



On 12/23/2016 10:15 AM, Nathan Andelin wrote:

How can we make the cause of this visible?

Are you asking how IBM i can provide visibility into something which is
occurring in .Net (i.e. resetting a socket)? Does that seem reasonable to
you?

The .NET Data Provider uses OLE/db and presents on the I as a QZDASONIT job.


I'm a bit confused by the assertion that OLE/db "presents on the i as a
QZDASOINIT job". I would say that OLE/db is a way for .Net programs to
communicate with QZDASOINIT jobs.

From the I's perspective is this the same as ODBC?

I would say that ODBC is another way for Windows applications to
communicate with QZDASOINIT jobs and that ODBC is quite comparable to
OLE/db.