This has been something that has been on my mind for a long time. It
seems that the GUI tools (Control Center, Command Center, Development
Center, etc) on Windows are flakey and prone to locking up. This has
included going to servers that run AIX, Linux, Dynix and Windows. I
have experienced this since V6 but just shifted over to doing my work
from command line, instead. I can't even find anybody at IBM that
actually uses the GUI tools for their normal work environment) I am
now in and environment where we are shifting from SQL Server (which
has very good GUI tools) to DB2. My developers are complaining
bitterly.

Is my perception in sync with what your experience. If they do work
reliably for you, did you have to do anything special to get them
stable? Have you replaced them with 3rd party tools? If so what
tools did you choose?

thanks

Jack

> I am
> now in and environment where we are shifting from SQL Server (which
> has very good GUI tools) to DB2. My developers are complaining
> bitterly.

That's a big step backwards ( talking about the GUI not the database )

The GUI tools are very bad. I don't understand why IBM is not improving
them. But there are better products on the market.

Maybe you should try : http://www.quest.com/

--
=====================

Grts, Pascal Loonen

I know of the issues on v7. Does anyone have specific complaints on v8?

Jack wrote:

> This has been something that has been on my mind for a long time. It
> seems that the GUI tools (Control Center, Command Center, Development
> Center, etc) on Windows are flakey and prone to locking up. This has
> included going to servers that run AIX, Linux, Dynix and Windows. I
> have experienced this since V6 but just shifted over to doing my work
> from command line, instead. I can't even find anybody at IBM that
> actually uses the GUI tools for their normal work environment) I am
> now in and environment where we are shifting from SQL Server (which
> has very good GUI tools) to DB2. My developers are complaining
> bitterly.
>
> Is my perception in sync with what your experience. If they do work
> reliably for you, did you have to do anything special to get them
> stable? Have you replaced them with 3rd party tools? If so what
> tools did you choose?
>
> thanks
>
> Jack

I'd be interested in seeing some examples where the syntax generated
doesn't work when running remotely.
As for the speed, how much memory do you have on your machine?

Fred Prose wrote:
> In an environment where the GUI tool resides on the same box as the
> instance (ie. a Windows server) the tools are acceptable - but not
> great. If your connection is client to server, learn the command
> line. Half the time the Control Center doesn't even generate the
> correct syntax!
>
> I was hoping that went we went from 7.2 to 8.1 (with fix packs) that
> things would get better. They didn't. And frankly, I don't have the
> patience to wait on the thing - it's too slow.

jbaker@marketron.com (Jack) wrote in message news:<13f72d37.0308190527.34cf3cf1@posting.google. com>...
> This has been something that has been on my mind for a long time. It
> seems that the GUI tools (Control Center, Command Center, Development
> Center, etc) on Windows are flakey and prone to locking up. This has
> included going to servers that run AIX, Linux, Dynix and Windows. I
> have experienced this since V6 but just shifted over to doing my work
> from command line, instead. I can't even find anybody at IBM that
> actually uses the GUI tools for their normal work environment) I am
> now in and environment where we are shifting from SQL Server (which
> has very good GUI tools) to DB2. My developers are complaining
> bitterly.
>
> Is my perception in sync with what your experience. If they do work
> reliably for you, did you have to do anything special to get them
> stable? Have you replaced them with 3rd party tools? If so what
> tools did you choose?
>
> thanks
>
> Jack

I'm looking for a good GUI as well. Something like phpMyAdmin would be
great. Basically, I want to manipulate my data without having to learn
DB2's version of SQL. Point to field, enter data, click - its done.

The control center only seems to go so far (like making the table, but
not being able to manipulate the data).

Anyone?

"Xyerp" <Xyerp@hotmail.com> wrote in message
news:3d7bc779.0309150408.7c6ea3f7@posting.google.c om...
> jbaker@marketron.com (Jack) wrote in message
news:<13f72d37.0308190527.34cf3cf1@posting.google. com>...
> > This has been something that has been on my mind for a long time. It
> > seems that the GUI tools (Control Center, Command Center, Development
> > Center, etc) on Windows are flakey and prone to locking up. This has
> > included going to servers that run AIX, Linux, Dynix and Windows. I
> > have experienced this since V6 but just shifted over to doing my work
> > from command line, instead. I can't even find anybody at IBM that
> > actually uses the GUI tools for their normal work environment) I am
> > now in and environment where we are shifting from SQL Server (which
> > has very good GUI tools) to DB2. My developers are complaining
> > bitterly.
> >
> > Is my perception in sync with what your experience. If they do work
> > reliably for you, did you have to do anything special to get them
> > stable? Have you replaced them with 3rd party tools? If so what
> > tools did you choose?
> >
> > thanks
> >
> > Jack
>
> I'm looking for a good GUI as well. Something like phpMyAdmin would be
> great. Basically, I want to manipulate my data without having to learn
> DB2's version of SQL. Point to field, enter data, click - its done.
>
> The control center only seems to go so far (like making the table, but
> not being able to manipulate the data).
>
> Anyone?

The IBM GUI is written in Java which seems to be part of the problem (or
most of the problem). I have seen similar problems with other Java GUI's.
The GUI does seem to get a little bit better with each release, but is no
match for a native GUI.

The decision to use Java probably sounded good to IBM when they decided to
use it (portability across platforms), but somehow Java just does not seem
to work well as a GUI.

For alternatives I have found Quest Central for DB2 extremely fast, bug free
and easy on the system memory that the db2 gui tools. The personal edition
is also free.
The website is www.quest.com .
Viswanath
"Mark A" <ma@switchboard.net> wrote in message
news:vak9b.21$5f6.14347@news.uswest.net...
>
> "Xyerp" <Xyerp@hotmail.com> wrote in message
> news:3d7bc779.0309150408.7c6ea3f7@posting.google.c om...
> > jbaker@marketron.com (Jack) wrote in message
> news:<13f72d37.0308190527.34cf3cf1@posting.google. com>...
> > > This has been something that has been on my mind for a long time. It
> > > seems that the GUI tools (Control Center, Command Center, Development
> > > Center, etc) on Windows are flakey and prone to locking up. This has
> > > included going to servers that run AIX, Linux, Dynix and Windows. I
> > > have experienced this since V6 but just shifted over to doing my work
> > > from command line, instead. I can't even find anybody at IBM that
> > > actually uses the GUI tools for their normal work environment) I am
> > > now in and environment where we are shifting from SQL Server (which
> > > has very good GUI tools) to DB2. My developers are complaining
> > > bitterly.
> > >
> > > Is my perception in sync with what your experience. If they do work
> > > reliably for you, did you have to do anything special to get them
> > > stable? Have you replaced them with 3rd party tools? If so what
> > > tools did you choose?
> > >
> > > thanks
> > >
> > > Jack
> >
> > I'm looking for a good GUI as well. Something like phpMyAdmin would be
> > great. Basically, I want to manipulate my data without having to learn
> > DB2's version of SQL. Point to field, enter data, click - its done.
> >
> > The control center only seems to go so far (like making the table, but
> > not being able to manipulate the data).
> >
> > Anyone?
>
> The IBM GUI is written in Java which seems to be part of the problem (or
> most of the problem). I have seen similar problems with other Java GUI's.

> The GUI does seem to get a little bit better with each release, but is no
> match for a native GUI.
>
> The decision to use Java probably sounded good to IBM when they decided to
> use it (portability across platforms), but somehow Java just does not seem
> to work well as a GUI.
>
>

"Viswanath Nandigam" <vnandigam@hotmail.com> wrote in message
news:bk7kre$3l5$1@news1.ucsd.edu...
> For alternatives I have found Quest Central for DB2 extremely fast, bug
free
> and easy on the system memory that the db2 gui tools. The personal edition
> is also free.

I think that it has an expiration date on it, so it is not free.

