Precompiled Hercules Binaries for Windows

Daily Snapshots

You will find precompiled binaries at the Daily Snapshots page.

The precompiled binaries for the current "Production Version" of Hercules is available at this page

Version 2.18 RELEASE NOTES

Reminder that CTCI device handling was changed starting with version 2.17 as follows:
- The CTCI-W32 protocol is deprecated. You should use the CTCI protocol instead.
- You MUST NOT define both even/odd CTCI device pairs in your configuration file. You should ONLY define the first even numbered device. Hercules will automatically define the odd numbered device for you. If you define the odd numbered device by mistake, an open error will occur on that device. This is by design. See the README.NETWORKING document for further details.
Hercules Dynamic Loader support: starting with version 2.18, Hercules now contains support for the dynamic loading of certain modules upon startup on some platforms (e.g. Linux and Windows for example). As a result of this new feature, "Hercules" itself now no longer consists of just the 'hercules.exe' module by itself, but rather consists of BOTH the 'hercules.exe' program AS WELL AS whatever dynamic modules (DLLs) that accompany it.
As a result if this change, whenever you install a new version of Hercules, you must ensure that you ALSO install the accompanying new versions of the new dynamic modules as well. Attempting to use a version of Hercules with a dynamic module that was not specifically built for that version will cause loading of that dynamic module to fail.
You CANNOT mix versions of hercules with differing versions of dynamically loaded modules.

The MODPATH statement in the configuration file can be used to point to the directory where the dynamically loaded modules can be found Linux only Ensure that you either have set the MODPATH statement correctly or that your library path LD_LIBRARY_PATH is set correctly such that it includes the directory of your hercules executables. Especially, message HHCCF042E will indicate that system is unable to locate necessary loadable modules.
ECPS:VM: Do not use ECPS:VM (See README.ECPSVM) in an AP or MP environment in VM/370. If AP=YES or MP=YES is coded in DMKSYS and the AP/MP control file is used to build the CP nucleus and NUMCPU is set to more than 1 in the hercules.cnf file, any of LOK001, LOK003 or other abends will occur. This occurs because the hercules ECPS:VM CP Assist implementation is not MP safe, and particularily, attemps VM dispatching without holding necessary AP or MP locks.

Target CPU Type

i586 i686 P 4

Thread
Model fthread

pthread

Source Code

Download Array for Hercules 2.17.b9 binaries

Which CPU Type?

i585: Any Pentium class CPU qualifies for this CPU type. If you have an older Pentium based PC, or a PC based on an Athlon K processor, you should choose the i586 column from the download Arrray
i686: The i686 CPU type include all processors from the Pentium Pro processor onwards. If you have a modern PC this should probably be the column to choose from the download array
P 4: The P4 CPU type include all processors from the Pentium 4 Processor onwards. I have tested this version, and it works on my system. If it brings any performance gain, I cannot tell. Try it out yourself. If you run into problems, you can always use the i686 version

Which Thread Model

fthread: Fish (aka David B. Trout) has developed an optimized threading model for Hercules running in a Cygwin environment, which obviously is called fish-thread or fthread. You should normally choose the fthread row from the download array.
pthread: The Cygwin system comes with its own posix compliant thread model, called pthread. You should only choose the pthread row from the download array if you have experienced serious problems when using the fthread model

Installation

If you have not yet installed Cygwin 1.3.22 or later you need to run the self extracting archive cygwin1322.exe. The installation path must be \CYGWIN on one of your drives, I assume drive C: here, in other words, choose C:\CYGWIN as the installation directory

After installation of the Cygwin support files you now run the Hercules installation archive you downloaded before. Again, the installation path is c:\cygwin. After installation you will have the following directories

C:\cygwin --+-- bin
            !
            +-- etc
            !
            +-- tmp
            !
            +-- usr --+-- local --+--- bin
                                  !
                                  +--- lib ---+--- hercules
                                  !
                                  +--- man ---+--- man1
                                  !           !
                                  !           +--- man4
                                  !
                                  +-- share --+-- hercules --+-- images
                                              !              !
                                              !              +-- include
                                              !
                                              +-- locale

