In this type of UAP, SQL statements are incorporated directly into a source program written in C language (based on ANSI-C) or in COBOL (based on COBOL85).

Table 3-1 lists the UAP descriptive languages that can be used in HiRDB.

Table 3-1 UAP descriptive languages

Operating environment	Descriptive languages
HP-UX	C language (Microsoft Visual C++) C++ language (Optimizing C++) COBOL language (COBOL85 and COBOL2002) OOCOBOL language (OOCOBOL) *
Solaris	C language COBOL language * COBOL85, COBOL2002, and COBOL language products of other companies (MicroFocusCOBOL and SUN Japanese COBOL)
AIX 5L	C language C++ language COBOL language (COBOL85 and COBOL2002)
Linux	C language (gcc) C++ language (GCC) COBOL language (COBOL85 and COBOL2002) OOCOBOL language (OOCOBOL)*
Windows	C language (Microsoft Visual C++) C++ language (Optimizing C++) COBOL language (COBOL85 and COBOL2002) OOCOBOL language (OOCOBOL) *

^* The multi-connection facility cannot be used.

An embedded-type UAP cannot be compiled or linked directly. Execute the SQL preprocessor and convert the UAP into a post-source program before compiling and linking the UAP. For details about how to preprocess, compile and link UAPs, see 8. Preparation for UAP Execution.