RE: Making command parameters off-limits

[Martin Rowe <martin@xxxxxxxxxx>]

On Tue, 19 Jun 2001, alan shore wrote:
> Thanks for the reply, but in answer to what you have written----
> The reason why I chose to use QTEMP, was to temporarily place these here and 
>only for that person taking that option for that time period. Once that person 
>was "out" of that option, these changed commands would no longer be available 
>and the "real" ones would be back in play. If the user lost communication, 
>whilst "in" this option, QTEMP would be purged/removed/no longer available. 
>Signing back on, the changed commands would NOT be available, therefore in 
>using the WRKSPLF command/screen for the users OWN reports, these reports 
>could be deleted etc.
> There IS method in my madness, and obviously if anyone can supply a different 
>method/procedure for what I am ultimately attepting to do, I am as always 
>grateful.

Hi Alan

I don't know if the following falls into your different method/procedure
category but you could try my WRKUSROUTQ utility. It's a WRKOUTQ/WRKSPLF
hybrid routine. As it comes as source code you could tweak it to prevent
deletes (or allow limited ones) and modify the CHGSPLFA option to stay at
SAVE(*YES). See http://www.dbg400.net/usroutq.html for more details.

Regards, Martin
-- 
martin@dbg400.net / jamaro@firstlinux.net
http://www.dbg400.net  DBG/400 - DataBase Generation utilities 
Open Source test environment tools for the AS/400 / iSeries and 
miscellaneous database & spooled file management commands.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---