Skip navigation.

Programming a Tuxedo ATMI Application Using FML

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

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:

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

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.

VIEW32 Support for MBSTRING

Starting with Tuxedo 9.0, VIEW32 supports MBSTRING typed buffers which correspond to the FLD_MBSTRING field type in FML32.

Fmbpack32(3fml)prepares an MBSTRING field in a VIEW32 buffer for encoding and Fmbunpack32(3fml)extracts it. TPMBENC and TPMBACONV environment variables are also used in VIEW32.


Skip navigation bar  Back to Top Previous Next