The documentation for CHANGE’s ROUND_UP parameter states, among other things, that
If the intermediate work fields involved do not have at least one more decimal position than the field nominated in the FIELD parameter, then the ROUND_UP parameter will be ignored and treated as if ROUND_UP(*NO) was specified.
I have difficulty finding documentation on how intermediate work fields are created, if no PRECISION parameter is given, but there are a few implied hints in the documentation for PRECISION.
So, in my concrete example, I have one 9,0 number divided by a 10,0 number. The documentation implies the intermediate work fields will be 10,0. My result field is a 3,0 number.
The actual numbers are 122,682,586 and 1,000,000, respectively. I really would like to get 123 as the result in this particular case.
Just doing a
Change Field(#RESULT) To('#BIG / #SMALL')
gives me 122. Doing
Change Field(#RESULT) To('#BIG / #SMALL') Round_Up(*YES)
gives me 123. Great, but not something that ought to have worked. Doing the right thing,
Change Field(#RESULT) To('#BIG / #SMALL') Precision(11 1) Round_Up(*YES)
also gives me 123. And, though the parameter is called ROUND_UP, it actually does the “half adjust” which I found a description of that seems like it would do the right thing.
Note: Embarrassingly, I was under the impression that the length of a numeric field was the number of digits before the decimal. It was just recently I found out it was the length including the decimals.