MIBJ - User input

You must enter a * line with a user code and a password.
Pos. Len. Value Meaning
2 1 '*' Line code
3 8 uuuuuuuu User code
11 8 pppppppp User password
Enter a J line with the extraction criteria.
Pos. Len. Value Meaning
2 1 'J' Line code
24 4 ssss Beginning session number
28 4 ssss End session number if a frozen session is selected
    9999 if the current session is selected
32 8 ccyymmdd Starting date of the selection
48 1   Version of the selected transactions
    ' ' All sessions
    'Z' Current session only
    'T' Frozen session only
49 3 bbb Code of the selected library
52 5 ssssT Selection of T-type session (test version of frozen session: 'ssssT')
Enter an O line to insert control cards in front or back of the generation commands.
Pos. Len. Value Meaning
2 1 'O' Line code
3 3 bbb Generation command
      'GCP': Program
      'GCO': Dialog
      'GGC': Client
      'GGS': Server
7 2 be Control card in front
9 2 af Control card in back

Principle of the migration

For each journal transaction, entity definition or folder, the extraction is performed from the library and session (frozen or current) of the transaction, and from the library of each element of its folder, in the lower network.

First step: Journal analysis

For each transaction, definition or folder, an RQ record is formatted with the entity type, entity code, the transaction library and session.

When a user entity is processed, its meta entity is extracted.

A deleted entity is indicatd in the RQ file.

The frozen sessions are listed in the RQ file.

For each entity, the procedure searches in the repository for its highest-level library and all the libraries higher and lower than the journal transaction library where the entity is overridden. The multiple presence of the definition or the existence or one or more parts of its folder in a library different from the definition library is detected.

The highest-level library is the reference library. In each lower library found, the folder of the entity will be created (next step).

For each library, a command line in 'C' view of the extracted entity, and an appropriate assign card are formatted and sorted.

All these lines make up the input file of the third step.

Second step: Recognition of the entities not retrieved

This step allows not to transfer in output all the entities that are listed in the PAC7NR file.

Then, it requires the presence of the NRFILE and NTFILE files of the entities not retrieved. These files are provided by MIAM and by the user.

Third step: PACX extraction in 'C' view

The entities are extracted in the extraction library and in the higher-level libraries.

In each extraction library, an entity folder is created, inherited from its higher or equal level libraries.

Only the erroneous requests are included in the PAC7EZ report.

Spliting of libraries

The MIBR procedure saves the user requests of libraries splitting. They are taken into account in the MIBJ procedure.

The OUTSPLT file, produced by MIBR, is used as input to MIBJ (SPLTFILE). It contains all the projects created by the splitting of libraries and their hierarchy.

Each entity extracted by MIBJ and present in the PAC7RQ file is processed to verify whether it must be moved to a new project, i.e. if its target library is a library to split.

If so, the new project specific to its entity type is assigned to this entity.


Feedback