Re: Authorizations needed for OpsNav SQL PerformanceMonitor
"Elvis Budimlic" <ebudimlic-Ebbh53c6wcYkzXN11fiE55igCaZBIYHkAL8bYrjMMd8@public.gmane.org> Tue, 22 May 2007 17:02:32 -0500
| Newsgroups | gmane.comp.systems.as400.security |
|---|---|
| Message-ID | <018801c79cbc$e93a8660$6e01a8c0@VMHXP> |
Dan, I am not aware of one, but that's no guarantee :) I do know that STRDBMON command which is used internally by SQL Performance Monitors requires *JOBCTL authority when collecting on someone else's job (even though F1 help doesn't specify that requirement). Elvis Celebrating 10-Years of SQL Performance Excellence http://centerfieldtechnology.com/training.asp -----Original Message----- Subject: [Security400] Authorizations needed for OpsNav SQL PerformanceMonitor (cross-posted on midrange-l) I am attempting to set up a performance monitor on select jobs (on demand) via OpsNav's SQL Performance Monitor. I've gotten this to work fine on our development box, but our production box is more secure, and when I try to set the "schema for the saved data", I get an error that tells me that I'm not authorized: "Not authorized to object QAUGDBLL in QUSRSYS type *FILE." A DSPOBJAUT on this object shows that *PUBLIC has only *USE authority. (Not sure why this isn't "enough" authority for OpsNav.) Anyway, before I go bugging the sysadmins to change the authorization on this particular object, it would be nice to know if there are other objects that SQL Performance Monitor uses that are impacted by *PUBLIC/*USE authority. Anybody know? FWIW, servers are at v5r3 and OpsNav is at v5r3. TIA, Dan _______________________________________________ This is the Security Administration on the AS400 / iSeries (Security400) mailing list To post a message email: Security400-Zwy7GipZuJhWk0Htik3J/[email protected] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/security400 or email: Security400-request-Zwy7GipZuJhWk0Htik3J/[email protected] Before posting, please take a moment to review the archives at http://archive.midrange.com/security400.