Interface tools for DB2

[Bob]

Hello and Welcome to Moviephone!

I have been working in DB2 8.x (on UNIX) for a couple of months now
using Windows as a client machine. Coming from an Oracle/SQLPlus
world, I have certain expectations of a tool like "Command Editor" -
or at least I did.

So I have a couple of questions for you db gurus out there that are
familiar with DB2 8.x. I have searched the web and have yet to find
any information.

1. Can I tell DB2 Command Editor that my script directory = "c:
\whatever\myscr ipts" so I don't have to navigate to it each time I
reopen the tool?

2. Can I save and open common scripts without dealing with a dialog
(similar to SQLPlus for those who are familiar with it)? This would
be - run a command and find I am happy with it, type "save myscript".
Then, the next day, type @myscript and have the query run again.

3. Can I define input parameters in saved scripts so that I can run
them and have it prompt me with something to the effect of "input for
Schema:" (or prompt me at all)?

If I can do all of these things, I will sing DB2's praises. I have no
problem with the database itself. If "Command Editor" cannot perform
these things BUT I can go in through a DOS cmd window, I would be just
as happy!

Also, how is DWB for 8.x (I cannot use DWB for 9.x - foolish
bureaucracy!)

[Lennart]

Re: Interface tools for DB2

Bob wrote:

Hello and Welcome to Moviephone!
>
I have been working in DB2 8.x (on UNIX) for a couple of months now
using Windows as a client machine. Coming from an Oracle/SQLPlus
world, I have certain expectations of a tool like "Command Editor" -
or at least I did.
>
So I have a couple of questions for you db gurus out there that are
familiar with DB2 8.x. I have searched the web and have yet to find
any information.
>
1. Can I tell DB2 Command Editor that my script directory = "c:
\whatever\myscr ipts" so I don't have to navigate to it each time I
reopen the tool?
>
2. Can I save and open common scripts without dealing with a dialog
(similar to SQLPlus for those who are familiar with it)? This would
be - run a command and find I am happy with it, type "save myscript".
Then, the next day, type @myscript and have the query run again.
>
3. Can I define input parameters in saved scripts so that I can run
them and have it prompt me with something to the effect of "input for
Schema:" (or prompt me at all)?
>
If I can do all of these things, I will sing DB2's praises. I have no
problem with the database itself. If "Command Editor" cannot perform
these things BUT I can go in through a DOS cmd window, I would be just
as happy!
>
Also, how is DWB for 8.x (I cannot use DWB for 9.x - foolish
bureaucracy!)
>

Many of the developers where I work, use squirrel (
http://www.squirrelsql.org/ ) as an sql frontend for db2, and they seem
to be happy with it. I havent used it much my self, so I can't really
tell whether it meet your needs or not, but it's free of charge so it
might be worthwhile to evaluate.

/Lennart

[Bob]

Re: Interface tools for DB2


Dave - I really appreciate the extended and timely reply.

I am also a command-line type of developer. Its faster, more control,
and it forces you to know more about what is going on - and you can do
things in batch (I generate a lot of batch db scripts using Excel).

I also have the ability to go directly into Unix and use that command
line. Do you know of a good reference for commands in there?

Lenhart - this place is so locked down on tool control its ridiculous
but I have a number of acquaintances that use squirrel and love it.

Bob