Page Comparison

As you become more familiar with using the command line to automate the queuing of certain jobs, it becomes obvious that you can build a greater automated pipeline on top.

...

When a run is completed, the CLI will return with one of the following exist codes:

In additiona, the last two lines in the output contain the final job status, and the location of the output file (if any) on disk.

...

By parsing the exit code and these lines you will be able to take further action in your automation script, depending on the outcome of the run/job.

rem Example Windows batch file

rem run the command:
pc2cmd -silent -auto "C:\MyFile.xlsx"

rem When complete the exit code will be accssible in the %errorlevel% variable
if %errorlevel%==200 (
   echo "Success"
) else if %errorlevel%==204 (
   echo "Suceeded, but no output file was created."
) else if errorlevel 400 (
   echo "There was a problem with your command."
) else (
   echo "Internal error - Something went wrong"
)

...