This is in response to the "Commands to Avoid Running in QINTER" article in the November 1990 issue.
I agree that the commands listed should never be run interactively. But no matter how often people hear this, someone always thinks "one time won't hurt anything." To prevent people from executing commands interactively, the following command should be executed from each command to restrict:
CHGCMD CMD(xxx) ALLOW(*BATCH *BPGM)
This will issue an error message, CPD0031 - Command xxx not allowed in this setting, when someone attempts to run the command interactively.
Just a few notes on using this technique. The CHGCMD should be coded in a CL program so that the same commands can be issued when a new release of the operating system is installed. Also, you should *EXCLUDE the public from using the CHGCMD, because they could change it right back!
Louise Best Milwaukee, Wisconsin
The technique shown above will work provided that there are no interactive programs that legitimately run the commands being blocked. In order for this technique to work better, each command should be changed by issuing:
CHGCMD CMD(xxx) ALLOW(*BATCH *BPGM *IPGM *EXEC)
If you are on Release 3.0, you may wish to consider adding *BREXX and *IREXX if you are considering using REXX.