IBM WorkSpace On-Demand 2.0 Multi-Language Support - DBCS Welcome to the IBM WorkSpace On-Demand 2.0 Feature for Multi-Language Support readme (DBCS language version). This readme explains how to enable the DBCS version of WorkSpace On-Demand 2.0 clients that are managed from an English OS/2 Warp Server for e-business. You will also find detailed information about IBM WorkSpace On-Demand 2.0 at the following web site: http://www.software.ibm.com/enetwork/workspace/support CONTENTS ________ 1.0 ENGLISH WARP SERVER for e-business OVERVIEW 1.1 English Warp Server for e-business 1.2 Installing CID Middleware 1.3 Updating the Operating System Level -- FixPaks 2.0 WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT ENVIRONMENT 3.0 WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT PREREQUISITES - DBCS 4.0 ENABLING WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT 4.1 DBCS NLV and English Clients 4.2 Setup and Configuration 4.3 Server Administration Restrictions and Workarounds 5.0 WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT RESTRICTIONS 5.1 Software Stack Restrictions and Limitations 5.2 Warp Server for e-business File Server 5.3 English Warp Server for e-business 5.4 WorkSpace On-Demand Restrictions and Limitations 5.4.1 English WorkSpace On-Demand Restrictions and Limitations 5.4.2 WorkSpace On-Demand 2.0 Feature for Windows Clients Support 5.5 LAN and File System Name Space Restrictions 5.6 Code Page Restrictions and Limitations 5.7 LAN Administration 5.8 Warp Server as a Print Server 6.0 TRADEMARKS ----------------------------------------------------------------------------------- 1.0 ENGLISH WARP SERVER for e-business OVERVIEW ________________________________________________ 1.1 English Warp Server for e-business ------------------------------------------ Warp Server for e-business primary domain controllers, boot (RIPL) servers, file servers, and application servers support English and a single national language version(NLV). Multiple NLVs are not supported on these servers. The supported NLV can be one of the following: * Simplified Chinese * Traditional Chinese * Korean * Thai * Arabic * Czech * Greek * Spanish * Swedish * Turkish 1.2 Installing CID Middleware --------------------------------- You can install CID middleware (English version) on an English server 1.3 Updating the Operating System Level -- FixPaks ------------------------------------------------------- You can install new FixPaks if your configuration conforms to the restriction described in section 1.1. For example, you can run both English and Chinese FixPaks on the same system because: * FixPak installations check the system level and the NLV level * Fixtool searches and applies fixes under the appropriate system level 2.0 WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT ENVIRONMENT ___________________________________________________________________ The following code pages and NLV combinations are supported combinations if two or less NLVs exist on a single server (English and Simplified Chinese; English and Korean, etc.): * English, code page 850/437 * Simplified Chinese, code page 1386/850 * Traditional Chinese, code page 950/850 * Korean, code page 949/850 * Thai, code page 874/850 * Arabic, code page 864/850 * Czech, code page 852/850 * Greek, code page 869/850 * Spanish, code page 850/437 * Swedish, code page 850/437 * Turkish, code page 857/850 3.0 WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT PREREQUISITES - DBCS __________________________________________________________________________ Before you enable WorkSpace On-Demand 2.0 for multi-language support, verify the following: - OS/2 Warp Server for e-business (English version) is installed on the server. - One of the following versions of WorkSpace On-Demand (depending on the language and operating systems--WorkSpace 2.0 or Windows-- you support in your client environment) is available to install on each of your clients: - WorkSpace on Demand Release 2.0 (English) - WorkSpace on Demand Release 2.0 (Desired DBCS NLV) - WorkSpace on Demand Release 2.0 Feature for Windows Clients (see section 5.4.2) - The DBCS fonts (for example, the code page for Traditional Chinese fonts is 950,850) are installed on the server and load each time the server boots. Refer to the instructions in section 4.1 to install the fonts. 4.0 ENABLING WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT ____________________________________________________________ 4.1 DBCS NLV and English Clients ------------------------------------ Use the following instructions to enable the correct language support: 1. Insert the OS/2 Warp Server for e-business CD into the CD-ROM drive. 2. From an OS/2 command prompt, type: install 3. From the OS/2 Warp Server for e-business Setup and Install window, click on the box next to Fonts and then click More... to view the list of available fonts. 4. Select the correct DBCS fonts from the list. 5. Click OK to install the fonts. 4.2 Setup and Configuration ------------------------------ After you install the fonts, manually edit the config.sys file to enable proper loading of the DBCS fonts (for example, for Traditional Chinese/English the code page would be 950,850). 1. Open the config.sys file with an OS/2 editor. 2. Change CODEPAGE= 437,850 to the same setting as the NLV client code-page setting (for example, for Traditional Chinese/English CODEPAGE= 950,850). 3. Save the config.sys file. 4. Reboot the server. 4.3 Server Administration Restrictions and Workarounds ---------------------------------------------------------- The following restrictions are server-based and do not apply to the clients: - Some OS/2 video display drivers are not compatible with DBCS code pages when viewed from the server (for example, Code Page 950 for Traditional Chinese). As a result, the following system error might occur during server boot-up (where nnn represents the DBCS code page): "SYS1729 Error, Code page nnn is not acceptable for the display." To allow the server to continue booting after encountering this message, edit the config.sys file as follows: 1. Open the config.sys file with an OS/2 editor. 2. Add the following statement: pauseonerror=no 3. Save the config.sys file 4. Reboot the server. - As a result of the video display driver/code page compatibility issue, you cannot type DIR to display Traditional Chinese file names, DBCS directories or file names, and users that reside in the server directory. To avoid this problem, change the language preference of the LAN administration icon to 850 (English). - Although you can apply FixPak 11 (for Workspace On-Demand 2.0) to the OS/2 Warp Server, the availability of DBCS FixPaks differs. For example, the Traditional Chinese version of this FixPak 11 is not available at this time. 5.0 WORKSPACE ON-DEMAND 2.0 MULTI-LANGUAGE SUPPORT RESTRICTIONS ________________________________________________________________ This section summarizes the restrictions and limitations for multi-language support for WorkSpace On-Demand 2.0 clients from an English OS/2 Warp Server for e-business. 5.1 Software Stack Restrictions and Limitations ----------------------------------------------------- Do not mix application data in different code pages. This condition could work in one circumstance, but not in another. It is not reliable. 5.2 Warp Server for e-business File Server ----------------------------------------------- DOS and WINOS2 sessions are not supported for Warp Server Clients and for WorkSpace On-Demand 2.0 clients. 5.3 English Warp Server for e-business -------------------------------------------- Following are limitations for Warp Server for e-business with English as the base code page (NLV): - HPFS is required for boot-server and WorkSpace On-Demand file systems - JFS is used only for shared applications, file sharing, user home directories, and domain controller databases - For DBCS/SBCS primary/alternate code page: * LAN name space is limited to the low 128 characters (x21 - x7E) * DBCS clients name space is limited to the low 128 characters (x20 - x7E) 5.4 WorkSpace On-Demand Restrictions and Limitations ----------------------------------------------------------------- Following are limitations for WorkSpace On-Demand 2.0: - HPFS is required for the boot-server and WorkSpace On-Demand file systems - JFS is used only for shared applications, file shareing, user home directories, and domain controller database - You cannot install the client image unattended 5.4.1 English WorkSpace On-Demand Restrictions and Limitations ------------------------------------------------------------------------- - Install WorkSpace On-Demand on an English Warp Server - Install NLV clients unattended only - When administering WorkSpace On-Demand, locally or remotely, do not use DBCS characters: * In the WorkSpace On-Demand name space * With the WorkSpace On-Demand CLI (such as, NET APPARM /ADD /INI....) * In REXX or .BAT or .CMD administration files - Use the WorkSpace On-Demand MKTMPENV method to install NLV public applications 5.4.2 WorkSpace On-Demand 2.0 Feature for Windows Clients Support -------------------------------------------------------------------- WorkSpace On-Demand 2.0 Feature for Windows Clients Support supports Windows NT workstations only. As a result of policy file conflicts, clients are supported in only one language for each server. 5.5 LAN and File System Name Space Restrictions --------------------------------------------------- Server Primary/Alternate Server Primary/Alternate Code Page Code Page DBCS/SBCS SBCS/SBCS DBCS Client SBCS Client SBCS Client LAN* x21 - x7E x21 - x7E No Restriction File System* No Restriciton x20 - x 7E No Restriction Avoid DBCS characters that are not common across code pages: - Cross code page command-line interface is not supported. This includes: * Commands using SBCS outside x20 - x 7E in file names under DBCS code page * Commands using DBCS in file names under SBCS code page * Commands issued though APIs, REXX, .BAT, and .CMD files - Path delimiter will be depicted as \ in English and as national currency symbol on clients for some DBCS languages - Server can be administered from an English server or client as well as a OS/2 Warp 4 client running the primary server code page 5.6 Code Page Restrictions and Limitations ------------------------------------------- - Support is not implied or provided for mixing IBM and Microsoft code pages that are treated as equivalent, such as: * Traditional Chinese * Simplified Chinese - Support is not implied or provided for generic differences between IBM and Microsoft code pages, such as: * User Defined Character (UDS) code ranges * Character extensions 5.7 LAN Administration ----------------------- You must perform local and remote LAN administration in the same language or with the same code page as the server. Do not use DBCS characters in LAN name space. For example, you cannot use the DBCS characters with any of the following: - Path name - Domain name - Computer name - User name - Net name - Alias - Messaging ID - Application ID 5.8 Warp Server as a Print Server ----------------------------------- If printing DBCS characters from clients, use an editor that supports WYSIWYG. 6.0 TRADEMARKS ______________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM OS/2 Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Microsoft, Windows, Windows NT, MS Word, and the Windows logo are registered trademarks of Microsoft Corporation. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (C) Copyright IBM Corporation 1999. All rights reserved.