![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The TIBCO Object Service Broker metadata (the definitions, characteristics, access paths, and storage locations of all TIBCO Object Service Broker data and programs) is represented using the TIBCO Object Service Broker system code page. TIBCO Object Service Broker uses the NLS bit to recognize tables that are exempt from NLS translation, as are the tables of the metadata. The NLS bit is part of the RESERVED field of the TABLES table.If the NLS bit is set for a table in TABLES.RESERVED, the table has its syntax C and V data represented in the system code page, which is always IBM‑037. If the NLS bit is not set, the syntax C and V data of the table is represented in the TDS code page, which is set by the customer or database administrator.
• Support for subview (SUB) and calculation (CLC) tables could be affected – refer to Subview and Calculation Tables for further details.
• The value of the NLS bit does not affect processing on the local node. It is used to decide what translations are necessary in peer-to-peer communication.
• This use of the NLS bit applies to data parameters as well as data fields. Location parameters are always interpreted as being represented in the system code page.The NLS bit is set on all tables (with a few exceptions) that satisfy all three of the following conditions:To turn the NLS bit on, that is, to indicate that NLS translation should not be used for this table, useSETNLSBIT (tablename, 'Y')SETNLSBIT (tablename, 'N')
With the implementation of data translations for peer-to-peer communication, tables that have mixed usage could produce unexpected results in remote requests. Therefore, if you chose a TDS code page that is not the same as the system code page, non‑English characters or special characters contained in the fields or parameters of a table with the NLS bit set could produce results different from what you expect.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |