Preparing the example project hierarchy

Use the following steps to install the example project data sets on your system. Follow the steps in the order listed and exactly as they are described. When you have completed all of the steps, you will have an SCLM project database with which you can experiment to better understand how SCLM works. If you encounter any errors during the following steps, use the TSO, ISPF, and SCLM messages to correct the problem. You can also define the sample project using the SCLM Sample Project utility (Option 10.7).

Note: This is the project that uses sample FLM01PRJ.

In the descriptions that follow, the default naming convention (PROJECT.GROUP.TYPE) is used. Assume for these examples that the project name is PROJ1. If you use a different name, be sure to inform those users who plan to complete the programmer scenario.

Sign on to TSO.
At the READY prompt, start ISPF.
Using the ISPF Data Set Utility, allocate the following partitioned data set with space in blocks (10,50), with 10 directory blocks, and with record format FB, LRECL 80:
```
         PROJ1.PROJDEFS.SOURCE
```
This partitioned data set will contain the source code for the library structure as defined in the project definition.
Using the ISPF Data Set Utility, allocate the following partitioned data set with space in blocks (10,50), with 10 directory blocks, and with record format FB, LRECL 80:
```
         PROJ1.PROJDEFS.OBJ
```
This partitioned data set will contain the object code for the library structure as defined in the project definition.
Using the ISPF Data Set Utility, allocate the following partitioned data set with space in blocks (10,50), with 10 directory blocks, and with record format U, LRECL 0, BLKSIZE 6144:
```
         PROJ1.PROJDEFS.LOAD
```
This partitioned data set will contain the load module for the library structure as defined in the project definition. This member is named PROJ1.

Note: Depending on the ISPF configuration for your site, you might receive warning or error messages when attempting to edit an SCLM project using the ISPF editor.
Use the ISPF Move/Copy Utility to copy the following members from ISP.SISPSAMP into PROJ1.PROJDEFS.SOURCE: FLM01ASF, FLM01ASM, FLM01CBE, FLM01PLE, FLM01PRJ, FLM01SCR, FLM01370, FLM02ALL, and FLM02ACT.
Note:
1. If you are not using Fault Analyzer, do not copy FLM01ASF.
2. If you are not using Fault Analyzer, delete the following lines from FLM01PRJ:
```
         IDILANGX FLMTYPE
         COPY  FLM01ASF
```
Member FLM02ALL of PROJ1.PROJDEFS.SOURCE is a background job that allocates all of the data sets needed for this example application. You must provide a job card and change any other information that is specific to your location; for example, change all the occurrences of USERID to PROJ1 and alter the job card. After you have made these changes, submit the job.
If this job allocates all the required data sets, you can skip to Step 9. Use the ISPF Data Set List Utility to determine whether the data sets were allocated.

If the required data sets have not been allocated, you can allocate them by following Step 8.

Note: If you are not using Fault Analyzer, remove the following step from FLM02ALL:
```
      //*
      //STEP3ID EXEC PGM=1EFBR14
      //DEV1     DD DSN=project.DEV1.IDILANGX,DISP=(NEW,CATLG),UNIT=SYSDA,
      //    DCB=(RECFM=VB,LRECL=1562,BLKSIZE=0),SPACE=(27998,(5,20,10))
      //DEV2     DD DSN=project.DEV2.IDILANGX,DISP=(NEW,CATLG),UNIT=SYSDA,
      //    DCB=(RECFM=VB,LRECL=1562,BLKSIZE=0),SPACE=(27998,(5,20,10))
      //TEST     DD DSN=project.TEST.IDILANGX,DISP=(NEW,CATLG),UNIT=SYSDA,
      //    DCB=(RECFM=VB,LRECL=1562,BLKSIZE=0),SPACE=(27998,(5,20,10))
      //RELEASE  DD DSN=project.RELEASE.IDILANGX,DISP=(NEW,CATLG),UNIT=SYSDA,
      //    DCB=(RECFM=VB,LRECL=1562,BLKSIZE=0),SPACE=(27998,(5,20,10))
```
If Step 7 fails, or if you choose not to use the FLM02ALL JCL member, follow these steps to allocate the required data sets.
1. Using the ISPF Data Set Utility, allocate the following partitioned data sets with space in blocks (10,50), with 10 directory blocks, and with record format FB, LRECL 80:
```
         PROJ1.DEV1.SOURCE
         PROJ1.DEV2.SOURCE
         PROJ1.TEST.SOURCE
         PROJ1.RELEASE.SOURCE
```
  These partitioned data sets will contain the source code for the project.
2. Using the ISPF Data Set Utility, allocate the following partitioned data sets with space in blocks (10,50), with 10 directory blocks, and with record format FB, LRECL 80:
```
         PROJ1.DEV1.ARCHDEF
         PROJ1.DEV2.ARCHDEF
         PROJ1.TEST.ARCHDEF
         PROJ1.RELEASE.ARCHDEF
```
  These partitioned data sets will contain the architecture definition for the project.
3. Using the ISPF Data Set Utility, allocate the following partitioned data sets with space in blocks (30,100), with 10 directory blocks, and with record format VB, LRECL 137:
```
         PROJ1.DEV1.LIST
         PROJ1.DEV2.LIST
         PROJ1.TEST.LIST
         PROJ1.RELEASE.LIST
```
  These partitioned data sets will contain the listings from the compilations and assemblies of the modules.
