On 13 September 2016 at 19:09, zMan <[email protected]> wrote: > This is probably a dumb question, but that's never stopped me before:
:-) > If my name were "*Étienne*", would I be able to have that as a TSO userid? No. > Or would I have to suffer through just "*Etienne*", sans accent aigu? Yes. Or of course some other id entirely, since there is nothing in place to reliably translate Étienne into Etienne if you are sending userids between other systems (e.g. Windows) that do support "fancier" characters, and z/OS. > Does the MVS side of z/OS "do" code pages in any meaningful way? I don't > mean in DB2 or some other application. I think I read that WTO really only > does code page 037, which suggests that the answer is "no". No, not really. RACF, in particular, effectively supports a small subset of CP 037 only. There are specific and quite restrictive rules for what byte values are allowed in userids, passwords, and password phrases. (I say byte values rather then characters, because RACF specifies the allowed characters this way, rather than in terms of e.g. Unicode u+nnnn or IBM GCGIDs.) There are also implicit restrictions on other fields such as the user name. While an authorized application program may well be able to write unsupported byte values into the database, there is no real support in the RACF commands for them, and results may get strange if you write an app that does this. > Any pointers to doc welcome; of course "z/os" and "code page" (or > "codepage") gets a zillion hits, too many to be particularly useful. The doc updates for RACF APAR OA43999 (in the z/OS 2.2 base doc) do contain the allowable characters in passwords, and their hex values. But I don't think there is really much, since z/OS, as you say, doesn't really support code pages. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
