RE: Debugging ODBC

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

SQL0901 is a generic 'catch all' sql error, telling you to look for the real
error somewhere further down in the joblog.
Finding a joblog on V5R4 is pretty easy provided consultant didn't hit the
OK button on the error on his PC, i.e. something like:

WRKACTJOB JOB(QZDASOINIT)

And then find the one running under the consultant's user profile.  
On previous releases (as well as V5R4) you could do:

WRKOBJLCK <consultant user profile> *USRPRF

And drill into consultant's QZDASOINIT jobs.

There are many causes for this error... one common one required recreating
QZDAPKG system sql package.

If you cannot find the joblog, you can always start an ODBC trace from
consultant's PC, but that doesn't give you information that's quite useful
as the joblog is.

Let's see what the real error is before offering further suggestions.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
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