The Cygwin support files are in C:\cygwin\bin, the Hercules binaries are in C:\cygwin\usr\local\bin, dynamic load libraries are in \C:\cygwin\usr\local\lib\hercules, the Hercules support files in C:\cygwin\usr\local\share, and additional documentation can be found in C:\cygwin\usr\local\man

Add the following to your system's search path:

c:\cygwin\usr\local\bin;c:\cygwin\bin;c:\cygwin\usr\local\lib\hercules

h2>Installation Verification Procedure

You now can run a quick test if the installation of Hercules was successful. Change to the following directory:

C:\Cygwin\usr\local\bin

which should contain the Hercules executable files. Now enter the command

hercules

which will invoke the emulator with a simple configuration file. You should see messages similar to this:

Hercules Version 2.17.b9
(c)Copyright 1999-2003 by Roger Bowler, Jan Jaeger, and others
Built on Aug 23 2003 at 00:14:23
Build information:
  compiled for p4
  Modes: S/370 ESA/390 ESAME
  Win32 (Windows) build
  Using fthreads instead of pthreads
  HTTP Server support
  No sqrtl support
  No SIGABEND handler
  National Language Support

Running on CYGWIN_NT-5.0 i686 1.3.22(0.78/3/2) 2003-03-18 09:20
HHC600I Console connection thread started: tid=0000032C, pid=1644
HHC630I CPU0000 Architecture Mode ESA/390
HHC650I Control panel thread started: tid=00000AD0, pid=1644
HHC610I Timer thread started: tid=00000828, pid=1644
HHS019I HTTP listener thread started: tid=00000898, pid=1644
HHS014I Waiting for HTTP requests on port 8081
HHC602I Waiting for console connection on port 3270

You may or may not see an error message like this;

Running on CYGWIN_NT-5.0 i686 1.3.17(0.67/3/2) 2002-11-27 18:54
** tt32_loaddll: LoadLibraryEx("TunTap32.dll") failed; rc=126: Das angegebene Modul wurde nicht gefunden.

which complains about a missing file TunTap32.dll. This DLL is only needed if you want/need TCP/IP support via TunTap services. This support must be installed separately and is described elsewhere

You now should connect a tn3270 session to your host on port 3270. When the client has connected, you will be rewareded by a message

HHC604I Client 192.168.1.196 connected to 3270 device 001F

Now enter the following command on the Hercules console

ipl 000c

Switch over to the tn3270 session and press the "Clear Screen" key. You should now see the initial screen of Jan Jaeger's excellent standalone editor, ZZSA:

 ZZSAPSWD                    Stand Alone Utilities







                         Enter Password:



                         ===> _










                                             Jan Jaeger - Version 12/07/98-12.15

If so, the IVP was successful. You can now enter the ZZSA password:

 ZZSAPSWD                    Stand Alone Utilities







                         Enter Password:



                        ===> zzsecret










                                             Jan Jaeger - Version 12/07/98-12.15

This will take you to the ZZSA Primary Menu:

 ZZSAPRIM                    Stand Alone Utilities

 Option ===>


     0 ListDev  - List all devices

     1 Browse   - Browse dataset or member                Console     001F/3278

     2 Edit     - Edit dataset or member                  IPL Device  000C/3505

     3 ListVTOC - List Volume Table Of Contents           IPL CPU     0000

     4 ListPDS  - List PDS directory                      CPU Version 00

     5 DispVol  - Display DASD volume label               CPU Serial  002623

     6 Dump     - Dump DASD record by CCHHR               CPU Model   3090

     7 Zap      - Alter DASD record by CCHHR              Date (TOD)  16/12/2002

     X Exit     - Terminate program                       Time (TOD)  10:00:21

                                             Jan Jaeger - Version 12/07/98-12.15

You can leave the ZZSA editor by selecting "x" from its primary menu. Then you leave Hercules by entering

quit

on the Hercules console

History of Changes

I will try and maintain a change log here - but no promises

That's all, folks

If I managed to confuse you with these instructions, just drop me a line.

Enjoy your private Hercules mainframe

		Target CPU Type
		i586	i686	P 4
Thread Model	fthread
Thread Model	pthread
Source Code