Container pricing

[Laurence Chiu]

Just wondering had anybody had any practical experience with container
pricing especially with dev/test environments and how did that work out for
you?

Just looking to see if there is some local application.

Thanks

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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Kirk Wolf]

Who could have predicted that this thread would attract so much activity on
ibm-main of all places? ;-)

Kirk Wolf
Dovetailed Technologies
http://dovetail.com



>
>

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

Re: Trying to understand IDENTIFY and module re-usage issue

[Charles Mills]

Thanks. I see the following in the Services Guide for search order:

The control program searches:
1. The requesting task's load list for an available copy.
2. The job pack area for an available copy.
3. The requesting task's task library and all the unique task libraries of its 
preceding
tasks. (For the ATTACH or ATTACHX macro, the attached task's library and all the
unique task libraries of its preceding tasks are searched.)
4. The step library; if there is no step library, the job library (if any).
5. The link pack area.
6. The link library.

Is it your impression that TASKLIB comes ahead of existing copies?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Attila Fogarasi
Sent: Thursday, December 5, 2019 12:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Trying to understand IDENTIFY and module re-usage issue

TASKLIB on ATTACH is one reason that pops to mind;  given you dont have
source code, can you do GTF trace to confirm that ATTACH has occurred?
There are probably several similar scenarios possible if not doing
TASKLIB.

On Fri, Dec 6, 2019 at 6:49 AM Charles Mills  wrote:

> Program A issues a successful IDENTIFY for entry point ABC and then
> transfers control to program XYZ. (I have no source code for nor ability to
> fully understand the logic of program XYZ, nor to modify it.) Program XYZ
> subsequently invokes entry point ABC but ends up with a new copy loaded
> from
> STEPLIB rather than using the IDENTIFY entry address.
>
> Why would that be?
>
> The documentation for IDENTIFY states that the entry point is always
> treated
> as RENT. The Services Guide says
>
> All reenterable modules (modules designated as reenterable using the
> linkage
> editor) from any library are completely reusable. Only one copy is normally
> placed
> in the link pack area or brought into your job pack area, and you get
> immediate
> control of the load module. However, there might be circumstances beyond
> your
> control that can cause an additional copy to be placed into your job pack
> area. The
> control program might do this, for example, to preserve system integrity.
>
> Can anyone elaborate?
>
> Charles
>
> --
> 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 IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Trying to understand IDENTIFY and module re-usage issue

[Attila Fogarasi]

TASKLIB on ATTACH is one reason that pops to mind;  given you dont have
source code, can you do GTF trace to confirm that ATTACH has occurred?
There are probably several similar scenarios possible if not doing
TASKLIB.

On Fri, Dec 6, 2019 at 6:49 AM Charles Mills  wrote:

> Program A issues a successful IDENTIFY for entry point ABC and then
> transfers control to program XYZ. (I have no source code for nor ability to
> fully understand the logic of program XYZ, nor to modify it.) Program XYZ
> subsequently invokes entry point ABC but ends up with a new copy loaded
> from
> STEPLIB rather than using the IDENTIFY entry address.
>
> Why would that be?
>
> The documentation for IDENTIFY states that the entry point is always
> treated
> as RENT. The Services Guide says
>
> All reenterable modules (modules designated as reenterable using the
> linkage
> editor) from any library are completely reusable. Only one copy is normally
> placed
> in the link pack area or brought into your job pack area, and you get
> immediate
> control of the load module. However, there might be circumstances beyond
> your
> control that can cause an additional copy to be placed into your job pack
> area. The
> control program might do this, for example, to preserve system integrity.
>
> Can anyone elaborate?
>
> Charles
>
> --
> 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: Syslog Message Normalization

[Matt Hogstrom]

Thanks all, this is helpful.  The second part is to parse the message apart 
into elements for some analysis.  I’ll process through the suggestions.

Matt Hogstrom
m...@hogstrom.org
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook   LinkedIn 
  Twitter 

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom

> On Dec 5, 2019, at 1:15 PM, Leonardo Vaz  wrote:
> 
> If you are writing to OPERLOG I consider using that, for each record, you'll 
> have the type (Single-line message, First line of a multi-line message, Data 
> line of a multi-line message, Data end line of a multi-line message) as 
> well as the multiline ID to guarantee you are not mixing lines.
> 
> IBM has a sample to read the operlog on SAMPLIB(IEAMDBLG)
> 
> Regards,
> Leonardo Vaz
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Vernooij, Kees (ITOP NM) - KLM
> Sent: Thursday, December 05, 2019 3:45 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Syslog Message Normalization
> 
> I think there is a difference in multi-line messages (where each line is 
> identified by an id, '808' in the example below) and long messages that are 
> spread in syslog over more than 1 line. I think your example belongs to the 
> latter.
> 
> MR000 MVSC 19339 09:30:47.49 ACTWRK02   .HASP003 RC=(52),D 
> 808
> DR808   .HASP003 RC=(52),D 
> JOBQ  - NO SELECTABLE ENTRIES FOUND MATCHING   
> ER808   .HASP003   
> SPECIFICATION  
> 
> Kees.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Matt Hogstrom
> Sent: 05 December 2019 02:28
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Syslog Message Normalization
> 
> I’m processing syslog messages and I’d like to combine multi-line messages 
> into a single entry before processing the entries.  For instance, these 
> messages
> 
> N 002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND PROGRAM 
> FOR 02 SECONDS. ===
> N 0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER   
> 00  4  0  0.20  0.000.0   
> S31  JES2 
> 0 0 0 0
> 
> 
> Would become
> 002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND PROGRAM 
> FOR 02 SECONDS. ===
> 0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER   
> 00  4  0  0.20  0.000.031  JES2 0 0   
>   0 0
> 
> Given there are a number of subtle rules I was wondering if anyone had 
> written or was aware of a general purpose normalizer.
> 
> 
> Matt Hogstrom
> m...@hogstrom.org
> +1-919-656-0564
> PGP Key: 0x90ECB270
> Facebook   LinkedIn 
>   Twitter 
> 
> “It may be cognitive, but, it ain’t intuitive."
> — Hogstrom
> 
> 
> --
> 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
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: 

