DECIMAL DIVIDE EXCEPTION IN REPORT

Products

• IDMS
• IDMS - Database
• IDMS - ADS

Issue/Introduction

Question:
My CULPRIT Report sometimes receives the following error message:  C750012 DECIMAL DIVIDE EXCEPTION IN REPORT
What is the cause and why is it only sometimes that it receives this error message?

Environment:
z/OS 

Answer:
This is a divide by zero abend. Review the 8 logic that was being executed in the CULPRIT program to see if there is
a zero being passed to a variable field that is used in a divide computation.

For example: 
 018 COMPUTE GROSS-PREMIUM / ACTUAL-CLAIM X 100 * GROSS-MANUAL

In this case the ACTUAL-CLAIM value was zero.  The resolution here is to find out why ACTUAL-CLAIM became zero.
The divide by zero abend is a data exception that occurred in the output phase. By default in the profile, Culprit
will tolerate 0 of these errors before it abends the job. This functionality and the action abend with dump is
controlled by PROFILE options OE=,EE=,OE=,EE=,IE=,SE=,ME=,EE=,IE=,PE=, each one for a different step. 

The error-action indicates the action to be taken in the event that one of the error thresholds described above is exceeded.
Expansion of Error-action:
IGNORE
STOP
ABEND

Additional Information:
CA CULPRIT Reference Guide, PROFILE PARAMETERS
https://support.ca.com/cadocs/0/CA%20IDMS%2018%205%20User%20Bookshelf-ENU/Bookshelf_Files/HTML/IDMS_Culprit_Ref_ENU/index.htm

 

Environment

Release:
Component: CULP