|
| Re: Querying the MIB for estabilished database connectivity |
 |
Fri, 18 Apr 2008 03:53:57 -070 |
Thanks for the reply Ed
Maybe I can monitor the Server Group?
Therefore, if the corresponding database goes down, providing it stops/starts
the relevant Tuxedo server group, I should know from the MIB the connectivity of
the db?
for e.g.
SENT pkt(1) is :
TA_OCCURS 1
SRVCNM .TMIB
TA_CLASS T_SVCGRP
TA_OPERATION GET
TA_SRVGRP DTSGRP_SUN56
RTN pkt(1) is :
TA_ERROR 0
TA_MORE 24
TA_OCCURS 1
TA_GRPNO 260
TA_LOAD 50
TA_PRIO 50
TA_SVCTIMEOUT 0
TA_TRANTIME 30
TA_SRVID 4220
TA_CLASS T_SVCGRP
TA_CURSOR ..TMIB0: 0x48087316
TA_STATE ACTIVE
TA_AUTOTRAN N
TA_BUFTYPE ALL
TA_ROUTINGNAME
TA_RQADDR POLS_RIMWARD_DTSq
TA_SERVICENAME POLSpolmovement
TA_SVCRNAM POLSpolmovement
TA_SVCTYPE APP
TA_SIGNATURE_REQUIRED N
TA_ENCRYPTION_REQUIRED N
TA_LMID SUN56
TA_SRVGRP DTSGRP_SUN56
This would be the call for the ICL idmsx database.
Database is up and therefore so is the server group. If db went down, if I made
it the responsibility of the db to stop the server group, I would know from the
MIB call ACTIVE/INACTIVE.
Do you agree?
|
| Post Reply
|
|
|
|
|
|
|
|
|
|