MIBR - Libraries splitting

Some very large libraries can be reduced by the MIBR procedure because this procedure splits them.

The library to be reduced is divided into N new projects.

Using P lines, you must specify the new project where each relevant Pacbase entity will be moved to. All the projects are dependent and their hierarchy depends on the associated Pacbase entity type.

The order is described in the input table of the P line.

However, you can put the projects of the User Entities wherever you want to.

The same project can be associated with several Pacbase entity types if their types are directly dependent (immediate hierarchy).

To ensure that the list of the new projects created by the splitting of libraries is coherent, a control verifies that all the Pacbase entity types (except the Meta Entities) are present in the P lines.

The following limits apply to P input:

To use this option, the migration request is made in descending mode 'D'.

The order for the MIBR input is the following:

You must respect the hierarchy of the libraries to split by sorting the P lines from the highest to the lowest level libraries.

The MIBR procedure saves the dispatching user requests. Thus, they can be taken into account by the MIBJ procedure.

The SPLITLIB file produced by MIBR will be used as input to the MIBJ procedure. It contains all the projects that were created from the splitting of the libraries and their hierarchy.


Feedback