If you are already running an existing SCLM project that has all the data types described in Defining the project environment, additional types must be created. The following types of data must be maintained and are the recommended naming conventions:

DBRM

Contains the source member input to a DB2® bind. It is generated by the DB2 preprocessing step.

DB2CLIST

A DB2CLIST that contains editable source members. These source members are used during SCLM Build to control bind and free functions for DB2.

For example, if you wish to use a DB2CLIST to do package binds as well as plan binds then you may want to give your DB2CLIST types more meaningful names such as PKGCLIST and PLNCLIST. The output member would then need to be named PKGOUT and PLNOUT.

To have DB2CLIST members and DBRM members with the same name, an FLMINCLS macro needs to be specified in the language definition for the DB2CLIST members. The FLMINCLS macro must list the DBRM type first on the TYPES parameter. Here is an example of an FLMINCLS macro to do this:

*
* SPECIFY TYPES TO SEARCH FOR DBRMS THAT ARE TRACKED AS
* INCLUDES TO THE DB2 CLIST MEMBERS
*
         FLMINCLS TYPES=(DBRM)

DB2OUT

This type contains non-editable build output that is used during SCLM Promote to control BIND and FREE functions for DB2. During a build of a DB2CLIST, a copy of the DB2CLIST is copied to the type DB2OUT into the group that is being built. During a promote, this member is called to bind the plan or package in the TO group and free the plan or package in the FROM group. Since the DB2OUT is the "output" from the DB2CLIST, SCLM will move both objects together during a Promote.

Note: The DB2OUT type must come after the DBRM type in the EBCDIC collating sequence. This is so that during the promote the bind is started after the DBRM has been promoted. SCLM promotes in EBCDIC collating sequence order.