Thomas, I will forward this to the appropriate developer. In the mean
time, can you specify exactly which permissions needed to be added? This
would be helpful in identifying the problem. Also, which TSM Operational
Reporting version/package did you install?

As to why Operation Reporting said it saved the information successfully,
but then could not retrieve it, I do not know. Without knowing more about
the problem, I would be hard-pressed to conclude that it is simply because
no error checking was done; but in the end, that could indeed be the case.
Rest assured, however, that we have no such "policy" to not check for
errors (if that was our policy, then I would simply say "this is working
as designed"... but I'm not :-) Rather, such code would be treated as a
bug.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/15/2004
06:53:37:

> I work for a large hospital. There is a standard Windows 2000 disk image
> designed for workstations deployed in patient areas. This image is
> installed on nearly all new desktop systems, including those used to
> administer TSM and other centralized infrastructure. I recently had a
> Windows Administrator install Operational Reporting on my desktop
system.
> I was initially unable to set up reports; Operational Reporting kept
> telling me I needed to enter a TSM administrator ID and password, even
> after I had entered that information repeatedly. I was able to set up
> reports after a Windows administrator changed some permission settings.
> I never at any point got an error message telling me that Operational
> Reporting was unable to save the administrator information.
>
> I am now trying to resolve a similar problem with mail server
information
> needed to e-mail reports. Here again, I have never gotten any error
> messages about problems saving the information. Operational Reporting
> claims to save the information successfully, but is subsequently unable
> to retrieve the information.
>
> It would appear that the developers made a policy decision that it was
> unnecessary to check the success of attempted registry updates.