IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents ]


Limitations in DBCS environments

This section describes limitations that affect DBCS environments found during the use of IBM(R) Tivoli(R) Configuration Manager, Version 4.2.1, GA version, which were not reported in the IBM Tivoli Configuration Manager Release Notes. It also describes limitations found during the use of IBM Tivoli Configuration Manager, Version 4.2.1, previous fix packs.

Defect 50163
The following message:
DISSE0612W Delete not completed. File or path non-existent: 
'c:\temp\dest\data.txt'
In the data moving log, is displayed in English only
Defect 50417
The Cancel Force button and menu option in the Activity Plan Monitor graphical user interface appears in English only and not in Japanese.
Defect 50527
In SuSE Linux(R) 8, the Japanese input method used to enter Japanese characters into several Tivoli Java-based GUIs, is not invoked when Shift + space bar is pressed. This problem occurs on the following GUIs: Activity Plan Monitor, Change Manager, and Software Package Editor.

Workaround: Add the line: export XMODIFIERS="@im=kinput2" to each of the following GUI start scripts:

Defect 50533
IBM Tivoli Configuration Manager 4.2.1 ISMP installation fails when the database is created in Japanese. Configuration Manager generates the error SQL0332N and wrimtest fails (FRWRA0012E: The RDBMS server call has failed.)

Workaround: After the ISMP fails at Step 22 (the registration of the Activity Planner plug-in):

  1. Run wsetlang -o -l ja_JP.
  2. Run odadmin reexec all.
  3. Change the Step 22 status to Available.
  4. Restart the ISMP installation.
Defect 50536
When you run the Data Moving Service from the Tivoli Desktop interface, if you select a file with DBCS characters and click Send and Close, you receive the error: FRWSL0024E: a failure was detected by the oserv, even though the Data Moving Service has run correctly. If you click Send, you do not receive this error.
Defect 50604
Windows(R) platforms: If you create a file using the Software Package Editor for endpoint with a DBCS name that contains the characters 5C in the second byte, when you attempt to import the file to the software package profile, the file name is corrupted and the file cannot be imported.

Workaround: Input the DBCS file name to the Import File Location field manually.

This limitation does not occur with SuSE Intel(R) Tivoli server.

Defect 55236
From the DataMovingRequest.1 profile, select the "Send" function, in the Data Moving Service Send Operation panel there is the Data Origin Type that contains "Source Host" in English while all the other fields are in Japanese.
Defect 55248
The installation performed through ISMP of the Disconnected Speditor of IBM Tivoli Configuration Manager 4.2.1 FP03 is in English only.

[ Top of Page | Previous Page | Next Page | Contents | ]