Controlling access to HCL Workload Automation for Z subresources

You can restrict access to HCL Workload Automation for Z data by specifying subresources. This level of protection is useful if you want to permit different users access to a particular HCL Workload Automation for Z function, while allowing the users' access only to their own HCL Workload Automation for Z data. For example, a user might not need access to all applications, only to payroll applications.

If you do not specify subresources, access to HCL Workload Automation for Z data is determined by a user's access to fixed resources or, if fixed resources are not defined, by the user's access to the HCL Workload Automation for Z subsystem. To implement specific protection of HCL Workload Automation for Z data, you must:
  • Give users access to the fixed resource that owns the subresource.
  • Add the subresource to the list of SUBRESOURCES on the AUTHDEF statement.
  • Define to RACF® the RACF® resource name that corresponds to the HCL Workload Automation for Z subresource name.
  • Set up the required RACF® profile for the resource.

Protected fixed resources and subresources shows the subresources that you can protect.

If you change a profile for a subresource while HCL Workload Automation for Z is active, the change does not take effect immediately. Three ways to effect the change are:
  • Stop and restart HCL Workload Automation for Z.
  • Use the modify command (F xxxx,P=GEN followed by F xxxx,S=GEN) to stop and restart the general service subtask.
  • Select Service Functions (item 9 on the HCL Workload Automation for Z dialog main menu), and then select RACF® Resources.
RACF® does not check for a RACF® class until that class is activated. You can activate a class by using the CLASSACT parameter of the SETROPTS command. To enable generic profile checking, define the class in the GENERIC parameter of SETROPTS.