Errors in converting System/370 floating-point and null fields

 

Any conversion errors will cause CPF2958 messages to be issued for up to 10 records with errors. A CPF2959 message will be issued after the copy operation; this message indicates the number of records that caused an error if more than 10 records caused conversion errors.

If there are no floating-point fields in the to-file and *CVTFLOAT is specified, no error messages are issued. However, no floating-point conversion is done. If you have not specified any null-capable fields in the to-file and *NULLFLAGS, no error messages are issued. However, the from-file data is assumed to have no null bytes (or flags). When you use *CVTFLOAT and *NULLFLAGS, the CPYF command expects the from-file data to be defined by the to-file format.

You should use the *CVTFLOAT and *NULLFLAGS values only for files that require conversion of the System/370™ hexadecimal floating-point fields or conversion with null flags. Using these values for other files might cause unpredictable results including possible data corruption and output errors. System/370 floating-point fields must be converted only once. If the fields are converted more than once, multiple conversions occur, and the data will be damaged.

This CPYF function is compatible with the data that is placed on tape by the DB2^® unload function (DSNTIAUL). You must manually create the result tables or files with SQL or DDS on the i5/OS^® operating system before you can run the CPYF function to convert the data. Use the formats produced by the DSNTIAUL function to create the result tables or files.

 

Parent topic:

Converting System/370 floating-point and null fields