Error codes that require a correction

Some error codes require a correction before the migration.

BLK: Instance that starts with or contains a space

Example:

Definition of an instance whose name is BL ANC.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6--
T0FTXTBL ANC                        BLKENTITY CONTAINING SPACE

A record is written in the NR file. This file contains the entities that are not retrieved in Rational® Programming Patterns. If the error is not corrected, the import of the TA2 file might be rejected and the compression of spaces in Rational Programming Patterns might originate duplicate instance codes.

You must correct in Pacbase. You must remember to enter & characters instead of spaces to access the instance.

EC7: Screen -CE line with a wrong length

Example:

Wrong length for a Screen -CE line.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0--
BMSECRPF0000                        EC7-CE LINE SCREEN WITH ERRONEOUS LENGH        110        44    00
BMSECRPF0000                        EC7-CE LINE SCREEN WITH ERRONEOUS LENGH        300        22    14
Column contents:
  • 84-86: Line number in -CE
  • 95-96: Stored length of the label
  • 101-102: Computed real length

Generation differences appear.

To correct, you must run the UPDP procedure. Use as input the transactions of the UP file that is generated by MIAM:
XECRRUB    PF0000110      A01020L        0000                        00
XECRRUB    PF0000300      A01020L        0000                        00 TITRE ECRANSSS/
The label length will be computed and updated automatically.
EC9: In the -CS, call of a preceding Segment that is not present in the same category

Example:

In the -CS, call of the VL20 preceding Segment that is not called in the same category as Segment CN20.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0-
T3FECRCI0001                        EC9PREVIOUS SEGMENT NOT EXISTING IN CATEG.          CN20  VL20  R
Column contents:
  • 89-92: Screen Segment
  • 95-98: Segment that precedes the call of Segment CN20
  • 101: Category code

Generation differences appear.

To correct, you must remove the reference to the preceding Segment that is not called in the same category.

ECC: Cross-references in OSC or OSD operator with special characters in the Screen external name

Example:

Call of an OSC operator in subfunction 91BB in the -P lines of the GVMIAM Screen.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+
BMSECRGVMIAM                        ECCX-REF IN OSC OR OSD WITH SPECIAL CHARS. 91BB100                                  AAGVP1
Column contents:
  • 80-86: Function, subfunction, and line number
  • 121-126: Macro

Problems can occur upon the migration because external names contain special characters.

To correct, you must replace the special characters in Pacbase.

ECE: N line not on a line 000 and SUP operator not on the first line

Example:

In the -P lines of Screen MIAMG1, the N line has a line number 100 and the SUP line is the second line.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+
BMSECRMIAMG1                        ECEOPERATOR N NOT AT LINE 000 WITH SUP     99NS100                                  AAGVNS
Column contents:
  • 80-86: Function, subfunction, and line number
  • 121-126: Macro

Problems can occur upon the migration.

You must correct in Pacbase. It is better to enter the N title line on line 000 or to enter the SUP operator on the first line in a function or subfunction.

FG1: Input Aid with more than 100 description lines

Example:

GVMIAM Input Aid that contains 101 description lines.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9-
BMSFOGGVMIAM                        FG1INPUT AID WITH MORE THAN 100 DESC LINES     101
Column contents:
  • 84-86: Line number in the description

Problems occur upon the migration because the number of description lines is limited to 100 for each Input Aid.

You must correct in Pacbase. You must divide the Input Aid into several Input Aids that contain no more than 100 description lines each.

GE1: Unknown reference (-GE)

Examples:

In the -GE of a Screen, call of a Data Element that does not exist in the Screen -CE, and call of a Segment that does not exist in the Screen -CS.

In the -GE of a Screen, call of a Text section that does not exist.

These examples apply to the -GE of a Screen. The first erroneous line calls a Data Element that is not defined in the Screen -CE. The second erroneous line calls a Segment that is not present in the Screen -CS. The third erroneous line calls a Text section that does not exist. The same error appears with a Text code that does not exist.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+-
BMSECRBCVC00                        GE1NON EXISTING REFERENCE (-GE) RUBRIQUE   F   100              VCOACT
BMSECRBCVC00                        GE1NON EXISTING REFERENCE (-GE) SEGMENT    S   140  CV00
GENECRGG00ME                        GE1NON EXISTING REFERENCE (-GE) TEXTE      T   099     GV0010 CM
Column contents:
  • 69-76: Name of the entity type
  • 80: Line type
  • 84-86: Line number
  • 89-92: Segment code
  • 92-97: Text code
  • 99-100: Text section
  • 101-106: Data Element code

