Setup

 

Introduction

This chapter deals with the setup of the FML32 environment. Before you can begin to work with FML32 fielded buffers you must set environment variables appropriate for your application. These activities are described in this chapter.

Directory Structure

The delivered FML32 software will reside in a subtree of the local file system. Several of the FML32 modules assume that the structure of this subtree is as described in this section. The sub-directories are:

• include-contains header files needed by writers of C application code.

• bin-contains the executable commands of FML.

• lib-contains subroutine packages of FML; when compiling a program that uses FML32 functions, $MESSAGEQ/lib/libfml32.suffix and $MESSAGEQ/lib/libgp.suffix should be included on the C compiler command line to resolve external references. (The suffix is .a for POSIX operating systems without shared objects, .so for use of shared objects, and .lib for Windows 95 and Windows NT.)

C application software using FML32 must include the following header files in the order shown:

#include <stdio.h> #include "fml32.h"

Environment Variables

This section describes several environment variables used by FML32.

The following variable is used in FML32 to search for system supplied files:

• TUXDIR-this variable should be set to the topmost node of the installed BEA MessageQ system software including FML32.

The following variables are used throughout FML32 to access field table files (described in Chapter 4):

• FIELDTBLS32-This variable should contain a comma-separated list of field table files for the application. Files given as full path names are used as is; files listed as relative path names are searched for through the list of directories specified by the FLDTBLDIR32 variable. If FIELDTBLS32 is not set, then the single file name fld.tbl is used (FLDTBLDIR32 still applies; see below.)

• FLDTBLDIR32-This variable specifies a colon-separated list of directories to be used to find field table files with relative file names. Its usage is similar to the PATH environment variable. If FLDTBLDIR32 is not set or is null, then its value is assumed to be the current directory.