How to display all objects authority in a library?
Is there anyway to display (or outfile) all objects authority in a library? DSPOBJAUT require the object name (which i need to key in the name 1 by 1 & there are thousand of them), PRTPUBAUT doesn't include those object which public authority is *EXCLUDE. But what I want to do is check all objects authority in that particular library (including Public *exclude & also their authorization list).
Software/Hardware used:
AS400 V5R4
Software/Hardware used:
AS400 V5R4
ASKED:
March 1, 2011 7:23 AM
UPDATED:
March 16, 2011 12:04 AM
Answer Wiki:
Write a CL program to do the following:
1. Build a list of objects to outfile1 - use DSPOBJD OUTPUT(*OUTFILE)
2. Read through outfile1 and perform DSPOBJAUT on each object. Output results to outfile2. Make sure OUTMBR parm is *ADD
Outfile2 will now have a record for each object with each of their authorities.
To see all answers submitted to the Answer Wiki: View Answer History.
NLKS,
One option would be to do a Display Object Description, DSPOBJD OBJ(YourLib/*ALL) OBJTYPE(*ALL), to an outfile. Then in a CL Program read thru the outfile doing a Display Object Authority to a 2nd Outfile. Remember to use *ADD as opposed to *REPLACE on the 2nd outfile.
Hope this helps,
Bill Poulin
Another quick option would be to create a command in PDM that does a DSPOBJAUT to an outfile with the *ADD option and run that against all objects in a library.
Option . . . . . . . . : OA
Command . . . . . . . . : DSPOBJAUT OBJ(&L/&N) OBJTYPE(&T) OUTPUT(*OUTFILE)
OUTFILE(Mylib/OBJAUT) OUTMBR(*FIRST *ADD)
…there are thousand of them … what I want to do is check all objects authority in that particular library (including Public *exclude & also their authorization list).
An authorization list may have many pages of users listed for each object. Private authorities for each object may print on many pages.
If there really are “thousands of them”, then it doesn’t make much sense to print them all out. The printed output could literally be “thousands of pages”.
Libraries with “thousands” of objects potentially implies a large system with many users. Reviewing authorities in printed form is risky.
It would be far better to have output go to a database file. The file could be queried at any time to see any desired details. The file could be saved for archiving. It could be queried from PCs for data mining. Query results could even be printed if that actually had some use.
Tom