If you have specific questions about zCX, feel free to post them here.
I'll do my best to answer them, or find someone else who can.
As far as the technical setup of zCX, it's essentially a z/OS hypervisor
(like z/VM) that is only configured to run Linux. The Linux guest OS is
running Docker, and is a turnkey appliance. You only have to configure
the appliance to run in your z/OS environment (network, DASD, CPUs, etc.)
Once zCX is configured and the address space (or spaces!) is started,
the Docker service will be available to you in the appliance. You can
use this service to pull containers from Docker registries. A container
is essentially a packaged application+OS+libraries, which rather neatly
solves the "dependency hell" problem. You can create your own
containers or use commercially published ones, and these can be deployed
to a "Docker registry" for use, either internally or externally.
On 5/16/19 3:25 PM, Tina M Tarquinio wrote:
> You can check out the details here -->
> https://www.ibm.com/support/z-content-solutions/container-extensions/
>
> There are some FAQs that cover what you ask below, and more!
>
> And if that doesnt cover it, we can get the team to meet with you
> directly!
>
>
> Tina M. Tarquinio
> Director, IBM z/OS | @tinatarq | tina...@us.ibm.com
>
--
Anthony Giorgio
Advisory Software Engineer, z/OS Container Extensions
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