4. Using the ISPF Data Set Utility, allocate the following partitioned data sets with space in blocks (15,50), with 10 directory blocks, and with record format FB, LRECL 80:
```
         PROJ1.DEV1.OBJ
         PROJ1.DEV2.OBJ
         PROJ1.TEST.OBJ
         PROJ1.RELEASE.OBJ
```
  These partitioned data sets will contain the object code from the compilations and assemblies of the modules.
5. Using the ISPF Data Set Utility, allocate the following partitioned data sets with space in blocks (7,13), with 10 directory blocks, and with record format U,LRECL 0, BLKSIZE 6144:
```
         PROJ1.DEV1.LOAD
         PROJ1.DEV2.LOAD
         PROJ1.TEST.LOAD
         PROJ1.RELEASE.LOAD
```
  These partitioned data sets will contain the load modules from the link-edits of the modules.
6. Using the ISPF Data Set Utility, allocate the following partitioned data sets with space in blocks (5,20), with 10 directory blocks, and with record format FBA, LRECL 121:
```
         PROJ1.DEV1.LMAP
         PROJ1.DEV2.LMAP
         PROJ1.TEST.LMAP
         PROJ1.RELEASE.LMAP
```
  These partitioned data sets will contain the load maps from the link-edits of the modules.
7. Using the ISPF Data Set Utility, allocate the following partitioned data set with space in blocks (300,100) with 10 directory blocks, and with record format VB,LREC 1562:
```
         PROJ1.DEV1.IDILANGX
         PROJ1.DEV2.IDILANGX
         PROJ1.TEST.IDILANGX
         PROJ1.RELEASE.IDILANGX
```
  These partitioned data sets will contain side files generated by Fault Analyzer.
  
  Note: If you are not using Fault Analyzer, do not allocate PROJ1.*.IDILANGX data sets.
Using the ISPF Library Utility, rename member FLM01PRJ in PROJ1.PROJDEFS.SOURCE to PROJ1. This member contains the source code for the project definition for PROJ1.
Using ISPF Edit, edit PROJ1.PROJDEFS.SOURCE(PROJ1). Change all occurrences of USERID to PROJ1.
Using ISPF Edit, edit PROJ1.PROJDEFS.SOURCE(FLM01ASM). Change all system macro library references to the library of macros at your location.
You must change the members FLM01ASF, FLM01CBE, FLM01PLE, FLM01SCR, and FLM01370 so that libraries, assemblers, and assembler options match the libraries and products in use at your location. The changes are specified in the samples delivered.

Note: If you make changes to these members after Step 14 while installing this example project, reassemble and relink the data set PROJ1.PROJDEFS.SOURCE(PROJ1). If you are not sure this step is required, reassemble and relink.
Using ISPF Edit, edit PROJ1.PROJDEFS.SOURCE(FLM02ACT). Be sure that the job card contains valid accounting information. Change all occurrences of USERID to PROJ1.
This member contains JCL that constructs the VSAM cluster used to contain the accounting information used by SCLM. You also need to alter the volumes for IDCAMS for your location, and you might need to make additional changes to conform to requirements at your location.
Submit the JCL in PROJ1.PROJDEFS.SOURCE(FLM02ACT). You know that your job has completed successfully when the PROJ1.ACCOUNT.FILE VSAM cluster is created.
This is the VSAM data set that contains the SCLM accounting information for the project. This job deletes the cluster and then creates the cluster. Because the cluster does not exist the first time you submit the job, you receive a return code of 8 in the listing data set.
Assemble PROJ1.PROJDEFS.SOURCE(PROJ1) using either ISPF Foreground Assembler (option 4.1) or the sample JCL in Assemble and link example.
Be sure that the SCLM macro library used at your location is in the concatenation sequence for the libraries used by the assembler. Specify the macro library in the Additional Input Libraries field on the Foreground Assembly panel.

Look at the listing and confirm that no statements were flagged.
If you used the sample JCL in the Assemble and link example, make sure that member PROJ1.PROJDEFS.LOAD(PROJ1) exists.
Otherwise, use the ISPF Foreground Linkage Editor to link-edit PROJ1.PROJDEFS.OBJ(PROJ1). This constructs the load module PROJ1.PROJDEFS.LOAD(PROJ1) that is executed by SCLM to control the library.

Verify that the link occurred without errors.
Use the ISPF Move/Copy Utility to copy the following members from ISP.SISPSAMP into PROJ1.DEV1.SOURCE (these are the source members for the application and are moved into PROJ1.RELEASE.SOURCE later): FLM01AD9, FLM01CDT, FLM01CD7, FLM01CD8, FLM01EQU, FLM01CIN, FLM01IIN, FLM01INC, FLM01MD1, FLM01MD2, FLM01MD3, FLM01MD4, FLM01MD5, and FLM01MD6.
Use the ISPF Move/Copy Utility to copy the following members from ISP.SISPSAMP into PROJ1.DEV1.ARCHDEF (these are the architecture definition members and are moved into PROJ1.RELEASE.ARCHDEF later): FLM01AP1, FLM01ARH, FLM01CMD, FLM01CM9, FLM01LD1, FLM01LD2, FLM01LD3, FLM01LD4, FLM01LD7, FLM01LD9, FLM01SB1, and FLM01SB2.
Note: If you are not using Fault Analyzer, edit FLM01CM9 as follows:
```
         Delete line OUT2  FLM1AD9 IDILANGX
         Change PARM1 to PARM
```