This SCLM project contains all the required components of SCLM
projects in general and serves as a model for future projects. A description
of the components of the project follows.
Figure 1 shows three layers in
the SCLM project hierarchy: development, test, and release.
- The development layer promotes to the test layer, and the test
layer promotes to the release layer.
- The development layer is composed of the groups DEV1 and DEV2.
You can think of these groups as being assigned to two separate developers.
The SCLM hierarchy looks like Figure 1.
Figure 1. Example Project Hierarchy
Figure 2 shows nine modules in
the hierarchy: FLM01AD9, FLM01CD7, FLM01CD8, FLM01MD1, FLM01MD2, FLM01MD3,FLM01MD4,
FLM01MD5, and FLM01MD6. These are the programs that the developers
edit in order to install fixes and new features.
- FLM01MD2 is written in PL/I and uses the Enterprise PL/I compiler.
FLM01MD2 includes the FLM01IIN copybook.
Note: Module FLM01MD2, copybook
FLM01IIN, and the language definition for the Enterprise PL/I Compiler,
are not included if the project is defined using the SCLM sample project
utility and the first optional compiler field was not selected.
- Module FLM01AD9 is written in High Level Assembler. FLM01AD9 includes
the FLM01INC copybook.
Note: Module FLM01AD9 and copybook FLM01INC
will be included if the project is defined using the SCLM sample project
utility, but no side file will be generated if the Fault Analyzer
field is not selected.
- FLM01CD7 and FLM01CD8 are written in COBOL and use the Enterprise
COBOL compiler. FLM01CD7 includes the FLM01CIN copybook. FLM01CD8
includes the FLM01CDT copybook.
Note: Modules FLM01CD7, FLM01CD8,
copybooks FLM01CIN, FLM01CDT and the language definition for the Enterprise
COBOL Compiler, are not included if the project is defined using the
SCLM sample project utility and the second optional compiler field
was not selected
- The other modules are written in S/370 Assembler. They include
a member named FLM01EQU that contains the register equates commonly
used in assembly language programs.
- The modules are compiled or assembled by the BUILD function into
an application named FLM01API. SCLM performs this operation using
the architecture definitions contained in the ARCHDEF data sets.
- FLM01AP1 does not directly call any language translators. It references
other architecture members. The Build process creates the load modules
FLM01LD7, FLM01LD9, FLM01LD1, FLM01LD2, FLM01LD3, and FLM01LD4.
Note: - Load module FLM01LD2 is not created if the project is defined
using the SCLM sample project utility and the first optional compiler
field was not selected.
- Load module FLM01LD7 is not created if the project is defined
using the SCLM sample project utility and the second optional compiler
field was not selected.
- FLM01AP1,FLM01SB1 and FLM01SB2 are high-level architecture members.
They do not call any language translators. FLM01LD7, FLM01LD9, FLM01LD1,FLM01LD2,FLM01LD3,
and FLMO1LD4 are LEC architecture members. FLM01CMD and FLM01CM9
are CC architecture members, and FLM01ARH is an architecture member
that is directly copied into FLM01LD3 and FLM01LD4.
Note: - Architecture member FLM01LD2 is not included if the project is
defined using the SCLM sample project utility and the first optional
computer field was not selected.
- Architecture member FLM01LD7 is not included if the project is
defined using the SCLM sample project utility and the second optional
compiler field was not selected.
Figure 2. Example Project Architecture
Note: - Source module FLM01MD2 and architecture member and load module
FLM01LD2 are not included if the project was defined using the SCLM
sample project utility (Option 10.7) and the first optional compiler
field was not selected.
- Source module FLM01CD7, FLM01CD8, and architecture member and
load module FLM01LD7, are not included if the project was defined
using the SCLM sample project utility (Option 10.7) and the second
optional compiler field was not selected.