Admin API equivalent to "db2 terminate"

[Dmitri]

Hi there,

Does anybody know what is DB2 UDB admin API equivalent to "db2 terminate"
command?

Some background:
I'm developing monitoring application(http://chuzhoi_files.tripod.com). I
want to be able to specify a node number during attachment, so I'm using
sqlesetc (API for "set client attach_dbpartitionum" command). If user
specifies an incorrect node number, DB2 will fail with something like:
SQL1469N Instance "DB2" (nodenum "1") does not have node "1" specified in
its db2nodes.cfg file. SQLSTATE=08004
In this case, I want to be able to reset active node to a "default" state,
but It seems like the only way to reset is to use "terminate" command and I
can not find corresponding API call.
I've tried to query client information BEFORE executing "set client", but
attach_dbpartionnum info is empty(-1/65535), if DB2NODE is not set.
I can always fall back to "0" as default node number (and it might work for
most of the configurations), but it's possible for some configuarions not to
have node 0.

thanks in advance,
Dmitri

[Sean McKeough]

For an instance attachment, you want 'sqledtin()' to detach.

Since connect/disconnect are SQL, there are no equivalent apis for db
connections.

Dmitri wrote:

Hi there,

Does anybody know what is DB2 UDB admin API equivalent to "db2 terminate"
command?

Some background:
I'm developing monitoring application(http://chuzhoi_files.tripod.com). I
want to be able to specify a node number during attachment, so I'm using
sqlesetc (API for "set client attach_dbpartitionum" command). If user
specifies an incorrect node number, DB2 will fail with something like:
SQL1469N Instance "DB2" (nodenum "1") does not have node "1" specified in
its db2nodes.cfg file. SQLSTATE=08004
In this case, I want to be able to reset active node to a "default" state,
but It seems like the only way to reset is to use "terminate" command and I
can not find corresponding API call.
I've tried to query client information BEFORE executing "set client", but
attach_dbpartionnum info is empty(-1/65535), if DB2NODE is not set.
I can always fall back to "0" as default node number (and it might work for
most of the configurations), but it's possible for some configuarions not to
have node 0.

thanks in advance,
Dmitri

[Amit]

You could prevent the user from specifying a node number - instead
have them select from a list of valid nodes for the database/instance.
This way the users will never be able to specify an invalid node.

You can get the default node number as by calling the get snapshot
function at database manager level before setting DB2NODE. The
node_number (from the collected grouping) will give you the default
node number for your attachments.
You can get the the list of valid nodes for the database by using the
query:
select distinct (dbpartitionnum) from syscat.dbpartitiongroupdef; (use
node and nodegroupdef for v7)
You can get a list of all participant nodes for the instance by using
the following query:
SELECT * FROM TABLE(DB_PARTITIONS()) A;
Of course the disadvantage of this method is that you will need to
have a connection to a database on the instance.

Another sneaky way to get the nodes for an instance is to take a
global snapshot for the database manager and use the node list from
the FCM send/recieve metrics.

thanks
Amit (singleton AT canada DOT com)

"Dmitri" <chuzhoi_at_yahoo_dot_com> wrote in message news:<46********************@comcast.com>...

Hi there,

Does anybody know what is DB2 UDB admin API equivalent to "db2 terminate"
command?

Some background:
I'm developing monitoring application(http://chuzhoi_files.tripod.com). I
want to be able to specify a node number during attachment, so I'm using
sqlesetc (API for "set client attach_dbpartitionum" command). If user
specifies an incorrect node number, DB2 will fail with something like:
SQL1469N Instance "DB2" (nodenum "1") does not have node "1" specified in
its db2nodes.cfg file. SQLSTATE=08004
In this case, I want to be able to reset active node to a "default" state,
but It seems like the only way to reset is to use "terminate" command and I
can not find corresponding API call.
I've tried to query client information BEFORE executing "set client", but
attach_dbpartionnum info is empty(-1/65535), if DB2NODE is not set.
I can always fall back to "0" as default node number (and it might work for
most of the configurations), but it's possible for some configuarions not to
have node 0.

thanks in advance,
Dmitri

[Dmitri]

sqledtin does not rest values specified by "set client".
And I do need to reset attach_dbpartitionnum

Eg.
I attached to node 4 of EEE instance, than I decided to attached to a EE
instance which has only one node or EEE instance where I do not know number
of nodes or node sequence.
Ideally I would like to be able to reset value I specified in prior call to
"set client attach_dbpartitionnum", but it seems like the only way to do so
is "terminate". And I can not find the corresponding API call.

P.S.
In general Admin API suck - for example it's impossible to attach to two
different instances at the same time (sure I can create some proxy code, but
it's almost like reinventing the API)

For an instance attachment, you want 'sqledtin()' to detach.

Since connect/disconnect are SQL, there are no equivalent apis for db
connections.

[Dmitri]

I can not get a list of valid nodes until I attach and I can not attach
until I selected a node (or use default one).
Once I've selected one, there is no way to go back to a default (I can not
find a "terminate" analog)

-dmitri

"Amit" <aa***@hotmail.com> wrote in message
news:85**************************@posting.google.c om...

You could prevent the user from specifying a node number - instead
have them select from a list of valid nodes for the database/instance.
This way the users will never be able to specify an invalid node.

You can get the default node number as by calling the get snapshot
function at database manager level before setting DB2NODE. The
node_number (from the collected grouping) will give you the default
node number for your attachments.

[Amit]

You need to create a new context and set the node number and create an
attachment within the new context. You can look at the following
functions to see how to use contexts (it doean't have to be
multithreaded)

* sqleAttachToCtx - Attach to Context
* sqleBeginCtx - Create and Attach to an Application Context
* sqleDetachFromCtx - Detach From Context
* sqleSetTypeCtx - Set Application Context Type

"Dmitri" <chuzhoi_at_yahoo_dot_com> wrote in message news:<ZL********************@comcast.com>...

I can not get a list of valid nodes until I attach and I can not attach
until I selected a node (or use default one).
Once I've selected one, there is no way to go back to a default (I can not
find a "terminate" analog)

-dmitri

"Amit" <aa***@hotmail.com> wrote in message
news:85**************************@posting.google.c om...

You could prevent the user from specifying a node number - instead
have them select from a list of valid nodes for the database/instance.
This way the users will never be able to specify an invalid node.

You can get the default node number as by calling the get snapshot
function at database manager level before setting DB2NODE. The
node_number (from the collected grouping) will give you the default
node number for your attachments.

[Dmitri]

Thanks a lot, it's working now.
I've seen *Ctx methods before, but I was under impression those API calls
are for connection sharing across threads.
Now I can easily implement multi-instance attachment in one application.

thanks,
Dmitri