W dniu 05.07.2023 o 20:16, Matt Hogstrom pisze:
I recently ran into a question that I didn’t know the answer to.   The question 
was, what code page are dataset names and other z/OS artifacts coded in?  Since 
the special characters like #, $ and @ are different in codepages 1047, versus 
037, etc does z/OS use one code page for these artifacts and translate if a 
data set is created with JCL created with 1047 and is later accessed using an 
037 code page for instance ?

I suspect someone out there has experience and knows the answer.

The devils is in the details.
You mentioned dataset names *and* other z/OS artifacts.
For dataset names and JCL keywords we use very basic subset of character set: A-Z, 0-9, (), /, comma, dot, and some other punctuation characters, and three "national" characters. There is no problem with alphanumeric and punctuations used in JCL and/or DSNs. As Gil wrote, there is no big pain with #,$,@. I use both EN-US and Polish (and sometimes other) codepages - no problems withe the above names.

Now we have "other z/OS artifacts". What artifacts???
Maybe unix file names?
Well, I can create file named *. Yes, it is misleading. And no, don't try to delete it using rm *. :-) However in many places one can put quite weird characters. Some of them can be "codepage-specific". My idea is to *avoid it* as it is very troublesome. However sometimes possible.

And now it's the time for our old, favorite complaints on [] square brackets popular in C code or | pipe characters in REXX and other languages. The last one is translated to ! in Polish CP-870. Did I say it is translated? No, it is *sometimes* translated and sometimes not. Good trap for newcomers. That's why I prefer XMI over plain txt.



--
Radoslaw Skorupka
Lodz, Poland

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to