It is the user input of the PACX procedure, with the following specific values.
Pos. | Len. | Value | Meaning |
---|---|---|---|
2 | 1 | '*' | Line code |
3 | 8 | uuuuuuuu | User code |
11 | 8 | pppppppp | User password |
19 | 3 | bbb | Extraction Library code |
22 | 4 | nnnn | Session number (Blank=current session) |
26 | 1 | 'T' | Session status if Test session |
29 | 4 | EXTR | Extractor code |
34 | 1 | '1' | Formatting for UPDP (PAF) |
49 | 1 | Lock management | |
' ' | No lock extraction | ||
'1' | Lock extraction with user code = user code of the * line | ||
'2' | Lock extraction with user code = initial user code | ||
55 | 1 | '1' | Timestamp request indicator |
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 |
Pos. | Len. | Value | Meaning |
---|---|---|---|
2 | 4 | 'W' | Line code |
3 | 1 | '1' | Line number |
4 | 2 | 'EX' | |
6 | 1 | '+' | Library selection code: |
Library and its upper-libraries with the generation of identification lines (* lines) | |||
7 | 33 | Choice | Entity to be extracted, coded in the same way as the Choice field in online mode. |
40 | 4 | Extraction type: | |
'ALL ' | Entity and used entities |
Principle of migration
The entities are extracted from each library of each element of its folder, within the same network.
First step: PACX extraction in view '+'
When the definition of en entity is extracted, the library of each element in its folder is searched for.
The highest-level library is the reference library. The folder of the entity is created later (next step) in each lower-level library found.
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 (and an appropriate assign card) is formatted and sorted. All these lines constitute the input file of the second step.
Second step: PACX extraction in view 'C'
The entities are extracted in the extraction library and in the 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 in the following way:
Only the erroneous requests are included in the PAC7EZ report.
This procedure requires the PAC7PM file as input to the BVPACS96 program.
This file, which is defined with 50-character records, contains in position 1 the VA Pac codes of the Programs 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 unauthorized words (Windows reserved words for example) with other codes. The matching table is the PAC7CS file used as input to the BVPACS94 and BVPACS96 programs (optional file that is created by the MIAM procedure).
If this file exists, it must be specified in the BVPMIBA script by giving a value to the WshEnv("BVP_MibaSpecChar") line.
If the line has no value, a MibaSpecChar.txt file will be created, empty, in the [database_name] directory.
This procedure also generates the input transactions to the following procedures: