Database Locking in Online 6.0

Question for you Online 6.0 gurus: HP-UX 9 4GL RDS 4.10 UE2 Online 6.0 ??? We can't execute a "database ourdb exclusive" command in a 4GL program. In our application, we have a login 4GL program that access our database for user logins and passwords to the application. This program then executes a "close database" statement and launches another 4GL program via a run statement. In the launched program, in certain instances we try to lock the database in exclusive mode. In all versions of database engine (SE and Online) up to 6.0 this works fine. The close database in the login program terminates the backend engine process and the sub-program has the only live database connection. Thus, it is able to lock the database. Our customer upgraded from Online 5.xx to Online 6.0 and now reports that he cannot lock the database in the subprogram like it used to work before he upgraded the engine. Is there some other command we have to give 6.0 to remove our connection to the engine daemons in the login program? Close database doesn't seem to work this way anymore. We have not recompiled our programs using the new engine. We didn't even know he was upgrading engines until he called with this problem! Thanks, ------------------------------------------------------------------------------ Alan Goodman | Data Systems Support Sr.Programmer/Analyst | 1228 Shelly Ct. internet : alan@dssmktg.com | Orange, CA 92668 USA bangpath: uunet.uu.net!dssmktg!alan | Voice 714-771-0454 Fax 714-771-3028 ------------------------------------------------------------------------------