X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	"Hans Horn" <hannes AT 2horns DOT com>
Subject:	accessing db2 v9 from cygwin shell
Date:	Wed, 7 Feb 2007 08:50:43 -0800
Lines:	27
Message-ID:	<eqdjh5$k1c$1@sea.gmane.org>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

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/

- Raw text -