Think of ZCX as a means of hosting Linux based software inside of a z/OS system much like one would run VirtualBox or VMware on a system to host another OS. For z/OS I see two main benefits. First, the open source software that so much new tech is built on does not have to be ported to USS but we can use it natively (notwithstanding the need for 390x binaries).
You could run dependent systems on platform where you used to run the software in another cloud. Service Management Unit, zAware, IBM operations Analytics for Z and a number of other current products are based on Linux open source. You get to save time, money, and run your supporting software on platform. Also, new work can be hosted on platform and co-located with other runtimes like CICS, IMS or Db2 and enjoy the lower latency, and business continuity of running in a Sysplex. Winner winner chicken dinner I think. Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook <https://facebook.com/matt.hogstrom> LinkedIn <https://linkedin/in/mhogstrom> Twitter <https://twitter.com/hogstrom> “It may be cognitive, but, it ain’t intuitive." — Hogstrom > On May 17, 2019, at 1:52 PM, Kirk Wolf <k...@wolf-associates.com> wrote: > > Docker is a virtualization technology which is different from a "virtual > machine". > See an overview like: > https://www.infoworld.com/article/3204171/what-is-docker-docker-containers-explained.html > > The zCX engine/host operating may be based on Ubuntu Linux; it isn't > technically correct to say the the "Linux *kernel* is Ubuntu". > Also, it doesn't matter too much that the Docker engine/host operating > system is a particular Linux distribution. Docker images derived from > different distributions can run in it. > > To confuse things, the zCX engine/host linux operating system runs inside a > z/OS address space using virtual machine technology. > > I'm sure I helped not at all :-) > > > On Thu, May 16, 2019 at 3:31 PM David Purdy < > 000000ac4b1d56b3-dmarc-requ...@listserv.ua.edu> wrote: > >> We learned at Share Phoenix that the Linux kernel is Ubuntu. >> >> David >> >> >> On Thursday, May 16, 2019 Jousma, David <IBM-MAIN@LISTSERV.UA.EDU> wrote: >> I've seen bits and pieces....I believe It's a blackbox secure setup. No >> on-site Linux administration aside from application admin or maintenance >> required, no ROOT access. All handled by IBM AFAIK. >> >> >> _____________________________________________________________________________________________________ >> Dave Jousma >> AVP | Manager, Systems Engineering >> >> Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand >> Rapids, MI 49546 >> 616.653.8429 | fax: 616.653.2717 >> >> >> >> -----Original Message----- >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf >> Of Frank Swarbrick >> Sent: Thursday, May 16, 2019 3:02 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: z/OS Container Extensions >> >> **CAUTION EXTERNAL EMAIL** >> >> **DO NOT open attachments or click on links from unknown senders or >> unexpected emails** >> >> Don't really know anything about this, but does anyone know what advantage >> there is to running a Docker container on z/OS over just running it Linux >> for Z? Is it just for those who don't have Linux for Z but want to run >> Linux applications on the mainframe? Does it allow "direct access" to z/OS >> resources (databases, CICS, etc.)? >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send email >> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION >> EXTERNAL EMAIL** >> >> **DO NOT open attachments or click on links from unknown senders or >> unexpected emails** >> >> >> This e-mail transmission contains information that is confidential and may >> be privileged. It is intended only for the addressee(s) named above. If >> you receive this e-mail in error, please do not read, copy or disseminate >> it in any manner. If you are not the intended recipient, any disclosure, >> copying, distribution or use of the contents of this information is >> prohibited. Please reply to the message immediately by informing the sender >> that the message was misdirected. After replying, please erase it from your >> computer system. Your assistance in correcting this error is appreciated. >> >> ---------------------------------------------------------------------- >> 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
