1390/1399 and 1137 Code Page Support

Code page 1390/1399 Unicode functionality is available only for 3270 and 5250 sessions. Code page 1137 Unicode functionality is available only for 5250 sessions.

The following session option differences must be noted for 1390/1399 and 1137 code page support in a Unicode session:
  • The session option STREOT should not be used for Unicode strings for the following reasons:
    • The session option STREOT specifies that the length of the string is not explicitly given. An EOT character indicates the end of the string. By scanning for the EOT character, the length of the string can be found. This EOT character is stored as a single-byte value. The single-byte EOT character cannot be used for Unicode strings.
      • Scenario: A user sets the EOT character as 'A' whose ASCII value is 0X'41'. If the string buffer that the user passes to the function contains a Unicode character, then the low byte of this Unicode character will be taken as the string delimiter. Therefore, a single-byte EOT character cannot be used as a string delimiter.
    • The EOT character cannot be stored as a Unicode character since the Set Session Parameter function is independent of the PCOMM session and the same setting applies to all the sessions of PCOMM. If the EOT is to be stored as a Unicode character, then SBCS and DBCS implementations will be affected by the way the EOT character is passed. At present, the EOT character is expected to be a single-byte value.
      Note: If you use the session option STREOT, then the results may not be as expected. You can use a single-byte delimiter with the Unicode strings if you are certain that the single-byte delimiter will not be a part of the Unicode values that you are passing in the buffer.
  • The session option ESC is not supported in a Unicode session for the same reason as listed for STREOT.
  • The session option XLATE is not supported in Unicode. Even if this option is set, it will be ignored.
Parent topic: Set Session Parameters (9)