The user file must have a UPDP format. It can come from an EXTR or PAF extraction for example.
Constraints: The folder of each entity must be complete in a context (definition, and folder elements (description, comments)). An assign line must be created for each context.
When a Segment is created, its Data Structure must be created too (if it does not already exist in RPP).
If a Segment is modified, only the Segment records must be supplied.
If a Screen is created, the Dialog, the common area and the help Screens must also be created (if they do not already exist in RPP).
If a Screen is modified, only the Screen records must be supplied.
If a Library is created, you must supply the LIBDEF (definition) and LIBNET (hierarchical order) records.
Processing of the user file
For each record, definition or folder, an RQ record is formatted with the entity type and code, the Library and session of the record. The RQ file and the UPDP-formatted user file (sorted and reformatted) will constitute the TA2 migration file.
Libraries splitting
The MIBR procedure saves the result of the Libraries splitting requested by the user in a file. This result is then used by MIBU.
The file that is produced by MIBR will constitute an input to MIBU. It contains all the projects that are produced by the Libraries splitting, sorted according to their hierarchy. Each entity extracted by MIBU and present in the PAC7RQ file will be moved to another project if its target Library is a Library to be split. The new project that is specific to its entity type is then assigned to it.