Re: Hex (was: Stupid JCL question)

[Paul Gilmartin]

On Sun, 24 Dec 2023 14:18:34 -0600, Michael Oujesky wrote:

>Just as an aside, the default EBCDIC to ASCIIi translation table in
>FTP has issues with some special characters.  We used CONVXLAT
>against TCPIP.SEZATCPX(EUS) to create one that works for the texts we
>have,  Then in the FTP control statements, used LOCSITE SBDataconn=
>to specify use of the created translation table for the transfer.
> 
Could that not have been done simply by supplying the correct:
(file_system_codepage,network_transfer_codepage)
in the SBDATACONN command:

with no need to "creat a translation table"?

The proper code pages according to:

appear to be "EUS   United States with Euro support 858<->1140"

-- 
gil

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

Re: Hex (was: Stupid JCL question)

[Michael Oujesky]

At 03:21 PM 12/24/2023, Paul Gilmartin wrote:


On Sun, 24 Dec 2023 14:18:34 -0600, Michael Oujesky wrote:

>Just as an aside, the default EBCDIC to ASCIIi translation table in
>FTP has issues with some special characters.  We used CONVXLAT
>against TCPIP.SEZATCPX(EUS) to create one that works for the texts we
>have,  Then in the FTP control statements, used LOCSITE SBDataconn=
>to specify use of the created translation table for the transfer.
>


Nope, kept it in it's own dataset.


Did you need to create your own table?  Did you need to add it to LNKLST?


Nope, just used EUS from the standard TCPIP library without any 
tweaks.  Just pointed to it's own sequential file, but would probably 
install it via a USERMOD if were going to make it the default text 
translation table.



Do you have unusual code pages?


Nope, just using the original system default.


More easily, I have used SBDATACONN(IBM-1047,ISO8859-1)


More absurdly, in 

When accessing z/OS UNIX files, you must specify the OEMVS311 
translation table ...

"must"?  IOW, IBM's default doesn't work.

--
gil

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


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

Re: Hex (was: Stupid JCL question)

[Paul Gilmartin]

On Sun, 24 Dec 2023 14:18:34 -0600, Michael Oujesky wrote:

>Just as an aside, the default EBCDIC to ASCIIi translation table in
>FTP has issues with some special characters.  We used CONVXLAT
>against TCPIP.SEZATCPX(EUS) to create one that works for the texts we
>have,  Then in the FTP control statements, used LOCSITE SBDataconn=
>to specify use of the created translation table for the transfer.
>
Did you need to create your own table?  Did you need to add it to LNKLST?
Do you have unusual code pages?
More easily, I have used SBDATACONN(IBM-1047,ISO8859-1)


More absurdly, in 

When accessing z/OS UNIX files, you must specify the OEMVS311 translation 
table ...
"must"?  IOW, IBM's default doesn't work.

-- 
gil

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

Re: Hex (was: Stupid JCL question)

[Michael Oujesky]

Just as an aside, the default EBCDIC to ASCIIi translation table in 
FTP has issues with some special characters.  We used CONVXLAT 
against TCPIP.SEZATCPX(EUS) to create one that works for the texts we 
have,  Then in the FTP control statements, used LOCSITE SBDataconn= 
to specify use of the created translation table for the transfer.


Michael

At 03:42 PM 12/22/2023, Paul Gilmartin wrote:


On Fri, 22 Dec 2023 16:23:31 -0500, Bob Bridges wrote:

>Just to be pedantic, aren't ~all~ characters hex characters?
>
I think the only hex characters are 0-9 and A-F.

> ... That is, they can be expressed in hex.  I suppose (but I'm 
not sure) that "non-hex character" is intended to mean a character 
that can be expressed directly, eg a space can be expressed as 
'40'x or as ' '.  Whereas a tab character in EBCDIC needs to show 
up as '05'x; there's no way to insert it into my data with the  character.

>
It's easy if you use the right editor.

--
gil

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


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

Re: Hex (was: Stupid JCL question)

[Michael Oujesky]

Why am I reminded of the Karate Kid?

Hex-on, hex-off?



At 03:42 PM 12/22/2023, Paul Gilmartin wrote:


On Fri, 22 Dec 2023 16:23:31 -0500, Bob Bridges wrote:

>Just to be pedantic, aren't ~all~ characters hex characters?
>
I think the only hex characters are 0-9 and A-F.

> ... That is, they can be expressed in hex.  I suppose (but I'm 
not sure) that "non-hex character" is intended to mean a character 
that can be expressed directly, eg a space can be expressed as 
'40'x or as ' '.  Whereas a tab character in EBCDIC needs to show 
up as '05'x; there's no way to insert it into my data with the  character.

>
It's easy if you use the right editor.

--
gil

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


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

Hex (was: Stupid JCL question)

[Paul Gilmartin]

On Fri, 22 Dec 2023 16:23:31 -0500, Bob Bridges wrote:

>Just to be pedantic, aren't ~all~ characters hex characters? 
>
I think the only hex characters are 0-9 and A-F.

> ... That is, they can be expressed in hex.  I suppose (but I'm not sure) that 
> "non-hex character" is intended to mean a character that can be expressed 
> directly, eg a space can be expressed as '40'x or as ' '.  Whereas a tab 
> character in EBCDIC needs to show up as '05'x; there's no way to insert it 
> into my data with the  character.
>
It's easy if you use the right editor.

-- 
gil

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