Description
This page provides solution to the warning Cannot resolve Paragraph <Paragraph name> and the same PARAGRAPH is being detected as SECTION
Screenshot showing the warning : Can not resolve Paragraph 'TERMINAR in Analysis log.
Here TERMINAR paragraph is taken as an example.
Screenshot showing Paragraph 'TERMINAR' being detected as Section, instead of Paragraph:
Observed in CAST AIP
Release | Yes/No |
|---|---|
| 8.3.x |  |
| 8.2.x | |
| 8.1.x | |
| 8.0.x | |
| 7.3.x |  x<6 |
| 7.2.x | |
| 7.0.x |  |
Observed on RDBMS
RDBMS | Yes/No |
|---|---|
| Oracle Server | |
| Microsoft SQL Server | |
| CSS3 | |
| CSS2 | |
| CSS1 | |
Step by Step Scenario
- Run Analysis with option "Source Code in Free-Form Format" checked. This option is available in CAST-MS under Analysis tab for Mainframe as shown below:
Action Plan
When there is no space in front of the paragraph, then it complains saying "Cannot resolve paragraph".
The problem is with lexer and it is a bug.
Workaround
- Add space before the paragraph for which warning is coming and is being detected as Section.
Impact on Analysis Results and Dashboard
Impact of warning: Paragraph is detected as Section
Impact of workaround: no warning in the log and paragraph is detected as paragraph
Notes/comments
This issue is fixed in CAST 7.3.6
Ticket # 2279
Related Pages
