If you absolutely cannot change the application or ISV that insists on key8 csa, implement RUCSA you can at least control what users have access to it, although not necessarily preventing one authorized RUCSA user from accessing another's storage.
Does anyone know what the charge is going to be for RUCSA? Dana On Thu, 12 Sep 2019 08:35:19 -0400, Steve Smith <[email protected]> wrote: >You ignored the context of my statement, and your response doesn't address >it. I don't see much added value of a new and complicated way of bypassing >the restriction, when there was already a nice simple way. While it may be >intended for particular customers, the "feature" is public. And while it's >common knowledge big customers tend to get what they want, I'm not clear >why RUCSA is what they wanted (vs. the parm). > >Regardless, I'm only idly curious, this has no effect on my business. > >sas > >On Wed, Sep 11, 2019 at 5:48 PM Mark Zelden <[email protected]> wrote: > >> On Tue, 10 Sep 2019 12:06:59 -0400, Steve Smith <[email protected]> wrote: >> >> >> > So, I'm not sure why >> >IBM is going to all this trouble to ban it, then unban it a little bit. >> > >> >> I think I alluded to it in my OP and IBM also responded that it was for "a >> particular set >> of customers". It wasn't because IBM thought "hey, this sounds like a >> good idea" and >> did all the development work to take a step backwards. >> >> Big customers paying IBM big money have big voices. It may have just been >> one big >> customer, who knows (other than IBM). >> >> Regards, >> > >---------------------------------------------------------------------- >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
