Specifying object types
Specify one or more object types that the user or users in the associated user definition is authorized to access. If you specify the object type but no attributes, the authorized actions defined for the user with the access keyword apply to all the objects of that type defined in the HCL Workload Automation domain. If an object type from the following list is omitted for a user or users, no objects of that type can be accessed.
The object types are the following:
- action
- Actions defined in scheduling event rules
- calendars
- User calendars
- cpu
- Workstations, domains and workstation classes
- event
- Event conditions in scheduling event rules
- eventrule
- Scheduling event rule definitions
- file
- HCL Workload Automation database file
- folder
- The folder within which scheduling objects such as, jobs, job streams, and workstations, to name a few, are defined.
- job
- Scheduled jobs and job definitions
- parameter
- Local parameters. See note below.
- prompt
- Global prompts
- report
- The reports on the Dynamic Workload Console that have
the following names:
- RUNHIST
- Job Run History
- RUNSTATS
- Job Run Statistics
- WWS
- Workstation Workload Summary
- WWR
- Workstation Workload Runtimes
- SQL
- Custom SQL
- ACTPROD
- Actual production details (for current and archived plans)
- PLAPROD
- Planned production details (for trial and forecast plans)
- resource
- Scheduling resources
- runcygrp
- Run cycle groups
- schedule
- Job streams
- userobj
- User objects
- vartable
- Variable tables. This includes authorization to the variable definitions in the tables. See the note below.
- wkldappl
- Workload applications
Note: Starting from version 8.5, the parameter object type
is reserved for parameters created and managed in a local parameter database with the
parms utility command, while authorization to act on global variables is managed
using the vartable object type. For this reason, when the security file is migrated from
previous versions to 8.5, a vartable security definition for the default variable
table is added to match each parameter definition found, as part of the upgrade
process documented in the HCL Workload Automation: Planning and Installation
Guide.