http://itknowledgeexchange.techtarget.com/itanswers/fixing-the-decimal-data-errors/ Thu, 23 May 2013 18:24:46 +0000 hourly 1 http://itknowledgeexchange.techtarget.com/itanswers/fixing-the-decimal-data-errors/#comment-112705 TomLiotta Wed, 24 Oct 2012 08:26:32 +0000 http://itknowledgeexchange.techtarget.com/itanswers/fixing-the-decimal-data-errors/#comment-112705 There shouldn’t be a need to use it in a new program. The only times it should have been used are for old System/36 files.
 
The OPM RPG IGNDECERR keyword originally helped in converting S/36 RPG II to RPG III, but its use should be long past by now. The FIXNBR update to IGNDECERR was an improvement in that its results were predictable, but it didn’t guarantee a ‘correct’ result. There was no significant use of COBOL on the S/36, so there was no need to handle converted programs.
 
In ILE programming, you should catch the data error and fix the data. Or more correctly, you shouldn’t allow data errors to get that far. The data should be cleaned first. See a related comment from an IBM RPG developer.
 
Tom

]]>