Re: Tape compression and modern encryption facilities.

[Timothy Sipples]

Radoslaw Skorupka wrote:
>NO MORE TAPES connected directly to the z/OS. The last physical drive
>TS1140 is out of support.

I don't think IBM ever offered any physical tape drives directly connected to 
z/OS, i.e. physical tape drives with FICON or ESCON ports on them. The IBM 
TS1140 certainly wasn't connected directly. The TS1140 (and its predecessors, 
for decades) required a tape controller of some kind for z/OS machine 
connection. For the TS1140 it was either a 3592-C07 or TS7600 as I recall.

Do you mean something like "non-virtualized physical tape" perhaps?

[What was the most recent IBM physical tape drive with parallel (bus/tag), 
ESCON, or FICON ports on it?]

— — — — —
Timothy Sipples
Senior Architect
Digital Assets, Industry Solutions, and Cybersecurity
IBM zSystems/LinuxONE, Asia-Pacific
sipp...@sg.ibm.com


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

Re: IBM z16 Model A02 Announcement

[kekronbekron]

If you have time, could you give us some examples of the interesting deployment 
options?
Apart from the "embedded" DS8K you've mentioned.

Thank you!

- KB

--- Original Message ---
On Monday, April 17th, 2023 at 10:17 AM, Timothy Sipples  
wrote:


> Enzo D'Amato wrote:
> 
> > I think that it's very good that we now have something like the
> > multiprise 3000 back again.
> 
> 
> Radoslaw Skorupka wrote:
> 
> > IMHO "back again" is not correct
> 
> 
> I assume Enzo's point is that IBM hasn't offered a physical model mainframe 
> in less than a single frame form factor for many, many years. Until now. 
> Prior to the IBM z16 AGZ (and LinuxONE Rockhopper 4 AGL) the physically 
> smallest mainframe required a whole rack footprint, a rack that IBM supplied. 
> Now it doesn't; the physical dimensions are much smaller.
> 
> There was some significant progress in recent years to pave the way for these 
> rack mount models. One big change was between the IBM z13s/LinuxONE 
> Rockhopper I and the IBM z14 ZR1/LinuxONE Rockhopper II. In that model cycle 
> IBM reduced the frame size significantly, converging on the industry standard 
> 19 inch rack size. And those models (and the IBM z15/LinuxONE III LT2) also 
> have some optional internal mounting space for a few use cases. As a notable 
> example, you can equip those models with internal ECKD storage (IBM DS8910F).
> 
> But I agree with Enzo that these new rack mount models available in most 
> countries are attractive. They open up some interesting new deployment 
> options.
> 
> — — — — —
> Timothy Sipples
> Senior Architect
> Digital Assets, Industry Solutions, and Cybersecurity
> IBM zSystems/LinuxONE, Asia-Pacific
> sipp...@sg.ibm.com
> 
> 
> --
> 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: IBM z16 Model A02 Announcement

[Timothy Sipples]

Enzo D'Amato wrote:
>I think that it's very good that we now have something like the
>multiprise 3000 back again.

Radoslaw Skorupka wrote:
>IMHO "back again" is not correct

I assume Enzo's point is that IBM hasn't offered a physical model mainframe in 
less than a single frame form factor for many, many years. Until now. Prior to 
the IBM z16 AGZ (and LinuxONE Rockhopper 4 AGL) the physically smallest 
mainframe required a whole rack footprint, a rack that IBM supplied. Now it 
doesn't; the physical dimensions are much smaller.

There was some significant progress in recent years to pave the way for these 
rack mount models. One big change was between the IBM z13s/LinuxONE Rockhopper 
I and the IBM z14 ZR1/LinuxONE Rockhopper II. In that model cycle IBM reduced 
the frame size significantly, converging on the industry standard 19 inch rack 
size. And those models (and the IBM z15/LinuxONE III LT2) also have some 
optional internal mounting space for a few use cases. As a notable example, you 
can equip those models with internal ECKD storage (IBM DS8910F).

But I agree with Enzo that these new rack mount models available in most 
countries are attractive. They open up some interesting new deployment options.

— — — — —
Timothy Sipples
Senior Architect
Digital Assets, Industry Solutions, and Cybersecurity
IBM zSystems/LinuxONE, Asia-Pacific
sipp...@sg.ibm.com


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

