Dave, The OP specs need clarification, that was what I was eluding to Scott ford www.identityforge.com from my IPAD
> On Mar 13, 2014, at 2:05 PM, "Gibney, Dave" <[email protected]> wrote: > > Solid control of access by VOLUME is not straight forward and requires an > exit (IG????PRE I think, RTM). Mitigating the need for this control is one of > the purposes of SMS. > Location is not a good criteria for security. Data ownership is much more > reliable. > > >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] >> On Behalf Of Scott Ford >> Sent: Thursday, March 13, 2014 6:29 AM >> To: [email protected] >> Subject: Re: Volume Restriction Using an EXIT >> >> Lizette and Elardus. Have excellent points furthermore it *sounds* like it >> can >> be done with RACF. >> But their question still stands and needs to be answered >> >> Scott ford >> www.identityforge.com >> from my IPAD >> >> >> >> >>> On Mar 12, 2014, at 10:41 AM, Elardus Engelbrecht >> <[email protected]> wrote: >>> >>> mf db (Peter) wrote: >>> >>>> Is there an exit which can help me to restrict a group of ID to access >> another Volume(Which has list of datasets). >>> >>>> For example : JLAB001 must be restricted to access any dataset sitting on >> JPM009. >>> >>> Lizette gave you good questions, but I have two more questions: >>> >>> 1. What will you do if those dataset(s) moved from that volser? What then? >> Will they be unprotected? I had rather use the dataset profile themselve and >> perhaps consider conditional access too if needed. >>> >>> 2. What will you use to access those datasets? Depending on the >> product/method, there may be alternatives. >>> >>> I will repeat Lizette question again: What are you trying to resolve? >>> >>>> I am at Z/OS 1.8 level >>> >>> Time for upgrade... :-) >>> >>> Groete / Greetings >>> Elardus Engelbrecht >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, send >>> email to [email protected] with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send email to >> [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
