DB21061E Command line environment not initialized.

Steve D. Perkins

unread,

Oct 17, 2001, 6:20:12 PM10/17/01

to

I've got a problem with DB2 7.1's Command Center (running on Windows
2000) that's driving me crazy, and I'm hoping that someone else might have
seen this before and can share their experience in overcoming it.

This is a fresh, plain-jane, vanilla DB2 installation... taking all the
defaults (actually SEVERAL installations, I've un-installed and re-installed
several times vainly loping that it would help). I pull up the Command
Center GUI tool on the same machine as the DB2 installation, no networking
issues are involved. I use the connection wizard to generate a "connect to
<MyDatabase>" command, but when it's executed it returns this error line in
the output window:

DB21061E Command line environment not initialized.

I'm absolutely stumped... reboots and re-installations haven't helped
any, I'm simply unable to connect to the database after a plain standard
installation. Has anyone else ever seen this message before, or perhaps
might be able to shed some light on what could be causing it?

Larry Menard

unread,

Oct 18, 2001, 8:20:21 AM10/18/01

to

Steve, that message usually occurs when you try to use CLP from a non-DB2
command window. I'm not that familiar with the Command Center, try launching it
from a DB2 command window.

Obviously this is just a work-around, not a solution... I don't have one of
those for you.

"Steve D. Perkins" wrote:

--
Larry Menard
IBM Workstation Database (DB2) Performance Team
Defender of Geese and of all things Natural

kmartin

unread,

Oct 18, 2001, 9:48:07 AM10/18/01

to

I've had similar problems, though only when I'm using Terminal Services
to admin a 2K machine remotely.

Ken Martinson ken.ma...@shawinc.com

--
www.MainFrameForum.com USENET Gateway

Message has been deleted

Larry Menard

unread,

Oct 18, 2001, 1:52:41 PM10/18/01

to

I had a similar (but not quite the same) problem once with Windows ME...
immediate error upon opening a CLP window. I didn't get the SQL1035N though.

In my case the problem was that the default environment size on Windows ME
was too small, & I had to update the setting in the properties of the CLP
Window desktop icon.

No idea if that'll help you, just thought I'd mention it.

"Steve D. Perkins" wrote:

> > Steve, that message usually occurs when you try to use CLP from a
> non-DB2
> > command window. I'm not that familiar with the Command Center, try
> launching it
> > from a DB2 command window.
> >
> > Obviously this is just a work-around, not a solution... I don't have
> one of
> > those for you.
>

> Interesting, I tried your suggestion and noticed that when I pull up a
> DB2 command window I am immediately presented with this error message:
>
> DB2CMD.EXE -> 0
> SQL1035N The database is currently in use.
>
> Apparently this may be the root cause of my problems. Anybody familiar
> with this or seen it before?

Mauro Amico

unread,

Oct 23, 2001, 4:33:46 AM10/23/01

to

I had same problem with w2k, ... look this page:

http://www-4.ibm.com/software/data/db2/udb/ad/db2ir/db2ir455.htm#Header_901

my solution is to set the right permission (write/modify to db2 users)to
C:\Program Files\sqllib\db2clp.dat

Hope this helps.

--
Mauro Amico
Department of Computer Science, University of Bologna
http://www.cs.unibo.it/~amico/

"Steve D. Perkins" wrote:

> > Steve, that message usually occurs when you try to use CLP from a
> non-DB2
> > command window. I'm not that familiar with the Command Center, try
> launching it
> > from a DB2 command window.
> >
> > Obviously this is just a work-around, not a solution... I don't have
> one of
> > those for you.
>