For each platform that uses default initialisation files, there are two available: the Master Initialisation file, and the Local Initialisation file (located in the current directory of the local system). The format for the two files are the same. When PROIV loads, it looks for the Master Initialisation file and loads the information. PROIV then looks in the current directory (or the directory where the executable is loaded for Windows) for the Local Initialisation file and loads that information.

The initialisation file can be used in the command line during startup. For example, if the name of the initialisation file is ‘myfile.ini’, and it is located in a directory named ‘mydir’, the Unix command line reads ‘pro /INI:/mydir/myfile.ini’.

Each initialisation file is divided into sections such as Database, Environment, etc. Each section provides PROIV with information that is specific to your installation. With respect to priorities and conflicts between the Master Initialisation file and the Local Initialisation file, the local file cannot override the Database section of the master file. However, the local file can override the Environment section of the master file.

PRORUNTYPE cannot be set up in the Master or Local Initialisation files. The following table provides the default names of initialisation files for several platforms. Although each platform is unique, the sections and settings within the initialisation files are understood across platforms.

Platform                                    Local Initialisation File                      Master Initialisation File

Windows                                     LOCAL.INI (16-bit)

Unix                                          .proivrc                                                  /etc/Proivrc

The environment variable PROAPPL, if defined, contains the location and name of the alternate Master Initialisation file. The environment variable PRO4CFG, if defined, contains the location and name of the alternate Local Initialisation file.

At start-up, PROIV checks for the environment variable PROAPPL.  If PROAPPL is not defined or does not exist, the default Master Initialisation file is used. Next, the environment variable PRO4CFG is checked. If PRO4CFG is not defined or does not exist, the default Local Initialisation file is used.

Comment on this topic

Topic ID: 750032