Read-only access to a non-*ALLOBJ user

Another simple way to provide read-only access to a non-*ALLOBJ user is put a STRDBG UPDPROD(*NO) in their sign on program and prevent them from executing a CHGDBG or ENDDBG.

In a recent tip Carol Woodbury covered a tip on the Read-only profile. Another simple way to provide read-only access to a non-*ALLOBJ user is put a STRDBG UPDPROD(*NO) in their sign on program and prevent them from executing a CHGDBG or ENDDBG. Assuming the files you want to protect are in production libraries, the user will not be able to open a file for update in those libraries.


This was last published in May 2006

Dig Deeper on iSeries system and application security

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchEnterpriseLinux

SearchDataCenter

Close