Update the job in plan.
-
--jobname | --jn (string)
-
--description | --des (string)
-
--workstation | --ws (string)
-
--parallel-servers | --ps (number)
- Number of parallel servers that can concurrently run the operation at the workstation
-
--r1-resources | --r1 (number)
- Maximum capacity of workstation resource 1
-
--r2-resources | --r2 (number)
- Maximum capacity of workstation resource 2
-
--form-number | --fn (string)
- Form number or Sysout forms name of the job
-
--extended-name | --en (string)
-
--job-class | --jclass (string)
- Job or sysout class of the job
-
--scheduling-environment | --env (string)
- Scheduling environmnent name of the job
-
--time-dependent | --td (boolean)
-
Jobs are to be submitted at a specific time or as soon as possible.
True: job must NOT start before the input arrival time is reached.
False: job can start as soon as predecessors are completed and resources are available.
-
--follow-job-stream-input-arrival | --fjs-ia | --fjs (boolean)
- Follow jobstream input arrival time. If not specified, current value is used.
-
--start-time | --st (string)
-
Start time date and time of the job, in the format YYYY-MM-DDTHH:MM:SS
The date and time cannot be earlier than the application input arrival, nor later than the application deadline.
Use it in combination with the follow-job-stream-input-arrival option set to false.
-
--deadline | --dl (string)
-
Deadline date and time of the job, in the format YYYY-MM-DDTHH:MM:SS
The date and time cannot be earlier than the application input arrival, nor later than the application deadline.
To clear existent deadline-time pass an empty "" value. Note that any correlated actions will be cleared.
-
--deadline-action | --dla (string)
-
Action to be taken if the operation is still not completed when deadline day and time are reached. If you specify an action, an alert message is issued. Optional.
ALERT: Alert only.
COMPLETE: Operation is completed if its status allows this kind of change, otherwise is NOPed.
NOP: Operation and all its internal successors are NOPed.
ERROR: Operation is set to error with error code ODEA if its status allows this kind of change.
BLANK: No action.
Allowed values: ALERT, COMPLETE, NOP, ERROR, BLANK
-
--not-started-alert-date | --nsald (string)
-
Date and time, in the format YYYY-MM-DDTHH:MM:SS, to check if the operation has not yet started. If so, an alert is issued.
To clear existent not-started-alert-date pass an empty "" value.
-
--not-started-action-date | --nsacd (string)
-
Date and time, in the format YYYY-MM-DDTHH:MM:SS, to check if the operation has not yet started.This check is applied only to ready operations. If you specify date and time, an action is required.
To clear existent not-started-action-date pass an empty "" value. Note that any correlated actions will be cleared.
-
--not-started-action | --nsa (string)
-
Action to be taken if the operation has not yet started when the specified time is reached. If you specify an action, day and time are required.
ALERT: Alert only.
COMPLETE: Operation is completed if its status allows this kind of change, otherwise is NOPed.
NOP: Operation and all its internal successors are NOPed.
ERROR: Operation is set to error with error code OLAT if its status allows this kind of change.
Allowed values: ALERT, COMPLETE, NOP, ERROR
-
--duration | --dur (number)
- Estimated duration of the job, expressed in milliseconds.
-
--critical | --crit (string)
-
If the job is to be considered a Critical Path target, eligible for WLM assistance, or Not eligible for WLM assistance.
Allowed values: NO, PATH, WLM
-
--wlm-policy | --wpol (string)
-
Policy to be used for WLM assistance, if the job has been defined as critical.
LONGDURATION: job is assisted if it runs beyond its estimated duration
DEADLINE: job is assisted if it has not finished when its deadline time is reached
LATESTSTART: job is assisted if it is submitted after its latest start time
CONDITIONAL: an algorithm calculates whether to apply the Deadline or Latest start policy
DEFAULT: the policy specified in OPCOPTS is applied
Allowed values: CONDITIONAL, DEADLINE, LATESTSTART, LONGDURATION, DEFAULT
-
--wlm-class | --wcla (string)
-
--monitored | --mon (boolean)
-
--auto-release | --ar (boolean)
-
Jobs submitted by other than the product must be automatically released at their appropriate time, if placed in HOLD status at job submission time.
True: release jobs at their appropriate time.
False: release jobs immediately.
-
--cancel-if-late | --clate (boolean)
-
Job must be submitted, regardless of the fact that its assigned start time has passed.
True: suppress the submit or release of a time-dependent job, if it is late.
False: submit or release a job when ready, even if the specified time has passed.
-
--auto-submit | --asub (boolean)
-
Job is to be automatically started.
True: job is automatically started.
False: job is NOT automatically started.
-
--auto-error-completion | --aerc (boolean)
-
How error conditions are to be managed for the job.
True: error conditions are automatically tracked and the job is assigned an ended-in-error status if it fails.
False: ignore error conditions and give the job a completed status when it ends.
-
--highest-return-code | --hrc (number)
- Highest accepted return code for a job NOT to be reported as ended-in-error. For FT workstations, this value can be only 0.
-
--user-data | --udata (string)
- User descriptive text to be associated with the job or operation.
-
--cleanup-option | --clean (string)
-
Cleanup action to be taken on computer workstations for operations that end in error or are rerun.
Allowed values: AUTOMATIC, IMMEDIATE, MANUAL, NONE
-
--user-sysout | --usys (boolean)
-
If User sysout support is needed.
True: data store logs User sysout.
False: data store does not log User sysout.
-
--restartable | --rest (string)
-
The operation can be restarted when its primary workstation becomes inactive. Ignored for Fault-Tolerant workstations. Use installation default action.
YES: the operation can be restarted.
NO: the operation CANNOT be restarted.
DEFAULT: use installation default action.
Allowed values: YES, NO, DEFAULT
-
--reroutable | --rero (string)
-
The operation can be rerouted if its primary workstation is rerouted. Ignored for Fault Tolerance Workstation.
YES: operation can be rerouted.
NO: operation CANNOT be rerouted.
DEFAULT: use installation default action.
Allowed values: YES, NO, DEFAULT