These rules apply:

• If half of a DBCS character is in the shift, it is excluded from the operation; the shift count is changed automatically.
• If a column shift causes a DBCS string and an EBCDIC string to be connected, a shift-out or shift-in character, as appropriate, is inserted between the strings. The shift count is changed automatically.
• If left, right, or both boundaries are set, a DBCS character can cross the boundary. The DBCS character that crosses the boundary is excluded from the operation, and the shift count is changed automatically.
• If a request to shift an odd number of columns causes an odd-length DBCS string, the requested shift number is discarded. The shift is processed up to the next field boundary within the boundary, if any. If no field boundary is found, the line number is replaced with this intensified warning message: ==ERR>. Also, the short message for an incomplete data shifting error is displayed.

If you are using the column shifting or data shifting line command while editing a formatted data set, note these points:

• The current boundaries are automatically changed during command processing, and are reset to the original values after processing is complete. Changes are as follows:
  • If the left boundary falls on the second byte of a DBCS character in a DBCS field, the boundary is shifted to the left by 1 byte.
  • If the right boundary does not fall on the same field as the left boundary, it is set to point to the last byte of the field that contains the left boundary. If it falls on the same DBCS field as the left boundary, and it also falls on the first byte of a DBCS character, the right boundary is shifted to the right by 1 byte.
• If you use the data shift or column shift line command to shift a DBCS field and you specify an odd-length shift amount, the shift amount is decreased by one to preserve DBCS data integrity.

• If a shift cannot be completed, it is partially done and the line number is replaced by this intensified warning message: ==ERR>. Remove the message by issuing the RESET primary command, or type over the message or data on that line.
• If a request to shift an odd number of bytes causes an odd-length DBCS string, the shift volume is decreased by one and the operation is performed. The line number is replaced with this intensified warning message: ==ERR>.