UOA:OMQCHGUA

From Remain Software
(Redirected from UOA:OMQCHGUA)
Jump to navigation Jump to search

Change User Authority API (OMQCHGUA) - Help

Change User Authority API (OMQCHGUA)

This Application Program Interface command allows you to manipulate the TD/OMS database. This can be done from a command line or from within your programs.


The command enables you to perform all allowed actions on a User authorization. you can use this command to add, update, and delete the User authorization.

Action code (ACTC)

Specify the action to be performed. The possible values are:

*ADD
Use this action code to add the user authorization.
*CHANGE
Use this action code to change the user authorization. Action code *CHANGE is not allowed for environment security.
*DELETE
Use this action code to remove the user authorization.

Application code (KEY)

Specify the application code. See the description of the application code for more information.

Environment code (PDLC)

Specify the environment code. See the description of the environment code for more information.

User ID or User Class (USER)

The user ID or user class element contains the name of an OS/400 system user, user group or user class. The following rules apply to each entry:

User ID
Enter a valid name of an existing user profile. This is the most detailed level to assign an authorization code to and will overrule any other definition.
User group
Enter a valid name of an existing user group profile. All members of this group are implicitly selected. Specifications at the user level, however, overrules the specifications per user group.
User Class
Valid user classes are:
  • *SECOFR
  • *SECADM
  • *PGMR
  • *SYSOPR
  • *USER

All users belonging to a specified class are implicitly selected. Specifications at group and user level, however, overrules the specification per class.

Authorization code (AUTC)

The OMS authorization code determines which OMS functions can be executed for a user, user class or user group. Some OMS functions also require authority at environment level. Valid authorization codes are:

0=None (*NONE)
No rights are assigned to the related users. This value is useful if authorization codes are assigned at the group or class level and one single user has to be omitted.
1=User (*USER)
Only functions at the end-user level can be executed. These users are in general able to maintain their own user requests and enquire about the related Fix information. The request processor is allowed to maintain the requests from all users if he has authorization code 1 assigned to him.
2=Programmer (*DEV)
Code two is specially meant for functions at the programmer level. They are allowed to maintain their own fixes, to connect objects to fixes, and start Fix Processing. Specific authorization depends on the rights assigned at environment level. The request processor is allowed to maintain the fixes from all programmers if he has authorization code 2 assigned to him.
3=Application manager (*ADMIN)
Users with code 3 are application managers and have rights for all functions at the application level.

Note: 1. See the description per function for a more detailed Note: explanation about rights. The assigned authorization code can be changed at any time.

*SAME
Use this value to indicate that the authorization code does not change if you are in change mode.