Is there any possibility to override the application name shown using
"db2 list applications" in the new Universal Driver. The default
"db2jcchttp8443..." is not very meaningful.

Regards
- Janick Bernet, SwissASP AG

Check out sqleseti() it lets you set app specific handles when you're
running on systems where the name is not helpful...you can use monitor,
or SQL fuctions to get your app name in sps etc.

Janick wrote:
[color=blue]
> Is there any possibility to override the application name shown using
> "db2 list applications" in the new Universal Driver. The default
> "db2jcchttp8443..." is not very meaningful.
>
> Regards
> - Janick Bernet, SwissASP AG[/color]

Check out sqleseti() it lets you set app specific handles when you're
running on systems where the name is not helpful...you can use monitor,
or SQL fuctions to get your app name in sps etc.

Janick wrote:
[color=blue]
> Is there any possibility to override the application name shown using
> "db2 list applications" in the new Universal Driver. The default
> "db2jcchttp8443..." is not very meaningful.
>
> Regards
> - Janick Bernet, SwissASP AG[/color]

Thanks, looks promising.
Now we only need to find a way to call that api from java ;)


Sean McKeough <mckeough@nospam.ca.ibm.com> wrote in message news:<c7qkp6$fb5$2@hanover.torolab.ibm.com>...[color=blue]
> Check out sqleseti() it lets you set app specific handles when you're
> running on systems where the name is not helpful...you can use monitor,
> or SQL fuctions to get your app name in sps etc.[/color]

Thanks, looks promising.
Now we only need to find a way to call that api from java ;)


Sean McKeough <mckeough@nospam.ca.ibm.com> wrote in message news:<c7qkp6$fb5$2@hanover.torolab.ibm.com>...[color=blue]
> Check out sqleseti() it lets you set app specific handles when you're
> running on systems where the name is not helpful...you can use monitor,
> or SQL fuctions to get your app name in sps etc.[/color]

sqleseti can be kind of wacky, but you should be able to use a small sp
to set/get these (sp needs to issue any small sql statement to actually
set the values in the agent)...originally this did not work this way in
v8, but one of the recent fixpacks should have it (can't find someone
right now that'd know the fixpack). Note that when you use sqleseti at
the server, the settings are not propegated back to the client, so you
need to use a consistent interface for accessing them (i.e. always use
your sp wrapper, never use the apis on the client).

Janick wrote:
[color=blue]
> Thanks, looks promising.
> Now we only need to find a way to call that api from java ;)
>
>
> Sean McKeough <mckeough@nospam.ca.ibm.com> wrote in message news:<c7qkp6$fb5$2@hanover.torolab.ibm.com>...
>[color=green]
>>Check out sqleseti() it lets you set app specific handles when you're
>>running on systems where the name is not helpful...you can use monitor,
>>or SQL fuctions to get your app name in sps etc.[/color][/color]

sqleseti can be kind of wacky, but you should be able to use a small sp
to set/get these (sp needs to issue any small sql statement to actually
set the values in the agent)...originally this did not work this way in
v8, but one of the recent fixpacks should have it (can't find someone
right now that'd know the fixpack). Note that when you use sqleseti at
the server, the settings are not propegated back to the client, so you
need to use a consistent interface for accessing them (i.e. always use
your sp wrapper, never use the apis on the client).

Janick wrote:
[color=blue]
> Thanks, looks promising.
> Now we only need to find a way to call that api from java ;)
>
>
> Sean McKeough <mckeough@nospam.ca.ibm.com> wrote in message news:<c7qkp6$fb5$2@hanover.torolab.ibm.com>...
>[color=green]
>>Check out sqleseti() it lets you set app specific handles when you're
>>running on systems where the name is not helpful...you can use monitor,
>>or SQL fuctions to get your app name in sps etc.[/color][/color]