The statement numbers are printed in the associated analysis report. ![]() FLOW activates a trace of the statements being executed. The statement number is then printed in the associated abnormal termination messages. STATE saves the statement number of the statement currently being executed. One method to discover the statement number and the statements that were executed prior to the S0C7 is to include in the PARM statement, the sub-parameter DEBUG (STATE FLOW).If this happened to be a very large program with pages and pages of code you may need to review the following two methods to determine which instruction caused the S0C7. This is a classic formula for an S0C7 data exception. ![]() WS-DATA-EXCEPTION is set to 5 hex '40' blanks and then WS-NUMBER is computed by adding 1. ![]() ![]() WS-DATA-EXCEPTION is a 5-byte alphabetic field that is redefined by the packed numeric field WS-NUMBER. The following program contains a deliberate data exception: 1 PARM LINK(EZTEST10 R) DEBUG (STATE FLOW)ģ NAME-LAST 17 8 A HEADING('LAST' 'NAME')Ĥ NAME-FIRST 25 8 A HEADING('FIRST' 'NAME')ĥ PAY-GROSS 94 4 P 2 HEADING('GROSS' 'PAY')ġ5 TITLE 01 'EZTEST10 - CONTROL BREAK ON DEPT' An S0C7 data exception occurs in CA Easytrieve programs when non-numeric data is placed in a numeric field.
0 Comments
Leave a Reply. |