viewc, viewc32(1)


	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 \| Reference \| Topic List \| Previous \| Next \| Contents

BEA Tuxedo Command Reference

viewc, viewc32(1)

Name

viewc, viewc32 - view compiler for BEA Tuxedo views

Synopsis

viewc [-n] [-d viewdir] [-C] viewfile [viewfile . . . ] 
viewc32 [-n] [-d viewdir] [-C] viewfile [viewfile . . . ]

Description

viewc is a view compiler program. It takes a source viewfile and produces:

A binary file, which is interpreted at run time to effect the actual mapping of data between FML buffers and C structures
One or more header files
Optionally COBOL copy files. (When 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, then 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 Application Using FML and Programming a BEA Tuxedo 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 Application Using C discusses how to create and use such an independent view description file.

The following options are interpreted by viewc.

-n: 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.
-d viewdir: Used to specify that the view object file is to be created in a directory other than the current directory.
-C: Used to specify that COBOL copy files are to be created.

Environment Variables

CC: 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 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.
CFLAGS: The environment variable CFLAGS is taken to contain a set of arguments to be passed as part of the compiler command line. If CFLAGS does not exist in viewc's environment, or if it is the string "", no compiler command-line arguments are added by buildclient.

Portability

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).

When a view file description file is compiled on DOS or OS/2, the name of the object file has a .VV suffix instead of a .V suffix because the file names are not case dependent. The following additional options are recognized.

-m { m | l }: Specifies the memory model to be used for compilation and linking of a client. The supported values for this option are m and l for the medium and large memory models, respectively. The large memory model is the default for this option. The -m option is supported for DOS only.
-c { m | b }: 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 DOS and WINDOWS only.
-1 filename: Specifies that pass 1 should be run, and the resulting batch file should be 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.
-2 filename: Specifies that pass 2 should be run to complete processing, using the output from pass 1.