Showing users how to write CC architecture definitions

Once you have written the language definition, and assembled and link-edited the project definition, your users can use SCLM to build their Finnoga 4 applications. To do so, however, they must know what information to supply in their architecture definitions. Table 1 lists the SCLM-controlled inputs and outputs for the Finnoga 4 build. It includes the ddnames of the data sets that are input to and output from the Finnoga 4 compiler. In addition, a KEYREF value and brief description of each ddname is given.

Table 1. DDnames and KEYREFs
ddname	KEYREF	Description of data set(s) allocated
SYSLIN	OBJ	A partitioned data set into which the Finnoga 4 compiler writes the object module. The OBJ keyword in the compiler's option string specifies the member name to use.
SYSLIB	SINC	One or more partitioned data sets through which the Finnoga 4 compiler searches for include members.
SYSIN	SINC	A sequential data set that contains Finnoga 4 source to be compiled.
SYSPRINT	LIST	A sequential listings data set. The Finnoga 4 compiler writes out a copy of the source that was compiled along with any error, warning, and informational messages.

In addition, the PARM1 parameter is used in the FLMTRNSL macro for the Finnoga 4 compiler.

When your users write CC architecture definitions for their Finnoga 4 applications, they must include each of the preceding KEYREFs. A typical Finnoga 4 CC architecture definition looks like this:

SINC   PROG   SOURCE
SINC   SUB1   SOURCE
OBJ    PROG   OBJ
LIST   PROG   FINLIST
PARM1  OPTIMIZE

This CC architecture definition, along with the language definition previously written, tells SCLM to compile the concatenation of Finnoga 4 members PROG and SUB1 in data set type SOURCE. The resulting object module and listing are to be saved in data set types OBJ and FINLIST, respectively. When the source is compiled, you want to use the OPTIMIZE compiler option.

You do not have to specify the modules that are included from ddname SYSLIB. Simply allocate SYSLIB to the proper libraries (with an IOTYPE=I) and the compiler will find the included members.

This simple template is all you have to give to your users. When they edit their Finnoga 4 source, they need to specify FINNOGA as the language name. Then they create their architecture definitions like the preceding one. SCLM and the language definition you created will perform the rest of the work.