MIBR - Libraries merge
The migration procedure enables you to merge libraries in a project.
The F lines contain the libraries to be merged. The first library that is specified is the merge library.
The extraction is performed from the merge library, which is the lowest-level library.
The extraction requests are specified in view C1 in this low-level library.
Example:
F line: FBI3BI2BI1
This line means that the BI1, BI2, and BI3 libraries are to be merged. All the identification lines of BI1 and BI2 will be replaced by BI3. The result of the merge will be contained in the BI3 library.
Transformation of the libraries hierarchies.
The libraries hierarchy is modified.
The upward hierarchy of the lowest library is created again and the libraries to be merged are removed.
Recognition of the NR, NT, NS and NM files.
The files that contain the entities not retrieved and not to be generated are produced by MIAM. They indicate, for each entity, the library that it belongs to before the merge. The merge library will replace the initial libraries.
Impact on the MIAn.TXT command files.
The GCx and GGx commands will be generated in the lowest library.
Principle of use.
Libraries can be merged if they are dependent in a sub-hierarchy and if there is no parallel sub-hierarchy.
Example:
BI1
|__ BI2
|__ BI3
|__ BI4
|__ BI5
|__ BI6
|__ BI7
The libraries to be merged must belong to the same sub-hierarchy. BI6 and BI5 cannot be merged.
The library to be merged must not be the origin of several sub-hierarchies. BI2 cannot be merged.
The list of the libraries to be merged must be complete. All the dependent libraries that are involved in the merge must be entered in the order of the upward hierarchy.
To merge BI3 and BI5, you must include BI4 in the merge request.
The F line will have the following structure: FBI5BI4BI3
9 levels of libraries can be entered.
- A library to be merged cannot be a merge library.
- A library to be merged must belong to the hierarchy that is extracted by MIBR.
- You must not enter F lines (merge) and O lines (split).
- Limits: 999 libraries to be merged.
The MIBR procedure saves the information after the merge request. This information will then be taken into account by the MIBJ procedure.
The SPLITLIB file that is produced by MIBR will be used as input to MIBJ.