Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML KM-Dim9: Codepage Translations on Heterogeneous ASCII Platforms
KM-Dim9: Codepage Translations on Heterogeneous ASCII Platforms
CMS-XML KM-Dim7: Dimensions not translating codepage correctly on fetch or checkout from OS/390
KM-Dim7: Dimensions not translating codepage correctly on fetch or checkout from OS/390
CMS-XML Dim CM 10.1.3.3: Build z/OS - codepage conversion not done when browsing file in compressed item library
Dim CM 10.1.3.3: Build z/OS - codepage conversion not done when browsing file in compressed item library
HTML Merant PVCS Version Manager Release Notes
PCLI Does Not Create Archives That Have German Characters in the File Name [1031395] On Windows, if a CodePage other than 1252 was used, the German umlaut characters were not displayed correctly. This has been fixed. Note: you can change or query your CodePage from a Command Prompt using the command chcp
CMS-XML Parameter CASE=RAISE does not work for Polish National Characters.
Parameter CASE=RAISE does not work if comparing records with Polish National Characters present. Codepage 870 isused and module COMPAREE has been customized so there is no problem with print. The problem is the same whether UNICODE or EBCDIC is used.
CMS-XML DIM: ZOS Bracket gets converted to quotation mark
Use correct code page for the ASCII to EDCDIC translation. Customer used to use code page 500 before migrating to dimensions 9.12. They took the default codepage with Dimensions 9.12 which is code page 1047.
CMS-XML Support: Understanding Novell Case Sensitivity
during the installation process. Filename Characters Selection of most options is done by choosing the codepage and country code for this server
MS-WORD FI – Fetch (Get) Item
[/[NO]OVERWRITE] [/ CODEPAGE =<code-page>|DEFAULT|SOURCE] [/[NO]TOUCH]
CMS-XML KM-Dim10: Reported Defect DEF106415: Accented Characters are not displayed in Eclipse Rich Plugin for Dimensions 10
What controls the way characters are displayed via the Eclipse plugin? Are there any variables that we can set to force the use of a correct character set or codepage when accessing Dimensions Requests via the Eclipse Rich plugin?
CMS-XML ZMF4ECL: # symbol incorrectly converted in dataset name processing for some CCSIDs
Using ZMF4ECL 7.1.2 the crosshatch/hash/pound/etc. symbol (i.e. '#') is not being handled correctly when used in staging dataset names for some international character sets. It appears that it is always being handled as a x’7B’ character regardless of the codepage /LCLCCSID in use.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs