_:n2e49d88c5ab248fdb630f43f71496fa0xb2
<http://schema.org/text>
"Sorry I missed this when it first appeared. \n \n Go to the File definition for this file. (I am using the Legacy Designer.) \n Using the f(x) button add the IsNumeric function to the file definition, and then add the numeric Pic 9 data-item (named MyItem for this discussion) to the function as its argument. Save changes. \n Select the IsNumeric function item you have just defined and add an 88 condition-item on that, for example named MyItem-is-bad with a value of 0 (zero). (IsNumeric returns 1 if numeric, 0 if not.) Save changes. \n Go to the NullValue field for the MyItem data-item, and select the MyItem-is-bad. Save changes. \n Finally go to the Table definition. Expand to detail mode. Select the column MyColumn, and click the Is Nullable check box. Save changes. \n Now invalid numeric data in that particular COBOL data item will produce a SQL NULL. \n \n Further to Swapnil&#39;s suggestion, if you simply want to throw away the entire row if there is non-numeric data in that item, use the 88 condition-item created above to add a filter to the table definition (AND NOT MyItem-is-bad). \n \n There is also a setting on the data source that can tell the Relativity SQL engine to produce NULL on all invalid numerics that do not appear in record keys. In my opinion it is better to use my first suggestion to address individual issues of non-numeric data, rather than use the data source setting. But if you have a lot of bad data in many fields, then this setting may be useful."
<https://community.microfocus.com/cobol/rmcobol/f/discussions/511148/relativity---error-when-querying-a-table>