A number of DB2 ECM demonstration applications are supplied in the Samples Browser, available from Start > All Programs > Micro Focus Enterprise Developer > Samples > Visual COBOL Samples. These files are located in the %PUBLIC%\Documents\Micro Focus\Enterprise Developer\Samples\sql\db2ecm (Windows) or $COBDIR/demo/sql/db2 (UNIX) directory.
Each sample application comes with a Readme file to explain how to use the application, and a makefile.
The following applications are provided:
Shows the syntax variants for connecting to and disconnecting from a DB2 database using Type 1 CONNECTs that IBM DB2 LUW supports.
A simple example of using dynamic SQL with IBM DB2 LUW, performing a variety of SQL operations. If this program was written as a STATIC SQL program, it would have to be broken apart into two programs, since static SQL requires that the table exists beforehand or it would cause a Compiler error.
Shows how LOB LOCATOR and VALUES functions to retrieve Lob data from DB2 LUW.
A simple example of using both singleton SELECT and cursor-based FETCH statements with IBM DB2 LUW.
Shows how to use EXEC SQL WHENEVER statements for error handling, and the DB2(MSGAREA) Compiler directive to specify a COBOL variable for retrieving error message text larger than the 70 bytes provided in SQLERRMC.
Shows the syntax variants for connecting to and disconnecting from a DB2 database using Type 1 CONNECTs that IBM DB2 LUW supports.
A simple example of using both singleton SELECT and cursor-based FETCH statements with IBM DB2 LUW.
A simple example of using dynamic SQL with IBM DB2 LUW, performing a variety of SQL operations. If this program was written as a STATIC SQL program, it would have to be broken apart into two programs, since static SQL requires that the table exists beforehand or it would cause a Compiler error.
Shows how LOB LOCATOR and VALUES functions to retrieve Lob data from DB2 LUW.
Shows how to use EXEC SQL WHENEVER statements for error handling, and the DB2(MSGAREA) Compiler directive to specify a COBOL variable for retrieving error message text larger than the 70 bytes provided in SQLERRMC.