Circumnavigation could be a problem - especially in areas such as SOX compliance. Certain actions must be logged without exception. This is where I need to go! That means calls from JCL, Programs, REXX, Clists, ....... must all be captured. One risk can of course never be fully controlled - a highly qualified system specialist with corresponding SAF permissions.
Regards Jon -----Ursprüngliche Nachricht----- Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag von David Andrews Gesendet: Montag, 29. Januar 2007 17:30 An: [email protected] Betreff: Re: Getting control > I am looking for a way to prevent users calling certain load modules > directly. Instead I would like my module to get control. As John McKown says, this is hard to make foolproof. But you can cover at least one vector pretty easily: if your users are executing the load module directly via JCL, you could code a JES2 exit #6 (presuming you have JES2) to substitute your own program in the EXEC statement internal text. It could be circumvented by a crafty user, but maybe you're not concerned about that. -- David Andrews A. Duda and Sons, Inc. [EMAIL PROTECTED] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.12/654 - Release Date: 27.01.2007 17:02 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
