Hercules (emulator)

Hercules
Original author(s) Roger Bowler
Developer(s) Jay Maynard, Jan Jaeger, David "Fish" Trout, Greg Smith, Bernard van der Helm, Ivan Warren, et allii[1]
Initial release 1999 (1999)
Stable release 3.12 / November 30, 2015 (2015-11-30)
Preview release 4.00
Development status Active
Written in C
Operating system Cross-platform
Type Emulator
License Q Public License
Website www.hercules-390.eu, www.hercules-390.org

Hercules is a computer emulator allowing software written for IBM mainframe computers (System/370, System/390, and zSeries/System z) and for plug compatible mainframes (such as Amdahl machines) to run on other types of computer hardware, notably on low-cost personal computers.

Although there are other mainframe emulators performing a similar function, Hercules is significant in enabling private individuals to run mainframe computer software on their own personal computers.

Hercules runs under multiple parent operating systems including GNU/Linux, Microsoft Windows, FreeBSD, Solaris, and Mac OS X and is released under the open source software license QPL.[2] It is analogous to Bochs and QEMU in that it emulates CPU instructions and select peripheral devices only. A vendor (or distributor) must still provide an operating system, and the user must install it. Hercules was notably the first mainframe emulator to incorporate 64-bit z/Architecture support, beating out commercial offerings.

Roger Bowler, a mainframe systems programmer, started development of the Hercules emulator in 1999.

Design

The emulator is written almost entirely in C. Its developers ruled out using machine-specific assembly code to avoid problems with portability even though such code could significantly improve performance. There are two exceptions: Hercules uses hardware assists to provide inter-processor consistency when emulating multiple CPUs on SMP host systems, and Hercules uses assembler assists to convert between little-endian and big-endian data on platforms where the operating system provides such services and on x86/x86-64 processors.

Operating systems status

Hercules is technically compatible with all IBM mainframe operating systems, even older versions which no longer run on newer mainframes. However, many mainframe operating systems require vendor licenses to run legally. Newer licensed operating systems, such as OS/390, z/OS, VSE/ESA, z/VSE, VM/ESA, z/VM, TPF/ESA, and z/TPF are technically compatible but cannot legally run on the Hercules emulator except in very limited circumstances, and they must always be licensed from IBM. IBM's Coupling Facility control code, which enables Parallel Sysplex, and UTS also require licenses to run.

Operating systems which may legally be run without license from IBM on Hercules include:

Debian GNU/Linux running on Hercules

Usage

Hercules can be used as a development environment to verify that code is portable (across Linux processor architectures, for example), supports symmetric multiprocessing (SMP), and is 64-bit "clean."

There is also a large community of current and former mainframe operators and programmers, as well as those with no prior experience, who use Hercules and the public domain IBM operating systems as a hobby and for learning purposes. Most of the skills acquired when exploring classic IBM mainframe operating system versions are still relevant when transitioning to licensed IBM machines running the latest versions.

The open source nature of Hercules means that anyone can produce their own customized version of the emulator. For example, a group of developers independent of the Hercules project implemented a hybrid mainframe architecture which they dubbed "S/380"[5] using modifications to both Hercules and to freely available classic versions of MVS, enhancing the latter with some degree of 31-bit binary compatibility with later operating system versions.

Performance

It is difficult to determine exactly how Hercules emulation performance corresponds to real mainframe hardware, but the performance characteristics are understandably quite different. This is partially due to the difficulty of comparing real mainframe hardware to other PCs and servers as well as the lack of concrete, controlled performance comparisons. Performance comparisons are likely legally impossible for licensed IBM operating systems, and those operating systems are quite different from other operating systems, such as Linux.

Hercules expresses its processing performance in MIPS. Due to the age of the earlier System/360 and System/370 hardware, it is a relatively safe assumption that Hercules will outperform them when running on moderately powerful hardware, despite the considerable overhead of emulating a computer architecture in software. However, newer, partially or fully configured System z machines outperform Hercules by a wide margin. A relatively fast dual processor X86 machine running Hercules is capable of sustaining about 50 to 60 MIPS for code that utilizes both processors in a realistic environment, with sustained rates rising to a reported 300 MIPS on leading-edge (early 2009) PC-class systems. Hercules can produce peaks of over 1200 MIPS when running in a tight loop, such as in a synthetic instruction benchmark or with other small, compute-intensive programs.

Tom Lehmann, co-founder of TurboHercules, wrote:

...We can run a reasonably sized load (800 MIPS with our standard package). If the machine in question is larger than that, we can scale to 1600 MIPS with our quad Nehalem based package, and we have been promised an 8 way Nehalem EX based machine early next year that should take us to the 3200 MIPS mark. Anything bigger than that is replicated by a collection of systems.[6]

Hercules generally outperforms IBM's PC based mainframes from the mid-1990s, which have an advertised peak performance of around 29 MIPS. Compared to the more powerful but still entry-level IBM Multiprise 2000 and 3000 mainframes (also from the 1990s), Hercules on typical x86 hardware would be considered a mid-range server in performance terms. For every mainframe after the 9672 Generation 1, Hercules would generally be the lowest end system. For comparison, current high-end IBM zEnterprise 196 systems can deliver over 52,000 MIPS per machine, and they have considerable I/O performance advantages. With the same number of emulated Sys Z processors, z/PDT is about 3 times faster than Hercules.

Note that there are other non-functional system attributes beyond performance which are typically relevant to mainframe operators.

TurboHercules

In 2009, Roger Bowler founded TurboHercules SAS, based in France, to commercialize the Hercules technology. In July, 2009, TurboHercules SAS asked IBM to license z/OS to its customers for use on systems sold by TurboHercules. IBM declined the company's request.[7] In March, 2010, TurboHercules SAS filed a complaint with European Commission regulators, alleging that IBM infringed EU antitrust rules through its alleged tying of mainframe hardware to its mainframe operating system, and the EC opened a preliminary investigation.[8] In November, 2010, TurboHercules announced that it had received an investment from Microsoft Corporation.[9] In September, 2011, EC regulators closed their investigation without action.[10]

See also

References

  1. ↑ "6.1", FAQ, EU: Hercules 390
  2. ↑ Approved licenses (alphabetical) (list), The Open Source Initiative.
  3. ↑ "2.02. What operating systems can I run legally?", Frequently-Asked Questions, EU: Hercules 390 Version 3.
  4. ↑ "wELCOME". Michigan Terminal System Archive. Retrieved Jan 29, 2013.
  5. ↑ "S/380 Diagram", MVS/380 project, Sourceforge.
  6. ↑ Hercules goes commercial! (Web log), Oracle
  7. ↑ Exchange of letters between TurboHercules and IBM, Turbo Hercules.
  8. ↑ Press Release, European Commission, 26 July 2010.
  9. ↑ News Release (PDF), TurboHercules, November 23, 2010.
  10. ↑ Press Release, EC, last paragraph.

External links

This article is issued from Wikipedia - version of the Tuesday, April 19, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.