Linux on System z

From Wikipedia, the free encyclopedia
Jump to: navigation, search
History of IBM mainframe operating systems

Linux on System z is the collective term for the Linux operating system compiled to run on IBM mainframes, especially System z machines. Other terms with the same meaning include Linux on zEnterprise 196, Linux on System z10, Linux on System z9, Linux on zSeries, Linux/390, zLinux, z/Linux, etc.

History[edit]

Linux on System z originated as two separate efforts to port Linux to IBM's largest 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.[1] IBM published a collection of patches and additions to the Linux 2.2.13 kernel on December 18, 1999, to start today's mainline Linux on System z.[2] 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.[3] Commercial Linux distributors introduced mainframe editions very quickly after the initial kernel work, and these mainframe versions have now been available for several years.

At the start of IBM's involvement, Linux patches for System z included some object code only (OCO) modules, without source code.[4] However, currently Linux on System z is completely free software under the GNU General Public License.[citation needed]

As of May 2006, according to IBM, over 1,700 customers run Linux on their mainframes.[5]

Virtualization[edit]

Virtualization is required by default on IBM System z, there is no option. First layer virtualization is provided by the Processor Resource and System Manager (PR/SM) to deploy Logical Partitions (LPARs). Variety of Operating Systems can be IPL'ed or booted in the LPARs. A System z hypervisor called z/VM can also be IPL'ed as the second layer virtualization in LPARs to create as many Virtual Machines (VM) as there are resources assigned to the LPARs to support them. This multi-layer virtualization capability allows System z to deploy hundreds or thousands of Virtual Machines within a single physical system. System z earned EAL5+ certification. z/VM earned Common Criteria EAL4+ certification for its ability to protect virtual machines in an LPAR. The first layer virtualization PR/SM allows a System z to be virtualized up to 60 LPARs. Therefore, with PR/SM alone, a System z can deploy up to 60 Linux instances. These can be considered as 60 Virtual Bare Metal servers because PR/SM allows CPUs to be dedicated to individual LPARs. With second layer virtualization z/VM in each of the up to 60 LPARs, and each z/VM LPAR supports typically hundreds of Linux instances, a single System z with 60 z/VM LPARs can deploy a very large number of Virtual Machines as long as there are adequate CPU, memory, and I/O resources configured with the system.

System z's PR/SM and hardware attributes allow compute resources to be dynamically changed to meet workload demands. CPU and memory resources can be nondisruptively added to the system and dynamically assigned, recognized, and used by LPARs. I/O resources such as IP and SAN ports can also be added dynamically. They are virtualized and shared across all LPARs. The hardware component of System z that provides this capability is called the Channel Subsystem. Each LPAR can be configured to either "see" or "not see" the virtualized I/O ports to establish desired "shareness" or isolation. System z's virtualization capability allows significant reduction in I/O resources because of its ability to share them and drive up utilization.

Inter-LPAR communication is facilitated by PR/SM and System z hardware. Intra-LPAR communication is facilitated by z/VM which originates the System Defined Networking concept. From a communication stands point, with the first layer virtualization PR/SM and the second layer virtualization z/VM, Linux instances in a System z do not have the need for top-of-rack IP switches and SAN switches. This eliminates a large portion of cost and complexity from the equation. System z's virtualization capability also allows a system to be highly utilized at 80%, 90%, or even 100% and still be productive.

When Linux applications in an LPAR access data and applications in other LPARs such as CICS, IBM DB2, IMS, Linux, and other mainframe subsystems, running on the same physical mainframe, they can utilize HiperSockets – fast, memory-only TCP/IP connections. As compared to TCP/IP over standard network interface cards (NICs, in the mainframe world called Open System Adapters, OSAs), HiperSockets can improve end-user responsiveness (reduce network latency and processing overhead), security (since there's no network connection to intercept), and reliability (since there's no network connection to lose).[6]

With the System z models EC12 and BC12, the Hipersocket is extended beyond the physical boundary to facilitate a secure and high speed inter-system communication. Applications in LPAR A in system A can use Hiperscocket to communicate with applications in LPAR B in system B to ensure the security and performance attributes. .

Hardware[edit]

Linux on System z is available in both 31-bit and 64-bit versions. The Linux kernel architecture designation is "s390" for 31-bit kernels and "s390x" for 64-bit kernels.[7] 64-bit distributions can still run 31-bit applications. The 31-bit versions are rapidly losing favor as z/Architecture mainframes become more prevalent than the earlier ESA/390 generation.

The Linux 2.6.x kernel added substantial support for mainframe hardware, such as ESCON, FICON, SCSI-attached storage devices, and System z cryptographic accelerators. Also several vendor distributions backported 2.6.x patches to the Linux 2.4.x kernel.