Trying to understand IDENTIFY and module re-usage issue

[Charles Mills]

Program A issues a successful IDENTIFY for entry point ABC and then
transfers control to program XYZ. (I have no source code for nor ability to
fully understand the logic of program XYZ, nor to modify it.) Program XYZ
subsequently invokes entry point ABC but ends up with a new copy loaded from
STEPLIB rather than using the IDENTIFY entry address.

Why would that be?

The documentation for IDENTIFY states that the entry point is always treated
as RENT. The Services Guide says

All reenterable modules (modules designated as reenterable using the linkage
editor) from any library are completely reusable. Only one copy is normally
placed
in the link pack area or brought into your job pack area, and you get
immediate
control of the load module. However, there might be circumstances beyond
your
control that can cause an additional copy to be placed into your job pack
area. The
control program might do this, for example, to preserve system integrity.

Can anyone elaborate?

Charles 

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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Mike Schwab]

Candidate for a Pullet Surprise.
http://english.ohmynews.com/articleview/article_view.asp?menu=c10400=378714_no=1

On Thu, Dec 5, 2019 at 1:38 PM Charles Mills  wrote:

> Mea culpa.
>
> https://en.wikipedia.org/wiki/Muphry%27s_law
>
> Charles
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lennie Dymoke-Bradshaw
> Sent: Thursday, December 5, 2019 10:47 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS
> ...)
>
> Whatever..
>
> But.
> I think the word in the title should be 'hexadecimal' rather than
> 'hexadecimnal' .
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Charles Mills]

Mea culpa. 

https://en.wikipedia.org/wiki/Muphry%27s_law 

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lennie Dymoke-Bradshaw
Sent: Thursday, December 5, 2019 10:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

Whatever..

But.
I think the word in the title should be 'hexadecimal' rather than 
'hexadecimnal' .

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

z/OS ISPF git Interface (zigi) Version 1.3 released

[Lionel B Dyck]

Version 1.3 was just released - get it from
https://github.com/wizardofzos/zigi and some intro here https://zigi.rocks/

 

wizardofzos   released this 15 minutes ago

Lionel has added so many new cool features in zigi it's just not fair to
call it 1.2
Hence, we proudly present: zigi V1R3.

A short summary of what's new in this release.

New Features:

*   Rollback to undo your commits
*   Merging
*   Full Tutorial and Help behind your trusted F1
*   Management of 'non z/OS' files in the repository
*   Git commands straight out of zigi
*   Help when cloning non-zigi managed repositories
*   Option to automatically set default userid when commiting
*   Option to auto push after commit

Bugfixes:

*   Support for "non-standard" env-files
*   Git version checking
*   Solved various edge-cases with 'funky' z/OS dataset- and member
names

Improvements:

*   Better handling of SSH-keys for remote repos (thanks davidegirardi)
*   Grep support for datasets and files
*   Multi-line commit messages
*   Warning in the README (thanks kadima!)
*   Show branch location (local, remote, local/remote)
*   Various performance improvements (string bpxwunix commands, remove
unneeded remote calls)

Planned for the next drop:

 

*   Rename elements (datasets, pds members, omvs files)
*   Remove an element from the repository 

*   Deletes the z/OS dataset, PDS member, OMVS file
*   Fully removes from git management

*   Improved,  more comprehensive ISPF tutorial

 

 

 

 

 

Lionel B. Dyck <
Website:   http://www.lbdsoftware.com

"Worry more about your character than your reputation.  Character is what
you are, reputation merely what others think you are." - John Wooden

 


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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Seymour J Metz]

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  on behalf of 
Charles Mills 
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 +, 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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Lennie Dymoke-Bradshaw]

Whatever..

But.
I think the word in the title should be 'hexadecimal' rather than 
'hexadecimnal' .

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd  
Web:  www.rsmpartners.com
‘Dance like no one is watching. Encrypt like everyone is.’

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: 05 December 2019 18:42
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] Misuse of the word hexadecimnal (Was RE: COPYING PDS TO 
PDS ...)

Or 12. or 9.

Bring back Stretch.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Charles Mills 
Sent: Wednesday, December 4, 2019 4:53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

I pretty much stuck to the term byte for that reason. A byte is eight 1/0 bits. 
A character starts to get off into cultural issues.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Gord Tomlin
Sent: Wednesday, December 4, 2019 11:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

On 2019-12-04 13:52, Tom Marchant wrote:
> The point of using a term like "any hexadecimal character" is to 
> indicate that all 256 possible values in the byte are acceptable.

Even that breaks down if you choose to let wide characters (e.g., UTF-16 or 
UTF-32) into the conversation.