Errors are indicated upon the import of the ta2 file. These lines are transformed into comments.

You must correct in Pacbase. Remove the -GE line, or enter a reference that exists in the -CE or -CS, or a Text or section that exists.

GE2: Duplicate lines in -GE

Example:

In the -GEof a Screen, duplicate calls of lines.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+-
T0FECRCG0004                        GE2DUPLICATE LINE IN -GE                   U   112  111         UUUU
T0FECRCG0004                        GE2DUPLICATE LINE IN -GE                   F   308  304         RUBW  2
T0FECRCG0004                        GE2DUPLICATE LINE IN -GE                   S   206  202         PR00  A
T0FECRCG0004                        GE2DUPLICATE LINE IN -GE                   S   226  224         SS10  A
Column contents:
  • 80: Line type
  • 84-86: Number of the first line
  • 89-92: Number of the second line
  • 101-106: Data Element or Segment code of the duplicate F or S-type line, or Data Element or Segment code of the duplicate U line
  • 107: Duplicate error code on the U-type line

Generation differences appear.

To correct, you must remove the duplicates.

GE3: Erroneous comment lines in -GE

Example:

In the -GE of a Screen, the comment lines start in column 01.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+
T0FECRCG0004                        GE3WRONG COMMENT LINE IN -GE               C   600Ssssscommentaire errone
T0FECRCG0004                        GE3WRONG COMMENT LINE IN -GE               C   602s    commentaire errone   bis
T0FECRCG0004                        GE3WRONG COMMENT LINE IN -GE               C   604    scommentaire errone   ter
Column contents:
  • 80: Line type
  • 84-86: Line number
  • 87-115: Description of the C-type line

Generation differences appear.

You must correct in Pacbase. The comment must start in the column 06 of the description field. For information, see chapter Error Messages in the manual Online Systems Development, at the following address:

http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477

GE4: Erroneous call of Text, Segment, or Data Element in the -GE

Example:

In the -GE of a Screen, in a T-type line, the call of a Text code starts in column 01 and the call of a section starts in column 05.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+--
BMSECRBCCBO0                        GE4WRONG CALL OF ENTITY IN -GE             T   357  Mis @ jour en Batch
BMSECRBCCBO0                        GE4WRONG CALL OF ENTITY IN -GE             T   358TEST EN TP
Column contents:
  • 80: Line type
  • 84-86: Line number
  • 87-115: Description of the T, S, or F-type line

Generation differences appear.

You must correct in Pacbase. The Text code must be indicated in columns 6-11 and the section code in columns 12-13 of the description field. For information, see chapter Error Messages in the manual Online Systems Development, at the following address:

http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477

GE5: Erroneous U-type line in the -GE

Example:

In the -GE of a Screen, some U-type lines do not have a correct input format.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+--
T0FECRCG0004                        GE5WRONG U LINE                            U   111UUUU
T0FECRCG0004                        GE5WRONG U LINE                            U   112UUUU
T0FECRCG0004                        GE5WRONG U LINE                            U   202G  A ERREUR-SEGMENT-pr00 affich
T0FECRCG0004                        GE5WRONG U LINE                            U   204F  A ERREUR-SEGMENT-pr10 recept
Column contents:
  • 80: Line type
  • 84-86: Line number
  • 87-115: Description of the U-type line

Generation differences appear.

You must correct in Pacbase and conform to the input format. For information, see chapter Error Messages in the manual Online Systems Development, at the following address:

http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477

MP6: Call of an extraction method in a Macro

Example:

Call of a METH01 extraction method in the -P of Screen AC0010, in subfunction 80CL.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----1----+----2----+----3----
FPJECRAC0010                        MP6EXTRACTION METHOD CALLED IN A MACRO                                80CL000  *C FF30 EX METH01

Errors occur when proxies are generated from a Business Component.

To correct, the administrator must update the Pacbase database with the OUTUP file that is produced by the MIAM migration procedure. The extraction method call lines are then transformed into specific code lines. Upon migration, these specific code lines are automatically transformed into a call to the ££80EX Macro, which is created by the import.

