MIAM - Migration help function
This procedure provides the following functions:
- Search for special characters: loading of the special characters file (CS file).
- Search for entities whose code corresponds to a string not allowed (not compatible with Windows for example): loading of the special characters file (CS file).
- Search for instances whose code starts with or contains blank characters.
- Search for non-existing Segments called in the -CD or -W.
- Search for non-existing Reports called in the -CD.
- Search for Segments renamed as 00 in the -CD or -W when the Segment 00 exists in the network, and also search for calls of different Data Structures for the same Segment code.
- Search for -CD with selection of Segments on continuation line whereas the first line does not contain any selection.
- Search for -CD continuation lines with a selection that is not a Segment selection whereas the preceding line contains a Segment selection (starting with *).
- Search for -Wxx999 F-type working lines for which a -CD line with the same xx code for placement exists, or whose DS code is xx if the code for placement is not specified.
- Search for Reports with duplicate labels.
- Search for gaps in the sequence of label numbers of Reports.
- Search for structures called in categories of a Report and not defined in the description of the Report.
- Search for Report structure lines that call several Data Elements with the same position.
- Search for labels called in Report categories and not defined in the description of the Report.
- Search in the Screen -GE: references to Segments that do not exist in the -CS, references to Data Elements that do not exist in the -CE, references to Texts or Text sections that do not exist, duplicate lines, erroneous C-type comment lines, erroneous Text call lines (T), erroneous Segment call lines (S), erroneous Data Element call lines (F), and erroneous U lines.
- Search for Programs with a generation variant different from N and with only a Definition.
- Search for Programs with an obsolete type and structure.
- Search for standard or Client Screens, other than help screens, with a generation variant different from N and with only a Definition or -CE lines.
- Search in the Screen -CS for calls of preceding Segments that are not present in the same category.
- Search in the Screen -CS for multiple uses of the same Segment in display or reception in the same category.
- Search in the Screen -CE for lines with an L nature and an erroneous length.
- Search for Macro working lines that declare a table whose name contains the $ character.
- Search for working lines not to retrieve (with a type L or A).
- Search for continuation working lines that contain characters before column 12 when the COBOL formatting option in the Library is set to Y.
- Search for obsolete generation variants.
- Search for generation variants or Block types that are not defined in the targets of the VA Pacbase access key.
- Search for Screens and Programs (not typed as Macros or not used as Macros) generated with the same external name.
- Search for duplicate map names for standard or Client Screens that have a generation variant X0, X1, X2, X3, 00, 01, 02, 03, 4F, 80, 10, or 12.
- Search for the uses of Model entities in standard entities.
- Search for EL-type function lines with a level not compatible with a CO- DU- DW-type function that precedes them.
- Search for duplicate P-lines with an N type.
- Search for P-lines of Macro with a function level lower than 99 and associated with an operator code different from N, *, SUP, and $n.
- Search for P entities to be transformed into Macros: loading of PM file.
- Search for Programs coming from PacReverse.
- Search in standard Screens, Clients, or Servers, for P lines that contain blanks (no operator, operand, level, type, or condition).
- Search in standard Screens, Clients, or Servers, for P lines that contain 99BL, 99IT, 99DV, 99DI, or 99DC preceded in the same function or subfunction by a comment line with an OR- or AN-type.
- Search, in Screens, for erroneous conditions in the P lines with a *A, *P, or *R type when these lines are present in functions 20, 25, 30, 35, 60, or 65.
- Search in standard Screens, Clients, or Servers for subfunctions whose first valid line has a 00-level and whose operator is different from SUP and COA.
- Search, in Servers, for erroneous conditions on *B-type P lines.
- Search, in Servers, for extraction methods that are called in Macros.
- Search, in Servers, for user services that are called in Macros.
- Search for entities not to retrieve: loading of the NR
file used by the MIBR and MIBJ procedures. It applies to
the following entities:
- Data Elements with a usage not recognized in RPP (different from 0 1 2 3 5 6 7 8 9 C D F G H I J N O P Q R T U W X Y Z). Data Elements with a usage 4 and a Large Object type (L-type) are exceptions and are recognized,
- Database Blocks with a type AR, D1, D3, QA, QD, QG, QI, QO, QV, SE, TI, TR
- Reports for layouts.
- Bulk-type Meta Entities and the associated User Entities
- Pacdesign Meta Entities and the associated User Entities as well as the Data Elements that define the 7M 7N 5Q Meta Entities if they have not been retrieved with the MT parameter in the BVPAMIAM file.
- SI-type Dialogs or Screens (Initialization server) or ST (Termination server).
- Dialogs, Screens or Programs that contain PAF commands (EXP operator) if the PF parameter with a value NO was indicated in the BVPAMIAM parameter file.
- Volumes that call an Extraction Master Path.
For each case, a record is written in the RQ error file.
For each error with a type EC3 EC6 EC9 ECA ET1 ET6 ET8 GE1 GE2 GE3 GE4 GE5 or SG4, a UPDP-formatted record will be generated in the OUTGY file. So, the error can be corrected in batch mode with the UPDP procedure. For the errors EC6 and ECA that are related to P lines, a GY record will be written on specific lines only. You must then manage the errors from the Macro lines.
For each error with a type EC7, WK2, MP6, or MP7, a UPDP-formatted record will be generated in the OUTUP file. So, the error can be corrected in batch mode with the UPDP procedure.
Pos. | Len. | Value | Meaning |
---|---|---|---|
1 | 2 | Type of character | |
WN | Character not compatible with WINDOWS | ||
CS | Special character | ||
3 | 6 | Detected character or string | |
9 | 6 | Substitute character or string: this field must be filled in before the execution of the MIBA or MIBR procedures | |
15 | 66 | FILLER |
Pos. | Len. | Meaning |
---|---|---|
1 | 3 | Library code |
4 | 3 | PAF type |
7 | 30 | Entity code |
37 | 2 | Block type |
39 | 1 | Data Element usage |
40 | 6 | Meta Entity |
46 | 35 | FILLER |
Description of the NS file:
This file contains the following entities:
- Screens that have only a Definition or -CE lines,
- Programs that have only a definition,
- Screens with an N generation variant,
- Programs not typed as Macros and not used as Macros
with an N generation variant.
Pos. Len. Meaning 1 3 Library code 4 3 PAF type 7 30 Entity code
Pos. | Len. | Meaning |
---|---|---|
1 | 6 | Entity code |
7 | 44 | FILLER |
Pos. | Len. | Value | Meaning |
---|---|---|---|
1 | 3 | Library | |
4 | 3 | PAF type | |
7 | 6 | Entity code | |
13 | 24 | FILLER | |
37 | 3 | Error type | |
BL | Block not to retrieve | ||
BLK | Instance whose code starts with or contains a blank character | ||
CS | Special character | ||
DI1 | Dialog with an SI type (Initialization server) or ST type (Termination server) | ||
EC2 | Screen with an SI type (Initialization server) or ST type (Termination server) | ||
EC3 | Screen whose -CS contains multiple uses of the same Segment in display or reception in the same category | ||
EC4 | Standard or Client Screen with a generation variant different from N, that contains only a definition or -CE lines | ||
EC5 | P line with 99BL, 99IT, 99DV, 99DI, 99DC, preceded by a comment line with an OR- or AN-type | ||
EC6 | P line with a *A, *P, or *R type, with an erroneous condition in functions 20, 25, 30, 35, 60, or 65 | ||
EC7 | Screen that contain L lines with an erroneous length in its -CE | ||
EC8 | Subfunction of Screen whose first valid line has a 00-level and whose operator is different from SUP and COA | ||
EC9 | Preceding Segment called in -CS but not present in the same category | ||
ECA | *B-type P line with an erroneous condition | ||
ECC | X-ref in the OSC and OSD operators with special characters in the external names | ||
ECD | Potential override of the generated standard functions F20 F25 F35 F60 F80 | ||
ECE | N title line not on line zero and SUP not on the first line | ||
ET1 | Report with duplicate label | ||
ET3 | Report for PDM layout | ||
ET4 | Non existing label called in a category of the Report | ||
ET5 | Non existing structure called in a category of the Report | ||
ET6 | Structure that calls several Data Elements with the same position | ||
ET7 | Missing label in the labels sequence of the Report | ||
ET8 | Non-existing Report called in -CD | ||
EU1 | Pacdesign User Entity not retrieved | ||
EU2 | Bulk-type User Entity not retrieved | ||
FG1 | Input Aid with more than 100 description lines | ||
GE1 | Non-existing reference (-GE) | ||
GE2 | Duplicate line in -GE | ||
GE3 | Erroneous comment line in -GE | ||
GE4 | Erroneous call of a Text, Segment, or Data Element | ||
GE5 | Erroneous U line in -GE | ||
MCN | Macro with no type (indicating PARAM or NO PARAM) | ||
MP4 | EL-type function whose level is not compatible with a preceding CO- DU- or DW-type function | ||
MP6 | Extraction method called in a Macro | ||
MP7 | User service called in a Macro | ||
MT1 | Pacdesign Meta Entity not retrieved | ||
MT2 | Bulk-type Meta Entity not retrieved | ||
MT3 | Data Element of Meta Entity not retrieved | ||
NV1 | Function level not compatible with the operator | ||
PA1 | Presence of PAF operator | ||
RU1 | Use of Model entity in standard entity | ||
PG1 | Duplicate P-line with N type | ||
PG2 | Program with an obsolete type and structure | ||
PG4 | Program coming from PacReverse not taken into account | ||
PG5 | Program with a generation variant different from N, that contains a definition only | ||
SG1 | Conflict of Segment naming in -CD or -W | ||
SG2 | On -CD, no selection on first line but selection on continuation lines | ||
SG4 | Non-existing Segment called in a -CD or in a -W | ||
SG5 | Wrong selection on -CD continuation line | ||
SP1 | X-ref of Data Elements with special characters | ||
UR | Data Element usage not to retrieve | ||
VAR | Obsolete generation variant | ||
VAK | Generation variant or Block type not defined in the access key targets | ||
VO1 | Volume that calls an Extraction Master Path | ||
WK | Working line with a type L or A | ||
WK1 | Macro working line that declares a table whose name contains a $ character | ||
WK2 | Continuation working line with characters before column 12 when the COBOL formatting option is set to Y in the Library | ||
WKC | -Wxx999 working line and presence of a -CD line with the same xx code for placement | ||
WN | Characters not compatible with Windows | ||
40 | 40 | Error label | |
80 | 2 | Section | |
82 | 2 | Paragraph | |
84 | 3 | Line number | |
87 | 2 | File code | |
89 | 4 | Segment code | |
93 | 2 | Label number | |
95 | 6 | Volume code | |
101 | 6 | Data Element code | |
107 | 3 | PAF type | |
110 | 6 | Entity code | |
116 | 2 | User Entity call type | |
118 | 3 | Screen type (1) | |
121 | 30 | FILLER |
(1) The Screen type is specified only for the errors detected on the Screen Definition, with the value SRC for a standard Screen, CLI for a Client Screen, SRV for a Server Screen, and ECR for the other Screens.
Code | Meaning | Consequence | Possible action | Consequence if no action |
---|---|---|---|---|
BLK | Instance that starts with or contains a blank character | Correct in VA Pacbase | TA2 import rejected. | |
CS | Special character, duplicate labels | Population of the CS file | (1) | TA2 import rejected. Generation error if the entity is used. |
WN | Character not allowed (example: not compatible with Windows) | Population of the CS file | (1) | TA2 import rejected. Generation error if the entity is used. |
MCN | Non-typed Macro | Population of the PM file | (2) | |
VAR | Obsolete generation variant | Error in the RQ file | Populate the NR file | Generation rejected |
EC3 | Multiple use of the same Segment in display or reception in the same category of the -CS of a Screen | Error in the RQ file | Correct in VA Pacbase (5) | Generation error |
EC5 | P line with 99BL, 99IT, 99DV, 99DI, 99DC preceded by a comment line with an OR- or AN-type | Error in the RQ file | Correct in VA Pacbase | Dot not generated before the line |
EC6 | P line with a *A, *P, or *R type with an erroneous condition | Error in the RQ file | Correct in VA Pacbase (5) | Generation difference in the migration help |
EC7 | -CE line with an L type and an erroneous length | Error in the RQ file | Correct in VA Pacbase (5): remove the line and create it again (5) | Generation difference in the migration help |
EC8 | Subfunction of Screen whose first valid line has a 00 level and whose operator is different from SUP and COA | Error in the RQ file | Correct in VA Pacbase | Generation difference in the migration help |
EC9 | Call of preceding Segment not present in the same category | Error in the RQ file | Correct in VA Pacbase (5) | Generation difference in the migration help |
ECA | *B-type P line with erroneous condition | Error in the RQ file | Correct in VA Pacbase (5) | Generation difference in the migration help |
ECC | X-ref in OSC/OSD with special characters in the external name | Error in the RQ file | Correct in VA Pacbase | Generation difference in the migration help |
ECD | Potential override of standard subfunctions | Error in the RQ file | Correct in VA Pacbase | Problems when using RPP after the migration |
ECE | N line not on line zero and SUP not on the first line | Error in the RQ file | Correct in VA Pacbase | Generation difference in the migration help |
ET1 | Report with duplicate label | Error in the RQ file | Correct in VA Pacbase (5) | Warning in RPP |
ET4 | Non-existing label called in a category of the Report | Error in the RQ file | Correct in VA Pacbase: remove the call to the label | Generation difference in the migration help |
ET5 | Non-existing structure called in a category of the Report | Error in the RQ file | Correct in VA Pacbase: remove the call to the structure | Generation difference in the migration help |
ET6 | Structure that calls several Data Elements with the same position | Error in the RQ file | Correct in VA Pacbase: correct the structure (5) | Generation difference in the migration help |
ET7 | Missing label in the labels sequence of the Report | Error in the RQ file | Correct in VA Pacbase | Generation difference in the migration help |
ET8 | Non-existing Report called in a -CD | Error in the RQ file | Correct in VA Pacbase (5) | Generation difference in the migration help |
FG1 | Input Aid with more than 100 description lines | Error in the RQ file | Divide into n Input Aids with less than 100 description lines | Generation difference in the migration help |
GE1 | Non-existing reference (-GE) | Error in the RQ file | Correct in VA Pacbase: modify the -CE or -CS or the call to text reference (5) | Error indicated in the TA2 import (transformed into a comment) |
GE2 | Duplicate line in -GE | Error in the RQ file | Correct in VA Pacbase: delete the duplicate line (5) | Differences upon generation |
GE3 | Erroneous comment line in -GE | Error in the RQ file | Correct in VA Pacbase: delete the comment line (5) | Differences upon generation |
GE4 | Erroneous call of a Text, Segment, or Data Element in -GE | Error in the RQ file | Correct in VA Pacbase: delete the call line (5) | Differences upon generation |
GE5 | Erroneous U-type line in -GE | Error in RQ file | Correct in VA Pacbase: delete the call line (5) | Differences upon generation |
MP4 | EL-type function whose level is not compatible with a preceding CO, DU, or DW type function | Error in the RQ file | Correct in VA Pacbase | Differences upon generation |
MP6 | Extraction method called in a Macro | Error in the RQ file | Line automatically transformed in VA Pacbase into a specific line through the OUTUP file | Generation problem |
MP7 | User service called in a Macro | Error in the RQ file | Line automatically transformed in VA Pacbase into a specific line through the OUTUP file | Generation problem |
NV1 | Function level not compatible with the operator | Error in the RQ file | Correct in VA Pacbase: modify the level or the operator, or both | Possible generation error |
RU1 | Model entity used in standard entity | Error in the Q file | ||
PG1 | Duplicate P-line with N type | Error in the RQ file | Correct in VA Pacbase | Possible generation error |
PG4 | Program from PacReverse not taken into account | Error in the RQ file | Wait for enhancements | Cannot be migrated |
SG1 | Conflicting Segment names in -CD or -W | Error in the RQ file | Correct in VA Pacbase | Generation differences in the migration help |
SG2 | On -CD: no selection on first line but selection on continuation line | Error in the RQ file | Correct in VA Pacbase | Generation differences in the migration help |
SG4 | Non-existing Segment called in a -CD or a -W | Error in the RQ file | Correct in VA Pacbase (5) | Generation differences in the migration help |
SG5 | Wrong selection on -CD continuation line | Error in the RQ file | Correct in VA Pacbase | Generation differences in the migration help |
SP1 | X-ref of Data Elements with special characters in their codes | Anomalie dans le fichier RQ | Correct dans VA Pacbase | Generation differences in the help migration |
WK | Working line with L or A type | Error in the RQ file | Not taken into account | |
WK1 | Working line with a table name that contains a $ character | Error in the RQ file | Manually correct in RPP either in the MIMA file or after the dispatching | Erroneous index of the table |
WK2 | Continuation working line with characters before column 12 | Error in the RQ file | Correct in VA Pacbase | Problem upon generation |
WKC | -Wxx999 working line and presence of a -CD line with the same xx code for placement | Error in the RQ file | Correct in VA Pacbase | Error upon generation |
BL | Database Block not to retrieve | Population of NR file | (3) | |
DI1 | Dialog with an SI type (Initialization server) or ST type (Termination server) | Population of NR file | (3) | |
EC2 | Screen with an SI type (Initialization server) or ST type (Termination server) | Population of NR file | (3) | |
ET3 | Report for PDM layout | Population of NR file | (3) | |
EU1 | Pacdesign User Entity not retrieved | Population of NR file | (3) Caution: it is an option. The input of the procedure must be modified to retrieve it | |
EU2 | Bulk-type UE not retrieved | Population of NR file | (3) | |
MT1 | Pacdesign Meta Entity not retrieved | Population of NR file | (3) Caution: it is an option. The input of the procedure must be modified to retrieve it | |
MT2 | Bulk-type Meta Entity not retrieved | Population of NR file | (3) | |
MT3 | Data Element of Meta Entity not retrieved | Population of NR file except for a Data Element of 7N, 7M, or 5Q Meta Entities if the MT parameter is positioned in the BVPAMIAM file | (3) | |
PA1 | Presence of PAF operator | Population of NR file | (3) | |
PG2 | Program with an obsolete type and structure | Population of NR file | ||
UR | Data Element usage not to retrieve | Population of NR file | (3) | |
VO1 | Volume that calls an Extraction Master Path | Population of NR file | (3) | |
EC4 | Screen with only a definition or -CE lines | Population of NS file | (4) | |
PG5 | Program with only a definition | Population of NS file | (4) |
(1) The CS file of special characters is used to replace characters or strings with valid values.
This file is used by the MIBA, MIBR, MIBJ, and MIMA procedures.
If there is no substitution value, the MIBA, MIBJ, and MIBR procedures stop.
(2) The PM file of Programs used as Macros (but that are not typed as Macros) allows the MIBA, MIBR, and MIBJ procedures to process them as Macros.
(3) The NR file contains the entities that are not retrieved after the processing.
It applies to the MIBR and MIBJ procedures.
This file can be edited and populated with obsolete entities.
(4) The NS file contains banner Screens, Screens or Programs with a definition only, and Screens or Programs with an N type of COBOL to generate.
(5) The GY file contains the erroneous transactions in a UPDP format. You must correct the errors either in online mode, or after the UPDP batch update after the modification of the data in the GY file.