Home
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
Managing HCL UnO agent in Unix operating systems
You can manage the agent by using scripts that are generated while configuring the agent or by Daemon process. It is recommended to use any method for ideal cohesion and efficient administration.
Decoding exit codes for script management
The exit code is displayed after each command runs, to indicate the status of the command output.

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.
- Job stream definition
  This topic introduces the job stream definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Job definition
  This topic introduces the job definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Calendar definition
  This topic introduces the calendar definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Folder definition
  This topic introduces the folder definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Credentials definition
  This topic introduces credentials definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Variable table definition
  This topic introduces the variable table definition, that can be managed from the Orchestration CLI and from the Dynamic Workload Console.
- Workstation definition
  This topic introduces the workstation definition, that can be done from the Orchestration CLI and from the Dynamic Workload Console.
- Managing an event source definition from the Orchestration CLI
  In this topic you can find the syntax to manage an event source definition.
- Event plug-in structure
- Static pools
  A static pool in HCL Universal Orchestrator groups multiple workstations together and manages the workload by assigning jobs to available workstations within the pool. This helps to optimize resource utilization.
- Managing matching criteria
  In this topic you can find a description of matching criteria.
- Managing HCL UnO agent in Unix operating systems
  You can manage the agent by using scripts that are generated while configuring the agent or by Daemon process. It is recommended to use any method for ideal cohesion and efficient administration.
  - Managing HCL UnO agent using Daemon process in Unix operating systems
    When you configure the agent for the first time, the process creates Daemon script that can be used to manage HCL UnO agent afterward. You can run each scripts to accomplish specific results.
  - Managing HCL UnO agent using scripts in Unix operating systems
    When you configure the agent for the first time, the process creates multiple scripts that can be used to manage HCL UnO agent afterward. You can run each scripts to accomplish specific results.
  - Decoding exit codes for script management
    The exit code is displayed after each command runs, to indicate the status of the command output.
- Managing HCL UnO agent in Windows operating systems
  You can manage the agent by using scripts that are generated while configuring the agent or by Daemon process. It is recommended to use any method for ideal cohesion and efficient administration.
- Managing time zones
  In this topic you can find information about managing time zones.
- Policy-driven plan
  The new HCL Universal Orchestrator policy-driven adaptive plan makes your workload more autonomous, dynamic and scalable.
- 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.

Decoding exit codes for script management

The exit code is displayed after each command runs, to indicate the status of the command output.

If you issue a command to run a script to manage an HCL UnO agent, an exit code is displayed based on the status of the command output. You can see the list of exit codes with their description in the following table:


Exit code	Description
`0`	The command runs successfully.
`3`	The command encountered a generic error. Check the Orchestration CLI log, lower the log level to display more information in the log using the `--messageLogLevel` command, and run the script again.
`4`	No agent configuration is found. This error can be solved by configuring the agent following this procedure.
`5`	The agent is running already. If the agent is already running, you cannot use the `start` script.
`6`	The agent is not running. Some scripts cannot function if the agent is not running. If you encounter this exit code, start the agent using the `start` script.
`7`	The stop command is failed. There might be cases where altough the `stop` sript runs successfully, the stop signal is not succesfully sent and the agent keeps running. In those cases, try running the `stop` script again. If the issue persists, check the Orchestration CLI log.
`8`	The agent name cannot be changed when reconfiguring the agent. The name given during the agent configuration procedure is final and it cannot be changed at a later stage.