Re: Disable saving of Query/400 queries.

rob@xxxxxxxxx wrote:

What menu option would allow them to create a query, but not save a query? Object authority might allow me to prevent them from saving into some particular library, but how would I prevent them from saving it into any library?

I know that you can restrict the running of Query/400 queries interactively by doing a CHGCMD on RUNQRY, however is there a way
to allow someone to create a query, run it, but never save it?

There is no supported way. Also, if prevented from saving into a permanent library, that prevents 3=Submit capability; i.e. can not even run it. Probably the only two ways would be to change the translated Y=Save to an obscure\difficult value [but I believe it uses a general Yes\No throughout the product] or to delete the program QQUDS from QQRYLIB [or replace it] which would prevent ever creating any [possibly to even prevent the product from starting].

The best that could be done is probably to be reactive. One could review for T-CO audit entries for the job, then delete those that were created. For example the WRKQRY could be encapsulated in a CLP which upon exit of the request, the program then scans the time period since entry of the request, for any created *QRYDFN objects within the job. The program could then [optionally prompt for] the DLTQRY of each one; probably combined with some reminder that this user is not allowed to create\save those objects.

Regards, Chuck