On Mon, 25 Jul 2016 16:46:30 -0500, Janet Graff wrote: > >Since WTO is restricted to CP-37 displayable EBCDIC characters this means that >the system console messages, and the job log messages are restricted to >readable EBCDIC characters. That codepage does define accented and >non-English characters so this would mean that some of these products could >issue latin codepage messages that were non-English. > It's worse than that. One may safely use those characters that are called in manuals Alphabetic, Numeric, or Special. They're enumerated. all others are considered Invalid. Alphabetic does *not* include lower case. The motivation: there are some terminals that support those three classes then dedicate other code points, particularly Latin lower case to Katakana, Cyrillic, or ...
To accommodate this, our products which have mixed-case message templates have a switch selecting whether message texts should be translated to upper case for display. >Can anyone confirm that they do that? If configured properly, will >DB2/IMS/CICS issue non-English messages to the console or job logs? > >In the local output files (non-console or job log) for the products do they go >beyond CP-37? Do they have output in non-latin codepages? Might they contain >DBCS? > DFSORT is quite eclectic. It allows specification independently of code page and collating sequence, for example En_GB.UTF-8. I don't know whether it will infer the code page from the UNIX file tag. But the collating sequence for En_US seems badly broken. I need to renew an old PMR concerning that. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
