MIBR - User input

You must enter a * line with the following format:
Pos. Len. Value Meaning
2 1 '*' Line code
3 8 uuuuuuuu User code
11 8 pppppppp User password
22 4 nnnn Session number (Blank = current session)
26 1   Session status
    'T' If selection of frozen session
    ' ' If current or H session
33 1   Code of library extraction
'A' Extraction of a lower level library and its higher level libraries
'D' Extraction of a library and its depending libraries
    'U' Extraction of only one library
49 1   Lock processing
    ' ' No lock extraction
'1' Lock extraction with user code = user code of the '*'-line
'2' Lock extraction with user code = initial user code
Enter as many following lines as Libraries to be extracted.
Pos. Len. Value Meaning
3 3 bbb Code of the library to be extracted
Enter an O line to insert control cards in front or back of 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
Enter an F line for the merge of Libraries.
Pos. Len. Value Meaning
2 1 'F' Line code
3 Table with 9 items (3 characters long) that contain the Libraries to be merged.
First item: Merge Library (lowest level)
Enter a P line to indicate a project created after the splitting of libraries.
Pos. Len. Value Meaning
2 1 'P' Line code
3 3 bbb Code of library to split
6 3 ccc Type of Pacbase entity to move
      'E ': Data Element
'S ': Data Structure and Segment
      'R ': Report
      'B ': Database Block
      'P ': Program
      'O ': Dialog and Screen
      'F ': Client Meta Entity
'$tt': Client User Entity (tt = call type)
      'T': Text
      'V': Volume
9 15   Code of the new project

Principle of the migration

An extraction context is selected. The session and the library, from which the ascending or descending network will be extracted, are specified.

First step: Extraction of the entities present in the context

All the indexes in the database are read sequentially.

The selection is made on the primary indexes of all the entity families. The highest level library of the entity definition is the reference library. If an element of the folder is detected in a lower level library, the entity folder will be created later in this library (next step).

The overrides of the entity definitions and complete folders are thus detected in a libraries network. The multiple presence of the definition or the existence of one or more elements of its folder in a library different from the definition library are detected.

In a network, all the libraries that contain an element of the folder are detected.

For each library, a command line in view 'C' of the extracted entity (with an appropriate assign card) is formatted and sorted. All these lines constitute the input file of the third step.

Second step: Recognition of entities not retrieved

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

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

Third step: PACX extraction in view 'C'

The entities are extracted in the extraction library and in its higher-level libraries. An entity folder is created in each extraction library. It is inherited from the higher or equal level libraries.

The PACX extraction has been enhanced:

Erroneous requests only are printed in the PAC7EZ report.

This procedure requires the PAC7PM file as input to the BVPACS96 program.

This file, defined with 50-character records, contains in position 1 the VA Pacbase codes of the Programs that are used as Macros but not defined as such in the repository.

This file is produced by the MIAM procedure.

This procedure also replaces unknown special characters in an entity code with other characters, or replaces Windows reserved words with other codes.

The matching table is represented by the PAC7CS file used as input to the BVPACS94 and BVPACS96 programs (optional file, created by the MIAM procedure).

This procedure also generates the input transactions to the following procedures:

The MODE option of the migration help comes from the NSFILE (MIAM) and NMFILE (user) files (See chapter "Migration perimeter").

This procedure also produces the following lists:


Feedback