Double-Byte Character Set Support › Data Manipulation

Data Manipulation

The following rules apply when one Type X field is moved to another under normal PDL processing (with non-DBCS data):

• When the fields are the same length, the data is moved with no inspection of the data values.
• When the sending field is shorter than the receiving field, the sending field is left justified in the receiving field and padded with spaces on the right.
• If the sending field is longer than the receiving field, the sending field is truncated on the right.

The normal PDL rules for comparing Type X fields also applies to Type X fields that contain DBCS data without regard for the value of the SET COMPILE DBCS command.

The manipulation of DBCS data, however, requires an added level of sensitivity. To truncate DBCS data without removing necessary S/D and S/S characters and without leaving half of a double-byte character, you can use a new option during a compile that makes CA Ideal sensitive to DBCS data. The option for a session is:

                 {YES|Y}
SET COMPILE DBCS {NO |N}

The option for a site is:

                    {YES|Y}
SET SITE COMPILE DBCS {NO |N}

When you specify YES, the data contents are examined to determine if a S/S character was removed; leaving an unmatched S/D character. If this occurs, further truncation is performed to add the S/S character to the end of the field. CA Ideal also keeps an even number of bytes between the S/D and S/S characters (this ensures that only complete DBCS characters are removed).

When you specify NO, Type X data fields are moved under the normal PDL rules without regard for S/D, S/S, or DBCS characters.