MIBR - Migration perimeter
All the VA Pacbase Programs and Screens are not in production. A migration help is proposed for these entities. It determines if the migration must be effective, standard or partial. To prevent manual modifications in the repository (deletion of the "Type of COBOL to generate" for example) or in the MIAn.txt files (deletion of entities for example), the MIBR procedure automates these actions.
With this procedure, you can constitute filters from the MIAMNR and MIAMNS files (produced by the MIAM procedure), and from the NTFILE and NMFILE user files.
You can select a list of entities not to be migrated.
You can assign a migration help MODE to the entities.
Filter of the model:
You can update the NTFILE file by indicating a list of entities not to be migrated to RPP.
Pos. | Len. | Meaning |
---|---|---|
1 | 3 | Library code |
4 | 3 | PAF type |
7 | 30 | Entity code |
If this file exists, it must be specified in the execution script by giving a value to the WshEnv("BVP_MibrNRetUsr") line.
If the line has no value, a Mvmibrnt.txt file will be created, empty, in the [database_name] directory.
Filter of the entities to be generated:
A MODE option is created for the migration help.
It can take the following values:
- N: No migration of the source code (the design is migrated),
- S: Standard migration.
You can update the MIAMNS file by assigning a migration help MODE to the Program and Screen entities that are not to undergo a standard migration.
This file has the following structure:Pos. Len. Meaning 1 3 Library code 4 3 PAF type 7 30 Entity code 49 1 Migration help mode
The MIAMNS file that is produced by the MIAM procedure contains the Screens or Programs whose source code is not to be migrated (Screens with an N type of COBOL to generate, Screens with a Definition only or with Descriptions only, or Programs with a Definition only). It is concatenated with the NMFILE file and transformed into an indexed file.
When the command files of the MIAn procedures are created, the migration help MODE option is deduced from the indexed file. If the source of entity is not to be migrated, the entity is not included in the MIAn.txt files.
Sample MIA2 command line:
Z90GCO SCREENC9 MODE=S
If the MIAMNS file exists, it must be specified in the execution script by giving a value to the WshEnv("BVP_MibrNotMigr") line.
If this line has no value, the Mvmibrns.txt file will be created, empty, under the [database_name] directory.
If the NMFILE file exists, it must be specified in the execution script by giving a value to the WshEnv("BVP_MibrNotStd") line.
If this line has no value, the Mvmibrnm.txt will be created, empty, under the [database_name] directory.