Certain software at VPAC requires licenses. You must be a member of the appropriate group for restricted software. Please reference the software license table (below) for help in acquiring the correct numbers of software licenses for your jobs.
To add restricted software to your account, you will need to login, using your HPC account, on the VPAC website:
You will then be redirected to your profile. Scroll down to the "Tasks" and select "Add Software". Once you have agreed to the license, you should be able to load the appropriate module.
When submitting a job, it is important to ensure that you have sufficient licenses for the job to run. This allows the queuing system to properly allocate jobs and licenses so they can run with maximum efficiency.
If licenses are not requested properly, it is very possible that you may submit a job, and whilst the job is in the queue waiting to run, another user takes the licenses that you desire. In this scenario the job will spawn, but then die.
For some software it is possible, prior to running a job to see how many licenses are available for MATLAB, for example;
When submitting a job it is possible to request licenses in advance from the qsub command;
qsub -l nodes=1 -l walltime=0:10:0 -W x=GRES:licenseA+1 -I
It is also possible to include this in a PBS script, for example to request 1 license from licenseA and 3 licenses from licenseB;
#PBS -W x=GRES:licenseA+1%licenseB+3
Example scripts for Fluent licenses can be found on the clusters at:
Please reference the software license table (below) for help in acquiring the correct numbers of software licenses for your jobs.
Please note that users must use the % symbol to separate different tokens and not a comma. This is a change as of Moab 5.4. Our submit script changes this for you and gives you a warning, except for interactive jobs.
The following sections detail how many licenses or tokens are required for specific software packages. Please refer to our licenses page  for information about how to request these. Also how to set up ANSYS/Fluent licenses  which have particular requirements in their own right.