Risky catches increase production risks
This code insight counts a violation each time in a single cobol source file :- a sorted file (SD) is never sorted : an instruction SD <SORT-FILE>. is found in DATA DIVISION, but not corresponding SORT <SORT-FILE> ....... is found in PROCEDURE DIVISION.
- a file (only FD) declared in data division is never open nor closed in the procedure division
- a file (only FD)declared in data division is open or close more than once, and the number of open is different from the number of closed.
- a file (FD or SD ) is open more than once.
- a file (FD or SD ) is closed more than once.
Why you should care
A file is not used properly or in compliance with its declaration.Business Impacts
[nz_btn text="Production Risk" target="_self" animate="false" animation_type="ghost" color="pink" size="small" shape="rounded" type="normal" hover_normal="opacity" hover_ghost="fill" link="http://casthighlight.wpengine.com/category/product/indicators-methodology/innovation/" icon="icon-office"]CAST recommendations
References
https://www.quantifiedcode.com/knowledge-base/correctness/Inherit%20from%20%60BaseException%60%20for%20all%20custom%20exceptions/72tTnTsJAbout CAST and Highlight’s Code Insights
Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.
For reference only. For the complete details please refer the original article
https://doc.casthighlight.com/alt_curiousfilepb-avoid-suspicious-file-usage-patterns/
https://doc.casthighlight.com/alt_curiousfilepb-avoid-suspicious-file-usage-patterns/
Comments