The following information describes the requirements for configuring the TIBCO Object Service Broker environment, the keyboard, and the end user display for the use of NLS.
NLS supports the full set of Latin-1 keyboard characters as described previously. The ability to exploit the keyboard is dependent upon the host operating system’s ability to recognize these characters. The end user must perform the necessary system configuration or setup to support the national keyboard. Guidelines for each host operating system follow.
Under Windows, you can reconfigure your keyboard driver dynamically without exiting a session. In this way you can enter multi-national characters from a single keyboard session.
By default, z/OS display devices attached to conforming display controllers provide identification that defines their supported display code page. NLS uses this code page to configure a suitable mapping between the display code page and the TDS code page. If you are using a 3270 emulator, consult your documentation to determine whether this identification is provided under software control.
If your display device does not provide this support, the TIBCO Object Service Broker initialization assumes that the display code page is the same as the TDS code page. If this is not the case (for example, connecting Swedish EBCDIC devices to a German Data Object Broker), you must provide additional customization. Refer to
Changing the EBCDIC Display Code Page.
Change the text and graphical display client fonts to an ISO8859‑1 font (for example, Courier, Courier New, Fixedsys, Lucida Console, or Modern). The installation default font is Terminal (a DOS font). In addition to choosing an ISO8859‑1 font, consider choosing one that is also fixed‑pitch and TrueType.
Refer to Keyboard Support, specifically the discussion on keyboard support for Windows.