Why would you like to want to to that? IMHO, responding to PINGing is a task for the network stack, not for the database engine. If you want to check whether a particular database engine or database is available in the network, you might use the DBLOCATE and DBPING utilities. Thanks Volker, was considering logging each time i get the ISO echo message as am interfacing two systems so would like to find out which system was responsible for the break in communication
(17 Aug '11, 03:44)
Takudzwa
|
Some ideas: If you are logging the messages outside the two databases, you could use SNMP to query the version and log when the query fails: http://dcx.sybase.com/index.html#1201/en/dbadmin/snmpconfig.html If you are logging inside the database you could setup a remote procedure call to a local procedure that selects the version and log when that fails: http://dcx.sybase.com/index.html#1201/en/dbusage/rpc-omni-using.html*d5e42098 |
Are you referring to ISO 8583, this is a financial application level message standard. I am not aware, that any database system is declaring to be in conformance with a business communication standard other than SQL... |