Welcome
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
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 plan commands to submit and run the task or workflows.
showjobs
You can use the showjobs command to view the information about tasks.
info format
You can add the info option in the showjobs command to view the information related to tasks displayed in the info format.

What's new
HCL Universal Orchestrator is constantly evolving to offer you the most comprehensive orchestration capabilities. For known limitations, workarounds, and contact information of HCL Customer Support, see Release notes.
What is HCL Universal Orchestrator
An introductory overview of HCL Universal Orchestrator.
Deploying and Administrating
All the information you need to deploy and administrate HCL Universal Orchestrator.
Using the UI
The UI is the HCL Universal Orchestrator interface, from which you can smoothly design your scheduling environment and monitor every process.
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
- 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 Dynamic Workload Console (DWC) or Orchestration CLI 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 Universal Orchestrator. 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, tasks, workflows, and other scheduling or security items.
  - Plan commands
    You can use the plan commands to submit and run the task or workflows.
    - adddep job
      You can use the command option to add dependencies to a task.
    - adddep sched
      You can use the adddep sched command to add dependencies to a workflow.
    - altjob
      You can use the altjob command to modify a task in plan before it starts running.
    - altpass
      You can use the altpass command to change the password of a user.
    - altpri
      You can use the altpri command to change the priority for a task or workflow.
    - cancel job
      You can use the cancel job command to cancel a task.
    - cancel sched
      You can use the cancel sched command to cancel a workflow.
    - confirm
      You can use the confirm command to change the status of a task after it finishes.
    - deldep job
      You can use the deldep job command to delete the dependencies from a task.
    - deldep sched
      You can use the deldep sched command to delete the dependencies from a workflow.
    - fence
      You can use the fence command to set the priority for a workstation to filter tasks.
    - kill
      You can use the kill command to stop a task in progress.
    - limit cpu
      You can use the limit cpu command to set the number of tasks that can run simultaneously on a workstation.
    - limit sched
      You can use the limit sched command to set the number of tasks that can run simultaneously in aworkflow.
    - 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 task.
    - release sched
      You can use the release sched command to release the regular and time dependencies from a workflow.
    - rerun
      You can use the rerun command to rerun a task.
    - set online and set offline
      You can use one of these commands to make a workstation available or unavailable for tasks to run, or to set an event source online or offline.
    - showcpu
      You can use the showcpu command to display the information about workstations.
    - showeventsource
      You can use the showeventsource command to display information about event sources.
    - showjobs
      You can use the showjobs command to view the information about tasks.
      - info format
        You can add the info option in the showjobs command to view the information related to tasks displayed in the info format.
      - Logon format
        You can add the Logon option with the showjob command to view the information related tasks in Logon format.
      - Standard format
        If you do not specify any options with the showjobs command, the results are displayed in the standard format.
    - showsched
      You can use the showsched command to display the information about workflows.
    - submit docommand
      You can use the submit docommand command to schedule the start of a command as a task.
    - submit job
      You can use the submit job command option to start a task.
    - submit sched
      You can use the submit sched command to start a workflow.
  - Plug-in commands
    You can use the plug-in commands to install, delete, or update plug-ins supported by HCL Universal Orchestrator.
  - 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.
  - Orchestration CLI keywords
    You can use Orchestration CLI keywords when defining a workflows and tasks.
  - 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.
  - 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
- Workflow definition
  A workflow is a set of tasks to be run, together with times, priorities, and other dependencies that define the processing order.
- Task definition
  A task definition is a unit of work that specifies an action to be performed on specific workstations in the HCL Universal Orchestrator network.
- Event source definition
  An event source is an item that allows HCL Universal Orchestrator to receive events from specific event plug-ins.
- Calendar definition
  Calendars define the days in which workflows do or do not run.
- Folder definition
  You can use folders to organize your items accordingly to your business needs.
- Credentials definition
  Credential definitions are used to store user IDs and passwords, or tokens.
- Variable table definition
  Variables are values that can change according to the purpose of workflows and task templates.
- Workstation definition
  A workstation is a scheduling item that runs tasks.
- Event plug-in structure
- Managing matching criteria
  In this topic you can find a description of matching criteria.
- Parsing OCLI files in streaming
  HCL Universal Orchestrator enables you to add or replace files containing multiple item types through OCLI in a single command.
- Data exchange and transformation
  This topic explains how you can streamline your workflows using data exchange and transformation.
Orchestrating from Mobile
You can use your mobile devices to manage quickly and easily your whole HCL Universal Orchestrator environment.
Monitoring
Take your environment under control.
Using REST API
Use REST APIs to easily integrate workload scheduling capabilities with external products and solutions.
Uno AI Pilot
Welcome to the HCL Universal Orchestrator AI Pilot documentation. This resource is designed to guide you through everything you need to know about using UnO AI Pilot effectively. You will find detailed instructions, feature overviews, and helpful tips to ensure you get the best experience with UnO AI Pilot.
Troubleshooting
Recover your environment if any issue occurs.
Notices

info format

You can add the info option in the showjobs command to view the information related to tasks displayed in the info format.

The following details are displayed in the info format. The performed command and credential details, such as user name and password are also displayed.

Workstation: The workstation on which the task runs.

Job Stream: The name of the workflow.

SchedTime: The date and time on which the task is scheduled to run. The date is displayed in mm/dd format.

job

The task name. The notation described in the following list might precede the task name.

rerun as
The task that was rerun by using the rerun command.
rerun step
The task that was rerun by using the rerun;step command.

Job File: The name of the script or the executable file of the task.
Note: File names that are too long might wrap, resulting in incorrect paging. You can use the more option to have a clear view of the results that are displayed.

Example

Run the following command:

ocli plan sj WS_AGT_0#TASK1_TASKS.TASK1 info

The result is displayed as follows:

Workstation      Job Stream       SchedTime  Job                                    JobFile
WS_AGT_0        #TASK1_TASKS   1425 03/24
                                             TASK1
    ---
    executable:
      script: ls
      credential:
        userName: trvuser
        password: "${password:trvuser}"