ODBC system dsn connections

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

We're struggling to implement an NT based data warehousing package for all
the usual reasons, most importantly "because."

We're currently importing data from the 400 as text files because we can't
make it work with ODBC.  I've tried an experiment with a system DSN, the
only kind the package will work with.  I tried connecting using Excel,
Access, Brio, and the data warehousing product.  Excel and Access were happy
and returned data from a 20,000 record file just fine.  Brio and the other
product choked on accessing the system table catalog.  The product generated
a nice long service dump on the QZDASOINIT job that was servicing it.  The
problem was MCH0601, a space pointer or offset error from QDBGETM.  

Has anyone had similar problems and fixed them?  We're on v4r4 and are not
current on ptfs.  We had the same problem on v4r3 when we were current on
ptfs.  We're using the CA ODBC driver 6.00.00.06. 

TIA
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---