Linux runs on standard general-purpose CPs (Central Processors) as well as IFLs (Integrated Facility for Linux). IFLs are mainframe processors dedicated to running Linux, either natively or under z/VM. Microcode restricts IFLs from running "traditional" workloads, such as z/OS; they are otherwise identical to other System z processors. IFLs are typically less expensive to license from IBM than CPs.[8]

Advantages[edit]

Linux on System z gives the flexibility of running Linux with the advantages of mainframe hardware. Using virtualization, numerous smaller servers can be combined onto one mainframe, gaining some benefits of centralization, but allowing specialized servers thanks to virtualization support, which can lower operating costs. IBM mainframes allow transparent use of redundant processor execution steps and integrity checking, which is necessary in the financial services industries[citation needed]. Mainframes typically allow hot-swapping of hardware, such as processors and memory. This swapping is typically transparent to the operating system, allowing routine repairs to be performed without shutting down the system.

Pricing and costs[edit]

Linux on System z is not appropriate for small businesses that would have fewer than about 10 distributed Linux servers, although some expensive per-processor licensed software can quickly reduce that rule of thumb. Most software vendors, including IBM, treat the highly virtualized IFLs just like non-virtualized processors on other platforms for licensing purposes. In other words, a single IFL running scores of Linux instances still counts as one "ordinary" CPU, at the same CPU price, for software licensing. Test, development, quality assurance, training, and redundant production server instances can all run on one IFL (or more IFLs, but only if needed for peak demand performance capacity). Thus, beyond some minimum threshold, Linux on System z can quickly become cost-advantageous when factoring in labor and software costs.

The cost equation for Linux on System z is not always well understood and is controversial, and many businesses and governments have difficulty measuring, much less basing decisions on, software, labor, and other costs (such as the costs of outage and security breaches). Acquisition costs are often more visible, and small, non-scalable servers are "cheap." Nonetheless, non-acquisition costs are no less real and are usually far greater than hardware acquisition prices[citation needed]. Also, individual users and departments within larger businesses and governments sometimes have difficulty sharing computing infrastructure (or any other resources, for that matter), citing a loss of control. Server centralization, as Linux on System z provides, might reward cooperation with better service and lower costs, but that's not to say that cooperation is always easily accomplished within a corporate bureaucracy.

Linux on System z also supports less expensive disk storage devices than z/OS because Linux does not require FICON or ESCON attachment, although z/OS may use disk space more efficiently due to hardware-assisted database compression on z/OS. This compression effect is somewhat variable and may be somewhat reduced due to the minimum space allocation requirements for z/OS data sets (a full disk track).

Appropriate workloads[edit]

Mainframe characteristics are designed for such business workloads as transaction processing or large database management. Mainframe design emphasizes input/output performance, implemented via channel I/O. Historically, the principle is to offload I/O activities from the CPU as much as possible, and the z/Architecture additionally offloads cryptographic calculations. Mainframes can scale to numerous processors in a single frame, e.g. up to 64 processors in the case of the System z10 EC Model E64, which gives as much as 28.000 MIPS.

On the other hand, mainframes in general, and Linux on System z in particular, do not perform well for single task computations. Examples include most scientific simulations, weather forecasting, and molecular modeling. Supercomputers, including Linux-based supercomputers, excel at these workloads. This distinction has blurred since the introduction of the System z10, a machine based on quad-core 4.4 GHz processors with hardware decimal floating point. In this regard, the System z10 more resembles a supercomputer processor than previous mainframes.

Mainframes do not provide graphics or sound adapters, and are as such ill-suited for digital media editing or computer-aided design (CAD) except perhaps in support roles (e.g. content storage, parts inventories, etc.)

Support[edit]

Like all other versions of Linux, Linux on System z is governed by the GPL free software license. Complete Linux on System z source code is available from numerous groups on a free and equal basis, and architectural support is now 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.

IBM currently supports two Linux distributions, Red Hat and SUSE.[9] Other notable Linux on System z distributions are Debian,[10] Fedora,[11] Slackware,[12] and Gentoo.[citation needed]

Nearly every free or open-source software package available for Linux generally is available for Linux on System z, including Apache HTTP Server, Samba software, JBoss, PostgreSQL, MySQL, PHP, Python programming language, Concurrent Versions System (CVS), GNU Compiler Collection (GCC), and Perl, among many others.[13]

Red Hat and SUSE offer mainline support for their distributions running Linux on System z.[14][15] IBM Global Services also offers support contracts, including 24x7 coverage.[16] Some standard Linux software applications are readily available pre-compiled, including popular closed-source enterprise software packages such as WebSphere,[17] DB2[18] and Oracle[19] databases and applications, SAP R/3, SAP ERP,[20] and IBM's Java Developer's Kit (JDK),[21] to name only a few.

Developer resources[edit]

