Convert your JCL decks to architecture definitions

Suppose your Finnoga 4 users have a library of JCL that they have been using to compile their Finnoga 4 source. The following example uses a sample Finnoga 4 compile job and shows how you would write an architecture definition with the information in the JCL. The JCL deck that you use might look like this:

//JOB  ...
//FINNOGA EXEC PGM=FNGAA40,
//        PARM='SOURCE,NOMACRO,OBJ(PROG1),NOOPTIMIZE'
//SYSLIN   DD DSN=USER02.PRIVATE.OBJ,DISP=OLD
//SYSLIB   DD DSN=USER02.PRIVATE.FINNOGA,DISP=SHR
//SYSIN    DD DSN=USER02.PRIVATE.FINNOGA(MAIN),DISP=SHR
//         DD DSN=USER02.PRIVATE.FINNOGA(SUB1),DISP=SHR
//         DD DSN=USER02.PRIVATE.FINNOGA(SUB2),DISP=SHR
//SYSPRINT DD SYSOUT=A
//FINLIB   DD DSN=SYS1.FINNOGA.LIB,DISP=SHR
//SYSUT1   DD UNIT=SYSDA,VOL=SER=,DCB=(LRECL=4000,RECFM=F),
//         SPACE=(TRK,(10,10))
//SYSUT2   DD UNIT=SYSDA,VOL=SER=,DCB=(LRECL=4000,RECFM=F),
//         SPACE=(TRK,(10,10))

In this example, you want SCLM to control the modules that are input or output through ddnames SYSIN, SYSLIN, and SYSPRINT. For the Finnoga 4 language definition, the keywords SINC, OBJ and LIST have been assigned to those modules. You create the architecture definition by listing the modules involved in the build and identifying their roles with the keywords SINC, OBJ, and LIST. In addition, you tell SCLM to concatenate the NOOPTIMIZE option to the end of the OPTIONS string being passed to the translator using the PARM1 keyword.

SINC    MAIN   SOURCE
SINC    SUB1   SOURCE
SINC    SUB2   SOURCE
OBJ     PROG1  OBJ
LIST    MAIN   FINLIST
PARM1   NOOPTIMIZE

Now you are prepared to move this application under SCLM control:

Copy the members MAIN, SUB1, and SUB2 from 'USER02.PRIVATE.FINNOGA' to a development group in the SCLM project hierarchy. In this example, the data set type is SOURCE. Also copy over any included source members.
Use the SCLM Migration Utility to migrate your source members using the language name FINNOGA (the name specified on the FLMLANGL macro).
Use the SCLM editor to create the architecture definition. Unless you have modified the ARCHDEF language definition, the language of this architecture definition should be ARCHDEF. SCLM asks for the language name when you first enter the SAVE or END edit command.

Your user is now ready to compile this application using SCLM. The source members are under SCLM control as are the architecture definitions. The object module and the Finnoga 4 listing have not yet been created. To build this application, select Build (option 10.4) from the SCLM Main Menu and enter the project, group, type, and member name of the architecture definition (ARCHDEF).