Re: Killing Idle Client Sessions

Hi There, You resolve this problem by doing the following :- 1. Change the default ReUse rule setting in your OpenLink "Session Rules" Book (oplrqb.ini). The section '[generic_inf7]' currently reads : ReUse = ifsame machine Change this to: ReUse = ifsame user, ifsame application, ifsame database 2. Enable our connection watch dog facility with an interval of 3600 seconds, this is done by modify the 'PingWatchDog' key-value (current default of 90 is too low), this is situated in the '[Protocol TCP]' section of the "OpenLink Session" Rules Book (oplrqb.ini) BTW - the command 'oplshut -s' will show you all current OpenLink ODBC connections, the user names associated with these connections, the source ODBC application name, and server process ID. You can selectively kill a particular OpenLink ODBC session via this utility . Please send e-mail to odbc_support@openlinksw.com if your problems persist. -- Best Regards, Kingsley Idehen President & CEO OpenLink Software http://www.openlinksw.com Universal Database Connectivity Technology Providers Cheryl Kendricks <cherylk@prod1.jcdc.doleta.gov> wrote in article <51ad26$or@cssun.mathcs.emory.edu>... > Ted could you send me that script? > > ------------------------------------------------------------------------- > Cheryl Kendricks > Internet:cherylk@prod1.jcdc.doleta.gov OR cherylk@gwysmtp.jcdc.doleta.gov > DTSI, Inc. > Database Administrator - DOL Job Corps San Marcos, Texas > ------------------------------------------------------------------------ > > On 12 Sep 1996, Ted Martinez wrote: > > > Jeff Craig (settler@hobbes.dbintellect.com) wrote: > > : Does anyone know how to determine whether a database connection from > > ...... > [SNIP] > > Jeff, > > this is kind of an indirect answer to your question; > > > > We have a script that cron runs every hour or so, that checks > [SNIP] > > > > Ted Martinez CIM > > Hewlett Packard (VCD) Factory Information > > > >