Using the migration utility, you can introduce members or groups of members to an SCLM project and place them under SCLM control in a development group. The migration utility also lets you verify authorization codes, prohibit simultaneous updates of members, and collect statistical, dependency, and historical information for each member processed without using the SCLM edit function. SCLM collects dependency information, which identifies software components that need another software component to complete successfully.

Before you start MIGRATE, the members must exist in the development library you specify. Upon successful completion of MIGRATE, each member selected will have valid SCLM accounting information. A typical scenario used to migrate existing project data follows:

1. Copy all of the members that have the same language into a development library.
2. Start MIGRATE using * for the member pattern and the appropriate language to parse all members and store their statistical, dependency, and historical information.
3. Copy all of the members that have a different language into the development library.
4. Start MIGRATE again using * for the member pattern and the new language.
5. Continue until all of the members have been migrated.

If some of the members have SCLM accounting information, the MIGRATE service verifies that the accounting information matches the member in the development library. MIGRATE takes no action for members that already have valid SCLM accounting information, unless executed in forced mode.

Use this utility when you have a large number of members that have not been entered in your project database, such as members that you did not create with the SCLM edit function.

In addition to the SCLM editor, the Migration Utility lets you indicate the members you want tracked. Use this utility to enter one or more members into a database of a project (for example, during a conversion to SCLM). In development groups, you can also use it to lock, parse, and create accounting records for members that have not been registered to SCLM.

Like the SCLM editor, the migration utility verifies authorization codes, prohibits simultaneous updates of members, and collects statistical, dependency, and historical information for every member processed. SCLM stores this information in the database of a project. For a complete description of the lock, parse, and store process, refer to:

• LOCK—Lock a Member or Assign an Access Key
• PARSE—Parse a Member for Statistical and Dependency Information
• STORE—Store Member Information in an Accounting Record

Figure 1 shows the panel that appears when you select Option 3, Migration, from the Utilities Panel.

   Menu  SCLM  Utilities  Jobcard  Help
 ──────────────────────────────────────────────────────────────────────────────
                      SCLM Migration Utility - Entry Panel
 Command ===>                                                                  

 Selection criteria:
   Project  . : PDFTDEV
   Group  . . . PDFTDEV 
   Type . . . . MOS     
   Member . . . SOURCE      (Pattern may be used)

 Member information:
   Authorization code  . . REL          Mode  . . . 1  1. Conditional
   Change code . . . . . . 2                           2. Unconditional
   Language  . . . . . . . PASCAL                      3. Forced
   Subproject  . . . . . .         
 Output control:
                Ex Sub                  Process . . 2  1. Execute
   Messages . . 3  3    1. Terminal                    2. Submit
   Report . . . 3  3    2. Printer
   Listings . . 3  3    3. Data set     Printer . .  
                        4. None         Volume  . .       

  F1=Help      F2=Split     F3=Exit      F7=Backward  F8=Forward   F9=Swap
 F10=Actions  F12=Cancel

The action bar displays the same choices as those discussed in SCLM main menu action bar choices. An additional choice is Jobcard.

The fields for the Migration Utility - Entry panel are.

Project

The project that you specified on the SCLM Main Menu. You cannot change this field. An Alternate field also appears if you specified an alternate project.

Group

The group in which the members to be migrated are located. This group must be defined in the project definition and must be a development group.

Type

The type in which the members to be migrated are located. This type must be defined in the project definition.

Member

The name of the member you want processed. You can use patterns for the member name. See Specifying selection criteria for details.

Authorization code

The authorization code for a member. SCLM cannot process a member if the authorization code assigned to a member is not in the group being accessed. Authorization codes cannot contain commas.

Change code

The change code for the member. To enter a different change code for the member, type over the displayed change code. A change code verification routine can verify the code you entered before it processes the member. Change codes cannot contain commas.

Language

The language of the member. See SCLM translators for a list of languages for which SCLM supplies parsers.

Mode

Select one of the following modes:

Conditional

To stop processing members if migrate discovers an error that is greater than the GOODRC parameter specified for a language parser in the project definition.

If you have a list of members that you want to place under SCLM control, and migrate fails for one of those members, processing stops after the first error. Migrate does not process any other members that match the specified criteria.

Unconditional

To continue processing regardless of errors discovered during parsing of each member.

If you have a list of members that you want to place under SCLM control, migrate attempts to process all the members matching the selection criteria, regardless of any errors encountered.

Forced

Forces SCLM to create a new accounting record for the members specified regardless of previous status. Processing stops after the first error is encountered.

If you have a list of members that need to be changed, migrate will create new accounting records for any members specified. This can be used to update language, authorization code or change code information for the specified members.

Output control

Specify the destination for messages, report, and listings when they are executed (Ex) or submitted (Sub), by entering the corresponding destination number: 1 for Terminal, 2 for Printer, 3 for Dataset, or 4 for None.

Process

You can call the processing part of the migration utility from the interactive or batch environment by selecting Execute or Submit, respectively. If you request batch processing by selecting Submit, you must specify the job statement information that is used in the JCL generated for batch processing.

For information about using a unique jobname on the jobcard in batch processing, see Batch Processing.

Printer

Specify the printer output class.

Volume

Specify the volume on which SCLM should save data sets.