Home
HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.2.2.
User's Guide and Reference
Orchestration CLI
The command line interface to run jobs or job streams and to interact with HCL Workload Automation.
Orchestration CLI commands
You can use the various command options in Orchestration CLI to achieve specific results. The command options are not case sensitive and you can use either uppercase or lowercase letters.
Plan commands
You can use the various command options in Orchestration CLI to achieve specific results. The command options are not case sensitive and you can use either uppercase or lowercase letters.
limit cpu
You can use the limit cpu command to set the number of jobs that can run simultaneously on a workstation.

HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.2.2.
- Planning and Installation
- User's Guide and Reference
  - HCL Workload Automation
  - Understanding basic processes and commands
  - Configuring the job environment
  - Managing the production cycle
  - Using workload service assurance
    Workload service assurance is an optional feature that provides the means to flag jobs as mission critical for your business and to ensure that they are processed in a timely manner. Using this function benefits your scheduling operations personnel by enhancing their ability to meet defined service levels.
  - Customizing your workload using variable tables
    This chapter introduces the concept of variable tables to group global parameters, from now on called variables, to customize your workload.
  - Condition-based workload automation
  - Running event-driven workload automation
  - Defining objects in the database
  - Managing objects in the database - composer
  - Managing workload applications
    Workload applications can be created and then exported so that they can be shared with other HCL Workload Automation environments. In the new environment, the workload application can be subsequently updated, replaced, or deleted.
  - Managing objects in the plan - conman
  - Using Orchestration Query Language from command line
    You can use the essential Orchestration Query Language keywords and syntax to effectively write queries from command line.
  - Orchestration CLI
    The command line interface to run jobs or job streams and to interact with HCL Workload Automation.
    - Configuring Orchestration CLI
      The extension for Orchestration CLI is bundled with the product. If required, you can download it as a stand-alone feature also.
    - Running commands from Orchestration CLI
      After you installed and configured the Orchestration CLI, you can run one or a combination of commands to accomplish specific results.
    - Authenticating Orchestration CLI using API Keys
      When you connect to HCL Workload Automation using Orchestration CLI for the first time, you need to authenticate the connection using API Keys.
    - Orchestration CLI commands
      You can use the various command options in Orchestration CLI to achieve specific results. The command options are not case sensitive and you can use either uppercase or lowercase letters.
      - Access required to run Orchestration CLI commands
        You must have specific permissions to run each command in Orchestration CLI. The level of access to run the command is customizable and you can use the Dynamic Workload Console to manage the roles.
      - Context commands
        The term context refers to the set of parameters in the config.yaml file that is used to establish an environment to run HCL Workload Automation. You can create multiple contexts in the config.yaml file to manage the workload. This helps you to utilize the resources in a more efficient manner.
      - Model commands
        You can use the model commands to create or modify the item definitions for folders, jobs, job streams, and workstations.
      - Plan commands
        You can use the various command options in Orchestration CLI to achieve specific results. The command options are not case sensitive and you can use either uppercase or lowercase letters.
        adddep job
        You can use the adddep command to add dependencies to a job.
        adddep sched
        You can use the adddep command to add dependencies to a job stream.
        altjob
        You can use the command option to modify a job in plan before it starts running.
        altrpri
        You can use the altpri command to change the priority for a job or job stream.
        cancel job
        You can use the cancel command to cancel a job.
        cancel sched
        You can use the cancel command to cancel a job stream.
        confirm
        You can use the confirm command to validate the status of a job after completion.
        deldep job
        You can use the deldep jobcommand to delete the dependencies from a job.
        deldep sched
        You can use the deldep schedcommand to delete the dependencies from a job stream.
        fence
        You can use the fence command to set the priority for a workstation to filter jobs.
        kill
        You can use the kill command to stop a job in progress.
        limit cpu
        You can use the limit cpu command to set the number of jobs that can run simultaneously on a workstation.
        limit sched
        You can use the limit sched command to update the limit set in the definition of a job stream.
        listfolder
        You can use the listfolder command to view the folders in a directory.
        release job
        You can use the release job command to release normal and time dependencies from a job.
        release sched
        You can use the release command to release the normal and time dependencies from a job stream.
        rerun
        You can use the rerun command to rerun a job.
        showcpu
        You can use the showcpu command to display the information related to workstations or cpus.
        showjobs
        You can use the showjobs command to view the informations related to jobs.
        showschedules
        You can use the showschedulescommand to display the informations related to job streams.
        submit docommand
        You can use the submit docommand command to schedule the start of a command as a job.
        submit job
        You can use the submit job command to launch a job.
        submit sched
        You can use the submit sched command to start a job stream.
    - help
      You can use the help command to view the online help or details about the commands that Orchestration CLI supports.
    - version
      You can use the version command to view the version of Orchestration CLI that is installed in your system.
    - Special characters as wildcards and delimiters
      When you want to use filters to select scheduling items in the database, you can use a list of selected special characters as wildcards and delimiters.
    - Orchestration CLI return codes
      Orchestration CLI return codes
    - Managing multiple config.yaml files
      You can create multiple config.yaml files in the database to run commands on different contexts without changing the default context. The feature permits you to use multiple config.yaml files at the same time.
    - Managing multiple formats
      You can set the format by configuring the config.yaml file or by adding the parameter in model commands.
  - Modifying context parameter temporarily
    You can temporarily modify the parameters in the default config.yaml file when you run a plan, model or plug-in command. This feature permits you to customize the behavior of a specific command without modifying the entire config.yaml file.
  - Monitoring HCL Workload Automation
    Using internal and third-party tools to monitor HCL Workload Automation
  - Extending HCL Workload Automation capabilities
    You can extend HCL Workload Automation capabilities by integrating with third-party products. This integration allows you to easily start HCL Workload Automation jobs on external products, while using HCL Workload Automation scheduling capabilities. HCL Workload Automation also provides jobs that perform everyday operations, such as file transfer and web services, and utility jobs that automate and simplify operations, such as the job stream submission.
  - Managing dynamic scheduling
    This section explains how you can manage dynamic scheduling capabilities in your environment to schedule both existing HCL Workload Automation jobs and job types with advanced options, both those supplied with the product and the additional types implemented through the custom plug-ins.
  - Using utility commands
  - Using utility commands in the dynamic environment
  - Getting reports and statistics
  - Managing time zones
  - Defining access methods for agents
  - Managing internetwork dependencies
  - Applying conditional branching logic
    With HCL Workload Automation you can define jobs to run when and as often as necessary. Sometimes some jobs might have to wait for other jobs to finish successfully before they start. Add even more flexibility to your job flows by choosing which job to run depending on the result of the job status or output of a previous job. Whenever you have conditions that specify whether or not a segment of your job flow should run, then that is a conditional dependency.
  - Defining and managing cross dependencies
  - Managing an IBM i dynamic environment
  - Event-driven workload automation event and action definitions
  - Quick reference for commands
  - Accessibility
- Administration Guide
- Scheduling with the Agent for z/OS
- Database Views
- High Availability Cluster Environment
- Driving HCL Workload Automation
- Extending HCL Workload Automation

limit cpu

You can use the limit cpu command to set the number of jobs that can run simultaneously on a workstation.

Overview

The default job limit depends on the type of workstation. For cloud task launcher, the default value is 1000 and for all other types of workstations the value is 100. You can use the limit cpu command to update the limit, and you must have limit access to run the command. Use the show cpu command to view the current limit of a workstation.

Syntax and command line options

You can enter the command as follows:

ocli plan (limit cpu|lc) [folder/]workstation limit noask

The [folder/]workstation and limit parameters are mandatory. The details required with each parameter are as follows:

[folder/]workstation: You can specify the name of the specific workstation to set the limit, by means of attributes and qualifiers. You can also specify the folder that contains the workstation definition. Specifying the folder is optional.

Limit: Specify the number of jobs that you want to run simultaneously on a workstation. There is no maximum limit, and you can specify any positive numerical value. If you do not want to set any specific limits, use the term system.
Important: If you set the limit to zero, only the jobs with hi or go priority run on the workstation.

noask: When you add the option as an argument the agent will not ask for confirmation before taking action on each qualifying job.

Example

To set 10 jobs as a limit on WA_AGT_0 as a workstation limit, run the following command:
```
ocli plan limit cpu WA_AGT_0 10
```