ummm, so what if someone copies it into their own clist lib, modifies the id check code, then runs it?
Been there......had to be there actually. we had an oldie where the original developer went off to other pursuits. my id was not authorized......45 seconds later it was. locks are meant to keep honest people out. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark H. Young Sent: Wednesday, July 25, 2007 2:01 PM To: [email protected] Subject: Re: Secure clist On Tue, 24 Jul 2007 08:40:09 -0400, Carroll, William <[EMAIL PROTECTED]> wrote: >Is there any way to secure certain clist from unauthorized use? >For example if I don't want applications to get into the wlm, >Application, how would I do it? If it can be done. >Thanks In Advance. > > > > >Bill Carroll > > I've been on vacation and then bringing up a new z/OS 1.7 in our sand box. So I haven't been on IBM-MAIN ListServ this month. Not sure if anyone suggested putting some code in your CLIST to check if the user is authorized to execute it? Like a TSO Userid validation check. Don't need anything real sofisticated and no need for a RACF/ACF2/Top Secret call. Just a simple id compare check. Either you ARE in the list and can use it, or NOT, then BYE-BYE. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
