| Warning |
|---|
This documentation is no longer maintained and may contain obsolete information. You should instead refer to Application onboarding. |
| Panel | |
|---|---|
On this page:
|
...
You will then need to create corresponding Working Folder entries for all the folders you have excluded here (see the section below about doing this).
Configure analysis settings at Analysis Unit level
...
If you have excluded (from an Analysis Unit) folders that ONLY contain copybooks, then CAST highly recommends that you now add Working Folder items to the Analysis Unit that exactly match the folders you have excluded (as explained above).
For example, if in the delivered source code there is a folder called "Copy" that only contains copybooks, and folder called "DB2" that only contains copybooks generated by DB2 to map, in COBOL, the table columns (known as DCLGEN), and these have been excluded from the Analysis Unit, you now need to add two Working Folder items that match the paths of the Copy and DB2 folders:
...
For example, the following log output indicates that all the dynamic calls and the paragraph call paths have been resolved but that the detection of cyclical paragraph calls via the PERFORM instruction was only successful in 80% of the cases. As such, the CyclicCall."String Concatenation" and CyclicCall."Procedure Call Depth" values could be raised slightly.
| No Format |
|---|
COBOL dynamic call resolution and paragraph call graph : - 100% on string concatenation - 100% on procedure call depth Paragraph cyclic calls detection : - 80% on string concatenation - 100% on procedure call depth - 83% on local procedure complexity Uninitialized COBOL variables detection : - 100% on string concatenation - 97% on procedure call depth - 100% on local procedure complexity OPEN in loop detection - 100% on string concatenation - 100% on procedure call dept |
...