Prerequisite steps to create job types with advanced options

To install dynamic agents, run the installation program. You can install the dynamic agent during the full installation of HCL Workload Automation or in a stand-alone installation of just the agent. During the installation, you have the option of adding the Java run time to run job types with advanced options, both those types supplied with the product and the additional types implemented through the custom plug-ins.

Follow the installation wizard to complete the installation.

See the section about installation options in HCL Workload Automation Planning and Installation for descriptions of the installation parameters and options.

Pools and dynamic pools help you organize the environment based on the availability of your workstations and the requirements of the jobs you plan to run.

1. From the navigation toolbar, click Administration > Workload Environment Design > Create Workstations.
2. Select a distributed or z/OS engine. The workstations you can create vary depending on the engine type you select.
3. Select the workstation type you want to create.
   • To create a pool, define the dynamic agents you want to add to the pool and the workload broker workstation where the pool is hosted.
   • To create a dynamic pool, specify the requirements that each dynamic agent must meet to be added to the dynamic pool.

The HCL Workload Automation administrator has to grant specific authorizations in the security file to allow the operators to create job types with advanced options.

• In the distributed environment, perform the following steps:
  1. Navigate to the TWA_home/TWSdirectory from where the dumpsec and makesec commands must be run.
  2. Run the dumpsec command to decrypt the current security file into an editable configuration file.

     For more information, see the section about dumpsec in HCL Workload Automation Administration.

  3. Add display and run access to the workstation, as follows:
     • If the operation is performed on the HCL Workload Automation Connector, display and run access is required on the CPU corresponding to the workstation where the job is created.
     • If the operation is performed on the workstation where the job runs, display access is required on the workload broker workstation.

     For more information, see the section about configuring the security file in HCL Workload Automation Administration.

  4. Close any open conman user interfaces using the exit command.
  5. Stop any connectors on systems running Windows operating systems.
  6. Run the makesec command to encrypt the security file and apply the modifications.

     For more information, see the section about makesec in HCL Workload Automation Administration.

  7. If you are using local security, the file is immediately available on the workstation where it has been updated.
     1. If you are using a backup master domain manager, copy the file to it.
     2. Distribute the centralized file manually to all fault-tolerant agents in the network (not standard, extended, or broker agents), and store it in the TWA_home/TWS directory.
     3. Run JnextPlan to distribute the Symphony file that corresponds to the new security file.
• In the z/OS environment, perform the following steps:
  1. Define the fixed resource that owns the subresource and give universal read access to it:

     RDEFINE (CLASS_NAME) FIXED_RESOURCE UACC(READ)

  2. Give user USER_ID update access to the FIXED_RESOURCE fixed resource:

     PERMIT FIXED_RESOURCE ID(USER_ID) ACCESS(UPDATE) CLASS(CLASS_NAME)

  3. Define a RACF resource, JSORACF_RESOURCE, to RACF and give universal read access to it:

     RDEFINE (OPCCLASS) JSORACF_RESOURCE UACC(READ)

     JSO is the 3-character code that RACF uses for JS.OWNER.
  4. Give user USER_ID update access to JSORACF_RESOURCE:

     PERMIT JSORACF_RESOURCE ID(USER_ID) ACCESS(UPDATE) CLASS(CLASS_NAME)

You can define job types with advanced options also using the composer command.

For more information, see the section about job definition in HCL Workload Automation User's Guide and Reference.

You can define job types with advanced options also using the JOBREC statement. See Scheduling End-to-end with Fault Tolerance Capabilities (z/OS).