"Mark A" <ma@switchboard.net> wrote in message news:<vak9b.21$5f6.14347@news.uswest.net>...
> "Xyerp" <Xyerp@hotmail.com> wrote in message
> news:3d7bc779.0309150408.7c6ea3f7@posting.google.c om...
> > jbaker@marketron.com (Jack) wrote in message
> news:<13f72d37.0308190527.34cf3cf1@posting.google. com>...
> > > This has been something that has been on my mind for a long time. It
> > > seems that the GUI tools (Control Center, Command Center, Development
> > > Center, etc) on Windows are flakey and prone to locking up. This has
> > > included going to servers that run AIX, Linux, Dynix and Windows. I
> > > have experienced this since V6 but just shifted over to doing my work
> > > from command line, instead. I can't even find anybody at IBM that
> > > actually uses the GUI tools for their normal work environment) I am
> > > now in and environment where we are shifting from SQL Server (which
> > > has very good GUI tools) to DB2. My developers are complaining
> > > bitterly.
> > >
> > > Is my perception in sync with what your experience. If they do work
> > > reliably for you, did you have to do anything special to get them
> > > stable? Have you replaced them with 3rd party tools? If so what
> > > tools did you choose?
> > >
> > > thanks
> > >
> > > Jack
> >
> > I'm looking for a good GUI as well. Something like phpMyAdmin would be
> > great. Basically, I want to manipulate my data without having to learn
> > DB2's version of SQL. Point to field, enter data, click - its done.
> >
> > The control center only seems to go so far (like making the table, but
> > not being able to manipulate the data).
> >
> > Anyone?
>
> The IBM GUI is written in Java which seems to be part of the problem (or
> most of the problem). I have seen similar problems with other Java GUI's.
> The GUI does seem to get a little bit better with each release, but is no
> match for a native GUI.
>
> The decision to use Java probably sounded good to IBM when they decided to
> use it (portability across platforms), but somehow Java just does not seem
> to work well as a GUI.

Maybe IBM should port there java GUI to java with SWT(native windowing
library for Java available on most platforms) like Eclipse... Once
Eclipse gets going it is extremly snappy and realiable... Looks great
too!

Scott

> Is anyone using candle as monitoring tool for UDB? Any experiences?

Michaela

spshealy@yahoo.com wrote in message news:<4cdf286e.0309170607.3881d099@posting.google. com>...
> "Mark A" <ma@switchboard.net> wrote in message news:<vak9b.21$5f6.14347@news.uswest.net>...
> > "Xyerp" <Xyerp@hotmail.com> wrote in message
> > news:3d7bc779.0309150408.7c6ea3f7@posting.google.c om...
> > > jbaker@marketron.com (Jack) wrote in message
> news:<13f72d37.0308190527.34cf3cf1@posting.google. com>...
> > > > This has been something that has been on my mind for a long time. It
> > > > seems that the GUI tools (Control Center, Command Center, Development
> > > > Center, etc) on Windows are flakey and prone to locking up. This has
> > > > included going to servers that run AIX, Linux, Dynix and Windows. I
> > > > have experienced this since V6 but just shifted over to doing my work
> > > > from command line, instead. I can't even find anybody at IBM that
> > > > actually uses the GUI tools for their normal work environment) I am
> > > > now in and environment where we are shifting from SQL Server (which
> > > > has very good GUI tools) to DB2. My developers are complaining
> > > > bitterly.
> > > >
> > > > Is my perception in sync with what your experience. If they do work
> > > > reliably for you, did you have to do anything special to get them
> > > > stable? Have you replaced them with 3rd party tools? If so what
> > > > tools did you choose?
> > > >
> > > > thanks
> > > >
> > > > Jack
> > >
> > > I'm looking for a good GUI as well. Something like phpMyAdmin would be
> > > great. Basically, I want to manipulate my data without having to learn
> > > DB2's version of SQL. Point to field, enter data, click - its done.
> > >
> > > The control center only seems to go so far (like making the table, but
> > > not being able to manipulate the data).
> > >
> > > Anyone?
> >
> > The IBM GUI is written in Java which seems to be part of the problem (or
> > most of the problem). I have seen similar problems with other Java GUI's.
> > The GUI does seem to get a little bit better with each release, but is no
> > match for a native GUI.
> >
> > The decision to use Java probably sounded good to IBM when they decided to
> > use it (portability across platforms), but somehow Java just does not seem
> > to work well as a GUI.
>
> Maybe IBM should port there java GUI to java with SWT(native windowing
> library for Java available on most platforms) like Eclipse... Once
> Eclipse gets going it is extremly snappy and realiable... Looks great
> too!
>
> Scott