ist on behalf of
scott Ford
Sent: Wednesday, March 7, 2018 12:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Codepage
All,
This isnt a Java issue see below:
Sample program calling EZACICTR with MODE in Table set to SINGLE...
CBL NOC(E),FLAG(W),DATA(31),NODYN,RES,RENT,OPT,MAP,NOSSR
CBL NO
AM Seymour J Metz wrote:
> GX20-0157-2, GX20-1850-3 and GX20-1850-36 have ~ at A1, with an alternate
> glyph of degree sign.
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> ____
> From: IBM Mainframe Discussion L
PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Codepage
Don't confuse glyphs with code points. ~ is perhaps a delimiter for humans who
are perceiving glyphs visually but not for software that is processing code
points in binary. It would facilitate clearer thinking to say "we
scott Ford wrote:
>We are using EZACICTR..we build a message inside our STC and convert EBCDIC
>data to ASCII data based on a Parm, I.e.; codepage=uk ...uk is in side the
>EZACICTR the entry is selected data converted, then encrypted and a
>socket-write issued to a Java server. Part of our mess
en?
In other words, where in the process does the translation break down?
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of scott Ford
Sent: Tuesday, March 6, 2018 6:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Codepage
We are usi
> which expects the message to be delimited with x'something'."
>
> Charles
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elardus Engelbrecht
> Sent: Tuesday, March 6, 2018 9:46 AM
&
Behalf
Of Elardus Engelbrecht
Sent: Tuesday, March 6, 2018 9:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Codepage
scott Ford wrote:
I see that J R replied to you, but I am still really confused about your post.
Since this is about code page, I am probably on a different [code] page ...
(yes, yes,
: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Codepage
>From an ASCII v EBCDIC standpoint, x'00' is NUL on both sides. Why not use it
>as your end of message delimiter.
Of course, you haven't given the complete picture. What else is in the message
stream? Is it text only?
scott Ford wrote:
I see that J R replied to you, but I am still really confused about your post.
Since this is about code page, I am probably on a different [code] page ...
(yes, yes, that was an intended crruel pun and I will not turn a new page,
mind you... ;-D )
>I need some help on l
>From an ASCII v EBCDIC standpoint, x'00' is NUL on both sides. Why not use it
>as your end of message delimiter.
Of course, you haven't given the complete picture. What else is in the message
stream? Is it text only? Are there any binary fields included? Control
fields? Etc?
> On Ma
On Thu, 28 Jul 2016 10:23:05 +0200, Peter Hunkeler wrote:
>...
>I'm not sure whether the text is inspected by WTO or only later by CONSOLE
>when displaying on consoles. The later would make sense to me. You want to
>avoid that strange things happen when strange data is displayed on terminals
>(c
I had a look at manual z/OS V2.1 MVS Assembler Services Guide. It describes the
characters "... that will be displayed on the console..." in a table. This
tbale contains this table shows a lot of special characters as well as all
upper *and* lower case letters. It also say that characters not in
>>I doubt this is still correct information. After all, even z/OS base
>>components issue WTOs in mixed case. ZFS is one that comes to my mind, and
>>I'm pretty sure there are more but I can't name them without looking up.
>>
>What about WTOR? You mention ZFS (ITYM zFS; they're not the same.)
>
On Tue, 26 Jul 2016 22:04:42 +0200, Peter Hunkeler wrote:
>
>>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.
>
>I doubt thi
>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.
I doubt this is still correct information. After all, even z/OS base comp
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 char
John,
Thanks, I looked up WTO and for the TEXT parameter it says "only standard
printable EBCDIC characters are passed to MCS-managed display devices. "
Not quite at the codepage level but good enough for me.
Janet
>On Mon, Jul 25, 2016 at 3:03 PM, Janet Graff <
>004dc9e91b6d-dmarc-requ...
On Mon, Jul 25, 2016 at 3:03 PM, Janet Graff <
004dc9e91b6d-dmarc-requ...@listserv.ua.edu> wrote:
> I have a theory question rather than a how-to-implement question.
>
> Does anyone know what the codepage restrictions are on the system console?
> Can you have a French console and have messages
18 matches
Mail list logo
