• Z/vm System Programmer Jobs
• Z/vm Disable Dirmaint
• Installing Z/vm On Hercules

IBM System 360 Mainframe Computer History Archives 1964 SLT, Course # CH-08 - Duration: 17:50. Computer History Archives Project 92,042 views. Z/VM 5.3 on Hercules390. Has anybody been able to install and run z/VM 5.3 (evaluation) on Hercules? If so, is there any guide on the net that shows how to install z. Installing IBM z/VM to Hercules Marc Schoechlin; Re: Installing IBM z/VM to Hercules David Boyes; Re: Installing IBM z/VM to Hercu. Installing VM/370 on Hercules.

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. Development started in 1999 by Roger Bowler, a mainframe systems programmer.

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 the first mainframe emulator to incorporate 64-bit z/Architecture support.

Design[edit]

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[edit]

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^{[citation needed]}, 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 costs, on Hercules include: Keygen x-force (xf-adsk64.exe).

Z/vm System Programmer Jobs

• Older IBM operating systems including OS/360, DOS/360, DOS/VS, MVS, VM/370, and TSS/370 which are either public domain or 'copyrighted software provided without charge.'^[3]
• The MUSIC/SP operating system may be available for educational and demonstration purposes upon request to its copyright holder, McGill University. Some of MUSIC/SP's features, notably networking, require z/VM (and thus an IBM license). However, a complete demonstration version of MUSIC/SP, packaged with the alternative Sim390 mainframe emulator, is available.
• The Michigan Terminal System (MTS) version 6.0A has been tailored to run under Hercules.^[4]
• There is no known legal restriction to running open-source operating systems Linux on z Systems and OpenSolaris for System z on the Hercules emulator. They run well on Hercules, and many Linux on System z developers do their work using Hercules. Several distributors provide 64-bit z/Architecture versions of Linux, and some also provide ESA/390-compatible versions. Mainframe Linux distributions include SUSE Linux Enterprise Server, Red Hat Enterprise Linux, Debian GNU/Linux, CentOS, and Slackware. Sine Nomine Associates brought OpenSolaris to System z, relying on features provided by z/VM. Emulation of those specific z/VM features for OpenSolaris is included starting with Hercules Version 3.07.
• Certain unencumbered editors and utilities which can run on a mainframe without a parent operating system may be available to run on Hercules as well.

Usage[edit]

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^{[citation needed]}. 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^{[citation needed]}.

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 (and later VM and DOS/VS), enhancing the operating systems with some degree of 31-bit (and as of 2016, 64-bit) binary compatibility with later operating system versions.

Performance[edit]

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.^{[citation needed]} With the same number of emulated Sys Z processors, z/PDT is about 3 times faster than Hercules.^{[citation needed]}

Note that there are other non-functional system attributes^[which?] beyond performance^{[clarification needed]} which are typically relevant to mainframe operators.

TurboHercules[edit]

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[edit]

References[edit]

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 29 January 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, archived from the original on 12 October 2011.
8. ^Press Release, European Commission, 26 July 2010.
9. ^News Release(PDF), TurboHercules, 23 November 2010, archived from the original(PDF) on 10 March 2012.
10. ^Press Release, EC, last paragraph.

External links[edit]

• Hercules (emulator) at Curlie
• Hercules, Son of Z's (Review on Tech-news.com)
• Public domain OS library (MVS version 3.8, VM/CMS release 6, DOS/VS release 34, TSS/370 version 3)
• Public domain software archive (includes Turnkey MVS CD image)

Hi Ivan,

Z/vm Disable Dirmaint

Yes indeed. Because of the information about the changes done regarding
SIE, I compiled yesterday the latest committed version of Hyperion.

In first level, up to now, I didn't face the problem of the TCP/IP start
any more. This is great. That bug of getting a network connection or not
was a nightmare for many years. However up to now I didn't face any DSP005
abends during a second level installation. That is new.

Some weeks ago I run a first level installation of zVM 6.3.0 and more ore
less it was successful. There the problem was that under some unknown
conditions CMS faced a corrupted storage area in its nucleus and abended.
That affected for instance the ipwizard exec and left the TCP/IP stack
unconfigured. So that problem seems to be fixed with the current change.

This time I wanted to run a clean install for 6.3 to replace my old 5.4
version once and for good. Well, unfortunately, there seems to be still at
leased one obstacle in front.

If I can provide you with more info please let me know.

Installing Z/vm On Hercules

Florian