--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: 
https://secure-web.cisco.com/1H6HvE9GVW8CUjGXUxBZBz9a9SP4KAnqHUyKZ8PN8Op7WhWKsa1_qr2Jyl5D_wCXzWFOD-jAHJnosAtPisXXQh5BBogiAki8_SXy5_Q65RhtIVA98W-TZAEGOjLsY9NDOZ573RJdq-XrcLvqihZHRQaryBbAYlecG_3WB27bGV4t9ZcYh6lVq0LUZyPQ0uopoHp17fNVuErKhc5xEdlbo6flitqMndh62o6hc5bmuyULzxyEeRLBoYr7tcnByMaWI7cx7VEccvlcSX5cwR1OM3zYnXa3lUYrOW3D_3O6VAx4cvjMxUOqT8j2TjKQvF-CxO1kXUy9KaDKghiyXKlFKRIxbPus28beK43o15YfJJq3vXNHUiZb8OS3OdNN7jo5E7tw8_TjC4zM_UvV4UnPn8mTuelJHl9Nyo7v-e2FtmV7b3snc2fgT1G-QldcgsTQh/https%3A%2F%2Factionsoftware.com%2Fsupport%2F

--
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 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: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Seymour J Metz]

ObPedant ITYM "raises the question"; begging the question is something quite 
different.

Even on the same physical printer, "printable" depends on such things as UCS 
tables and font definitions. To add to the mess, many PC code pages have 
infected the code points reserved for control characters with other uses.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Charles Mills 
Sent: Wednesday, December 4, 2019 5:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

It's true, "non-printable" begs the question of "what printer?" I have seen 
character sets that included little 2-character "hex" glyphs that could 
therefore "print" or represent any byte value. I work mostly in C++ so I tend 
to think in terms of the C library. The standard C library has a Boolean 
function isprint(). I just looked up the spec for that function and it is so 
self-referential as to be useless: Test for a printable character including 
space, as defined in the print locale source file and in the print class of the 
LC_CTYPE category of the current locale. (i.e., printable means printable). And 
I just looked up the Microsoft definition and it is even more convoluted and 
effectively useless. Still, I think "printable character" is useful: I think 
most people have a good general idea of what it means. But granted it is not so 
precise as, say, alphanumeric.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Wednesday, December 4, 2019 10:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

On Wed, 4 Dec 2019 10:01:36 -0800, Charles Mills wrote:

>"Non-printable" (or sometimes non-alphanumeric/national) is the
>word people are looking for.

I disagree. "non-printable" is a term that has little meaning.
Even if you mean "non-printable using a TN print train", for
example, that is only a subset of the 256 possible values in a
byte.

The point of using a term like "any hexadecimal character" is to
indicate that all 256 possible values in the byte are acceptable.
It could just as well be "a byte with any hexadecimal value", or "a
byte with any binary value".

--
Tom Marchant

--
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 IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Seymour J Metz]

Or 12. or 9.

Bring back Stretch.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Charles Mills 
Sent: Wednesday, December 4, 2019 4:53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

I pretty much stuck to the term byte for that reason. A byte is eight 1/0 bits. 
A character starts to get off into cultural issues.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Gord Tomlin
Sent: Wednesday, December 4, 2019 11:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

On 2019-12-04 13:52, Tom Marchant wrote:
> The point of using a term like "any hexadecimal character" is to
> indicate that all 256 possible values in the byte are acceptable.

Even that breaks down if you choose to let wide characters (e.g., UTF-16
or UTF-32) into the conversation.

--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: 
https://secure-web.cisco.com/1H6HvE9GVW8CUjGXUxBZBz9a9SP4KAnqHUyKZ8PN8Op7WhWKsa1_qr2Jyl5D_wCXzWFOD-jAHJnosAtPisXXQh5BBogiAki8_SXy5_Q65RhtIVA98W-TZAEGOjLsY9NDOZ573RJdq-XrcLvqihZHRQaryBbAYlecG_3WB27bGV4t9ZcYh6lVq0LUZyPQ0uopoHp17fNVuErKhc5xEdlbo6flitqMndh62o6hc5bmuyULzxyEeRLBoYr7tcnByMaWI7cx7VEccvlcSX5cwR1OM3zYnXa3lUYrOW3D_3O6VAx4cvjMxUOqT8j2TjKQvF-CxO1kXUy9KaDKghiyXKlFKRIxbPus28beK43o15YfJJq3vXNHUiZb8OS3OdNN7jo5E7tw8_TjC4zM_UvV4UnPn8mTuelJHl9Nyo7v-e2FtmV7b3snc2fgT1G-QldcgsTQh/https%3A%2F%2Factionsoftware.com%2Fsupport%2F

--
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 IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Seymour J Metz]

Give me ligatures or give me death. Also, does foo match the normalized form of 
foo?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Phil Smith III 
Sent: Wednesday, December 4, 2019 5:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

Not to mention that "character" is fuzzily defined. You might mean:

byte

character

glyph

grapheme

.all of which will vary per code page, encoding, etc



.phsiii (who was trying not to jump in here, but can't stand it)


--
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: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Seymour J Metz]

"Hexadecimal character" is a piece of faux erudition; google for "buzzword 
bingo".


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, December 4, 2019 10:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

Re:
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. ...

On Wed, 4 Dec 2019 14:09:29 -0500, Gord Tomlin wrote:

>On 2019-12-04 13:52, Tom Marchant wrote:
>> The point of using a term like "any hexadecimal character" is to
>> indicate that all 256 possible values in the byte are acceptable.
>
>Even that breaks down if you choose to let wide characters (e.g., UTF-16
>or UTF-32) into the conversation.
>
At various times programmers on various hardware architectures have
used "byte" to mean 6, 7, 8, 9, or 12 bits.  Internet standards (RFC)
have coined the unambiguous term "octet".

ISTR that many releases ago the document cited explicitly forbade
DBCS characters so those would not have been considered "valid
hexadecimal".  I no longer see the restriction; I doubt that it was
ever enforced.

