Managing Batch Users
Most platforms require a valid user account associated with each job that OpCon submits. The Batch Users page in Solution Manager lets you create, edit, and delete those accounts and manage which roles can use them.
Batch user privileges — which roles are allowed to use which batch users — are configured separately. Select Manage Privileges on the page toolbar to open the Batch User Privileges dialog, or refer to Batch User Privileges for conceptual background.
To create, edit, or delete batch users, your role must have the All Administrative Functions or All Function Privileges function privilege.
Batch Users page
The Batch Users page lists all defined batch users with the following columns:
| Column | Description |
|---|---|
| Batch User | The login name used to run jobs on the target platform |
| OS Type | The platform the batch user is defined for |
Use the toolbar buttons to manage batch users:
| Button | Action |
|---|---|
| New Batch User | Opens the Add Batch User dialog |
| Edit Batch User | Opens the Edit Batch User dialog for the selected record |
| Delete | Deletes the selected batch user(s) after confirmation |
| Manage Privileges | Opens the Batch User Privileges dialog to grant or revoke role access |
OpCon includes system-reserved batch users that cannot be edited or deleted. The Windows batch user Use Service Account is one such reserved record.
Adding a batch user
To add a batch user, complete the following steps:
- Go to Library > Batch Users in Solution Manager.
- Select New Batch User. The Add Batch User dialog opens.
- In the Select the OS list, select the target platform.
- Enter the login name in the field for the selected platform:
- IBM i: enter a value in User Profile (maximum 61 characters).
- MCP or OpenVMS: enter a value in Identifier. OpenVMS identifiers are limited to 12 characters.
- UNIX: enter the account in Group/User format (for example,
operators/jsmith). - Windows or SQL: enter a value in User (maximum 61 characters).
- If the platform is Windows, enter a password in Password and repeat it in Confirm Password. For SQL, a password is optional; if you enter a password, you must also confirm it.
- Select Save.
Result: The new batch user appears in the list. The platform cannot be changed after the batch user is saved.
Editing a batch user
To edit a batch user, complete the following steps:
- Go to Library > Batch Users in Solution Manager.
- Select the batch user to edit.
- Select Edit Batch User. The Edit Batch User dialog opens.
- Update the login name and, if applicable, the password fields.
- Select Save.
Result: The updated batch user is saved. The platform field is read-only in edit mode.
System-reserved batch users, including the Windows batch user Use Service Account, cannot be edited.
Deleting a batch user
Before deleting a batch user, reassign any jobs that reference it. OpCon blocks deletion of batch users that are still referenced by master jobs or daily jobs.
To delete a batch user, complete the following steps:
- Go to Library > Batch Users in Solution Manager.
- Select the batch user to delete.
- Select Delete. A confirmation dialog opens.
- Select Delete to confirm or Cancel to exit without changes.
Result: The batch user is permanently removed from OpCon.
To see which jobs reference a batch user before deleting it, select the batch user and use the Cross References option. The cross-reference report lists master jobs and daily jobs that use the account.
Managing batch user privileges
Batch user privileges control which roles can submit jobs under a given batch user. Privileges are managed per role and per platform.
To grant or revoke batch user privileges, complete the following steps:
- Go to Library > Batch Users in Solution Manager.
- Select Manage Privileges. The Batch User Privileges dialog opens.
- In Select Role, select the role to update.
- In Select the OS, select the target platform.
- Move batch users between the Available Batch Users and Assigned Batch Users lists as needed.
- Select Save.
Result: The selected role can now run jobs using only the batch users in the Assigned Batch Users list for the chosen platform.
The Role_ocadm role automatically has access to all batch users and cannot be restricted.