If those aren't supported, what about implementing
DataSource.setLoginTimeout() or
SybDataSource.setLoginTimeout()?
Thanks
AseCommand.CommandTimeout
<bc> wrote in message news:4b281b70.1a2...@sybase.com...
The driver should easily be able to implement it's reaction to
DriverManager.setLoginTimeout().
All that call does is to set a value in DriverManager so when/if a
driver calls getLoginTimeout()
it gets that value. Setting the socket timeout on the driver's
creation of the socket it uses
to connect to the DBMS is as simple as it can be...
Joe Weinstein at Oracle (nee j...@sybase.com in the 80's and mid 90's)