|e-docs > Tuxedo > Programming a Tuxedo ATMI Application Using FML > Setting Up Your Environment for FML and VIEWS|
Programming a Tuxedo ATMI Application Using FML
Setting Up Your Environment for FML and VIEWS
This topic includes the following sections:
Environment Requirements for FML and VIEWS
Before you can begin to work with FML fielded buffers, or to use the VIEWS functions that move fields between structures and fielded buffers, you must set up your environment to accommodate these methods by setting the necessary environment variables. This section provides instructions for doing so.
FML Directory Structure
The FML software delivered with the BEA Tuxedo system resides in a subtree of the local file system. Several FML modules depend on the subtree structure described here. We assume that you have set the TUXDIR environment variable to the full path name of the directory in which the BEA Tuxedo ATMI Server is installed.
The BEA Tuxedo installation directory contains the following subdirectories:
C applications in which FML is used must include the following header files in the order shown:
The file fml.h or fml32.h contains definitions for structures, symbolic constants, and macros used by the FML software.
Environment Variables Used by FML and VIEWS
Several environment variables are used by FML and VIEWS.
When the application server or client process receives an FML32 buffer that includes an FLD_MBSTRING field, and assuming another environment variable named TPMBACONV is set, the code-set encoding name defined in TPMBENC is automatically compared to the code-set encoding name included for the FLD_MBSTRING field in the received buffer; if the names are not the same, the FLD_MBSTRING field data is automatically converted to the encoding defined in TPMBENC before being delivered to the server or client process.
TPMBENC has no default value. For an application server or client using FLD_MBSTRING fields, TPMBENC must be defined for automatic conversion to work.