Home
Altair Accelerator User Guide
Basic tasks in Accelerator, including submitting jobs, tracking job information, and analyzing and solving common problems.
Job Management
Jobname Attribute
The jobname is an attribute of a job.

Welcome
What's New
View new features for Accelerator 2025.1.0.
Accelerator Overview
Discover the available Altair Accelerator guides.
Accelerator Tutorials
Discover Accelerator functionality with interactive tutorials.
Altair Accelerator User Guide
Basic tasks in Accelerator, including submitting jobs, tracking job information, and analyzing and solving common problems.
- Use Accelerator Help
  Accelerator documentation is available in HTML and PDF format.
- Accelerator Quick Start
  Accelerator has two main commands, nc and ncmgr.
- Command Line Interface
- Quick Reference
- User Shell Setup
  To set up your user shell with Accelerator you need to know where the Altair Accelerator software has been installed.
- Running a Job
  This section summarizes how to submit and run a job.
- Job Management
  - Job Arrays
    Using an array provides the option of submitting multiple jobs in a specific order.
  - Jobname Attribute
    The jobname is an attribute of a job.
  - Jobclasses
    A jobclass allows multiple job parameters to be set in a single object that can be requested at submission time.
  - Pre-Command and Post-Command Job Conditions
    When a job is being submitted, a pre-condition and/or a post-condition can be specified.
- Schedule Job Submission
- Modify Running Jobs
- FairShare Groups
- Job Placement Policies
- Clean Up Log Files
  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.
- Debug Jobs without Running Accelerator
  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.
- Job Runtime - Monitor and Profile
  When a job is running through a vovtasker, the tasker automatically monitors RAM and CPU utilization of the job, including all of its children.
- Monitor the Workload
- Statistical Information about Resources and Jobs
  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.
- Environment Control
  Setting the environment is critical for correct job execution. Accelerator provides two methods to control the execution environment.
- Job Resources
  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.
- Advanced Information
- Frequently Asked Questions and Troubleshooting Tips
- Deprecated Commands
  This section lists the recently deprecated and obsoleted Accelerator commands and options, and the corresponding current commands and options.
- LSF Emulation
  This document is intended for those who have been using the Platform LSF batch system and are now moving over to the Accelerator system.
Altair Accelerator Administrator Guide
Configure and manage the use of Accelerator after it is installed.

View All Altair Accelerator Help

Jobname Attribute

The jobname is an attribute of a job.

The default value is the null string "".

The jobname does not need to be unique for each job.
The jobname, if defined, is used in the GUI as the primary label for the jobs; otherwise, the tool name is used.
The field associated with the jobname is @JOBNAME@.

To set the jobname in the Flow Design Language (FDL), use the procedure N. For example:

N "Clock Routing"; # A short name for the job.
J vw /some/long/path/to/an/executable/script/script.pl arg1 arg2

Jobname in Accelerator

In Accelerator, the jobname can be set with the option -N. For example:

% nc run -N this_is_my_job  sleep 100

For all products, strict job name checking has been enabled and invalid job name characters will cause an error. For Accelerator and Accelerator Plus, this can be overridden by putting the following in $VOVDIR/local/vncrun.config.tcl:

set ::jobname_lexicon legacy or set ::jobname_lexicon replace.

Legacy will use the more lax job naming rules from earlier releases.

Replace will identify invalid characters in the job name, replace them with "_", and issue a warning to the console.