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.