Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Data Interpretation : Data Translation

Data Translation
Types of Data Translated
If data translations are being performed on peer‑to‑peer (remote) communication, the following types of data values are translated:
 
The NLS shareable tool enables a database administrator to set code page values in translation tables. See TIBCO Object Service Broker Shareable Tools for information about using the NLS tool.
Translation of Non-character Data
Non-character values created by tools, utilities, or application code that are stored in character string variables are treated as characters and are subject to translation from one code page to another as required. The results of such translation are defined when the data is considered as characters and are otherwise undefined. In particular, the string results produced by the GENBIN scalar shareable tool are undefined if they undergo code page translation.
Translation of Data in Peer‑to‑Peer Communication
Translations performed on customer data for peer-to-peer communication are faithful. The code point used to represent a character on the first Data Object Broker is translated to the corresponding code point to represent the same character on the second Data Object Broker, if both of the following occur:
Example
Data Object Broker1 uses IBM‑037 (U.S. English) and Data Object Broker2 uses IBM‑280 (Italian). If a string of customer data contains the “a with grave accent” character (à), the representation on Data Object Broker1 (0x44) is translated to 0xC0 when the data is transmitted to Data Object Broker2.
Maintaining a faithful translation ensures that the operation is reversible. Data translated from code page CP1 (IBM‑037) to code page CP2 (IBM‑280) and then back again appears exactly as it did originally.
Translation for Remote Access
For a remote request/response, a translation is performed on a data value if all the following conditions are satisfied:
Mapping of Shaded Entries
The mapping of shaded table entries (control and illegal characters) from one code page to another is implementation dependent and is subject to change.1 However, the translation of a code point from one Latin‑1 EBCDIC code page to another Latin‑1 EBCDIC code page results in the same encoded value. For example, translating 0xFF from IBM‑037 EBCDIC to IBM‑500 EBCDIC results in the value 0xFF.
Binary Values
The specification of binary values corresponding to shaded table entries in character fields is also implementation dependent. The translation of such a binary value from one Latin‑1 EBCDIC code page to another Latin‑1 EBCDIC code page results in the same encoded value. However, the mapping between a Latin‑1 EBCDIC code page and the ISO8859‑1 code page, or the reverse mapping from the ISO8859‑1 code page to the Latin‑1 EBCDIC code page is undefined. This could, for example, invalidate ASCII printer control strings (for example, LaserJet PCL sequences) stored in TIBCO Object Service Broker.

1
Refer to the code page IBM037, illustrated in Character Support, for an example of shaded entries.


Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved