Why is this an issue?
Moving a large number into a small field will result in data truncation. Generally, numeric values are truncated from the left. However, in the
case of floating point values, when the target field has too little precision to hold the value being moved to it, decimals will be truncated (not
rounded!) from the right.
In any case, data loss is always the result when too-large values are moved to too-small fields.
Noncompliant code example
01 NUM-A PIC 9(2)V9.
MOVE 88.89 TO NUM-A *> Noncompliant. Becomes 88.8
MOVE 178.7 TO NUM-A *> Noncompliant. Becomes 78.7
MOVE 999.99 TO NUM-A *> Noncompliant. Truncated on both ends; becomes 99.9
01 NUM-A PIC 9(3)V99.
MOVE 88.89 TO NUM-A
MOVE 178.7 TO NUM-A
MOVE 999.99 TO NUM-A
- S3921 - for truncation of string values