Restrict command line functions

5 pts.
Tags:
AS/400
AS/400 commands
AS/400 printing
We have users that need access to a specific output queue for printing purposes. However, when we setup a menu option call for them, they are able to get function options line F22 Printers. Is there away to restrict the use of these functions?

Software/Hardware used:
AS/400

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

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

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

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
  • TomLiotta

    What can they do from a command line that causes any problem? If there is anything that they have authority to do that causes trouble, then that's the problem that should be solved. A system shouldn't be vulnerable just because a command line is available. Nowadays, many users are far more familiar with other interfaces than with AS/400 command lines (that shouldn't be a problem to begin with). Commands can be run from a PC (or even from home) without ever seeing an AS/400 command line.

    However, if the command line is your concern, your only two real choices are to run CHGUSRPRF USRPRF(profilename) LMTCPB(*YES) for every user you want to control or to set *PUBLIC *EXCLUDE for every command you want to control. There are approximately 2000 commands in i 6.1, with additional commands in most products you might install plus any commands that might be created on your system. (And excluding users from commands might cause some of your programs to fail, and each future upgrade will require fully reviewing command authorities again.)

    Neither choice will do much to secure your system.

    Tom

    125,585 pointsBadges:
    report

Forgot Password

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

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

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

Thanks! We'll email you when relevant content is added and updated.

Following