Another consideration is using SCLM's ability to have the same member names across different types, thus linking your parts with a common name. Take the scenario where you have a COBOL program called SCLMDB2P that creates a load module of the same name SCLMDB2P.

You may want to name the LEC architecture definition and the HL architecture definition that controls the compilation, link and bind the same name. This can be achieved by creating a different SCLM type, for example LECDEF. This member will contain the Linkedit control architecture definition as described in Figure 1. Then your HL architecture definition will reside in your ARCHDEF type and will reference the LECDEF and the DB2CLIST as shown in Figure 1.

INCL  SCLMDB2P LECDEF
INCLD SCLMDB2P DB2CLIST

This way your program source, OBJ, DBRM, LOAD, DB2CLIST member, LECDEF member and HL architecture definition member will all have the same member names. If you wish to utilize this implementation, your SCLM Administrator will need to define the SCLM type that will hold the Linkedit architecture definition members.