My assumption is that QALWOBJRST would normally be *NONE and system programmers would change it to *ALL before applying PTFs.
*NONE is certainly the best practice setting. But sometimes that doesn't work for some environments. In cases where the application adopts authority, *NONE will prevent the promotion of programs through most change management software. So to enable the promotion of these programs, you'd have to specify *ALWPGMADP rather than *NONE. Then, to allow PTFs to be applied, you'd also want to specify *ALWPTF in addition to *ALWPGMADP.
Dig Deeper on Systems Management Tools
Related Q&A from Carol Woodbury
Before changing password levels and upgrading operating systems on the AS/400, ensure the clients connecting to the NetServer do not need the old ... Continue Reading
Look in the audit journal (QAUDJRN) on the AS/400 for an authority failure message with the name of the library as the object name. Use the ... Continue Reading
On AS/400, the journal type AF subtype K, shows that a user profile lacks the special authority required by the function attempting to run. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.