Nowadays it requires that the "assembled length" be from 1 to 256.

The motivation may have been that operator Display commands show
intelligible QNAME and RNAME.  But still, what code page of the console?

-- 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: COPYING PDS TO PDS ...

[Seymour J Metz]

Buzz Word Bingo.

Eschew obfuscation.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Vernooij, Kees (ITOP NM) - KLM 
Sent: Thursday, December 5, 2019 3:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: COPYING PDS TO PDS ...

In my Venn diagram, there are (a.o.) alphanumeric and hexadecimal characters. 
One is a subset of the other, so sometimes you can use only 'some' hexadecimal 
characters, sometimes you can use 'all' hexadecimal characters / 'any' 
hexadecimal character.

Since English is not my native language, my words might not express exactly 
what I mean.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: 04 December 2019 18:39
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: COPYING PDS TO PDS ...

On Wed, 4 Dec 2019 07:18:11 +, 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/10ZJHDJcnI3o0B3GaYKETiuyp9qKbQhV4a1Za1KKe79GpLmHXBK-wq_jRR_Uqbeau6Edb7uJIN3Jn3PO7nz9gYmngFYOd0sR12HE6gpD302wEet-frbleH2jaD0Dk49geMUrvMZHjPaEbTPgDzrNPU8NBUFiMDhY7C0HNSvx0-m4yimRstKA-DZksqLotobTV-snkimLNsldf0GFC569Q2JN3SP50rSwCLedaD7_F4tsRrbhh4W8ZZbEVYLp07NNL0FcHELZsx70eO_4_stkkVo7Ija2SmFZG--RwGJvAdolo0yPBavUo06athbhIVt92J3dBzOjxkmU7qh_tjiYAIqCvfG6nRB5TZjOLsDdxEA99o7a_1JFh_dRBeGc1x_R_1YI52O_zsCOFHWbqmMtPCCNE0p5X301u4wLUHkc6tOE23BGiUGdq_SO_2tk1ONSn/https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FVenn_diagram
where invalid hexadecimal characters and valid non-hexadecimal characters are 
prohibited.

I'm tempted to submit an RCF requesting a clarification.

-- gil

--
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://secure-web.cisco.com/1Xjz4Og05AwqUyXuj0rUfgVn--mjoPaPymqwLR7GUFKAL8esGziwnQ1Gdwa91LRQZannrZ0juj7p5y2ROGoB8-oAdSYkphwuEWx7VzfSQLm_pGw4BQY3NH7FKSEXss5bnAdNttZCrEUcYAPk6OMLuxxRKkAXMAbopzFxvTHM0gV66kjoA2pH9ZgxVMwnr-oUiJv7WAxd4s4X91Bd7fCucEkvE-_mM0H1iJiy-O8LgLWybGags3jyUqFFL_-yf04WcXfB2MUeNL108csdUesvVBaVX38qWlnfRO8mX-QH75L9Mt1knL6-q_Vtnxf3X10KUXQZJuWiUKz9amQHt1JUl2p_wCDfAVhw6yh9U7rYR8-Hry3aHrvP1PIIQTGxc_pQG6DnGhXjhpTxdJJcBUEV2D0kPOtOIB2ILVqv_sDABajYqt9Qw8QqB2vnuDIgsz51W/http%3A%2F%2Fwww.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

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

Re: Syslog Message Normalization

[Leonardo Vaz]

If you are writing to OPERLOG I consider using that, for each record, you'll 
have the type (Single-line message, First line of a multi-line message, Data 
line of a multi-line message, Data end line of a multi-line message) as 
well as the multiline ID to guarantee you are not mixing lines.

IBM has a sample to read the operlog on SAMPLIB(IEAMDBLG)

Regards,
Leonardo Vaz

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vernooij, Kees (ITOP NM) - KLM
Sent: Thursday, December 05, 2019 3:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Syslog Message Normalization

I think there is a difference in multi-line messages (where each line is 
identified by an id, '808' in the example below) and long messages that are 
spread in syslog over more than 1 line. I think your example belongs to the 
latter.

MR000 MVSC 19339 09:30:47.49 ACTWRK02   .HASP003 RC=(52),D 808  
  
DR808   .HASP003 RC=(52),D JOBQ 
 - NO SELECTABLE ENTRIES FOUND MATCHING   
ER808   .HASP003   
SPECIFICATION  

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Matt Hogstrom
Sent: 05 December 2019 02:28
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Syslog Message Normalization

I’m processing syslog messages and I’d like to combine multi-line messages into 
a single entry before processing the entries.  For instance, these messages

N 002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND PROGRAM 
FOR 02 SECONDS. ===
N 0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER   
00  4  0  0.20  0.000.0   
S31  JES2 0 
0 0 0


Would become
002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND PROGRAM FOR 
02 SECONDS. ===
0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER   00  
4  0  0.20  0.000.031  JES2 0 0 0   
  0

Given there are a number of subtle rules I was wondering if anyone had written 
or was aware of a general purpose normalizer.


Matt Hogstrom
m...@hogstrom.org
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook   LinkedIn 
  Twitter 

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom


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

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

Re: GOODBYE

[Jerome Benting]

Have a ripper mate...you deserve it

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, December 5, 2019 4:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GOODBYE

G'Day,
 I am about to retire and become a lazy sod for the rest of my life.  I 
