Understanding the architecture definition

This section describes the architecture definition and its importance in an SCLM project. The architecture definition describes to SCLM how the components of an application fit together. For more information about architecture definitions, see Architecture definition.

There are four types of architecture members:

HL (high level): HL architecture members reference application and subapplication components.
CC (compilation control): CC architecture members contain the information to produce and track software components with object module output.
LEC (link-edit control): LEC architecture members contain the information to produce a complete load module.
Generic: Generic architecture members identify the source member or groups of source members to be processed by a processor other than a standard compiler. The sample project does not contain examples of generic architecture members.

If you have several architecture definition statements that are used together in many places, you can put them into a member and reference the member using the COPY statement wherever you need the statements. When you use the COPY statement, the contents of the specified member are inserted directly into the respective architecture members.

Select View from the SCLM Main Menu. Specify PROJ1 in the Project field and specify DEV2 in the Group field. Press Enter.
Specify ARCHDEF in the Type field and leave the Member field blank. Press Enter. The architecture members are shown in the following table.

Table 1. The architecture members
Member	Type	Comments
FLM01AP1	HL	References FLM01SB1 and FLM01SB2 with the INCL statement. A build performed on FLM01AP1 results in a complete build for all the code in the project, if necessary.
FLM01SB1	HL	References FLM01LD1,FLM01LD2,FLM01LD7, and FLM01LD9 with the INCL statement. A build performed on FLM01SB1 results in a complete build of the FLM01SB1 subapplication, if necessary. If the Enterprise PL/I Compiler is not included as a language in the sample project, FLM01SB1 does not reference FLM01LD2. If the Enterprise COBOL Compiler is not included a language in the sample project, FLM01SB1 does not reference FLM01LD7.
FLM01SB2	HL	References FLM01LD3 and FLM01LD4 with the INCL statement. A build performed on FLM01SB2 results in a complete build of the FLM01SB2 subapplication, if necessary.
FLM01LD1	LEC	Directs SCLM to produce the load module and load map for FLM01LD1. The INCL statement references architecture member FLM01CMD. The PARM statements pass parameters to the SCLM BUILD translators.
FLM01LD2	LEC	Directs SCLM to build load module FLM01LD2 from the source FLM01MD2. The INCLD architecture statement is used to identify FLM01MD2 as the source. Note that LOAD, LMAP, and SOURCE are types identified by the FLMTYPE macro in the project definition. If the Enterprise PL/I Compiler is not included as a language in the sample project, FLM01LD2 is not included.
FLM01LD7	LEC	Directs SCLM to build load module FLM01LD7 from the source FLM01CD7 and FLM01CD8. The INCLD architecture statement is used to identify FLM01CD7 and FLM01CD8 as the source. Note that LOAD, LMAP, and SOURCE are types identified by the FLMTYPE macro in the project definition. If the Enterprise COBOL Compiler is not included as a language in the sample project, FLM01LD27 is not included.
FLM01LD9	LEC	Directs SCLM to produce the load module and load map for FLM01LD9. The INCL statement references architecture member FLM01CM9. The PARM statements pass parameters to the SCLM BUILD translators.
FLM01CMD	CC	Directs SCLM to produce object code from FLM01MD1. SINC identifies FLM01MD1 as the source member. Note that in addition to object code (OBJ), there is also source listing (LIST). OBJ and LIST are identified in the project definition with the FLMTYPE macro.
FLM01CM9	CC	Directs SCLM to produce object code from FLM01AD9. SINC identifies FLM01AD9 as the source member. Note that in addition to object code (OBJ), there is also source listing (LIST). OBJ and LIST are identified in the project definition with the FLMTYPE macro.
FLM01LD3	LEC	References FLM01MD3 with the INCLD statement. Other modules are referenced with the copy of FLM01ARH. In this example, FLM01ARH references FLM01MD5 and FLM01MD6. FLM01LD3 indirectly references FLM01MD5 and FLM01MD6 via the COPY statement in FLM01ARH.
FLM01LD4	LEC	References FLM01MD4 with the INCLD statement. Other modules are referenced with the copy of FLM01ARH. In this example, FLM01ARH references FLM01MD5 and FLM01MD6. FLM01LD4 indirectly references FLM01MD5 and FLM01MD6 via the COPY statement in FLM01ARH.
FLM01ARH	CC	References modules FLM01MD5 and FLM01MD6 with the INCLD statement. The LEC architecture members FLM01LD3 and FLM01LD4 use the COPY directive to copy the contents of FLM01ARH into their members for a build.

To create an architecture report:

Select Architecture Report (option 3.5) from the SCLM Main Menu, and press Enter.
Type:
ARCHDEF

in the Type field

FLM01AP1

in the Member field

6

in the "Report cutoff" field

1

in the Process field

1

in the Messages field

1

in the Report field

Press Enter.

The output shows the hierarchy, the kinds of architecture members (HL, CC, and LEC), and various cross-references. See Architecture Report example for an example of the architecture report.