On Sun, 6 Jun 2021 20:18:00 +, Farley, Peter x23353 wrote:
>
>> Hmmm. In my desktop Linux, in sed regexen, both BRE and ERE, /./ matches a
>> character. In awk /./ matches an octet. Grrr.
>> And printf field width specifications seem to assume octets, not characters.
>
>Both awk and the
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> Paul Gilmartin
> Sent: Sunday, June 6, 2021 12:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: git clone w/o mainframe internet access
>
>
> Hmmm. In my desktop Linux, in sed regexen, both BRE and ERE, /./
On Sun, 6 Jun 2021 20:04:55 +, Robert Prins wrote:
>In a discussion:
>
>"Currently [...] only supports ELF files for s390, and those usually contain
>ASCII strings(at least those compiled by GCC). To see EBCDIC, you can try
>changing the default string encoding to a EBCDIC one (e.g. codepage
In a discussion:
"Currently [...] only supports ELF files for s390, and those usually contain
ASCII strings(at least those compiled by GCC). To see EBCDIC, you can try
changing the default string encoding to a EBCDIC one (e.g. codepage 37/1140 or
others)."
Is that true?
Robert
--
Robert AH
On Sat, 5 Jun 2021 10:16:26 +0800, David Crayford wrote:
>
>Git on z/OS used to only support IBM-1047 and ISO8859-1. The latest
>release supports many more code pages including UTF-8 but the default
>
z/OS isn't monolithic. ISPF Edit has long well supported UTF-8 within the
limitations of
On Sun, 6 Jun 2021 05:54:17 +, Seymour J Metz wrote:
>Presumably he's saying that nobody in his right mind would simply copy the
>data on the tape to a byte stream, and that the most obvious way to archive
>the tape is to convert it to AWSTAPE format. Once it's in AWSTAPE format, then
"There is another requirement here: to read REAL tape using PC tools.
How to read?
a) dataset by dataset
b) whole tape => AWS tape image"
Radoslaw,
Hercules has a really cool utility called TAPECOPY! It reads a real tape
and copies it to an AWSTAPE format disk file. Of course, being written by
