Read-only access to a non-*ALLOBJ user

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 first published in May 2006

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
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
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.