Sample application using architecture definitions

The following application is composed of two subapplications. The first subapplication consists of four load modules and the second subapplication consists of two load modules, that are composed of a series of object modules. Load module FLM01LD1,FLM01LD2, and FLM01LD9 contain one object module each, while FLM01LD3,FLM01LD4,and FLM01LD7 contain multiple object modules. Figure 1 shows a diagram of the design of this application (FLM01AP1) and Figure 2 shows the architecture members for the FLM01AP1 application.

Note: SCLM tracks the included members; therefore, there is no need to mention FLM01EQU in the architecture definition.

Figure 1. Application FLM01AP1

In this network, the Application is FLM01AP1. The Subapplications are FLM01SB1 and FLM01SB2. These then split into further LEC Architecture Membesr, CC Architecture Members, and Source Modules.

Figure 2. Architecture Members for Application Sample FLM01AP1 (Part 1 of 2)

This is an alternative view of the hierarchy in the previous figure. For each member there is a report showing the associated members.

Figure 3. Architecture Members for Application Sample FLM01AP1 (Part 2 of 2)

There are three members. Information is shown for each. For the member FLM01CM9, there are two versions. The first version, with Fault Analyzer, includes the OUT2 object module. The second version, without Fault Analyzer, does not cinlude this object module.

The HL architecture member in part 1 of this figure includes references to two subapplications: (FLM01SB1 and FLM01SB2). The subapplication HL architecture members reference the LEC architecture members that define the load modules they contain. Note that the referenced LEC architecture members have the same names as the load modules they produce.

The LEC architecture members contain all the information necessary to produce the load modules in the application. Two PARM statements in FLM01LD1 override the default linkage editor options.

Load modules FLM01LD3 and FLM01LD4 contain copy statements. These statements identify the architecture member FLM01ARH, that references two source modules for SCLM to insert into the FLM01LD3 and FLM01LD4 load modules.

Thus, copy architecture members are an efficient technique for grouping commonly used architecture statements into a single member. Additions to and deletions from FLM01ARH affect FLM01LD3 and FLM01LD4 and all the other architecture members that might reference FLM01ARH.