| Target | Conversion |
| c | Content is handled in the same way as a source field of type c |
| d | Content is handled in the same way as a source field of type c |
| f | Content is handled in the same way as a source field of type c |
| i, b, s | Content is handled in the same way as a source field of type c. |
| n | The characters from the target field are positioned right- aligned in the target field. Trailing blanks are copied. If the target field is longer than the characters transferred, the field is filled with "0" characters from the left. If the target field is shorter, the characters are cut off from the left. |
| p | Content is handled in the same way as a source field of type c. |
| string | type c. |
| t | Content is handled in the same way as source field of type c. |
| x | The content of the source field is first converted to the data type i (see above), and then to the type x. (see conversion table for source field type i, b, or s). |
| xstring | The content of the source field is first converted to the data type i (see above) and then to the type xstring (see conversion table for source field type i, b, or s). |
The conversion rules are designed so that data objects of type n exhibit character-type behavior when assigned to character-type data objects, and numeric behavior when assigned to numeric data objects. Valid data for data objects of type n is in the form of pure character strings. When assigning valid data to numeric data objects, the numeric value of the character string is assigned to the target object. The conversion rules, however, also allow assignment of numeric text fields that contain invalid data. The latter is not recommended.