During the installation of SLC Hub you can choose the location of the 'var' directory (on Windows this is in C:\ProgramData) which Hub will use for certain files including the WORK temporary libraries. You should choose a 'var' directory with a suitable amount of disk space for all user WORK space.
In SLC Hub the WORK location is managed by the 'nomad' service (which creates session files and WORK libraries under the 'var' directory) and the usual setting of WORK in the .cfg file is not used.
If your 'var' directory is running out of space then you may want to override this default behaviour and you can do it by (perhaps surprisingly) CLEARING the WORK option in a 'Facet' of your 'Execution Profile'.
(A 'facet' is simply a collection of system options. Note that the system options in a facet are labelled with: SET or CLEAR or INSERT or APPEND. This allows system options to be added/changed (SET), removed (CLEAR), or edited [INSERT/APPEND - for multi-part system options] relative to the base set of system options from the initial configuration. By default, an Execution Profile has no facets, so no special system options, in which case the usual initial system options are found from the .cfg files etc.)
You can specify a system option to be SET for all worker nodes. For example I might set WORK to be /big_disk (if I was sure that /big_disk was available on all workers).
There is also the option to specify CLEAR (instead of SET). In this case, the central control of the setting is released, and the specific setting (e.g. in altairslc.cfg) is honoured.
By default, all temporary storage is owned by 'nomad' and is released when the hub session terminates ... but we recognise that other strategies for WORK are often needed.
If you do take WORK outside of nomad control then you need to provide some way to clean up WORK folders if they are orphaned. The 'cleanwork' utility can be used (see separate FAQ). In other words, if the WORK library folders/directories are within 'nomad' directories then nomad takes care of garbage collection. Otherwise, 'cleanwork' should be configured to delete any 'work' directories that have been left lying around (e.g. if a session terminates unexpectedly).
