![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The following restrictions apply to NLS‑enabled TIBCO Object Service Broker:
• NLS does not set the decimal separator. This is done through the DECIMALSEPARATOR session parameter.
•
• Subview (SUB) and calculation (CLC) tables defined on TIBCO Object Service Broker system tables are not supported in peer data requests. Such requests could return invalid data.
• Subview (SUB) and calculation (CLC) tables defined on user-defined tables are supported in peer requests. This implies that character fields can undergo a code page translation.A set of characters defined on a given code page could sort (collate) differently when translated to a second code page. Refer to Collation for more information.Table definitions that include default values for character fields could produce incorrect results if the table definition is transferred between Data Object Brokers with different TDS code page values.To enable interoperability of NLS‑enabled TIBCO Object Service Broker Data Object Brokers, the following naming restrictions apply:
• Standard TIBCO Object Service Broker node name conventions apply, that is, a maximum of 16 alphanumeric characters, case insensitive (that is, A‑Z and 0‑9).
• TIBCO Object Service Broker user IDs and passwords are restricted to the characters a‑z, A‑Z, and 0‑9. Blank (‘ ’) is supported on z/OS platforms. Use of other characters can result in undefined behavior in NLS‑enabled environments.The following exceptions must be considered when implementing NLS in TIBCO Object Service Broker:
• Accented characters are not valid in TIBCO Object Service Broker object, field, and parameter names, except when used as substitution characters for the special characters at sign (@), number sign (#), and dollar sign ($). Refer to Expanded EBCDIC Code Page Substitution Characters for a list of the supported substitution characters.
• The operation of the LOAD and UNLOAD tools (both the interactive and batch versions) is not defined when the TDS code page of the unloaded system’s data does not match that of the system being loaded with the data. This restriction applies whether the TDS code page is implicit (non‑NLS) or explicit (NLS-enabled).
• The use of accented or national characters is not supported in objects that are used to form system-dependent names (such as filenames).To enable interoperability of NLS‑enabled TIBCO Object Service Broker Data Object Brokers, the following naming restrictions apply:
• Standard TIBCO Object Service Broker node name conventions apply, that is, a maximum of 16 alphanumeric characters, case insensitive (that is, A‑Z and 0‑9).
• TIBCO Object Service Broker user IDs and passwords are restricted to the characters a‑z, A‑Z, and 0‑9. Blank (‘ ’) is supported on z/OS platforms. Use of other characters can result in undefined behavior in NLS‑enabled environments.TIBCO Object Service Broker Shareable Tools for information about the LOAD, UNLOAD, and LOWERCASE tools.TIBCO Object Service Broker for z/OS Utilities or TIBCO Object Service Broker for Open Systems Utilities for information about the offline load and unload tools.TIBCO Object Service Broker Parameters for information about the DECIMALSEPARATOR parameter.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |