Step 8: Create the project definition

The project definition defines the development environment for an individual project. The project definition is organized into three parts: the hierarchy definition, project controls, and language definitions.

The hierarchy definition determines the structure of the hierarchy and how data moves through the hierarchy.
Project controls define how SCLM operates for the project.
The language definitions define the languages for the project.

When creating a project definition, it is usually easier to copy a sample project definition and make the necessary project-specific modifications. The following project definitions are supplied in the ISPF sample library ISP.SISPSAMP:

FLM@EXM1 uses several languages such as COBOL, PL/I, and Script.
FLM@EXM2 shows several languages using Cross System Product, DB2®, and IMS™ support.
FLMWBPRJ includes languages that are used to build an application on your workstation using SCLM's workstation build capability.
FLM01PRJ is used for the example scenario in Project manager scenario, and by the SCLM Sample Project dialog (see Sample Project Utility (option 7)).

Copy the project definition that is appropriate for your project, FLM@EXM1, FLM@EXM2 or FLMWBPRJ into your project.PROJDEFS.SOURCE data set. All project definitions and language definitions for your project should reside in your project.PROJDEFS.SOURCE data set.

Each part of the project definition uses SCLM macros to define the data so that SCLM understands it. The flexibility of these macros allows you to customize each project definition for specific purposes. SCLM macros describes the use of these macros in detail.

Note: Because these are S/370 Assembler language macros, all rules pertaining to macros apply. In addition, there are some SCLM rules involving the use of the macros.