ABA Defaults Form
- Last UpdatedNov 05, 2025
- 4 minute read
This form has three functions:
-
To define the location of all libraries and output files
-
To set the attributes for batch users
-
To allow easy loading of macro files.
The default setup assumes a single defaults file and a single set of ABA libraries. However, it is possible to create several defaults files and accompanying libraries; one for each discipline. You could then access a specific defaults file and hence reference the libraries defined for a specific discipline.
When you access a new defaults file, a record of it is saved in the %PDMSUSER%/aba_defaults file. This file is loaded on entry to the ABA application and removes the need to set the defaults form on each and every entry. If you organize a multi-discipline project and you want this to function, consider a PDMSUSER environment for each user.
To have different defaults across different projects, determine a location for separate defaults files, and modify the location path for each project. Each project default file can then, in turn, reference differently named libraries if so required.
Select Settings then Area Based ADP Defaults to display the ABA Defaults form.

Use the File menu options Save and Load to save or load the default settings to, or from, the defaults file.
To define the location of the libraries, type the location in the relevant field, or navigate to it in the members list and click CE.
The hierarchy is checked every time the defaults form is loaded to ensure that all libraries are correctly located. If this is not the case the 'face' button does not smile, and the hierarchy must be checked to find the problem.
Note: The use of this form in the installation of ABA is covered in the ABA Installation Guide.
The fields in the defaults form are as follows:
|
Defaults file |
Specifies the location directory and name of the defaults file used to store the ABA default settings. |
|
Library |
The top-level LIBY element which holds all the required ABA administrative elements. |
|
Template |
A LIBY or DRTMLB is used to hold all the ABA drawing templates. If a LIBY is used, all relevant DRTMLBs are scanned for templates. |
|
Area |
This can be a LIBY or DLLB to hold all the IDLI (ID List) elements that store the physical limit co-ordinates for each of the ABA geographical areas. Using a LIBY enables multiple DLLBs to be used to split areas by discipline. |
|
Classification |
A LIBY or DLLB used to contain all the IDLI elements for each ABA classification. |
|
Keyplans |
A SHLB is a sheet library used to hold all the OVER (overlay) elements for the keyplans. |
|
Symbols |
A SYLB is a symbol library that contains all ABA symbols, for example north arrows. |
|
Labelling |
A TRLB is a tag-rule library that contains all the ABA tag rules. |
|
Tasks |
A TASKLB is a task library, which holds all the ABA tasks. |
|
Create Hierarchy |
This option is used to automatically create the administrative hierarchy specified in the defaults form. |
|
To use this functionality: Modify the names to the desired settings. If the required structure exists, the Create Hierarchy button will show However, if it does not exist, the button will show Note: This only detects the existence of the LIBY, but not the elements contained within it. |
|
|
To create the hierarchy specified in the defaults form, click the
|
|
|
The previously mentioned process will also create some initial SYMBol elements. The
button icon will then turn to |
|
|
Logfile Location |
Gives the directory path for process logfiles. |
|
User Name |
Specifies the name of the user that will enter the AVEVA base product. |
|
Password |
Specifies the password of the user. |
To load and review macros click the Input File button.
.
.
