Re: Preventing users from RUNQRY Interactively

[NigsRpgId@xxxxxxx]

Randy,

I hope what I am going to say next is right as it is some time since I last 
did this & I dont have access to an as400 just now to check this out....

The method I have seen used most often is to put a library with special 
versions of os400 commands (say QSYS_MOD) above QSYS in QSYSLIBL.  This 
leaves QSYS in tact, and QSYS_MOD has the full list of changed comands. Since 
QSYS_MOD is in the system portion of the library list, it is out of harms way 
for edtlibl, chglibl etc..

Then if you ever want to use the genuine command either qualify it on the 
command line (QSYS/RUNQRY) or create a menu option or new comand which points 
to the QSYS version of the required command and give users access to this 
menu option / command if required.

This way you have a full list of changed commands in one place - QSYS_MOD.

To cope with upgrades and new releases of os400, you could write a CL program 
which executes crtdupobj and chgcmddft or grtobjaut etc for the commands that 
you need special versions of.

hth
Nigel .
+---
| 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
+---