Clearing log in SE/ESQL

I am looking for a way to clear the database transaction log in the SE without shutting down all ESQL applications for the period of time it takes to do a total database backup, and then starting the database. The scenario I would like to follow is to run a program on a periodic basis that: 1. Waits until it can gain exclusive access to the database, 2. locks all the tables, 3. turns off database logging, 3. clears the database log file, 4. starts the database, 5. then releases all of the locks. The goal is to have a periodic process that keeps the log file from growing very large even if the administrator forgets to monitor the size of the log file. I am trying to avoid a situation where the log file fills a file system because an administrator forget to notice that the log file is filling up the disk. I want to keep the transaction log intact between the periods when this special program isn't running so that BEGIN WORK, COMMIT and ROLLBACK statements can be used in ESQL programs. Suggestions/comments on how to achieve this will be greatly appreciated. If someone has successfully dealt with this issue, I would like to hear about it. -- Paul D. Brunner, Software Engineer | "My God.... it's full of stars!" General DataComm, Inc. | - 2001: A Space Odyssey Middlebury, CT 06762 | E-mail: brunner@gdc.com Voice: (203) 758-1811 Ext. 7507