Created On: 19 March 2011
Problem:
We have a COBOL attribute as follows:
03 W300-MSG15A
05 FILLER
05 W300-15a-DET
When I propagate W300-15a-DET should it not highlight the fact that it is a lower level of the overall W300-MSG15A? As it doesn't do that I miss the fact that W300-MSG15A is used in a call to an external module.
03 W300-MSG15A
05 FILLER
05 W300-15a-DET
When I propagate W300-15a-DET should it not highlight the fact that it is a lower level of the overall W300-MSG15A? As it doesn't do that I miss the fact that W300-MSG15A is used in a call to an external module.
Resolution:
A COBOL program - PGM1 contains the following structure:
03 W300-MSG15A
05 FILLER
05 W300-15a-DET
PGM1 calls PGM2 in the following way:
CALL PGM2 USING W300-MSG15A.
To retrived the call the second program, the impact analysis has to be performed in two steps:
On step1 "05 W300-15a-DET" is set as a starting point and after the analysis of the step is performed the reference with 03 W300-MSG15A is discovered.
On step2 "03 W300-MSG15A" has to be set as a starting point and then the reference with the second program will be discovered.
A document containing an example is attached to this Knowledge Base article.
03 W300-MSG15A
05 FILLER
05 W300-15a-DET
PGM1 calls PGM2 in the following way:
CALL PGM2 USING W300-MSG15A.
To retrived the call the second program, the impact analysis has to be performed in two steps:
On step1 "05 W300-15a-DET" is set as a starting point and after the analysis of the step is performed the reference with 03 W300-MSG15A is discovered.
On step2 "03 W300-MSG15A" has to be set as a starting point and then the reference with the second program will be discovered.
A document containing an example is attached to this Knowledge Base article.
Incident #2480918
Old KB# 33718
#SupportTip
#ImpactAnalysis
#variablestructure
#EnterpriseAnalyzer