|
> if I set the user profile to LMTCPB(*YES), the profile should not be able to access any limited command from any ibm tool. The limit capabilities option only works for function that goes through the command analyzer. The SQL CALL command in STRSQL is not a CL command. If you do have object authority in place on the programs that a developer might call from the SQL CALL command in STRSQL, I think they would be prevented from calling that program. In addition, if the called program attempts to manipulate data that the programmer is not authorized to, the program will not complete successfully (assuming that the program doesn't adopt authority). My point in all of this, is that relying on LMTCPB(*YES) as your only access control mechanism for data or programs provides very little security. Patrick Botz
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.