Content deleted Content added
WP:NOTBROKEN z/OS, z/TPF, z/VM and z/VSE are the current systems, with VSEn replacing z/VSE soon |
|||
(47 intermediate revisions by 18 users not shown) | |||
Line 1:
{{Short description|Usage of Linux operating system on IBM mainframes}}
{{Multiple issues|
{{advert|date=September 2023}}
{{COI|date=October 2023}}
}}
{{History of IBM mainframe operating systems}}
Line 7 ⟶ 11:
Linux on IBM Z originated as two separate efforts to port Linux to IBM's [[IBM System/390|System/390]] servers. The first effort, the "Bigfoot" project, developed by [[Linas Vepstas]] in late 1998 through early 1999, was an independent distribution and has since been abandoned.<ref>{{cite web|last=Vepstas|first=Linas|title=Linux on the IBM ESA/390 Mainframe Architecture|url=http://www.linas.org/linux/i370-bigfoot.html|access-date=5 June 2013}}</ref> IBM published a collection of patches and additions to the Linux 2.2.13 [[Kernel (operating system)|kernel]] on December 18, 1999, to start today's mainline Linux on IBM Z.<ref>{{cite web|title=Linux/390 - Notes and Observations|url=http://linuxvm.org/penguinvm/notes.html|access-date=5 June 2013}}</ref> Formal product announcements quickly followed in 2000, including the [[Integrated Facility for Linux]] (IFL) engines. [[Think Blue Linux]] was an early mainframe distribution consisting mainly of [[Red Hat]] packages added to the IBM kernel.<ref>{{cite web|title=Linux for S/390|url=http://linux.s390.org/|access-date=5 June 2013}}</ref> Commercial Linux distributors introduced mainframe editions very quickly after the initial kernel work.
IBM manager Karl-Heinz Strassemeyer of Böblingen in Germany was the main lead to get Linux running on S/390.<ref>{{cite web|last=Lettice|first=John|title=IBM's S/390 Linux guru on the Open Source patent question|date=19 November 2002|website=[[The Register]]|url=https://www.theregister.com/2002/11/19/ibms_s_390_linux_guru/}}</ref>
At the start of IBM's involvement, Linux patches for
According to IBM,
==Virtualization==
[[Hardware virtualization|Virtualization]] is required by default on IBM Z; there is no option to run Linux on IBM Z without some degree of virtualization. (Only the very first 64-bit mainframe models, the z900 and z800, included a non-virtualized "basic mode.") First layer virtualization is provided by the Processor Resource and System Manager ([[logical partition#PR/SM|PR/SM]]) to deploy one or more Logical Partitions (LPARs). Each LPAR supports a variety of operating systems including Linux on IBM Z. A [[hypervisor]] called z/VM can also be run as the second layer virtualization in LPARs. This allows an LPAR to
When Linux applications in an LPAR access data and applications in other LPARs such as [[CICS]], [[IBM Db2]], [[IBM Information Management System|IMS]], [[Linux]], and other mainframe subsystems running on the same physical mainframe, they can utilize [[HiperSocket]]s – fast, memory-only [[Internet protocol suite|TCP/IP]] connections. As compared to TCP/IP over standard [[network interface controller
With the zEC12, zBC12, and later models, the HiperSocket concept is extended beyond the physical machine boundary via an [[RDMA over Converged Ethernet]] (RoCE) adapter to facilitate a secure and high speed inter-system communication. Applications in LPAR A in system A can thus use HiperSockets to communicate with applications in LPAR B in system B to ensure the security and performance attributes.{{citation needed|date=August 2014}}
Line 23 ⟶ 27:
Beginning with Linux kernel version 4.1 released in early 2015, Linux on IBM Z is only available as a [[64-bit computing|64-bit]] operating system compatible with [[z/Architecture]] mainframes. Previously Linux on IBM Z was also available as a [[32-bit computing|32-bit]] operating system, with [[31-bit computing|31-bit]] addressing, compatible with older model mainframes introduced prior to 2000's z900 model. However, the newer 64-bit Linux kernel and 64-bit Linux on IBM Z distributions are still backward compatible with applications compiled for 32-bit Linux on IBM Z. Historically the Linux kernel architecture designations were "s390" and "s390x" to distinguish between the 32-bit and 64-bit Linux on IBM Z kernels respectively, but "s390" now also refers generally to the one Linux on IBM Z kernel architecture.
Linux runs on standard, general purpose mainframe CPs (Central Processors) as well as IFLs ([[Integrated Facility for Linux]]). IFLs are mainframe processors dedicated to running Linux, either natively or under a hypervisor (z/VM or KVM on IBM Z). [[Microcode]] restricts IFLs from running "traditional" workloads, such as [[z/OS]], but they are physically identical to other IBM Z processors. IFLs are typically less expensive to acquire from IBM than CPs.<ref>{{cite web|title=IBM Z: Linux on IBM Z - Solutions - IFL|url=http://www-03.ibm.com/systems/z/os/linux/solutions/ifl.html|archive-url=https://web.archive.org/web/20080917051719/http://www-03.ibm.com/systems/z/os/linux/solutions/ifl.html|url-status=dead|archive-date=September 17, 2008|publisher=IBM|access-date=5 June 2013}}</ref>
Linux on IBM Z gives the flexibility of running Linux with the advantages of [[Mainframe computer|fault-tolerant mainframe hardware]] capable of over 90,000 I/O operations per second<ref>{{cite web|url=https://www.ibm.com/it-infrastructure/z/capabilities/connectivity|title=IBM Z - I/O Connectivity: FICON/zHPF/CTC|date=2012-11-15|website=www.ibm.com|language=en-US|access-date=2016-06-01|archive-url=https://web.archive.org/web/20171201182203/https://www.ibm.com/it-infrastructure/z/capabilities/connectivity|archive-date=2017-12-01|url-status=dead}}</ref> and with a [[Mean time between failures|mean time between failure (MTBF)]]<ref>{{cite web|url=http://www.computerworld.com/article/2560019/computer-hardware/mtbf.html|title=MTBF|last=staff|first=Computerworld|website=Computerworld|date=31 October 2005|access-date=2016-06-01}}</ref> measured in decades.<ref name=":0">{{cite web|url=http://www.fool.com/investing/general/2015/01/24/heres-why-ibm-is-still-building-mainframes.aspx|title=Here's Why IBM Is Still Building Mainframes -- The Motley Fool|last=Green|first=Timothy|website=The Motley Fool|date=24 January 2015|access-date=2016-06-01}}</ref> Using virtualization, numerous smaller servers can be combined onto one mainframe, gaining some benefits of centralization and cost reduction, while still allowing specialized servers. Instead of [[paravirtualization]], IBM mainframes use [[full virtualization]], which permits workload density far greater than paravirtualization does.{{citation needed|reason=Provide source for definition of workload density and relationship to paravirtualization|date=October 2018}} Combining full virtualization of the hardware plus lightweight [[Z/VM|Virtual Machine]] containers that run Linux in isolation (somewhat similar in concept to [[Docker (software)|Docker]]) result in a platform that supports more virtual servers than any other in a single footprint,<ref>{{cite web|url=
▲Linux on IBM Z gives the flexibility of running Linux with the advantages of [[Mainframe computer|fault-tolerant mainframe hardware]] capable of over 90,000 I/O operations per second<ref>{{cite web|url=https://www.ibm.com/it-infrastructure/z/capabilities/connectivity|title=IBM Z - I/O Connectivity: FICON/zHPF/CTC|date=2012-11-15|website=www.ibm.com|language=en-US|access-date=2016-06-01}}</ref> and with a [[Mean time between failures|mean time between failure (MTBF)]]<ref>{{cite web|url=http://www.computerworld.com/article/2560019/computer-hardware/mtbf.html|title=MTBF|last=staff|first=Computerworld|website=Computerworld|date=31 October 2005|access-date=2016-06-01}}</ref> measured in decades.<ref name=":0">{{cite web|url=http://www.fool.com/investing/general/2015/01/24/heres-why-ibm-is-still-building-mainframes.aspx|title=Here's Why IBM Is Still Building Mainframes -- The Motley Fool|last=Green|first=Timothy|website=The Motley Fool|date=24 January 2015|access-date=2016-06-01}}</ref> Using virtualization, numerous smaller servers can be combined onto one mainframe, gaining some benefits of centralization and cost reduction, while still allowing specialized servers. Instead of [[paravirtualization]], IBM mainframes use [[full virtualization]], which permits workload density far greater than paravirtualization does.{{citation needed|reason=Provide source for definition of workload density and relationship to paravirtualization|date=October 2018}} Combining full virtualization of the hardware plus lightweight [[Z/VM|Virtual Machine]] containers that run Linux in isolation (somewhat similar in concept to [[Docker (software)|Docker]]) result in a platform that supports more virtual servers than any other in a single footprint,<ref>{{cite web|url=http://www.vm.ibm.com/overview/index.html|title=IBM: About the z/VM Operating System|date=2015-01-14|website=www.vm.ibm.com|language=EN|access-date=2016-06-01}}</ref> which also can lower operating costs. Additional savings can be seen from reduced need for floor space, power, cooling, networking hardware, and the other [[Data center infrastructure management|infrastructure]] needed to support a [[data center]]. IBM mainframes allow transparent use of [[Mainframe computer|redundant processor execution steps]] and [[Mainframe computer|integrity checking]], which is important for critical applications in certain industries such as banking.{{citation needed|reason=dubious|date=June 2013}} Mainframes typically allow [[Hot swapping|hot-swapping of hardware]], such as processors and memory. IBM Z provides fault tolerance for all key components, including processors, memory, I/O Interconnect, power supply, channel paths, network cards, and others. Through internal monitoring, possible problems are detected and problem components are designed to be switched over without even failing a single transaction.<ref>{{cite web|url=https://www.ibm.com/it-infrastructure/z/capabilities/resiliency|title=IBM Z - Business resiliency: Data Driven - Server|date=2010-10-26|website=www.ibm.com|language=en-US|access-date=2016-06-01}}</ref> In the rare event of failure, firmware will automatically enable a spare component, disable the failing component, and notify IBM to dispatch a service representative. This is transparent to the operating system, allowing routine repairs to be performed without shutting down the system. Many industries continue to rely on mainframes where they are considered to be the best option in terms of reliability, security, or cost.<ref name=":0" />
IBM mainframes allow transparent use of [[Mainframe computer|redundant processor execution steps]] and [[Mainframe computer|integrity checking]], which is important for critical applications in certain industries such as banking.{{citation needed|reason=dubious|date=June 2013}} Mainframes typically allow [[Hot swapping|hot-swapping of hardware]], such as processors and memory. IBM Z provides fault tolerance for all key components, including processors, memory, I/O Interconnect, power supply, channel paths, network cards, and others. Through internal monitoring, possible problems are detected and problem components are designed to be switched over without failing a transaction.<ref>{{cite web|url=https://www.ibm.com/it-infrastructure/z/capabilities/resiliency|title=IBM Z - Business resiliency: Data Driven - Server|date=2010-10-26|website=www.ibm.com|language=en-US|access-date=2016-06-01}}</ref> In the rare event of failure, firmware will automatically enable a spare component, disable the failing component, and notify IBM to dispatch a service representative. This is transparent to the operating system, allowing routine repairs to be performed without shutting down the system. Many industries continue to rely on mainframes where they are considered to be the best option in terms of reliability, security, or cost.<ref name=":0" />
==Support==
Like all other versions of Linux, Linux on IBM Z is governed by the GPL [[free software]] license. Complete Linux on IBM Z [[source code]] is available from numerous parties on a free and equal basis, and architectural support is part of the main Linux kernel effort. IBM assigns several of its programmers to the community effort, but IBM is by no means the only participant.
Though there are no obstacles to running any Linux on IBM Z distribution on an IBM z System, IBM routinely tests three particular Linux on IBM Z distributions: [[Red Hat Enterprise Linux|Red Hat]],<ref>{{cite web|title=Linux on IBM Z/IBM LinuxONE tested platforms|date=7 June 2024 |url=https://www.ibm.com/support/pages/node/6191619|publisher=IBM|access-date=
Nearly every free or open-source software package available for Linux generally is available for Linux on IBM Z, including [[Apache HTTP Server]], [[Samba (software)|Samba]], [[JBoss]], [[PostgreSQL]], [[MySQL]], [[PHP]], [[Python (programming language)|Python programming language]], [[Concurrent Versions System]] (CVS), [[GNU Compiler Collection]] (GCC), [[LLVM]],
Red Hat and SUSE offer mainline support for their distributions running Linux on IBM Z.<ref>{{cite web|title=Red Hat Enterprise Linux for IBM Z|url=http://www.redhat.com/products/enterprise-linux/for-ibm-system-z/|publisher=Red Hat|access-date=5 June 2013}}</ref><ref>{{cite web|title=SUSE Linux Enterprise Server for Z|url=https://www.suse.com/products/systemz/|publisher=SUSE|access-date=5 June 2013}}</ref> In 2015 Canonical announced plans to offer official support for its distribution starting in early 2016. [[IBM Global Services]] also offers support contracts, including 24x7 coverage.<ref>{{cite web|title=IBM Services and Support for Linux|url=http://www-03.ibm.com/linux/services.html|publisher=IBM|access-date=5 June 2013|archive-url=https://web.archive.org/web/20131213233247/http://www-03.ibm.com/linux/services.html|archive-date=2013-12-13|url-status=dead}}</ref> Some standard Linux software applications are readily available pre-compiled, including popular closed-source enterprise software packages such as [[IBM WebSphere|WebSphere]],<ref>{{cite web|title=WebSphere MQ for Linux for System z |url=http://www-01.ibm.com/software/integration/wmq/linux_systemZ/ |publisher=IBM |access-date=5 June 2013 |url-status=dead |archive-url=https://web.archive.org/web/20130102035347/http://www-01.ibm.com/software/integration/wmq/linux_systemZ/ |archive-date= 2 January 2013}}</ref> [[IBM Db2]]<ref>{{cite web|title=Installation requirements for DB2 servers and IBM data server clients (Linux)|url=
==Developer resources==
Line 58 ⟶ 49:
* The Linux Remote Development Program, a fee-based extended developer support program.<ref>{{cite web|title=Linux Remote Development Program|url=https://www.ibm.com/partnerworld/wps/servlet/ContentHandler/stg_com_sys_linux_rdp|publisher=IBM|access-date=5 June 2013}}</ref>
Linux on IBM Z supports [[Unicode]] and [[ASCII]] just like any other Linux distribution—it is not an [[EBCDIC]]-based operating system.<ref>{{cite web|title=Mainframe operating system: Linux for System z|url=
Porting Linux applications to Linux on IBM Z is fairly straightforward. Potential issues include [[endianness]] (Linux on IBM Z is big-endian) and reliance on non-portable libraries particularly if source code is not available.<ref>{{cite web|last=Gellerich|first=Wolfgang|title=Porting applications to Linux for Z|url=http://www.ibm.com/developerworks/library/l-systemz/|work=IBM developerWorks|publisher=IBM|access-date=23 October 2013}}</ref> Programs can be easily [[cross compiler|cross compiled]] to z/Architecture binaries on non-mainframe Linux systems.<ref>{{cite web|title=How to|url=http://www.ibm.com/developerworks/linux/linux390/howto.html#how_to_3|work=IBM developerWorks|access-date=23 October 2013}}</ref>
Line 84 ⟶ 75:
==External links==
* [https://www.ibm.com
* [https://www.ibm.com
* [http://www.openmainframeproject.org/ Open Mainframe Project]
* [http://www.vm.ibm.com/linux/ Linux on z/VM]
* [
* [http://linuxvm.org/ Linux for S/390 and zSeries] web site
* [http://wiki.linuxvm.org/ Linux for S/390 and zSeries] {{Webarchive|url=https://web.archive.org/web/20160304071339/http://wiki.linuxvm.org/ |date=2016-03-04 }} community wiki
* [http://www2.marist.edu/htbin/wlvindex?LINUX-390 linux-390], users mailing list
* [http://vger.kernel.org/vger-lists.html#linux-s390 linux-s390], kernel devel mailing list
|