RE: SQL CLI: I'm puzzled.

I think of CLI as native (local) ODBC interface.  I haven't had much call to
use it on iSeries since embedded SQL serves my purposes well.
That said, I think you don't really need to specify server name, user id and
password on SQLConnect.  You should be able to pass *LOCAL for server name
and NULLs for user id and password, i.e.:

SQLConnect (*hdbc, "*LOCAL", SQL_NTS, NULL, SQL_NTS, NULL, SQL_NTS);

There are excellent CLI FAQs on IBM site:
http://www-03.ibm.com/servers/eserver/iseries/db2/clifaq.htm
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/info/cli/rzadpk
ickoff.htm

Elvis

-----Original Message-----
 Subject: SQL CLI: I'm puzzled.

I'm starting to read up on SQL CLI, and the SQLConnect 
call has me puzzled: it seems to assume the data is on any 
arbitrary server.

What if the data is sitting in a bunch of physical files 
on the same box that's executing the call, and the program 
making the call doesn't necessarily know the user-ID it's 
running under, much less the password?

". . . we're awake, but we're very puzzled."

--
JHHL