Some error codes indicate cases that might cause potential differences between the Pacbase generation and the Rational® Programming Patterns generation. If you analyze these codes, you can anticipate problems before migrating.
The following error codes indicate potential generation differences:
Example:
Segment WQ00 is called twice in display with the code A. Segment BM00 is called twice in the repetitive category with the codes T and L.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+-
BMSECRCG0003 EC3MULTIPLE CALL OF SEGMENT IN CATEGORY WQ00
HF0ECRCG0003 EC3MULTIPLE CALL OF SEGMENT IN CATEGORY BM00 R
Errors occur upon the generation.
To correct, you must delete the irrelevant duplicates.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+-
BMSECRBC0000 EC5DOT NOT GENERATED ON THE PREVIOUS LINE 45DE800 AYERRP
Generation differences occur because Pacbase does not generate a period on line 780, contrary to Rational Programming Patterns.
To correct, you can modify the lines in Pacbase, but with caution. The absence of a period might have generated, in Pacbase, nested IF statements that might be relevant.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+-
BMSECRBCTEMA EC6WRONG CONDITION FOR FUNCTION *A *P *R 25DI APR CGPRGM 10*R Z
Generation differences appear.
You must correct in Pacbase, according to the information of chapter Use of Structure Code in the manual Online System Development, at the following address:
http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----
BMSECRBCHF01 EC8INVALID FIRST LINE FOR THE FUNCTION 01BB000
Generation differences appear.
To correct, you must add an operator N, SUP, or COA, depending on the context.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+---
HF0ECRCG000B ECAWRONG CONDITION FOR *B ASDD HF0 CGMACO 25*BZZZZ
Generation differences appear.
You must correct in Pacbase, according to the information of chapter Inserting and replacing automatic subfunctions in the manual Business Logic & TUI Clients, at the following address:
http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1
BMSECRCG9002 ECBP LINE WITH ONLY SPACE AABB111
BMSECRCG9002 ECBP LINE WITH ONLY SPACE AAFB100 CG999A
Generation differences appear, especially in the generation of the period.
To correct, you must remove the line with the spaces in Pacbase.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----
BMSETANPO ET1REPORT WITH DUPLICATE LABEL 15
Warnings appear in .Rational Programming Patterns.
You must correct in Pacbase by removing the label number of one of the duplicate lines.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----
BMSETAMBO ET4NON EXISTING LABEL CALLED IN CATEGORY DD100 08
Generation differences appear.
You must correct in Pacbase by removing the label call on the line.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----
APRETAPBA ET5NON EXISTING STRUCTURE CALLED IN CATEG CB130 03
Generation differences appear.
You must correct in Pacbase by removing the label call on the line.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+----3--
BMSETACG2 ET6STRUCT CALLING DATA ELEM ON SAME POS. 01111 X01 0 CSSSSSSSSSSXXX YYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
HFYETACG2 ET6STRUCT CALLING DATA ELEM ON SAME POS. 01111 X03 0 CSSSSSSSSSSXXX YYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Generation differences appear.
You must correct in Pacbase by removing the duplicates, by keeping the call of the most relevant Data Element, and by taking the functions and conditions into account.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----
HF0ETAANC ET7MISSING LABEL IN SEQUENCE 01
HF0ETAANC ET7MISSING LABEL IN SEQUENCE 02
HF0ETAANC ET7MISSING LABEL IN SEQUENCE 03
HF0ETAANC ET7MISSING LABEL IN SEQUENCE 04
Generation errors occur.
You must correct in Pacbase. Renumber the labels to correct the sequence gap and adapt the labels calls in the categories.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+-
BMSPGMAEBDIN NV1FUNC.LEVEL NOT COMPATIBLE WITH OPERATOR 99RB100 EXQ 10
Generation problems can occur.
To correct, you must change the operator or the level, or both, in Pacbase.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+
APRPGMCGNDVP PG1DUPLICATE P LINE WITH N TYPE 05BB000
APRPGMCGNDVP PG1DUPLICATE P LINE WITH N TYPE 05BB010 CGMAC0
Generation problems can occur.
You must correct in Pacbase. You must change the operator or the level, or both, or remove the duplicate line.
Example:
In this example, the condition levels 10DW and 10EL of functions FF10 and FF14 are not compatible.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8---
HFYECRCG0003 MP4CO DU DW FOLLOWED BY ELSE NOT COMPATIBLEFF14
Generation differences appear.
To correct, you must modify in Pacbase. For example, you can change the 10EL from FF14 into 10IT COND01 NOT = 'A'.
Example 1: Only one -CD line is involved.
This example shows a -CD where the MB Data Structure is called with the Program code DC with a selection *01=00. The MB00 Segment exists, so there will be a conflict with MB01.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+---
BMSPGMCGNDVP SG1SEGMENT RENAME IN -CD OR -W DC00 MB00 MB01
Example 2: Only one -W line is involved.
This example shows a -W where the AC Data Structure is called with the Program code HH with a selection *01=00. The AC00 Segment exists, so there will be a conflict with AC01.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+
HF0PGMCGPRGA SG1SEGMENT RENAME IN -CD OR -W HH00 AC00 AC01 AA110
Example 3: Two -W lines are involved.
This example first shows a -W where a BC Data Structure is called in the XX100 work area with the BC Program code and a selection 10. It then shows the call, in the ZZ100 work area, of the MB Data Structure with the BC Program code, with a selection 1020. The same BC Program code is used to call two different Data Structures that point to the same selection (10).
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----
BMSPGMCGPRGA SG1SEGMENT RENAME IN -CD OR -W BC10 MB10 BC10 ZZ100 XX100
Example 4: A -CD and a -W are involved.
This example first shows a -CD where an MB Data Structure is called with the HH Program code and a selection *20=00. It then shows the call, in the AA110 work area, of the MB Data Structure with the HH Program code, with a selection 01=00. The same HH Program code is used to call two different Data Structures that point to the same selection (00).
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+
HF0PGMCGPRGA SG1SEGMENT RENAME IN -CD OR -W HH00 AC00 AC01 AA110
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9--
T0VPGME23543 SG4NON EXISTING SEGMENT CALL IN -CD OR -W LE10 BC10
Generation differences appear.
To correct, you must indicate an existing Segment code and remove the call.
Example:
In this example, the selection of arguments is missing on the first -CD line for the Segment.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1--
BMSPGMCGPRGN SG5WRONG SELECTION ON SUITE LINE IN -CD D0AA 25*BZZZZ
Generation errors occur.
You must correct in Pacbase, according to the information of subchapter Call of Data Structures in the manual Batch Applications, at the following address:
http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477
Example 1: Database Block
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8--
BMSDBDARHF00 VAKTYPE CODE TO GENERATE NOT DEFINED IN KEY AR
The Database Block is not generated.
To correct, you must indicate a value that is defined in the access key targets.
Example 2: Batch Program
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8--
T0FPGMTRTMSG VAKTYPE CODE TO GENERATE NOT DEFINED IN KEY Q
The Program is not generated.
To correct, you must indicate a value that is defined in the access key targets.
Example:
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----
BMSPGMCGMAQ1 WK1PRESENCE $ IN TABLE AREA OF WSS MACRO AA110 $3CCC
Generation errors occur. The table index is wrong.
You must correct the relevant Macros in Rational Programming Patterns or in the migration inputs.