would like to take this opportunity to thank everybody who answered my 
questions and for the invaluable help that was given to me.Looking back over 
the years I am surprised that I survived the cuts and stress of the job.  Every 
year when the budget was being drawn up I hardly slept because I was scared 
that I would be a casualty.  In my Mainframe career I survived 3 brutal cuts 
(jobs transferred to India, Philippines etc. etc) and I was lucky to get 
employment in this firm. A massive thanks to all of you for your support 
especially during the early hours of the morning.
Bye and good luck to all.  A Happy Christmas to those who celebrate it and a 
prosperous 2020 !


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

JMR Software
Waterview Corner, 2 Ernest Oppenheimer Avenue, Johannesburg
2198, Gauteng, ZA
t: +27 (0)11 484 5070
m: +27 (0)73 195 6766
e: jer...@jmr.co.za
www.jmr.co.za [Facebook icon] 
  [LinkedIn icon] 
  [Twitter icon] 

[Banner] 
The content of this email is confidential and intended for the recipient 
specified in message only. It is strictly forbidden to share any part of this 
message with any third party, without a written consent of the sender. If you 
received this message by mistake, please reply to this message and follow with 
its deletion, so that we can ensure such a mistake does not occur in the future.

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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Mike Schwab]

Basically, any printable character is any character with a recognized
value in your selected character set and excludes the control
characters X'00'- X'1F' (in UTF-8, ASCII, and all EBCDIC code pages).
Bell, Carriage Return, Line Feed, Vertical Tab, Page Feed are some
assigned printer control characters that would be included in a
constant or variable for a print statement.

On Wed, Dec 4, 2019 at 4:03 PM Charles Mills  wrote:
>
> It's true, "non-printable" begs the question of "what printer?" I have seen 
> character sets that included little 2-character "hex" glyphs that could 
> therefore "print" or represent any byte value. I work mostly in C++ so I tend 
> to think in terms of the C library. The standard C library has a Boolean 
> function isprint(). I just looked up the spec for that function and it is so 
> self-referential as to be useless: Test for a printable character including 
> space, as defined in the print locale source file and in the print class of 
> the LC_CTYPE category of the current locale. (i.e., printable means 
> printable). And I just looked up the Microsoft definition and it is even more 
> convoluted and effectively useless. Still, I think "printable character" is 
> useful: I think most people have a good general idea of what it means. But 
> granted it is not so precise as, say, alphanumeric.
>
> Charles
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Tom Marchant
> Sent: Wednesday, December 4, 2019 10:52 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)
>
> On Wed, 4 Dec 2019 10:01:36 -0800, Charles Mills wrote:
>
> >"Non-printable" (or sometimes non-alphanumeric/national) is the
> >word people are looking for.
>
> I disagree. "non-printable" is a term that has little meaning.
> Even if you mean "non-printable using a TN print train", for
> example, that is only a subset of the 256 possible values in a
> byte.
>
> The point of using a term like "any hexadecimal character" is to
> indicate that all 256 possible values in the byte are acceptable.
> It could just as well be "a byte with any hexadecimal value", or "a
> byte with any binary value".
>
> --
> Tom Marchant
>
> --
> 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



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: A minimum of 8 GB of real memory is required to IPL

[Steve Partlow]

Correct, this requirement applies only to z/OS v2.3 and above (e.g. also v2.4) 
when running on z14 and later (e.g. also the ZR1 and z15). The only enforcement 
is the new WTOR during IPL:
IAR057D LESS THAN 8 GB OF REAL STORAGE IMPACTS SYSTEM AVAILABILITY - ADD 
STORAGE OR REPLY C TO CONTINUE

So if you are on a z13 there is no requirement or WTOR. Likewise if you are 
running v2.2 on any hardware. For z/OS on zPDT and zVM there is the requirement 
but it's just a smaller amount of 2GB. zPDT isn't actually running on z14 but 
if it emulates one, then z/OS checks for the requirement.

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

Re: A minimum of 8 GB of real memory is required to IPL

[Lennie Dymoke-Bradshaw]

I have successfully IPLed z/OS 2.3 in a 4GB region using zPDT.

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd  
Web:  www.rsmpartners.com
'Dance like no one is watching. Encrypt like everyone is.'

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Richards, Robert B.
Sent: 05 December 2019 14:51
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [IBM-MAIN] A minimum of 8 GB of real memory is required to IPL

  *   For z/OS V2R3 with the IBM z14(tm) (z14) server, a minimum of 8 GB of 
real memory is required to IPL.

Does this statement only apply only to the z14 or all models *after* it?  For 
example, the z14_ZR1 and the z15?

--
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: A minimum of 8 GB of real memory is required to IPL

[Parwez Hamid]

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.e0zm100/BCP_zNext_Memory_Reqs_V2R3.htm


Ensure that enough real memory is installed - 
IBM
Description. For z/OS V2R3 with the IBM z14™ (z14) server, a minimum of 8 GB of 
real memory is required to IPL. When running as a z/VM guest or on an IBM Z® 
Personal Development Tool (zPDT), a minimum of 2 GB is required for z/OS V2R3.
www.ibm.com
Applies to z/OS 2.3 or higher and All z14s/z15s. Doesn't really say what the 
'impact' will be if you don't have 8 GB.

Regards

Parwez Hamid​


From: IBM Mainframe Discussion List  on behalf of 
Richards, Robert B. <01c91f408b9e-dmarc-requ...@listserv.ua.edu>
Sent: 05 December 2019 14:50
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: A minimum of 8 GB of real memory is required to IPL

  *   For z/OS V2R3 with the IBM z14(tm) (z14) server, a minimum of 8 GB of 
real memory is required to IPL.

Does this statement only apply only to the z14 or all models *after* it?  For 
example, the z14_ZR1 and the z15?

