MIBJ - 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 MIBJ procedure automates these actions.

This procedure enables you to constitute filters from the NRFILE and NSFILE 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. This file has the following structure:
Pos. Len. Meaning
1 3 Library code
4 3 PAF type
7 30 Entity code

Filter of the entities to be generated:

A MODE option is created for the migration help. It can take the following values:

You can update the NMFILE 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 NSFILE file that is produced by the MIAM procedure contains the Screens or Programs whose source code is not to be migrated (Screens with a Definition only or with Descriptions 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 entity is not to be migrated, it is not included in the MIAn.txt files.

Sample MIA2 command line:

Z90GCO SCREENC9 MODE=S


Feedback