Before you can compile your application, you must precompile the Embedded SQL/C code, using:
cpre
[-Ccompiler]
[-Ddatabase_name]
[-Ffips_level]
[-G[isql_file_name]]
[-H]
[-Iinclude_path_name]
[-Jcharset_locale_name]
[-Ksyntax_level]
[-L[listing_file_name]]
[-Ninterface_file_name]
[-Otarget_file_name]
[-Ppassword]
[-Sserver_name]
[-Ttag_id]
[-Uuser_id]
[-Vversion_number]
[-Zlanguage_locale_name]
[@options_file]...
[-a] [-b] [-c] [-d] [-e] [-f] [-h] [-l] [-m] [-p] [-r] [-s] [-u] [-v] [-w] [-x] [-y]
filename[.ext]
You can flag options using either a slash (/)
or a dash (-); cpre /l and cpre -l are equivalent.
If you enter an invalid option, the precompiler lists the available options.
You must enter filename, the name of the Embedded SQL/C source file. The default extension for filename is .cp. The cpre statement generates an output file with a .c extension.
Some of the options activate features of the precompiler, such as generating stored procedures. By default, these features are turned off. To turn them on, include the option on the cpre statement line. Other statement qualifiers specify values for the preprocessor—a password, for example. Enter the value after the option (with or without intervening spaces).
See Appendix A, “Utility Commands Reference,” for a detailed description of the cpre options.