IBM offers resources to developers wishing to target Linux for System z:

  • The Linux Test Drive, a free program granting a single Linux on System z virtual machine for 30 days.[22]
  • The IBM Systems Application Advantage for Linux (Chiphopper), a developer program to help developers write and publish cross-platform Linux software.[23]
  • The Community Development System for Linux on System z (CDSL) program, a platform for providing open source developers a platform for porting to Linux on System z.[24]
  • The Linux Remote Development Program, a fee-based extended developer support program.[25]

Linux on System z supports Unicode and ASCII just like any other Linux distribution—it is not an EBCDIC-based operating system.[26] Linux is able to read kernel parameters in EBCDIC; this ability is used in z/VM installations.

Porting Linux applications to Linux on System z is fairly straightforward; issues include endianness (Linux on System z is big-endian) and conversion between 32-bit integers and 31-bit pointers on the s390 architecture.[27]

Programs can be easily cross compiled to z/Architecture binaries on non-mainframe Linux systems.[28]

Emulators[edit]

There are at least three software-based System z mainframe emulators.

  • FLEX-ES from Fundamental Software is a commercially offered option.[29]
  • The open source Hercules emulator supports Linux on System z (and can even run on Linux on System z itself).
  • In 2010, IBM introduced the Rational Developer for System z Unit Test Feature, which provides a restricted use execution environment that can run on X86 hardware. IBM's license terms limit use of the Unit Test Feature to certain application development tasks, not including final pre-production compiling or pre-production testing (such as stress testing). The Unit Test Feature includes z/OS (with common middleware) and is also compatible with Linux on System z.[30]

See also[edit]

References[edit]

  1. ^ Vepstas, Linas. "Linux on the IBM ESA/390 Mainframe Architecture". Retrieved 5 June 2013. 
  2. ^ "Linux/390 - Notes and Observations". Retrieved 5 June 2013. 
  3. ^ "Linux for S/390". Retrieved 5 June 2013. 
  4. ^ "Kernel 2.2 based". developerWorks. IBM. Retrieved 5 June 2013. 
  5. ^ Milberg, Ken. "The Gen Xer's Guide to the Mainframe Part III". IBM Systems Magazine. Retrieved 5 June 2013. 
  6. ^ "HiperSockets". z/OS basic skills information center. IBM. Retrieved 5 June 2013. 
  7. ^ "Porting applications to Linux for System z". developerWorks. IBM. Retrieved 5 June 2013. 
  8. ^ "IBM System z: Linux on System z - Solutions - IFL". IBM. Retrieved 5 June 2013. 
  9. ^ "IBM System z: Linux on System z - Resources - Tested platforms". IBM. Retrieved 5 June 2013. 
  10. ^ "S/390 Port". Debian. Retrieved 5 June 2013. 
  11. ^ "Architectures/s390x". Fedora Project. Retrieved 5 June 2013. 
  12. ^ "AWelcome to the Slack/390 Project". Slackware Inc. Retrieved 22 April 2014. 
  13. ^ "Debian autobuilder status for s390, 29 April 2013". Debian. Retrieved 5 June 2013. 
  14. ^ "Red Hat Enterprise Linux for IBM System z". Red Hat. Retrieved 5 June 2013. 
  15. ^ "SUSE Linux Enterprise Server for System z". SUSE. Retrieved 5 June 2013. 
  16. ^ "IBM Services and Support for Linux". IBM. Retrieved 5 June 2013. 
  17. ^ "WebSphere MQ for Linux for System z". IBM. Retrieved 5 June 2013. 
  18. ^ "Installation requirements for DB2 servers and IBM data server clients (Linux)". IBM DB2 Version 10.1 Information Center. IBM. Retrieved 5 June 2013. 
  19. ^ "IBM System z: Linux on System z - Solutions - zSolution Oracle - Overview". IBM. Retrieved 5 June 2013. 
  20. ^ "SAP Applications Empower Business". Retrieved 5 June 2013. 
  21. ^ "developerWorks : Technical Topics : Java™ technology : IBM Developer kits : Linux : Download information". Retrieved 5 June 2013. 
  22. ^ "Linux Test Drive". IBM. Retrieved 5 June 2013. 
  23. ^ "IBM Systems Application Advantage for Linux (Chiphopper)". IBM. Retrieved 5 June 2013. 
  24. ^ "IBM System z: Linux on System z - Community Development System for Linux - Registration Form". IBM. Retrieved 5 June 2013. 
  25. ^ "Linux Remote Development Program". IBM. Retrieved 5 June 2013. 
  26. ^ "Mainframe operating system: Linux for System z". z/OS basic skills information center. IBM. Retrieved 5 June 2013. 
  27. ^ Gellerich, Wolfgang. "Porting applications to Linux for System z". IBM developerWorks. IBM. Retrieved 23 October 2013. 
  28. ^ "How to". IBM developerWorks. Retrieved 23 October 2013. 
  29. ^ "System/390 on Intel-Based Servers". Retrieved 5 June 2013. 
  30. ^ "Rational System z Development and Testing Hub". IBM. Retrieved 5 June 2013. 

External links[edit]