Re: Disable saving of Query/400 queries. -- MIDRANGE-L

Subject: Re: Disable saving of Query/400 queries.
From: daparnin@xxxxxxxxxxxxxx
Date: Tue, 10 Feb 2009 11:10:26 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

If you can't easily prevent people from saving there queries in restricted
libraries, you could create a scheduled job that scans the restricted
libraries for *QRYDFN objects, and moves them to a designated query
library. Granted, it's not the ideal solution but it would help keep your
restricted libraries somewhat clean. It might also increase help desk
calls from people asking "Hey, where did my query go?". It also doesn't
address the possibility that a query could create a database file in the
restricted library. In that event, I suppose that you could scan for
*FILE objects with a creation date greater than xx/xx/xxxx. Just a
thought...

Dave Parnin

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Disable saving of Query/400 queries. , Charles Wilt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.