> On 3/8/2006 4:55 AM, Bruce Hewson wrote:
> > Can anyone explain why the BMC RECOVER UTILITY for VSAM, Version 2.1
> > requires users to have ALTER access to BMCRUV.SUBSYS.ssid,
> BMCRUV.COMMAND
> > and BMCRUV.REPOSITORY profiles.
> >
> > The Customization Guide insists that ALTER access is mandatory.
> >
> > I need an explanation to satisfy the auditors.


And Walt Farrell replied;

> Those appear to be BMC-related resources.  As such, I believe the only
> answer can be either:
> (a) ask BMC; or
> (b) because, for reasons of their own, BMC decided to check for ALTER
in
> order to authorize use of their utility.
> 
> Personally, I don't understand why your auditors would care.  Your
only
> responsibility should be to run things as the product developers
> documented that you should run them.  If you do not do so, then I
would
> expect the auditors to question why you chose to do things
differently.
>   However, if you're running things as the documentation requires,
then
> the auditors should not have a problem.  If they do, then (again,
> personally, not making a statement for IBM here) I think you should
> respectfully suggest that they take it up with BMC.

To which I say - "what he said". I am not involved in the VSAM recovery
products so I won't speculate why the developers felt they needed those
profiles and access levels - however, they are clearly BMC-specific and
granting the required access to those individuals who use the product,
while potentially inconvenient, is unlikely to bring an end to
civilization as we know it. 

You can always call our support line to have these questions answered by
people much more qualified than me. If you would like, I can ask our
VSAM guys to respond to the list so everyone gets to see the answer.

CC

----------------------------------------------------------------------
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

Reply via email to