MP7: Call of a user service in a Macro

Example:

Call of a AAPRIN user service in the -P of Screen AC0011, in subfunction 22DM.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----1----+----2----+--
MA4ECRAC0011                        MP7USER SERVICE CALLED IN A MACRO                                22DM000  *C USER AAPRIN

Errors occur when proxies are generated from a Business Component.

To correct, the administrator must update the Pacbase database with the OUTUP file that is produced by the MIAM migration procedure. The user service call lines are then transformed into specific code lines. Upon migration, these specific code lines are automatically transformed into a call to the ££USER Macro, which is created by the import.

SG2: In the -CD, no selection on the first line but selection on a continuation line

Example:

In the -CD of a Program, no selection on the first line but selection on the continuation line.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9-
BMSPGMCG0001                        SG2SEGMENT CONTINUATION WITHOUT SEL ON 1RST       DCAADC
Column contents:
  • 87-92: -CD line identifier

Generation differences appear.

You must correct in Pacbase by indicating the selection on the first line.

SP1: Cross-references of Data Elements that include special characters in their codes

Example:

Call of the GV%RUB Data Element in subfunction 9999, in the -P lines of Screen GVMIAM.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+
CENPGMGVMIAM                        SP1X-REF IN DATA ELEMENTS WITH SPECIAL CHAR9999110                                  AAGV99
Column contents:
  • 80-86: Function, subfunction, and line number
  • 121-126: Macro

Problems can occur upon the migration because special characters are substituted in the instance codes.

To correct, you must replace the special characters in Pacbase.

WK2: Continuation line that starts before margin B in the COBOL code
This error is detected when the COBOL Formatting Option is set to Y in the Library Definition. This option is not recognized upon the generation for Rational Programming Patterns.

Example:

The COBOL Formatting Option field is set to Y in the Library Definition.

In -W, a continuation line starts before margin B.

Message in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----
HFYECRCG0012                        WK2WSS LINE WITH CHARACTERS IN COLUMNS 1-11  AA121                                  
                                                                          'SYSTEMS CORPORATION.  ALL RIG
Column contents:
  • 82-86: Line number in -W
  • 121-150: Description of the work area

The generation for Rational Programming Patterns runs with the value N in the COBOL Formatting Option, so some continuation lines of literals (lines with type - in the -W lines) might be generated before margin B in the COBOL code. It generates an error.

To correct, move the literal to the right so that it is generated at margin B or after. You can move it manually. You can also move it by running the UPDP procedure with the transactions of the UP file as input. This file is generated by MIAM. When it is possible, MIAM creates a UPDP transaction by inserting 4 blanks in front of the literal. When it is not possible, MIAM outputs in DISPLAY the line that must be moved manually.

WKC: Work area line -Wxx999 and presence of a -CD line with the same xx code
The following two cases are possible:
  • The xx code is indicated in the COBOL placement field on a -CD line (example 1),
  • No xx code is indicated in the COBOL placement field, but an xx code is assigned to a Data Structure code in the program in the -CD (example 2).

Example 1: A DX999 work area is created and a D0 Data Structure is called with the DX code in the COBOL placement field.

In the -CD of a Program, call of a D0 Data Structure with the DX code in the COBOL placement field.

In the -W of a Program, creation of a DX999 work area line.

Example 2: A HH999 work area is created and a HH Data Structure is called without any code in the COBOL placement field.

In the -CD of a Program, a HH Data Structure is called without any code in the COBOL placement field.

In the -Wof a Program, creation of a HH999 work area line.

Messages in the RQ file:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8---
HF0PGMCGPRGE                        WKC-WXX999 LINE WITH SAME LOCATION IN -CD  DXD0
BMSPGMCGPRGE                        WKC-WXX999 LINE WITH SAME LOCATION IN -CD  HHHH
Column contents:
  • 80-81: Beginning of the work area line number, which ends with 999.
  • 82-83: Data Structure code in the Program, in the -CD

Errors due to line conflicts occur upon the generation.

You must correct in Pacbase. In the work area line, change the beginning of the line number so that it does not correspond to the COBOL placement code of a -CD line or to the Data Structure code in the Program of a -CD line. You can also change the line number (999 to 998 for example).


Feedback