Re: Making command parameters off-limits

AH - HA . We are presently on V4r3, but are planning to upgrade to V4r5 on the 
weekend of July 20. Even though I have this magazine, I have only perused it. 
Now which pile of paper is that under.
Thanks, this sounds exactly what I am looking for
VERY much appreciated.

>>> "Ed Fishel" <edfishel@us.ibm.com> 06/19/01 09:38AM >>>

Alan,

>>This is where my problem comes in. Is there anyway of ensuring that this
parameter can then be made OFFLIMITS to the user, so that if option 2
(change) on the WRKSPLF screen is taken, the SAVE parameter will remain
untouchable at *YES.<<

If you are using V4R5 or V5R1 there is one other solution you can use to
prevent a user from using the SAVE parameter on the CHGSPLFA command. You
can use a Change Command exit program to do this.

I wrote an article that was published in the May issue of News/400 that
showed how to use one of these exit programs to prevent a user from using
the RUNPTY parameter on the CHGJOB command. You should be able to take the
sample RMVRUNPTY program and modify it to remove or protect the SAVE
parameter on CHGSPLFA.

Ed Fishel,
edfishel@US.IBM.COM 


+---
| 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 
+---

+---
| 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
+---