RE: Debugging ODBC

["John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx>]

You've probably already done this but this is what I found:

For iSeries Access ODBC: Server machine (function) check error

Probable cause:

Another, previously reported error has prevented the processing of a SQL
statement. The previous error is logged only in the i5/OST job log and is
not returned to the ODBC application. You must locate and retrieve the job
log to identify and resolve the problem.

To find the job log, open a PC5250 emulation session and issue a WRKSPLF
where user is the iSeries user profile used on the ODBC connection. However,
in some cases the joblog is found using WRKSPLF QUSER. For example, it is
necessary to use WRKSPLF QUSER to find the associated joblog when the
prestart jobs fail to start. 


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, May 29, 2008 4:20 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Debugging ODBC

Consultant can ODBC from Excel to LPAR1.  Get's SQL0901 when trying to get 
to LPAR2.  Checked his ID and everything.
No QSYSOPR messages of note.
Nothing in DSPLOG grabs me by the gills.
How do I chase this down?

Rob Berendt