EVALUATE instructions without default treatment causes Production Risk

Software ResiliencyProgramming Best Practices

EVALUATE instructions without default treatment causes Production Risk

This code insight counts one violation each time the statement WHEN OTHER is missing for an EVALUATE instruction.
5362

Why you should care

Each EVALUATE structure should have a WHEN OTHER statement to provide a default treatment in case the program has an unexpected behaviour.

Nested EVALAUTE instructions should have their own default treatment.

Business Impacts

Production Risk

CAST recommendations

References

5362

About 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.

See featuresHow it works