![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
To allow for the NLS configuration of a TIBCO Object Service Broker node (Data Object Broker), the customer locale and code page information must be specified at system installation. These specifications appear in the @NLS1 TDS table. The two occurrences of this table (SELF and REMOTE) currently define:
• The locale.codepage for user character data stored in user TDS tables in the local Data Object Broker (SELF).
• The locale.codepage to be used for character data in peer-to-peer communication (REMOTE)The database administrator (or another level‑7 user) is responsible for correctly defining the contents of the @NLS1 table for each Data Object Broker in the enterprise.
An incorrect specification can result in unexpected behavior and/or data corruption on one or more Data Object Brokers.
The locale + code page; can be any valid locale.codepage value, for example, SVEN.IBM‑278, ENGL.IBM‑037.The @NLS1 table is bound in session storage. To unbind the table and reset the values, complete the following steps:
− In a z/OS TSO environment, log out and log in again to a TIBCO Object Service Broker session to obtain the unbound version of the table.
− In all other environments, shut down and restart the Execution Environment, and then restart the session to obtain the unbound version of the table.
− In a z/OS TSO environment, log out and log in again to a TIBCO Object Service Broker session to obtain the revised NLS settings. For peer-to-peer connections, you must also shut down and restart the peer servers to obtain the revised NLS settings.
− In all other environments, shut down and restart the Execution Environment, and then restart the session to obtain the revised NLS settings. Peer servers are re-initialized for you when the Execution Environment is restarted.TIBCO Object Service Broker Application Administion for more information about binding and unbinding tables.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |