Identifying users' system authority

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT iSeries Security Changing password security levels and upgrading operating systems on the IBM i Determine the value of parameter UPPWEI in the DSPUSRPRF field Define journal code value "K" Modify content within a journal receiver file Change password parameters on the AS/400 without deactivating user's passwords Prevent insiders with *READ or *USE access from circumventing object authority on IBM i Prevent insiders from obtaining user ids and passwords on the IBM i Change the IBM i system to allow only certain types of SSL protocol versions Authorize a specific user to select files in a separate library Allow a user to view a library prod without granting full access to all data

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

Users will have permission to run commands based on their authority to the command. They or their group can be given an individual or private authority to the command. Or they may have sufficient authority to run the command based on the *PUBLIC authority to the command. *PUBLIC authority is the default access that everyone has to the command if they haven't been given a private authority. Permissions to commands can be granted by running the Edit Object Authority (EDTOBJAUT), Grant Object Authority (GRTOBJAUT), Work with Authority (WRKAUT) or Change Authority (CHGAUT) command. To find out the permissions on the commands listed, run the Display Object Authority command. For example, DSPOBJAUT CHGUSRPRF *CMD will display the users authorized to the Change User Profile command.