The following steps prepare the example project data. Perform the
steps in the order listed and exactly as they are described. When
you have completed all of the steps, all necessary data will reside
at the RELEASE group. At this point, you or other SCLM users can use
the data to experiment with and understand SCLM.
- Select the SCLM option from the ISPF Primary Option panel.
- Select the Utilities option from the SCLM Main Menu. Type:
- PROJ1
- in the Project field
- DEV1
- in the Group field
Leave the Alternate field blank.
- Skip this step if you are not using Fault Analyzer. Otherwise:
- From the Utilities panel, select the Migration option. Type:
- SOURCE
- in the Type field
- FLM01AD9 (the ASM module)
- in the Member field
- 1
- in the Mode field
- HLAF
- in the Language field
- 1
- in the Process field
- 1
- in the Messages field
- 4
- in the Report field
- 4
- in the Listings field
Press Enter to begin processing. The migration
utility registers new modules (in this case, FLM01AD9) into an SCLM
library by creating accounting records for them.
- Skip this step if you are not using Fault Analyzer. Otherwise,
from the Utilities panel, select the Migration option. Type:
- SOURCE
- in the Type field
- FLM01INC (the ASM copybook)
- in the Member field
- 1
- in the Mode field
- HLAF
- in the Language field
- 1
- in the Process field
- 1
- in the Messages field
- 4
- in the Report field
- 4
- in the Listings field
Press Enter to begin processing. The migration
utility registers new modules (in this case, FLM01INC) into an SCLM
library by creating accounting records for them.
- From the Utilities panel, select the Migration option. Type:
- SOURCE
- in the Type field
- FLM01C* (the COBOL copybook)
- in the Member field
- 1
- in the Mode field
- COBE
- in the Language field
- 1
- in the Process field
- 1
- in the Messages field
- 4
- in the Report field
- 4
- in the Listings field
Press Enter to begin processing. The migration
utility registers new modules (in this case, FLM01CIN,FLM01CDT,FLM01CD7,FLM01CD8)
into an SCLM library by creating accounting records for them.
- From the Utilities panel, select the Migration option. Type:
- SOURCE
- in the Type field
- FLM01IIN (the PL/I copybook)
- in the Member field
- 1
- in the Mode field
- PLIE
- in the Language field
- 1
- in the Process field
- 1
- in the Messages field
- 4
- in the Report field
- 4
- in the Listings field
Press Enter to begin processing. The migration
utility registers new modules (in this case, FLM01IIN)into an SCLM
library by creating accounting records for them.
- From the Utilities panel, select the Migration option. Type:
- SOURCE
- in the Type field
- FLM01MD2 (the PL/I copybook)
- in the Member field
- 1
- in the Mode field
- PLIE
- in the Language field
- 1
- in the Process field
- 1
- in the Messages field
- 4
- in the Report field
- 4
- in the Listings field
Press Enter to begin processing. The migration
utility registers new modules (in this case, FLM01MD2)into an SCLM
library by creating accounting records for them.
- When the migration is complete, you receive the message MIGRATION
UTILITY COMPLETED with RETURN CODE = 0. The Migration Utility panel
reappears. Type:
- *
- in the Member field
- ASM
- in the Language field
Press Enter to begin processing.
Notice
that you did not have to type EX on the command line or re-enter
a value in the Process field. The value is carried from panel to panel
and is maintained as is until you change it.
The Migration
Utility registers the SCLM accounting information for the remaining
new modules (in this example, all are assembler language modules).
Each time you use the Migration Utility, you can only migrate modules
written in the same language. This example migrates FLM01MD2 first.
After its migration, the other modules can be referenced as a group
by using the asterisk (*). Because FLM01CDT, FLM01CIN, FLM01IIN, FLM01CD7,
FLM01CD8, FLM01MD2, FLM01INC, and FLM01AD9 were migrated first, SCLM
does not migrate them again when an * is specified.
Note: FLM01INC
and FLM01AD9 would be migrated already only if you are using Fault
Analyzer.
- When the migration is complete, you receive the message MIGRATION
UTILITY COMPLETED with RETURN CODE = 0. The Migration Utility panel
reappears. Type:
- ARCHDEF
- in the Type field
- *
- in the Member field
- ARCHDEF
- in the Language field
Press Enter to begin processing.
- Return to the SCLM Main Menu. Select the Build option and press
Enter.
- On the Build panel, type:
- DEV1
- in the Group field
- ARCHDEF
- in the Type field
- FLM01AP1
- in the Member field
- / (slash)
- in the Error Listings only field
- 1
- in the Mode field
- 2
- in the Scope field
- 1
- in the Messages field
- 1
- in the Report field
- 3
- in the Listings field
Press Enter. All modules in the project are assembled
or compiled. SCLM updates the accounting information to indicate that
a build operation was performed on each module. The Build Messages
and Build Report reappears. The build should complete with a RETURN
CODE = 0. The Build panel reappears.
If all of the site-dependent
changes to the system macro library references were not made in 10, build errors can
occur during this step. If this happens, correct the macros, reassemble
and link-edit the project definition, and repeat this step.
- Return to the SCLM Main Menu. Select the Promote option and press
Enter.
- On the Promote panel, type:
- DEV1
- in the From Group field
- ARCHDEF
- in the Type field
- FLM01AP1
- in the Member field
- 1
- in the Mode field
- 1
- in the Scope field
- 1
- in the Messages field
- 1
- in the Report field
Press Enter. SCLM copies all members for all types
at the DEV1 group to the TEST group and then purges all members from
the DEV1 group. The Promote Messages and Promote Report appears. The
Promote should complete with a RETURN CODE = 0. The Promote panel
reappears.
- On the Promote panel, type:
- TEST
- in the From Group field
- ARCHDEF
- in the Type field
- FLM01AP1
- in the Member field
- 1
- in the Mode field
- 1
- in the Scope field
- 1
- in the Messages field
- 1
- in the Report field
- EX
- on the command line
Press Enter. SCLM copies all members for all types
at the TEST group to the RELEASE group and then purges all members
from the TEST group. The Promote Messages and Promote Report appears.
The Promote should complete with a RETURN CODE = 0. The Promote panel
reappears.
All of the modules are located in the RELEASE group, and the SCLM
example project, PROJ1, is now ready to use. This scenario illustrates
the status of a current release of a product that does not have any
maintenance, test, or development activities underway.