6.3 Setting registered users
When you have settled the range in which to manage user access permissions and the host that will manage access permissions, you must register the JP1 users at JP1/AJS3. Register JP1 users according to their purpose, and set the appropriate permissions for each JP1 user.
The following table gives an example of the registration of JP1 users.
|
JP1 User name |
Purpose |
|---|---|
|
jp1admin |
Used to manage the entire system. This user has administrator's permissions for JP1/AJS3 (JP1/AJS3 Console), JP1/IM, and JP1/Base set as defaults. The following permissions are set: jp1admin: *=JP1_AJS_Admin, JP1_JPQ_Admin, JP1_Console_Admin JP1_AJS_Admin : Administrator's permission for JP1/AJS3 JP1_JPQ_Admin : Administrator's permission for JP1/AJS3 job execution environment, queues, etc., and Administrator's permission for agent management information JP1_Console_Admin : Administrator's permission for JP1/IM We recommend that JP1 users who perform normal operations such as defining or executing jobnets use jp1mngr, not jp1admin. |
|
jp1mngr |
Used to manage work tasks (user who is a work task administrator) and execute processing (user for executing jobs). Set for this user the permission to refresh, execute and monitor all work tasks. Also set the permission that enables execution of processing that - owing to the specifications of the OS or program - cannot be executed without an administrator's permission or superuser permission. The following is an example of a permission setting. jp1mngr: *=JP1_AJS_Manager, JP1_JPQ_Operator JP1_AJS_Manager : permission to edit and execute work tasks JP1_JPQ_Operator : permission to operate job execution environments, queues, etc., permission to operate jobs, and permission to operate agent management information |
|
jp1user |
Used to execute processing (user who executes jobs) To ensure efficient operation management, standardize the users who execute jobs at the work task manager host. The following is an example of a permission setting. jp1user: *=JP1_AJS_Manager, JP1_JPQ_Operator JP1_AJS_Manager : permission to edit and execute work tasks JP1_JPQ_Operator : permission to operate job execution environments, queues, etc., permission to operate jobs, and permission to operate agent management information |
|
jp1ope |
Used to monitor work tasks and to rerun them manually. This user is intended for operators, allowing them to monitor work tasks and perform manual operations. The following is an example of a permission setting. jp1ope: *=JP1_AJS_Operator JP1_AJS_Operator : permission to execute work tasks, permission to view work tasks |
|
jp1guest |
Used to monitor work tasks only. This is a work task monitoring user for operators. The following is an example of a permission setting. jp1guest: *=JP1_AJS_Guest JP1_AJS_Guest : permission to reference work tasks |
|
root |
Used to monitor JP1/AJS3 job execution environments, queues, etc. Note that when the jpqxxxx command is executed from the command prompt, the OS user that executes the command must be registered as a JP1 user. The JP1 user called root explained in this example means the root user of the OS (UNIX). (When using Windows, the OS user of the Administrators group must be registered as the JP1 user of the Administrators group.) The following is an example of a permission setting. root: *=JP1_JPQ_Admin JP1_JPQ_Admin : permission to manage job execution environments, queues, etc. |
For details on the permissions that can be set for JP1 users, see 6.4.1(2) Determining JP1 permission levels.
You can omit registration of JP1 users but you need to register such JP1 users to execute jobs.
If you omit the registration of JP1 users and set access permissions as described in 6.4 Setting access permissions, JP1/AJS3 assumes that JP1 users having the same names as the OS users are registered.