Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Programming   |   Topic List   |   Previous   |   Next   |   Contents

   Programming a BEA Tuxedo Application Using FML

Field table files are created using a standard text editor, such as vi. They have the following format:

• Blank lines and lines beginning with # are ignored.

• Lines beginning with a dollar sign ($) are ignored by the mapping functions but are passed through (without the $) to header files generated by mkfldhdr. (Refer to mkfldhdr, mkfldhdr32(1) in the BEA Tuxedo Command Reference.) The ability to have lines ignored by the mapping functions is useful, for example, when an application passes C comments, what strings, and so on, to the generated C header file.

  Note: In COBOL applications, however, such lines are not passed through to the COBOL copy files.

• Lines beginning with the string *base contain a base for offsetting subsequent field numbers. This optional feature provides an easy way to group and renumber sets of related fields.

• All other lines should have the form

  name       rel-number      type      flag      comment

  where:

  • name is the identifier for the field. It should not exceed the C preprocessor identifier restrictions (that is, it should contain only alphanumeric characters and the underscore character). Internally, the name is truncated to 30 characters, so names must be unique within the first 30 characters.

  • rel-number is the relative numeric value of the field. It is added to the current base, if *base is specified, to obtain the field number of the field.

  • type is the type of the field. It is specified as one of the following: char, string, short, long, float, double, carray, ptr, fml32, or view32.

  • The flag field is reserved for future use; use a dash (-) in this field.

  • comment is an optional field that can be used for clarifying information.

Note that these entries must be separated by white space (blanks or tabs).

The following is an example field table in which the base shifts from 500 to 700. The first field in each group will be numbered 501 and 701, respectively.

# following are fields for EMPLOYEE service
# employee ID fields are based at 500
*base 500
#name           rel-number      type           flags   comment
#----           ----------      ----           ------  -------
EMPNAME         1               string         -       emp name
EMPID           2               long           -       emp id
EMPJOB          3               char           -       job type
SRVCDAY         4               carray         -       service date
*base 700
# all address fields are now relative to 700
EMPADDR         1               string         -       street address
EMPCITY         2               string         -       city
EMPSTATE        3               string         -       state
EMPZIP          4               long           -       zip code