--
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: A minimum of 8 GB of real memory is required to IPL

[Mullen, Patrick]

We have z/OS 2.3 lpars running on z14_ZR1 machines without impact to 
availability in as little as 3 GB. We do of course see message:

IAR057D LESS THAN 8 GB OF REAL STORAGE IMPACTS SYSTEM AVAILABILITY - ADD 
STORAGE OR REPLY C TO CONTINUE

Automation replies C. These are not production workload lpars though. We plan 
to install sufficient additional storage when it is time to replace the 14s, or 
if 2.4 (or some maintenance on 2.3) enforces the requirement.



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Allan Staller
Sent: Thursday, December 05, 2019 8:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXT] Re: A minimum of 8 GB of real memory is required to IPL

I believe this is not currently a *requirement*.

My recollection is that a warning message will be issued @IPL, but the IPL will 
continue.
I have not heard of this being enforced at this time.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Richards, Robert B.
Sent: Thursday, December 5, 2019 8:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: A minimum of 8 GB of real memory is required to IPL

  *   For z/OS V2R3 with the IBM z14(tm) (z14) server, a minimum of 8 GB of 
real memory is required to IPL.

Does this statement only apply only to the z14 or all models *after* it?  For 
example, the z14_ZR1 and the z15?

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


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

[Roberto Halais]

Good luck!!!

On Thu, Dec 5, 2019 at 10:03 AM John Dawes <
00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote:

> G'Day,
>  I am about to retire and become a lazy sod for the rest of my life.
> I would like to take this opportunity to thank everybody who answered my
> questions and for the invaluable help that was given to me.Looking back
> over the years I am surprised that I survived the cuts and stress of the
> job.  Every year when the budget was being drawn up I hardly slept because
> I was scared that I would be a casualty.  In my Mainframe career I survived
> 3 brutal cuts (jobs transferred to India, Philippines etc. etc) and I was
> lucky to get employment in this firm.
> A massive thanks to all of you for your support especially during the
> early hours of the morning.
> Bye and good luck to all.  A Happy Christmas to those who celebrate it and
> a prosperous 2020 !
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
-- 
Politics: Poli (many) - tics (blood sucking parasites)

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

RDZ or WDZ 7.6

[Jean-Loup PIETIN]

Hi everibody

I have a problem with a web service CICS that i generate in 2014 with RDZ 7.6.. 
 So a new parameter in input and ouput zone force to recreate the service.

The problem, i cannot recreate my web service with the new RDZ because i have 
an APIG error when i call it... 

And unfortunately the lower version of RDZ that i can download from IBM 
passport Advantage is the version 8.0

I don't know if i can tell you for an image Copy of the version 7.6. If anybody 
got It and can help us ...

Thanks in advance !

Jean-Loup PIETIN

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

Re: GOODBYE

[scott Ford]

John,

Best of luck and enjoy life...

Scott

On Thu, Dec 5, 2019 at 9:55 AM Steve Beaver  wrote:

> Lazy does not apply to any of us.  You'll be kack
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John Dawes
> Sent: Thursday, December 5, 2019 8:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: GOODBYE
>
> G'Day,
>  I am about to retire and become a lazy sod for the rest of my life.
> I would like to take this opportunity to thank everybody who answered my
> questions and for the invaluable help that was given to me.Looking back
> over the years I am surprised that I survived the cuts and stress of the
> job.  Every year when the budget was being drawn up I hardly slept because
> I was scared that I would be a casualty.  In my Mainframe career I survived
> 3 brutal cuts (jobs transferred to India, Philippines etc. etc) and I was
> lucky to get employment in this firm.
> A massive thanks to all of you for your support especially during the
> early hours of the morning.
> Bye and good luck to all.  A Happy Christmas to those who celebrate it and
> a prosperous 2020 !
>
>
> --
> 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
>
-- 
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

Re: A minimum of 8 GB of real memory is required to IPL

[Allan Staller]

I believe this is not currently a *requirement*.

My recollection is that a warning message will be issued @IPL, but the IPL will 
continue.
I have not heard of this being enforced at this time.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Richards, Robert B.
Sent: Thursday, December 5, 2019 8:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: A minimum of 8 GB of real memory is required to IPL

  *   For z/OS V2R3 with the IBM z14(tm) (z14) server, a minimum of 8 GB of 
real memory is required to IPL.

Does this statement only apply only to the z14 or all models *after* it?  For 
example, the z14_ZR1 and the z15?

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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


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

Re: A minimum of 8 GB of real memory is required to IPL

[Vernooij, Kees (ITOP NM) - KLM]

Related question: and does it not apply to a z13?

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: 05 December 2019 15:51
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: A minimum of 8 GB of real memory is required to IPL

  *   For z/OS V2R3 with the IBM z14(tm) (z14) server, a minimum of 8 GB of 
real memory is required to IPL.

Does this statement only apply only to the z14 or all models *after* it?  For 
example, the z14_ZR1 and the z15?

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

Re: GOODBYE

[Steve Beaver]

Lazy does not apply to any of us.  You'll be kack

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of John Dawes
Sent: Thursday, December 5, 2019 8:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GOODBYE

G'Day,
 I am about to retire and become a lazy sod for the rest of my life.  I 
would like to take this opportunity to thank everybody who answered my 
questions and for the invaluable help that was given to me.Looking back over 
the years I am surprised that I survived the cuts and stress of the job.  Every 
year when the budget was being drawn up I hardly slept because I was scared 
that I would be a casualty.  In my Mainframe career I survived 3 brutal cuts 
(jobs transferred to India, Philippines etc. etc) and I was lucky to get 
employment in this firm.  
A massive thanks to all of you for your support especially during the early 
hours of the morning.
Bye and good luck to all.  A Happy Christmas to those who celebrate it and a 
prosperous 2020 !


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

