EAD or NOEAD

DBCS EHLLAPI supports EAD/NOEAD in addition to EAB/NOEAB.

EAD

The presentation space data will be passed with DBCS related extended attributes which use two bytes per character (or per byte in the case of DBCS characters) in read functions. In other words, DBCS 3270 Emulator and DBCS 5250 Emulator have two additional planes and the attributed information in the planes. You can get the attribute information in these planes using the EAD option. See Field and Character Attributes for information on the attributes. In the write function (COPY STRING TO PS), you should pass the presentation space data with the two byte for each display position (although the two bytes are not used).
NOEAD
The two bytes for the DBCS related extended attributes will not be passed in read functions. In the write function, you should pass only the presentation space data (and EAB if the session option is set so).

---

[Back: EAD/NOEAD, SO/NOSO/SPACESO and Affected Functions]
[Next: SO, NOSO or SPACESO]