Order of user definition
You must order user definitions from most specific to least specific. HCL Workload Automation scans the security file from top-down, with each user ID being tested against each definition in turn. If the user ID is satisfied by the definition, it is selected, and the matching stops.
For example:
- Incorrect:
-
The definitions are intended to determine the following:#First User Definition in the Security File USER TwsUser CPU=@+LOGON=TWS_user Begin job name=@ access=modify End #Second User Definition in the Security File USER Twsdomain:TwsUser CPU=@+LOGON=TWSDomain\\TWS_user Begin job name=@ access=display End
- Users on all workstations with a logon of "TWS_user" will be given "modify" access to all jobs
- Users on all workstations with a logon of "TWSDomain\TWS_user" will be given "display" access to all jobs
- Correct
-
By putting the more specific definition first, both object access definitions are applied correctly.#First User Definition in the Security File USER Twsdomain:Tws_User CPU=@+LOGON="TWSDomain\\TWS_user" Begin job name=@ access=display End #Second User Definition in the Security File USER Tws_User CPU=@+LOGON=TWS_user Begin job name=@ access=modify End
See Sample security file for a practical example.