|
Steve, >In future releases, will there be a security level that prevents the >creating of a cmd that has the same name as an ibm cmd? I have never heard of anyone suggesting that we prevent customers from naming their commands (or programs) anything they want. >Is this the purpose of the new chgc0100 exit pgm? Provides the ability to >customize parm values, but thru the registered exit pgm route, not thru a >customized version of the cmd. Yes, that is one of its main purposes. The change command exit point and the retrieve command exit point can also be used to determine what command parameters are being used. It has always been a fact that if you provide a customized version of a command in a library that is ahead of QSYS in the library list, that a user that does not want to use that version of the command can key QSYS/Command-name from the command line. So if you customize a command to provide some type of security, then any user that can use a command line can bypass that security. Hopefully, the two new command exit points allow for a more secure design. 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.