Currently, we only run an Oracle listener, ftpmon and jinetd, all of
which we do take down before the backup, as well as NS. Not that we are
not interested in IMAGE/SQL, ODBC, JDBC, etc., and may very well have to
face that question. Good point that LIMIT does not even touch these. So,
setting LIMIT does not matter one way or the other for these; that goes
to answer my question about other issues. Thanks.

> -----Original Message-----
> From: Tony Furnivall [SMTP:[log in to unmask]]
> Sent: Tuesday, September 22, 1998 4:46 PM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] Quiescing before backups
>
> There is also the question of ODBC and other C/S connections.
> Typically
> these do not show up as jobs or sessions, and the only way you can get
> rid
> of them is by shutting down the listener job. Not a problem as long as
> you
> have strong control over the entire system.
>
> I have a client where they need to be able to isolate different
> accounts,
> and this is creating a real problem for C/S type connections.
>
> TOny