Re: What is "Mapped-I/O-addressing facility" in z16?

[kekronbekron]

If I were to guess, I think this is plumbing related to the new (?) capability 
of PCIe-attached NVMe storage.

Also, what's "CP support of Linux on Z"?

- KB

--- Original Message ---
On Monday, April 17th, 2023 at 12:17 AM, Seymour J Metz  wrote:


> IBM has been using PCI and PCIe internally for some time.
> 
> Memory-mapped I/O is a process whereby an address generated by the CPU os 
> translated to an address in an I/O device connected to the CPU, in this case 
> an I/O device on a PCIe bus.
> 
> Does anybody use that feature other than Linux on Z and CP support of Linux 
> on Z?
> 
> 
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> 
> 
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Farley, Peter [031df298a9da-dmarc-requ...@listserv.ua.edu]
> Sent: Sunday, April 16, 2023 11:42 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: What is "Mapped-I/O-addressing facility" in z16?
> 
> A question out of pure curiosity: In the z16 version of PoOP (SA22-7832-13) 
> there is mention in the "Summary of Changes in Fourteenth Edition" section of 
> this enhancement:
> 
> Mapped-I/O-addressing facility [PCI ONLY]
> 
> I can find no other reference to such a facility anywhere in that document.
> 
> Does anyone know what that item refers to?
> 
> Peter
> 
> 
> 
> This message and any attachments are intended only for the use of the 
> addressee and may contain information that is privileged and confidential. If 
> the reader of the message is not the intended recipient or an authorized 
> representative of the intended recipient, you are hereby notified that any 
> dissemination of this communication is strictly prohibited. If you have 
> received this communication in error, please notify us immediately by e-mail 
> and delete the message and any attachments from your system.
> 
> --
> 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

Auto: Re: zOSMF and zOWE for non-mainframers

[Frederic Mancini]

Je suis absent le 17 avril 2023.

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

Re: zOSMF and zOWE for non-mainframers

[Andrew Rowley]

On 1/03/2023 9:01 am, Andrew Rowley wrote:

The Achilles heel for Java on z/OS seems to be dataset I/O. It's 
adequate, but feels like it should be faster. (I haven't actually done 
direct comparisons with other languages.)


Following up an old post of my own here, because I did actually compare 
the JZOS RecordReader to other languages (C and Assembler).


It turns out I was wrong, and the Java I/O using RecordReader seems to 
be close to the speed of Assembler and C. Certainly not slow as I 
thought. So Java is fast all round.


Incidentally, zEDC compressed datasets give a big boost in I/O speed for 
reading SMF data in my testing, e.g. 2-5x faster. This was tested on 
the  on the Dallas RDP system under VM - I don't know whether VM affects 
I/O performance.


--
Andrew Rowley
Black Hill Software

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

Re: What is "Mapped-I/O-addressing facility" in z16?

[Seymour J Metz]

IBM has been using PCI and PCIe internally for some time. 

Memory-mapped I/O is a process whereby an address generated by the CPU os 
translated to an address in an I/O device connected to the CPU, in this case an 
I/O device on a PCIe bus.

Does anybody use that feature other than Linux on Z and CP support of Linux on 
Z?


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Farley, Peter [031df298a9da-dmarc-requ...@listserv.ua.edu]
Sent: Sunday, April 16, 2023 11:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: What is "Mapped-I/O-addressing facility" in z16?

A question out of pure curiosity: In the z16 version of PoOP (SA22-7832-13) 
there is mention in the "Summary of Changes in Fourteenth Edition" section of 
this enhancement:

Mapped-I/O-addressing facility [PCI ONLY]

I can find no other reference to such a facility anywhere in that document.

Does anyone know what that item refers to?

Peter



This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

--
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: What is "Mapped-I/O-addressing facility" in z16?

[David L. Craig]

On 23Apr16:1717+, David L. Craig wrote:

> On 23Apr16:1542+, Farley, Peter wrote:
> 
> > A question out of pure curiosity: In the z16 version of PoOP (SA22-7832-13) 
> > there is mention in the "Summary of Changes in Fourteenth Edition" section 
> > of this enhancement:
> > 
> > Mapped-I/O-addressing facility [PCI ONLY]
> > 
> > I can find no other reference to such a facility anywhere in that document.
> > 
> > Does anyone know what that item refers to?
> > 
> > Peter
> 
> That technology is an intruder from the x86 line of
> processing.  It it's a legitimate change, there should
> be a whole lot of explanation somewhere.  In the IBM
> deployment, it might reside below the PoPs realm entirely.
> PCI seems to mean the same as in the x86 domain, thus an
> interface type for motherboard extension cards, including
> the PCI/e specification.  Is PCI a PRQ?  Does IBM still
> market facilities for x86 coprocessing within Z boxen?

Sigh... s/It it/If it/ and s/PRQ/RPQ/

Everything you ever wanted to know about PCI and memory
mapped I/O (MMIO) in one post:
https://resources.infosecinstitute.com/topic/system-address-map-initialization-in-x86x64-architecture-part-1-pci-based-systems/
-- 

May the LORD God bless you exceedingly abundantly!

Dave_Craig__
"So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe."
__--from_Nightfall_by_Asimov/Silverberg_

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

Re: What is "Mapped-I/O-addressing facility" in z16?

[David L. Craig]

On 23Apr16:1542+, Farley, Peter wrote:

> A question out of pure curiosity: In the z16 version of PoOP (SA22-7832-13) 
> there is mention in the "Summary of Changes in Fourteenth Edition" section of 
> this enhancement:
> 
> Mapped-I/O-addressing facility [PCI ONLY]
> 
> I can find no other reference to such a facility anywhere in that document.
> 
> Does anyone know what that item refers to?
> 
> Peter

That technology is an intruder from the x86 line of
processing.  It it's a legitimate change, there should
be a whole lot of explanation somewhere.  In the IBM
deployment, it might reside below the PoPs realm entirely.
PCI seems to mean the same as in the x86 domain, thus an
interface type for motherboard extension cards, including
the PCI/e specification.  Is PCI a PRQ?  Does IBM still
market facilities for x86 coprocessing within Z boxen?
-- 

May the LORD God bless you exceedingly abundantly!

Dave_Craig__
"So the universe is not quite as you thought it was.
 You'd better rearrange your beliefs, then.
 Because you certainly can't rearrange the universe."
__--from_Nightfall_by_Asimov/Silverberg_

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

Re: What is "Mapped-I/O-addressing facility" in z16?

[Paul Gilmartin]

On Sun, 16 Apr 2023 15:42:14 +, Farley, Peter wrote:

>A question out of pure curiosity: In the z16 version of PoOP (SA22-7832-13) 
>there is mention in the "Summary of Changes in Fourteenth Edition" section of 
>this enhancement:
>
>Mapped-I/O-addressing facility [PCI ONLY]
>
>I can find no other reference to such a facility anywhere in that document.
>
>Does anyone know what that item refers to?
>
Could it be Single-level store 
?
You can do a lot with 64-bit addressing.

-- 
gil

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

What is "Mapped-I/O-addressing facility" in z16?

[Farley, Peter]

A question out of pure curiosity: In the z16 version of PoOP (SA22-7832-13) 
there is mention in the "Summary of Changes in Fourteenth Edition" section of 
this enhancement:

Mapped-I/O-addressing facility [PCI ONLY]

I can find no other reference to such a facility anywhere in that document.

Does anyone know what that item refers to?

Peter



This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

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

Re: Tape compression and modern encryption facilities.

[Phil Smith III]

John Young wrote, in part:
>Nowadays, we've got pervasive encryption on z/OS. As a result, any

>data that is backed up (for instance, ADRDSSU/FDR), is already

>encrypted.

 

You have data set encryption. "Pervasive encryption" is a strategy, not a
product or feature. And it's not that *any* data is encrypted: you have to
turn it on, and it doesn't work for all data set types, right?

 

I won't go into (again) how little actual protection it provides, though for
the backup case it would presumably apply.if set up right (i.e., if the
backup process is enabled to read the data in its protected state).


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

Re: Tape compression and modern encryption facilities.

[kekronbekron]

Thank you, found it here - 
https://www.ibm.com/docs/en/zos/2.4.0?topic=keywords-compress

Is it just me or does one need to be in 100% concentration just to understand 
what this means.
A simple decision flowchart would have made it a lot easier on the common man's 
brain.

- KB

--- Original Message ---
On Sunday, April 16th, 2023 at 8:20 AM, Michael Oujesky 
 wrote:


