Home
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 job or job streams.
altjob
You can use the altjob command to modify a job in plan before it starts running.

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.
  - Model commands
    You can use the model commands to create or modify the item definitions for folders, jobs, job streams, and other scheduling or security items.
  - Plan commands
    You can use the plan commands to submit and run the job or job streams.
    - adddep job
      You can use the command option to add dependencies to a job.
    - adddep sched
      You can use the adddep sched command to add dependencies to a job stream.
    - altjob
      You can use the altjob command to modify a job in plan before it starts running.
    - altpass
      You can use the altpass command to change the password of a user.
    - cancel job
      You can use the cancel job command to cancel a job.
    - cancel sched
      You can use the cancel sched command to cancel a job stream.
    - confirm
      You can use the confirm command to change the status of a job after it finishes.
    - deldep job
      You can use the deldep job command to delete the dependencies from a job.
    - deldep sched
      You can use the deldep sched command to delete the dependencies from a job stream.
    - kill
      You can use the kill command to stop a job in progress.
    - 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 sched command to release the regular and time dependencies from a job stream.
    - rerun
      You can use the rerun command to rerun a job.
    - set a workstation online and offline
      You can use one of these commands to make a workstation available or unavailable for jobs to run.
    - showcpu
      You can use the showcpu command to display the information about workstations.
    - showjobs
      You can use the showjobs command to view the information about jobs.
    - showschedules
      You can use the showschedules command to display the information about 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 option to start 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. You can use the command either with a plan or a model.
  - 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
- 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 matching criteria
  In this topic you can find a description of matching criteria.
- 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.
- Data exchange and transformation
  This topic explains how you can streamline your workflows using data exchange and transformation.

altjob

You can use the altjob command to modify a job in plan before it starts running.

Overview

You can use the altjob command to make changes to a job definition in plan and start the run. The updated job definition starts separately and you can keep the original definition in the database. You must have submit access to the job.

Syntax and command line options

Before you run the command, you must specify details of the command line options such as job stream name, dependencies,and required permissions. you can enter the command as follows:

ocli plan altjob | aj jobselect ;[streamlogon|logon=new_logon] ;[docommand="new_command"|script="new_script"] ;[noask]

The details that are required with each parameters are as follows:

Restriction: The docommand and script parameters are mutually exclusive and you cannot use them together.

Note: If you edit the definition of a job in plan that contains variables, the job finishes the run, but the variables are not resolved with their current value.

jobselect

For example, enter the following command WA_AGT_0#JOB_STREAM.JOB.

Specify the job to update, by using attributes and qualifiers.

streamlogon|logon=new_logon: You can specify a new user name to run the selected job under.

docommand="new_command": You can specify a new command that the job must run in place of the original command.

script="new_script": You can specify a new script that the job must run in place of the original script.

noask: When you add the noask option as an argument, the agent does not ask for confirmation before it acts on each qualifying item.