A job can be stopped when it is running or queued. Stopping a job does not "forget it" from the vovserver database. A job can only be stopped by the owner or the Accelerator administrator.
The autoforget flag sets up a job to automatically be forgotten by the system after a certain time, (not including
suspension time) if and only if the job is done, failed, or idle. Jobs that are scheduled, running, suspended or transfer
are never autoforgotten.
All log files are normally stored under the subdirectory ./vnc_logs. To remove all obsolete log files in the current working directory, use the nc clean command.
On occasion, jobs that run successfully outside of Accelerator fail when run through Accelerator. When this occurs, mostly likely the setups are not the same: the environment, inputs or other parameters may be
different, a misconfiguration or there is a problem with NFS.
Reports provide statistical information about all the jobs that are run during a specified time and the usage of the
resources that run jobs. The resources include CPU time, licenses, memory and more.
Some jobs may require a specific platform or operating system (OS) to run. As Accelerator automatically lists platform/OS as a tasker resources, the task of finding the right host to execute a job is easy: specify the required platform/OS as part
of the job resource requirements.
Accelerator provides several commands of job controls, including
wait, stop, cleaning and debugging.
Wait for Jobs
To wait for one or more jobs to complete, use the nc wait command.
Stop Jobs
A job can be stopped when it is running or queued. Stopping a job does not "forget it" from the vovserver database. A job can only be stopped by the owner or the Accelerator administrator.
Autoforget Jobs
The autoforget flag sets up a job to automatically be forgotten by the system after a certain time, (not including suspension time) if and only if the job is done, failed, or idle. Jobs that are scheduled, running, suspended or transfer are never autoforgotten.