> SMS compression is limited to sequential DASD datasets, but some
> utilities (ADRDSSU) uses it internally for tape files. For those
> that do, turning off IRDC save cycles in the tape controller.
> 
> 
> 
> At 09:12 PM 4/15/2023, kekronbekron wrote:
> 
> > And an add-on question if I may - zEDC or z15+ on-chip
> > compression... does this apply only to data heading to disk, or does
> > it apply for data heading to tape too.
> > If it applies for data heading to tape also, does that mean there
> > are 2 levels of compression now - CP's on-chip compression + zstd on
> > the TS7700?
> > 
> > - KB
> > 
> > --- Original Message ---
> > On Sunday, April 16th, 2023 at 7:17 AM, John Young
> > john.b.yo...@cox.net wrote:
> > 
> > > Although my post today is probably rhetorical question, I wanted
> > > to find out whether this matters anymore or not.
> > > 
> > > Back in the late 2000's, IBM developed encryption facilities
> > > within the tape drives, as this is also where compression was being
> > > performed. The idea was that compression of data must occur before
> > > encryption, as encrypted data does not compress well, and obviates
> > > the use of compression.
> > > 
> > > Nowadays, we've got pervasive encryption on z/OS. As a result,
> > > any data that is backed up (for instance, ADRDSSU/FDR), is already 
> > > encrypted.
> > > 
> > > Also, we now have zEDC, to compress data prior to storage,
> > > typically on disk.
> > > 
> > > To my question: With all the encryption and compression being
> > > performed on disk, to what degree does TAPE COMPRESSION matter anymore?
> > > 
> > > --
> > > 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: Fascinating Interview with Steve Jobs [non-mainframe] - now Gary Kildall

[Radoslaw Skorupka]

W dniu 05.04.2023 o 05:20, Bill Johnson pisze:

David Crayford said:
”I'm calling BS. None of the challenger banks (Startling, Yolt, Monzo, Moneze, 
N26 etc) run mainframes.  Sent from Yahoo Mail for iPhone

[...]

The first internet-only (no real branch offices) bank in Poland ran on 
mainframe. I started it (the mainframe and the bank as member of the 
team). After 20+ years it is fourth largest bank in Poland. And it 
converged to universal retail, however the banking offices are far from 
typical branches.


--
Radoslaw Skorupka
Lodz, Poland

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

Re: Tape compression and modern encryption facilities.

[Radoslaw Skorupka]

W dniu 16.04.2023 o 03:47, John Young pisze:

Although my post today is probably rhetorical question, I wanted to find out 
whether this matters anymore or not.

Back in the late 2000's, IBM developed encryption facilities within the tape 
drives, as this is also where compression was being performed.  The idea was 
that compression of data must occur before encryption, as encrypted data does 
not compress well, and obviates the use of compression.

Nowadays, we've got pervasive encryption on z/OS.  As a result, any data that 
is backed up (for instance, ADRDSSU/FDR), is already encrypted.

Also, we now have zEDC, to compress data prior to storage, typically on disk.

To my question: With all the encryption and compression being performed on 
disk, to what degree does TAPE COMPRESSION matter anymore?


Well, I would call it variety of choices.
Few remarks:
1. NO MORE TAPES connected directly to the z/OS. The last physical drive 
TS1140 is out of support.
2. The above implies you use some VTS/VTL. IBM, EMC, Visara, 
Secureagent, Luminex...
3. For IBM VTS you have several flavours of compression. One gives 
better compression ratio, the other provide better throughput, etc.
4. Compressed data sent to VTS and compressed again yield "negative" 
compression ratio, that means x:1, where x<1. This is not big increase, 
BTW.
5. There is much richer variety of encryption types and flavours. 
However I would bet not everyone encrypted every (possible) data on 
DASD. Not to mention some encryption is completely transparent to tape 
as the data is decrypted when sent to VTS CU. Example: FDE or FC end to 
end.
6. Sometimes we encrypt already encrypted data. Example: encrypted 
dataset sent over encrypted FICON to DASD with FDE (encrypted disk 
modules). Sometimes it makes sense, sometimes it is redundant, but 
really cheap (or free).


6. IMHO the most important: it is *our responsibility* to choose 
features which are appropriate to given scenario.


My €0.02

--
Radoslaw Skorupka
Lodz, Poland

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