Configuration files are members of a PDSE. The data set record format is fixed or fixed block with a record length of 80. No line numbers can exist in columns 72-80. All 80 columns are processed as data.
 
All configuration files are installed in the UNVCONF library. See #Configuration File Syntax, below, for the configuration file syntax.

Configuration files are regular text files on UNIX. The files can be edited with a text editor. See #Configuration File Syntax, below, for the configuration file syntax.
 
Universal Broker searches for the configuration files in a fixed list of directories. The Broker will use the first configuration file that it finds in its search. The directories are listed below in the order they are searched.

• /etc/opt/universal
• /etc/universal (installation default)
• /etc/stonebranch (obsolete as of version 2.2.0)
• /etc
• /usr/etc/universal
• /usr/etc/stonebranch (obsolete as of version 2.2.0)
• /usr/etc

Although configuration files can be edited with any text editor (for example, Notepad), the Universal Configuration Manager application, accessible via the Control Panel, is the recommended way to set configuration options. Universal Configuration Manager provides a graphical interface and context-sensitive help, and helps protect the integrity of the configuration file by validating all changes to configuration option values.

The configuration files on IBM i are stored in a source physical file named UNVCONF in the UNVPRD520 library. The files can be edited with a text editor. See #Configuration File Syntax, below, for the configuration file syntax.

The configuration files on HP NonStop are stored as EDIT files, file code 101, within the $SYSTEM.UNVCONF subvolume. The files can be edited with the EDIT editor. See #Configuration File Syntax, below, for the configuration file syntax.