Just in case anybody happens to care: I found a nice solution to this on http://groups.google.ca/group/comp.databases.ibm-db2/browse_thread/thread/f0a561a079408485/dd5fbeba774bf9fe#dd5fbeba774bf9fe, basically exporting export DB2CLP=**$$** during bash startup does the trick!
solong, H. "Hans Horn" wrote in message news:[EMAIL PROTECTED] > Folks, > > I used to be able to access db2 (v8 and prior) from within a cygwin bash > shell after doing some tricks with the DB2CLP variable (see > http://www.cygwin.com/ml/cygwin/2003-02/msg00635.html). > > e.g. > export DB2CLP=$CLP_SAVE # saved during db2cmd session > > db2 connect to mydb > db2 list tables for all > db2 terminate > > > With db2 v9 this doesn't work anymore, as the db2 connection seems to be > gone after "db2 connect to mydb": when issuing "db2 list tables for all" > I > get now a nasty: > "SQL1024N A database connection does not exist. SQLSTATE=08003" > > does anybody know a workaround? > Or do I really have to use that db2cmd abomination? > > thx, > H. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
