Table of Contents

Search

  1. Preface
  2. PWX-00000 to PWX-00099
  3. PWX-00100 to PWX-00999
  4. PWX-01000 to PWX-01999
  5. PWX-02000 to PWX-04999
  6. PWX-05000 to PWX-06999
  7. PWX-07000 to PWX-09999
  8. Abend, Return, and Reason Codes in PowerExchange Messages

Message Reference Volume 1

Message Reference Volume 1

PWX- 01591

PWX-
01591

Error
error_reason
at offset
offset
in UTF8 text. Length
text_length
Character length
length
Record type
type
.
The specified field contains invalid UTF8 text. Data maps that contain a VERSION record must have all fields in the UTF8 code page. For example, characters POUND SIGN must be X'C2A3' and YEN SIGN must be X'C2A5'; a failure occurs if the lead byte is not X'C2'.
The error reasons are:
  • 1. Lead byte is greater than X'7F'.
  • 2. Four bytes in character.
  • 3. Unknown character length.
  • 4. Truncated character at end of string.
  • 5. Non-leading byte less than X'80' in multi byte sequence.
The data map is not loaded. Processing ends.
If the problem exists in the exported data maps file used by the PowerExchange Listener, then refresh the data map by sending it from the PowerExchange Navigator.
If the problem exists in the data map (DMP) file used by the PowerExchange Navigator, edit the DMP file by using an external editor.
If a VERSION record is present and the characters are not in UTF8, then it is best to delete the VERSION record, ensure that the characters are in the ISO-8859 code page (on Windows, save as type ANSI), and then edit the map in the PowerExchange Navigator. If that is not successful, correct the invalid characters - either in UTF8 if the VERSION record is present, or in ISO-8859 if the VERSION record is absent.

0 COMMENTS

We’d like to hear from you!