The File/User/System DSN issue really only affects how the DSN is locally stored and how it is accessible. The actual implementation is the same in all cases.

I have used ODBC quite a bit in SQL EM to import data using DTS. Beyond that particular application I am not sure how else SQL EM would use iSeries data (e.g. there is no "connector" and it can't, to my knowledge, manage iSeries tables).

DTS works well though.  A heckofalot better than the DB2 tools.

Pete Helgren

Fleming, Greg (ED) wrote:

Mike,

Mine seems to be set up as a User DSN.
I also don't recall setting it up, although I did set one up on one of
our other machines.

I may be wrong, but I think it was automatically set up when I installed
Iseries Access.
Anyhow, I'm not sure what all can be done with it.  I've only played
with it a little to fetch some data via DTS package.  And I think I also
used it from Query Analyzer.
Sounds like Pete Helgren might know more.  See his earlier reply and let
him know what kind of tree you're trying to bark up, and I think he'll
point you in a better direction than I can.

Greg

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.