Troubleshooting
Problem
Resolving The Problem
The older IBM i Access for Windows client incorrectly handled zoned and packed values differently. It handled zoned (numeric) values as described above but if the number was stored as a packed value and the precision was an even number, it would add an extra leading space. This isn't necessary or correct but since the product worked this way for many years, it is not going to be changed. The correction was put into the newer ACS client.
If you would like to get the old behavior where you have an extra space before the sign with packed numbers that have an even precision value, you can modify your select statement to add that space.
For example, I have a table defined with the following DDL:
CREATE TABLE NUMBERS (F1 NUMERIC (10,0), F2 DECIMAL (10,0), F3 DECIMAL (11,0))
The F2 column is a packed (numeric) with an even precision (10). If I download the data in this file to an ASCII Text format using the older Access for Windows client, it will make F1 11 characters wide, and both F2 and F3 12 characters wide. I can modify the equivalent ACS transfer by clicking on the 'Data Options' button and select a single space enclosed in quotes as a column between F1 and F2:

The result will be a text file with the same (incorrect) format as the Access for Windows client creates.
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1021775