FML Directory Structure


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Programming BEA Tuxedo ATMI Applications Using FML \| Local Topics \| Previous Topic \| Next Topic \| Contents

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:

include—contains header files needed by writers of C application code.
cobinclude—contains COPY files needed by writers of COBOL application code. (This directory is named cobinclu for operating systems with an 8.3 file name limitation.)
bin—contains the executable commands of FML.
lib—contains subroutine packages of FML. When compiling a program that uses FML functions, you should include $TUXDIR/lib/libfml.suffix and $TUXDIR/lib/libgp.suffix on the C compiler command line to resolve external references. libfml32.suffix contains the FML32 and VIEW32 functions. (The suffix is .a for POSIX operating systems without shared objects, .so.release for use of shared objects, .lib for Windows; it is part of the BEA Tuxedo system DLL for platforms that use dynamic link libraries.)

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.