A minimum of 8 GB of real memory is required to IPL

[Richards, Robert B.]

  *   For z/OS V2R3 with the IBM z14(tm) (z14) server, a minimum of 8 GB of 
real memory is required to IPL.

Does this statement only apply only to the z14 or all models *after* it?  For 
example, the z14_ZR1 and the z15?

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

Re: Misuse of the word hexacriminal (Was RE: COPYING PDS TO PDS ...)

[Steve Smith]

Good that someone like it :-).

"Any hexadecimal character" is semantic nonsense (as many have said, one
way or another).  Nevertheless, it's a more-or-less established idiom
meaning "any value"; and we know what they mean.

sas

On Thu, Dec 5, 2019 at 3:39 AM Vernooij, Kees (ITOP NM) - KLM <
kees.verno...@klm.com> wrote:

> Hilarious, this is what I like about this forum.

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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Gord Tomlin]

On 2019-12-04 23:37, Paul Gilmartin wrote:

It was at the beginning of the text you trimmed:

Re:
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. ...

Looks like I need to upgrade my glasses.
--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/

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

Re: GOODBYE

[Allan Staller]

Best of luck in all of your future endeavors!

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
John Dawes
Sent: Thursday, December 5, 2019 8:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GOODBYE

G'Day,
 I am about to retire and become a lazy sod for the rest of my life.  I 
would like to take this opportunity to thank everybody who answered my 
questions and for the invaluable help that was given to me.Looking back over 
the years I am surprised that I survived the cuts and stress of the job.  Every 
year when the budget was being drawn up I hardly slept because I was scared 
that I would be a casualty.  In my Mainframe career I survived 3 brutal cuts 
(jobs transferred to India, Philippines etc. etc) and I was lucky to get 
employment in this firm. A massive thanks to all of you for your support 
especially during the early hours of the morning.
Bye and good luck to all.  A Happy Christmas to those who celebrate it and a 
prosperous 2020 !


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

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


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

GOODBYE

[John Dawes]

G'Day,
     I am about to retire and become a lazy sod for the rest of my life.  I 
would like to take this opportunity to thank everybody who answered my 
questions and for the invaluable help that was given to me.Looking back over 
the years I am surprised that I survived the cuts and stress of the job.  Every 
year when the budget was being drawn up I hardly slept because I was scared 
that I would be a casualty.  In my Mainframe career I survived 3 brutal cuts 
(jobs transferred to India, Philippines etc. etc) and I was lucky to get 
employment in this firm.  
A massive thanks to all of you for your support especially during the early 
hours of the morning.
Bye and good luck to all.  A Happy Christmas to those who celebrate it and a 
prosperous 2020 !


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

Re: Syslog Message Normalization

[Sri h Kolusu]

I’m processing syslog messages and I’d like to combine multi-line messages
into a single entry before processing the entries.

Matt,

DFSORT has the capability of combining multiple lines into a single line
using WHEN=GROUP.   You can easily identify the continuation line as it
will NOT have the Timestamp at position 21 ( assuming your syslog dataset
is FBM 133 LRECL) . You validate that value and push the records and
finally create 1 single line of data. I already have a working example of
combining up to 20 lines into a single record. We can automate this job to
combine up to 999 records also.

If you are interested I can post the solution if you let me know

1. Your Syslog DCB properties (LRECL, RECFM)
2. Maximum number of continuation lines that you want to combine (2 to 999)
3. Do you want the intermittent spaces to be squeezed out and have the data
as a continuous text?

Thanks,
Kolusu
DFSORT Development
IBM Corporation

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

Re: AUTHPGM in IKJTSOxx

[Lennie Dymoke-Bradshaw]

Yes. My mistake. I should have said AUTHTSF.

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd  
Web:  www.rsmpartners.com
‘Dance like no one is watching. Encrypt like everyone is.’

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Walt Farrell
Sent: 04 December 2019 21:38
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] AUTHPGM in IKJTSOxx

On Wed, 4 Dec 2019 01:28:39 +, Lennie Dymoke-Bradshaw 
 wrote:

>Jesse / Skip,
>
>This is actually defined as being a requirement in "DFSMS Access Method 
>Services Commands" SC23-6846-30. See Page 6, or just search for AUTHCMD 
>and you will quickly find it. It states the following,
>
>"To use IDCAMS and some of its parameters from TSO/E, your system programmer 
>must update the system by one of these means:
>. Update the IKJTSOxx member of SYS1.PARMLIB. This is the method that IBM 
>recommends. Add IDCAMS to the list of authorized programs (AUTHPGM). If you 
>want to use SHCDS, SETCACHE, LISTDATA, DEFINE or IMPORT from TSO/E, add them 
>(and abbreviations) to the authorized command list(AUTHCMD).
>. Update the IKJEGSCU CSECT instead of IKJTSOxx, see z/OS TSO/E Customization 
>for more information."
>
>This does not introduce the exposure that placing IDCAMS into AUTHPGM does. 
>Several forms of DEFINE require APF authorisation.

There is no exposure, today, with having IDCAMS in the AUTHPGM list. There was, 
I believe, in the distant past before the AUTHTSF list was created. There would 
be an exposure putting IDCAMS in the AUTHTSF list.

For more: 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ikjb700/ikjb700_Program_Authorization_and_Isolation.htm

--
Walt

