Kbase P14241: AS/400: Workaround to resolve error 4601
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/25/2005 |
|
Status: Unverified
SYMPTOM(s):
AS/400 data mapping error (invalid field value). (4601)
Used the workaround for the legacy support for the progress unknown value as per solution #
CHANGE:
Workaround applied to for the legacy support for the progress unknown value as described in the solution #
CAUSE:
This error may appear even when the workaround is applied. This is caused when a field is type DATE *ISO, the initial value is ?, and the field is non Null Capable. When a CREATE statement is executed on the table, this error comes.
To solve it, it is necessary to dump all data, delete the table,
create it manually with the fields marked as Null Capable, and then
load the data using the windows client. If UNIX client is used, the DDS in the as/400 needs to be changed to allow null support.
FIX:
dump all the data and delete the table using the Windows DB/400 Data Dictionary.
Using the same utility recreate the table manually with the fields marked as Null Capable, and then load the data.
If UNIX client is used, the DDS of that table in the as/400 needs to be changed to allow null support and recompile it. Then use the HP command for the same library to make the change effective. Re-synchronize the client schema holder.
CAUTION: If the DDS is changed in the as/400 the progress attribute may change to as/400 format. If the original database was DB then this is not a problem. If the original database is a progress and transformed into DB/400 database using Progress/400 then it will be a problem. In this case the original progress database needs to be changed and create a new server schema from the scratch from the progress database.