Command Reference
viewc
, viewc32
—View compiler for BEA Tuxedo ATMI views.
viewc [-n] [-d
viewdir
] [-C]viewfile
[viewfile
. . . ]
viewc32 [-n] [-dviewdir
] [-C]viewfile
[viewfile
. . . ][-s]
viewc
is a view compiler program. It takes a source viewfile and produces:
FML
buffers and C structures.viewc
is executed a C compiler must be available.)viewc32
is used for 32-bit FML. It uses the FIELDTBLS32
and FLDTBLDIR32
environment variables.
The viewfile
is a file containing source view descriptions. More than one viewfile
can be specified on the viewc
command line as long as the same VIEW
name is not used in more than one viewfile
.
By default, all views in the viewfile
are compiled and two or more files are created: a view object file (with a .V
suffix) and a C header file (with a .h
suffix). The name of the object file is viewfile.V
in the current directory unless an alternate directory is specified through the -d
option. C header files are created in the current directory.
If the -C
option is specified, one COBOL copy file is created for each VIEW
defined in the viewfile
. These copy files are created in the current directory.
At viewc
compile time, the compiler matches each fieldid
and field name specified in the viewfile
with information obtained from the field table file, and stores mapping information in an object file for later use. Therefore, it is essential to set and export the environment variables FIELDTBLS
and FLDTBLDIR
to point to the related field table file. For more information on FIELDTBLS
and FLDTBLDIR
, see Programming a BEA Tuxedo ATMI Application Using FML and Programming a BEA Tuxedo ATMI Application Using C.
If the viewc
compiler cannot match a field name with its fieldid
because either the environment variables are not set properly or the field table file does not contain the field name, a warning message, Field not found
, is displayed.
With the -n
option, it is possible to create a view description file for a C structure that is not mapped to an FML
buffer. Programming a BEA Tuxedo ATMI Application Using C discusses how to create and use such an independent view description file.
The following options are interpreted by viewc
.
Used when compiling a view description file for a C structure that does not map to an FML buffer. It informs the view compiler not to look for FML information.
Used to specify that the view object file is to be created in a directory other than the current directory.
viewc
normally uses the default C language compilation command to produce the client executable. The default C language compilation command is defined for each supported operating system platform and is defined as cc(1)
for a UNIX system. In order to allow for the specification of an alternate compiler, viewc
checks for the existence of an environment variable named CC
. If CC
does not exist in viewc
's environment, or if it is the string ""
, viewc
will use the default C language compiler. If CC
does exist in the environment, its value is taken to be the name of the compiler to be executed.
The output view file is a binary file that is machine and compiler-dependent. It is not possible to generate a view on one machine with a specific compiler and use that view file on another machine type or with a compiler that generates structure offsets differently (for example, with different padding or packing).
The following additional options are recognized.
Specifies the C compilation system to be used. The supported value for this option is m
for the Microsoft C compiler. The Microsoft C compiler is the default for this option. The -c
option is supported for Windows only.
Specifies that pass 1 should be run, and the resulting batch file called filename
.bat
should be created. After this file is created, it, should be executed before running pass 2. Using pass 1 and pass 2 increases the size of the views that can be compiled.