--
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: Syslog Message Normalization

[Vernooij, Kees (ITOP NM) - KLM]

I think there is a difference in multi-line messages (where each line is 
identified by an id, '808' in the example below) and long messages that are 
spread in syslog over more than 1 line. I think your example belongs to the 
latter.

MR000 MVSC 19339 09:30:47.49 ACTWRK02   .HASP003 RC=(52),D 808  
  
DR808   .HASP003 RC=(52),D JOBQ 
 - NO SELECTABLE ENTRIES FOUND MATCHING   
ER808   .HASP003   
SPECIFICATION  

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Matt Hogstrom
Sent: 05 December 2019 02:28
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Syslog Message Normalization

I’m processing syslog messages and I’d like to combine multi-line messages into 
a single entry before processing the entries.  For instance, these messages

N 002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND PROGRAM 
FOR 02 SECONDS. ===
N 0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER   
00  4  0  0.20  0.000.0   
S31  JES2 0 
0 0 0


Would become
002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND PROGRAM FOR 
02 SECONDS. ===
0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER   00  
4  0  0.20  0.000.031  JES2 0 0 0   
  0

Given there are a number of subtle rules I was wondering if anyone had written 
or was aware of a general purpose normalizer.


Matt Hogstrom
m...@hogstrom.org
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook   LinkedIn 
  Twitter 

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom


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

Re: Syslog Message Normalization

[Vernooij, Kees (ITOP NM) - KLM]

No, 31 is the continuation of the message text. The id is always 3 digits and 
is more to the left. "808" in the example below.


MR000 MVSC 19339 09:30:47.49 ACTWRK02   .HASP003 RC=(52),D 808  
  
DR808   .HASP003 RC=(52),D JOBQ 
 - NO SELECTABLE ENTRIES FOUND MATCHING   
ER808   .HASP003   
SPECIFICATION  

Met vriendelijke groet,
Kees Vernooij
KLM Information Services
z/OS Systems
Tel +31 6 10 14 58 78


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ITschak Mugzach
Sent: 05 December 2019 05:26
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Syslog Message Normalization

"31" in your sample is the correlation id of the original message. I can't see 
it in the original line in your sample, but it is there. it is not part of the 
message and you have to drop it from the concatenated line.

ITschak

On Thu, Dec 5, 2019 at 3:28 AM Matt Hogstrom  wrote:

> I’m processing syslog messages and I’d like to combine multi-line 
> messages into a single entry before processing the entries.  For 
> instance, these messages
>
> N 002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND
> PROGRAM FOR 02 SECONDS. ===
> N 0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER
>00  4  0  0.20  0.000.0
> S31  JES2
>0 0 0 0
>
>
> Would become
> 002 PROD 19111 16:00:40.08 JOB08657 0090  +=== SUSPEND PROGRAM
> FOR 02 SECONDS. ===
> 0004000 PROD 19111 16:00:40.08 JOB08657 0290  -STIMER
>  00  4  0  0.20  0.000.031  JES2 0
>  0 0 0
>
> Given there are a number of subtle rules I was wondering if anyone had 
> written or was aware of a general purpose normalizer.
>
>
> Matt Hogstrom
> m...@hogstrom.org
> +1-919-656-0564
> PGP Key: 0x90ECB270
> Facebook   LinkedIn < 
> https://linkedin/in/mhogstrom>  Twitter 
>
> “It may be cognitive, but, it ain’t intuitive."
> — Hogstrom
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


--
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for 
Legacy **|  *

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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Vernooij, Kees (ITOP NM) - KLM]

Hilarious, this is what I like about this forum.

Throw any digital bone into the this group of dogs (no offence intended) and 
they will all jump on it, analyze it, cut it into pieces, rephrase it, write 
their solution, convince all others of their personal findings and branch off 
into any possible hexadecimal direction, where the process is iterated.

And it even ain't Friday yet.

Thanks,
Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: 04 December 2019 19:52
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

On Wed, 4 Dec 2019 10:01:36 -0800, Charles Mills wrote:

>"Non-printable" (or sometimes non-alphanumeric/national) is the word 
>people are looking for.

I disagree. "non-printable" is a term that has little meaning. 
Even if you mean "non-printable using a TN print train", for example, that is 
only a subset of the 256 possible values in a byte.

The point of using a term like "any hexadecimal character" is to indicate that 
all 256 possible values in the byte are acceptable. 
It could just as well be "a byte with any hexadecimal value", or "a byte with 
any binary value".

--
Tom Marchant

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

Re: Misuse of the word hexadecimnal (Was RE: COPYING PDS TO PDS ...)

[Vernooij, Kees (ITOP NM) - KLM]

See my answer to Gil about Venn diagrams.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 04 December 2019 19:02
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 +, 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://en.wikipedia.org/wiki/Venn_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 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

Re: COPYING PDS TO PDS ...

[Vernooij, Kees (ITOP NM) - KLM]

In my Venn diagram, there are (a.o.) alphanumeric and hexadecimal characters. 
One is a subset of the other, so sometimes you can use only 'some' hexadecimal 
characters, sometimes you can use 'all' hexadecimal characters / 'any' 
hexadecimal character.

Since English is not my native language, my words might not express exactly 
what I mean.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: 04 December 2019 18:39
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: COPYING PDS TO PDS ...

On Wed, 4 Dec 2019 07:18:11 +, 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://en.wikipedia.org/wiki/Venn_diagram
where invalid hexadecimal characters and valid non-hexadecimal characters are 
prohibited.

I'm tempted to submit an RCF requesting a clarification.

-- gil

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