Starting the iSeries Navigator SQL tool from shortcut
Patrick Bielen
This question already appeared on the list, but we never had
a suitable answer.
A while ago it was possible to create a shortcut to
"C:\Program Files\IBM\Client Access\Shared\cwbundbs.exe"
to start the SQL tool from iSeries access.
But since a few versions back that does not seems to work
anymore, and indeed as the previous person mentioned,
the process starts, but the SQL tools never gets visible.
The only way to start that puppy is by starting iSeries
Navigator, browse to your databases and then click it
on the botton of the screen (the shortcut in iSeries Nav).
No need to say this is a big overhead if you ask me.
So anybody any idea how to fix this, or does somebody
knows some developers of the iSeries Navigator project
and wants to report this issue ?
Cause this is annoying, really.
Best Regards,
Patrick
Sun Certified Java Programmer
Jonathan Ball
This doesn't create a shortcut, but it's just as good,
and the easiest thing in the world. Two ways:
1. a. Go through the tedious process you describe one
LAST time.
b. In the SQL script window that opens, select
File + Save As; give it some name like 'Basic
SQL Script';
leave the file type as the default, .sql
c. Save it to the desktop.
2. a. Open Notepad.
b. Select File + Save As
c. Change the type to 'All files'; key in the
name, e.g. Basic SQL Script; be *sure* to specify
'.sql' as the file extension.
d. Save it to the desktop.
NOTE: Both of these (effectively, the same thing)
assume that '.sql' is registered to be opened with
cwbundbs.exe, which it should be.
Jonathan Ball
Hmm... I don't know what the problem might be. After
my initial reply, I decided to try to create a shortcut
instead of a .sql file. I located cwbundbs.exe in the
iSeries access folder, right-clicked on it, selected
Create Shortcut, moved the shortcut to the desktop,
opened it, and the SQL script window opened right up,
as expected.
I did it on two machines, one running Client Access
Express at V5R1 on a Windows ME machine, the other
running iSeries Access Express at V5R2 on a Windows XP
Pro machine. The shortcut worked correctly on both.
Robert Comer
> decided to try to create a shortcut instead of a .sql file. I located
> cwbundbs.exe in the iSeries access folder, right-clicked on it, selected
> Create Shortcut, moved the shortcut to the desktop, opened it, and the SQL
> script window opened right up, as expected.
>
> I did it on two machines, one running Client Access Express at V5R1 on a
> Windows ME machine, the other running iSeries Access Express at V5R2 on a
> Windows XP Pro machine. The shortcut worked correctly on both.
That is not the case for V5R3. That executable isn't even included in V5R3
of Client Access. (It appears to be part of CWBUNNAV.exe now)
- Bob Comer
"Jonathan Ball" <jon...@whitehouse.not> wrote in message
news:5a0gd.4590$kM....@newsread3.news.pas.earthlink.net...
Jonathan Ball
>>Hmm... I don't know what the problem might be. After my initial reply, I
>>decided to try to create a shortcut instead of a .sql file. I located
>>cwbundbs.exe in the iSeries access folder, right-clicked on it, selected
>>Create Shortcut, moved the shortcut to the desktop, opened it, and the SQL
>>script window opened right up, as expected.
>>
>>I did it on two machines, one running Client Access Express at V5R1 on a
>>Windows ME machine, the other running iSeries Access Express at V5R2 on a
>>Windows XP Pro machine. The shortcut worked correctly on both.
>
>
> That is not the case for V5R3. That executable isn't even included in V5R3
> of Client Access. (It appears to be part of CWBUNNAV.exe now)
That would change everything. However, my first
technique - create an empty .sql file on the desktop -
will still work, assuming CWBUNNAV.exe is registered to
open that file extension.
I wonder if there's some parameter that can be passed
when calling CWBUNNAV.exe that would tell it to open
the SQL script window?
Robert Comer
> empty .sql file on the desktop - will still work, assuming CWBUNNAV.exe is
> registered to open that file extension.
Yep, that works well, I tried it after I saw your suggestion and it actually
opens up faster this way than doing the shortcut in older CA.
> I wonder if there's some parameter that can be passed when calling
> CWBUNNAV.exe that would tell it to open the SQL script window?
There may be, but I can't find anything in the docs on that.
- Bob Comer
"Jonathan Ball" <jon...@whitehouse.not> wrote in message
news:1T8gd.4797$kM....@newsread3.news.pas.earthlink.net...
Jonathan Ball
>>That would change everything. However, my first technique - create an
>>empty .sql file on the desktop - will still work, assuming CWBUNNAV.exe is
>>registered to open that file extension.
>
>
> Yep, that works well, I tried it after I saw your suggestion and it actually
> opens up faster this way than doing the shortcut in older CA.
I think the .sql files were intended to be used to save
useful scripts, plus the source for SQL functions,
procedures, triggers, etc.
>
>
>>I wonder if there's some parameter that can be passed when calling
>>CWBUNNAV.exe that would tell it to open the SQL script window?
>
>
> There may be, but I can't find anything in the docs on that.
Neither can I; nor anything on the iSeries Access websites.
Patrick Bielen
> Hmm... I don't know what the problem might be. After my initial reply, I
> decided to try to create a shortcut instead of a .sql file. I located
> cwbundbs.exe in the iSeries access folder, right-clicked on it, selected
> Create Shortcut, moved the shortcut to the desktop, opened it, and the SQL
> script window opened right up, as expected.
Sure it does, it was working here aswell, but since a few
versions i use V5R3M0 and it seems to be broken there.
And cause i need the .net managed DB/2 driver downgrading
back to V5R2M0 is not an option.
Just did the same thing as you, and the cwbundbs is active
now in the taskmanager, but unvisible at the desktop, there
is no way it is popping up. If i start it true iSeries navigator
all is fine. And YES i know V5R3M0 is beta.
Oh and by the way, saving a file as .sql and double click it
doesn't work either, just to be informative :-)
Best Regards,
Patrick
Patrick Bielen
> That is not the case for V5R3. That executable isn't even included in
> V5R3 of Client Access. (It appears to be part of CWBUNNAV.exe now)
Well at least it's still in my folders.
Shouldn't it be deleted while updating then ?
Best Regards,
Patrick
Patrick Bielen
> Yep, that works well, I tried it after I saw your suggestion and it
> actually opens up faster this way than doing the shortcut in older CA.
Nope that doesn't work, same problem.
When linking the sql to cwbundbs.exe the program is started
in taskmanager but never pops up.
When i link the .sql to cwbunnav.exe then iSeries Navigator opens
but nothing happens.
Well that proves again, do not touch something that works,
now they've touched it and it's broken... duh.
Jonathan Ball
It works at my client's office, where I use V5R3 (I
have V5R1 and V5R2 on two different machines at home).
It sounds like something in your PC.
Robert Comer
It's not beta anymore, perhaps you should get the released version?
> Oh and by the way, saving a file as .sql and double click it
> doesn't work either, just to be informative :-)
It does here.
- Bob Comer
"Patrick Bielen" <bie...@stafa-nospam.nl> wrote in message
news:4181d091$0$43451$e4fe...@news.xs4all.nl...
Robert Comer
> Shouldn't it be deleted while updating then ?
Yes, at least it did on mine. Maybe I'm at a more recent servicepack level,
or GA vs. beta?
- Bob Comer
"Patrick Bielen" <bie...@stafa-nospam.nl> wrote in message
news:4181d0f9$0$43451$e4fe...@news.xs4all.nl...
Jim Flanagan
>>> Hello,
>>>
>>> I am an IBM developer for iSeries Navigator - Database function.
>>> I wanted to help clear up some of the questions in this chain of posts.
>>> The capability to launch Run SQL Scripts directly from the desktop or
>>> a .sql file is still available in V5R3.
>>> The exe file named cwbundbs.exe does still exist in the Client Access
>>> directory structure. If you installed to your C: drive it should be in
>>> C:\Program Files\IBM\Client Access\Shared
>>> If you are experiencing problems with launching Run SQL Scripts from
>>> a shortcut or a .SQL file, then I would ask that you open an issue through
>>> IBM service to help you get the issue resolved.
>>> Regards,
>>> Jim.
maframaran
In this directory exist a file with name Unity.Toolkit.User$YOURUSERNAME.ser
This file is corrupt, delete it and try to open the application. A new file will be generated.
Sorry for my english, i speack spanish.
maframaran
Jonathan Ball
of IBM i Navigator, then cwbundbs.exe is registered to open files with
a .sql extension. Use a text editor to create a new empty text file;
give it a name like "new SQL script" and a .sql extension. When you
open it, it will start cwbundbs.exe.