The process of creating a DB2® UDB for iSeries™ application program may result in the creation of several objects. This section briefly describes the process of creating a DB2 UDB for iSeries application.
DB2 UDB for iSeries supports both non-ILE and ILE precompilers. Application programs may be either distributed or nondistributed.
With DB2 UDB for iSeries you may need to manage the following objects:
With a non-distributed non-ILE DB2 UDB for iSeries program, you must manage only the original source and the resulting program. The following shows the objects involved and steps that happen during the precompile and compile processes for a nondistributed non-ILE DB2 UDB for iSeries program:
With a non-distributed ILE DB2 UDB for iSeries program, you may need to manage the original source, the modules, and the resulting program or service program. The following shows the objects involved and steps that happen during the precompile and compile processes for a non-distributed ILE DB2 UDB for iSeries program when OBJTYPE(*PGM) is specified on the precompile command:
With a distributed non-ILE DB2 UDB for iSeries program, you must manage the original source, the resulting program, and the resulting package. The following shows the objects and steps that occur during the precompile and compile processes for a distributed non-ILE DB2 UDB for iSeries program:
With a distributed ILE DB2 UDB for iSeries program, you must manage the original source, module objects, the resulting program or service program, and the resulting packages. An SQL package can be created for each distributed module in a distributed ILE program or service program. The following shows the objects and steps that occur during the precompile and compile processes for a distributed ILE DB2 UDB for iSeries program: