3.1.13.2 Job Owner Designation in Different Scenarios
The Job owner designated by JES system depends on the combination of configurations on artjesadmin and PRIVILEGE_MODE. The following table shows the relation between job owner designation and different configuration scenarios.
Table 3-10 Job Owner Designation in Different Configuration Scenarios
| Configuration Scenario | Job Owner | |
|---|---|---|
When
artjesadmin
is executed
with...
|
When
PRIVILEGE_MODE
is set to...
|
|
| a profile containing a user name |
NONE
|
Oracle Tuxedo user |
| a profile containing a user name |
USER_IDENTICAL or USER_MAPPING
|
Oracle Tuxedo user Note: Oracle Tuxedo SECURITY parameter must be set to USER_AUTH, ACL or MANDATORY_ACL, otherwise JES system fails to start up and the following error message is printed into ULOG: "ERROR: The current Tuxedo security level disallow the given privilege mode".
|
| no profile or a profile containing no user name |
NONE
|
*
A job with an owner “*” can be controlled by anyone. |
| no profile or a profile containing no user name |
USER_IDENTICAL or USER_MAPPING
|
artjesadmin fails to login and the following error message is displayed: "ERROR: failed to join
application."
|
Parent topic: TuxJES User Substitution