How can RACF stop someone when they have a legitimate need to update something 
like clists? Or do we keep making the processes so complicated that more people 
jump to Unix where they have complete freedom and control. Security is a 
balancing act of risk versus cost.
Jon.


    On Friday, December 22, 2017 3:40 PM, Paul Gilmartin 
<[email protected]> wrote:
 
 On 2017-12-22, at 14:26:07, Jon Perryman wrote:

>The most obvious and least complicated is by employee's. >Put your dataset in 
>production JCL and it will be caught when added to the job scheduler.>Put your 
>dataset into production program and it will usually go unnoticed. How about 
>Clist libraries that
> 
RACF.
   

Reply via email to