Command Central 10.7 | Using the Command Line Interface | Options for the Commands | sync-job
 
sync-job
When you use this option, Command Central monitors and reports progress details while the job is running, and returns the job status and status description after the job completes. When you omit this option, Command Central does not monitor and report the job progress.
Syntax
{--sync-job | -j}
Arguments and Options
None.
Usage Notes
*Even if the {--wait-for-cc | -t} option is not included in a command, using the {--sync-job | -j} option automatically triggers {--wait-for-cc | -t}. If you use only {--sync-job | -j} and omit {--wait-for-cc | -t}, the command uses the value of the CC_WAIT environment variable, or 120 seconds if CC_WAIT is not specified. For more information, see wait-for-cc.
*If you execute a command with {--sync-job | -j} and {--expected-values | -e} , the result that the command returns is verified against the specified expected values.
*Use in conjunction with the {--retry | -y} and {--wait-for-cc | -t} options to execute commands with long-running operations more reliably. This will ensure that the command is resubmitted in case Command Central is restarted during the operation. For an example, see the "Examples" section of the sagcc exec templates composite apply.
*You can also set syncJob as a parameter of the cc tasks included in an Ant script that executes CLI commands. See Parameters to Use with the cc Task.
*Running a command with {--sync-job | -j} and includeHeaders=none does not return job result and progress details. To obtain job result and progress details, do use{--sync-job | -j} together with includeHeaders=none in the same command.
Examples
*To enable job monitoring and resubmit the command two times when Command Central is restarted and does not come online for 160 seconds and wait a total of 200 seconds for the whole command to be completed:
--sync-job --retry 2 --wait-for-cc 160 --wait 200