Learning is never a bad thing, the older you are and more experience one
realizes there are a lot of items in this industry to learn...


On Mon, Dec 9, 2019 at 2:35 AM Vernooij, Kees (ITOP NM) - KLM <
kees.verno...@klm.com> wrote:

> Thanks.
> Again, one is never too old to learn, even at 98.5% of one's mainframe
> career.
>
> Kees.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Seymour J Metz
> Sent: 05 December 2019 19:49
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS
> ...)
>
> The industry has long been afflicted by people slinging around words whose
> meanings they don't know. "Hexadecimal value" is just the tip of the
> iceberg.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> ________________________________________
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf
> of Charles Mills <charl...@mcn.org>
> Sent: Wednesday, December 4, 2019 1:01 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)
>
> "Hexadecimal" might be the most misused word in our industry. "Any
> hexadecimal character" -- umm, can you give me an example of a
> non-hexadecimal character? Is x'C1' a hexadecimal character? Sure looks
> like hex to me.
>
> Hexadecimal is a *method of representation*. If I have a byte that
> contains b'0101 1010' that is kind of a tedious way of writing it. The
> industry formerly used octal and wrote it as 0132 but that is kind of
> tedious and maps poorly to 8-bit (as opposed to 6-bit) characters. x'5A'
> conveys it fairly well. That method of conveyance is called hexadecimal.
> The byte is not hexadecimal: it's the same byte as it was when I wrote it
> as b'0101 1010'.
>
> "Non-printable" (or sometimes non-alphanumeric/national) is the word
> people are looking for. No byte is hexadecimal. All byte values may be
> represented in hexadecimal.
>
> Charles
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Paul Gilmartin
> Sent: Wednesday, December 4, 2019 9:39 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: COPYING PDS TO PDS ...
>
> On Wed, 4 Dec 2019 07:18:11 +0000, Vernooij, Kees (ITOP NM) - KLM wrote:
>
> >Jeez Gil,
> >
> >There is nothing restrictive to 'hexadecimal', only to 'any' or 'some'.
> >Between quotes you can put *any* hex char in a dsname, without quotes you
> can use only the *alphanumeric* hex chars. (And you *can* of course use all
> 256, if you accept JCL errors).
> >
> What meaning does "hexadecimal" add in "any hexadecimal character"  Is it
> any
> different from "any character"?  If not, "hexadecimal" is a noise word.
>
> I'm similarly perplexed by IBM's frequent usage, as in:
>
> https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa200/ENQ_Description.htm
>     ... The name can contain any valid hexadecimal character. ...
>
> I visualize a Venn diagram:
> https://secure-web.cisco.com/1PM-B8kCix2WWZn6q1Vh6voOtKz7viyNw8ESZv-Aq5bojVqDLWvaBjXct5iS4oPcA185iDTfCohjIpNC-fWu8MvNQ0vJb5vItF7ZlPeUEeOIB_Rk1NSMnlSUEcA2ycq7v_x-IB6Ou1uCNNaqzvU_lVHbpYViDMTc7pkBR2V-1ariNB4Q62_cBw66z81wq3M6ETjSNnfRZAbUlNIIg1OgbAvGUWqoQRoVC2oTzmuA-eyYSLt1cxQ-kAgQ9_PqPzxBRQkSnnsVenuXrRUUtLtCiiHJBcoFCfQNaFbnOtqcbQ6Tkes8JvhUlI6P0hwD7aV_YXZjF5S-S5W3uDJ8rdQt87UuMoClaZNHuXjQQtJ1aYAPCa3_4I9TdNxiI-849oi9iSR1kTPUvE4Qh3HbS8welLlsRUUjX6vKhC7yVjGDx8i53KFggUxCu4tLCItjAHHaP/https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FVenn_diagram
> where invalid hexadecimal characters and valid non-hexadecimal characters
> are prohibited.
>
> ----------------------------------------------------------------------
> 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
> ********************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> ********************************************************
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
-- 
Scott Ford
IDMWORKS
z/OS Development

----------------------------------------------------------------------
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