Discussion:
Improvements for CTC Enhanced (CTCE) Device, incl. XCF Support, Now Available
(too old to reply)
peter_j_jansen@yahoo.com [hercules-390]
2016-04-04 08:16:07 UTC
Permalink
I completed developing and testing improvements to the Enhanced CTC device emulation in Hercules. Up to now, CTCE supported only Basic Mode CTC's (like for MVS GRS connections). In addition to a number of bug fixes and performance improvements, CTCE now also supports Extended Mode CTC connections, like for XCF channel programs. As a result, CTC's connecting multiple Hercules PC's running base sysplex MVS systems are now possible.
This development started under SuSE SLES 12 and Windows 7 VS2010 and SDK 7, but the latter was later upgraded to Windows 10 and VS2015 (community edition, update 1 of December 2015). Also, both Hercules spinhawk 3.12 as well as hyperion 4.00 were used and successfully tested. The testing environment included two Windows 10 PC's and one SLES 12 system, using z/OS 1.10 in LPAR mode with up to 3 systems in the XCF ring, relying on Hercules' shared DASD support; initial testing was under z/VM 5.3. The source is available on GitHub, but users will need to generate the Hercules binaries themselves. The current documented instructions to do so still apply, except that also VS2015 is supported (effectively simpler to download and install than VS2010 which still needed the separate SDK and various updates).
This work took quite a bit of effort and the result was carefully tested over an estimated number of about 1500 IPL's, many of which using 2 or 3 CTCE connected Hercules systems. However, as per usual, no guarantees can be given, although I'd be interested to learn from experiences, positive or negative.


Peter J. Jansen
Mike Stramba mikestramba@gmail.com [hercules-390]
2016-04-04 10:17:14 UTC
Permalink
Post by ***@yahoo.com [hercules-390]
The source is available on GitHub, but users will need to generate the Hercules binaries
Perhaps you might share the url ? :)

Mike
Post by ***@yahoo.com [hercules-390]
I completed developing and testing improvements to the Enhanced CTC device
emulation in Hercules. Up to now, CTCE supported only Basic Mode CTC's
(like for MVS GRS connections). In addition to a number of bug fixes and
performance improvements, CTCE now also supports Extended Mode CTC
connections, like for XCF channel programs. As a result, CTC's connecting
multiple Hercules PC's running base sysplex MVS systems are now possible.
This development started under SuSE SLES 12 and Windows 7 VS2010 and SDK 7,
but the latter was later upgraded to Windows 10 and VS2015 (community
edition, update 1 of December 2015). Also, both Hercules spinhawk 3.12 as
well as hyperion 4.00 were used and successfully tested. The testing
environment included two Windows 10 PC's and one SLES 12 system, using z/OS
1.10 in LPAR mode with up to 3 systems in the XCF ring, relying on Hercules'
shared DASD support; initial testing was under z/VM 5.3. The source is
available on GitHub, but users will need to generate the Hercules binaries
themselves. The current documented instructions to do so still apply,
except that also VS2015 is supported (effectively simpler to download and
install than VS2010 which still needed the separate SDK and various
updates).
This work took quite a bit of effort and the result was carefully tested
over an estimated number of about 1500 IPL's, many of which using 2 or 3
CTCE connected Hercules systems. However, as per usual, no guarantees can
be given, although I'd be interested to learn from experiences, positive or
negative.
Peter J. Jansen
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-04-04 10:23:37 UTC
Permalink
Sure Mike, here it is:



https://github.com/Peter-J-Jansen/hyperion



The Git Pull Request for this one is still outstanding, hopefully Fish can help here; the equivalent one for Spinhawk 3.12 has been merged already by Roger.



I’m interested in feedback of course, especially perhaps from people able to test z/VM SSI (I only have z/VM 5.3 available to me).



Cheers,



Peter J.



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Monday, 4 April, 2016 12:17
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Improvements for CTC Enhanced (CTCE) Device, incl. XCF Support, Now Available
Post by ***@yahoo.com [hercules-390]
The source is available on GitHub, but users will need to generate the Hercules binaries
Perhaps you might share the url ? :)

Mike
Post by ***@yahoo.com [hercules-390]
I completed developing and testing improvements to the Enhanced CTC device
emulation in Hercules. Up to now, CTCE supported only Basic Mode CTC's
(like for MVS GRS connections). In addition to a number of bug fixes and
performance improvements, CTCE now also supports Extended Mode CTC
connections, like for XCF channel programs. As a result, CTC's connecting
multiple Hercules PC's running base sysplex MVS systems are now possible.
This development started under SuSE SLES 12 and Windows 7 VS2010 and SDK 7,
but the latter was later upgraded to Windows 10 and VS2015 (community
edition, update 1 of December 2015). Also, both Hercules spinhawk 3.12 as
well as hyperion 4.00 were used and successfully tested. The testing
environment included two Windows 10 PC's and one SLES 12 system, using z/OS
1.10 in LPAR mode with up to 3 systems in the XCF ring, relying on Hercules'
shared DASD support; initial testing was under z/VM 5.3. The source is
available on GitHub, but users will need to generate the Hercules binaries
themselves. The current documented instructions to do so still apply,
except that also VS2015 is supported (effectively simpler to download and
install than VS2010 which still needed the separate SDK and various
updates).
This work took quite a bit of effort and the result was carefully tested
over an estimated number of about 1500 IPL's, many of which using 2 or 3
CTCE connected Hercules systems. However, as per usual, no guarantees can
be given, although I'd be interested to learn from experiences, positive or
negative.
Peter J. Jansen
Harold Grovesteen h.grovsteen@tx.rr.com [hercules-390]
2016-04-08 15:24:11 UTC
Permalink
On Mon, 2016-04-04 at 12:23 +0200, 'Peter J. Jansen'
Post by 'Peter J. Jansen' ***@yahoo.com [hercules-390]
https://github.com/Peter-J-Jansen/hyperion
The Git Pull Request for this one is still outstanding, hopefully Fish
can help here; the equivalent one for Spinhawk 3.12 has been merged
already by Roger.
Merged into Hyperion.

Harold Grovesteen
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-05-01 14:00:11 UTC
Permalink
Thanks Harold, very much appreciated.



Cheers,



Peter Jansen



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Friday, 8 April, 2016 17:24
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Improvements for CTC Enhanced (CTCE) Device, incl. XCF Support, Now Available





On Mon, 2016-04-04 at 12:23 +0200, 'Peter J. Jansen'
Post by 'Peter J. Jansen' ***@yahoo.com [hercules-390]
https://github.com/Peter-J-Jansen/hyperion
The Git Pull Request for this one is still outstanding, hopefully Fish
can help here; the equivalent one for Spinhawk 3.12 has been merged
already by Roger.
Merged into Hyperion.

Harold Grovesteen
'Shelby Beach' shelby.beach@comcast.net [hercules-390]
2016-04-04 19:17:18 UTC
Permalink
Great job Peter. Knowing what I know about CTCs (which is just enough to get
by !), this was no easy task. The CTCE device will greatly increase the
opportunities for just playing around.

Shelby



________________________________

From: hercules-***@yahoogroups.com
[mailto:hercules-***@yahoogroups.com]
Sent: Monday, April 04, 2016 1:16 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Improvements for CTC Enhanced (CTCE) Device,
incl. XCF Support, Now Available




I completed developing and testing improvements to the Enhanced CTC
device emulation in Hercules. Up to now, CTCE supported only Basic Mode
CTC's (like for MVS GRS connections). In addition to a number of bug fixes
and performance improvements, CTCE now also supports Extended Mode CTC
connections, like for XCF channel programs. As a result, CTC's connecting
multiple Hercules PC's running base sysplex MVS systems are now possible.

This development started under SuSE SLES 12 and Windows 7 VS2010 and
SDK 7, but the latter was later upgraded to Windows 10 and VS2015 (community
edition, update 1 of December 2015). Also, both Hercules spinhawk 3.12 as
well as hyperion 4.00 were used and successfully tested. The testing
environment included two Windows 10 PC's and one SLES 12 system, using z/OS
1.10 in LPAR mode with up to 3 systems in the XCF ring, relying on Hercules'
shared DASD support; initial testing was under z/VM 5.3. The source is
available on GitHub, but users will need to generate the Hercules binaries
themselves. The current documented instructions to do so still apply,
except that also VS2015 is supported (effectively simpler to download and
install than VS2010 which still needed the separate SDK and various
updates).

This work took quite a bit of effort and the result was carefully
tested over an estimated number of about 1500 IPL's, many of which using 2
or 3 CTCE connected Hercules systems. However, as per usual, no guarantees
can be given, although I'd be interested to learn from experiences, positive
or negative.


Peter J. Jansen
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-04-04 20:28:16 UTC
Permalink
Thanks for your nice words Shelby.



Yes, these CTCE's allow (Base) Sysplex; mine's been running without a hitch
now for quite some time between a Windows 10 and a SLES 12 system. (Does
zPDT support such XCF CTC's ? Don't know.)



Cheers,



Peter



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Monday, 4 April, 2016 21:17
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Improvements for CTC Enhanced (CTCE) Device,
incl. XCF Support, Now Available





Great job Peter. Knowing what I know about CTCs (which is just enough to get
by !), this was no easy task. The CTCE device will greatly increase the
opportunities for just playing around.

Shelby


________________________________

From: <mailto:hercules-***@yahoogroups.com> hercules-***@yahoogroups.com
[ <mailto:hercules-***@yahoogroups.com> mailto:hercules-***@yahoogroups.com]

Sent: Monday, April 04, 2016 1:16 AM
To: <mailto:hercules-***@yahoogroups.com> hercules-***@yahoogroups.com
Subject: [hercules-390] Improvements for CTC Enhanced (CTCE) Device,
incl. XCF Support, Now Available




I completed developing and testing improvements to the Enhanced CTC
device emulation in Hercules. Up to now, CTCE supported only Basic Mode
CTC's (like for MVS GRS connections). In addition to a number of bug fixes
and performance improvements, CTCE now also supports Extended Mode CTC
connections, like for XCF channel programs. As a result, CTC's connecting
multiple Hercules PC's running base sysplex MVS systems are now possible.

This development started under SuSE SLES 12 and Windows 7 VS2010 and
SDK 7, but the latter was later upgraded to Windows 10 and VS2015 (community
edition, update 1 of December 2015). Also, both Hercules spinhawk 3.12 as
well as hyperion 4.00 were used and successfully tested. The testing
environment included two Windows 10 PC's and one SLES 12 system, using z/OS
1.10 in LPAR mode with up to 3 systems in the XCF ring, relying on Hercules'
shared DASD support; initial testing was under z/VM 5.3. The source is
available on GitHub, but users will need to generate the Hercules binaries
themselves. The current documented instructions to do so still apply,
except that also VS2015 is supported (effectively simpler to download and
install than VS2010 which still needed the separate SDK and various
updates).

This work took quite a bit of effort and the result was carefully
tested over an estimated number of about 1500 IPL's, many of which using 2
or 3 CTCE connected Hercules systems. However, as per usual, no guarantees
can be given, although I'd be interested to learn from experiences, positive
or negative.


Peter J. Jansen
Ivan Warren ivan@vmfacility.fr [hercules-390]
2016-04-04 23:18:06 UTC
Permalink
Post by 'Peter J. Jansen' ***@yahoo.com [hercules-390]
Thanks for your nice words Shelby.
Yes, these CTCE’s allow (Base) Sysplex; mine’s been running without a
hitch now for quite some time between a Windows 10 and a SLES 12
system. (Does zPDT support such XCF CTC’s ? Don’t know.)
Cheers,
Peter
*Sent:* Monday, 4 April, 2016 21:17
Peter,

Not sure - but z/PDT probably has the ICF capability (which would allow
multiple z/OS hosts running under z/VM to run as a full blown sysplex
using a CF virtual machine) - But not necessarily to have multiple z/PDT
systems to run z/OS full blown sysplex (I guess it would then require a
standalone z/PDT to act as a CF).

Anyway, nice work on your work ! (I can't test it though).

I'd be curious to know if anyone managed to build a z/VM SSI system with
your enhancements (But you also need PVM I think - I'm not THAT familiar
with SSI - And yes - I know - I'm stuck with z/VM 5.3 too).

--Ivan

(PS : CTCE and CF are different beasts right ?)



[Non-text portions of this message have been removed]



------------------------------------

------------------------------------

Community email addresses:
Post message: hercules-***@yahoogroups.com
Subscribe: hercules-390-***@yahoogroups.com
Unsubscribe: hercules-390-***@yahoogroups.com
List owner: hercules-390-***@yahoogroups.com

Files and archives at:
http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
http://www.hercules-390.org


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/hercules-390/join
(Yahoo! ID required)

<*> To change settings via email:
hercules-390-***@yahoogroups.com
hercules-390-***@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
hercules-390-***@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-04-05 08:36:39 UTC
Permalink
Ivan,
Thanks for your nice comments.
Yes, zPDT supports ICF as described in "SG24-7859-02, zPDT and Parallel
Sysplex", but this remains restricted to a single PC as I understand it. And
yes, CTCE's emulation of CTC's now supporting XCF only allows BASE Sysplex.
The full blown PARALLEL Sysplex would require Coupling Facility (CF)
emulation to support XES, and this is totally impossible to implement
without its detailed specifications being available. Even with such
specifications I think it would be a gigantic task if not impossible; the
CTC specifications are, and you won't believe how many times I had to
re-read those before I got the CTCE emulation to work correctly.
Peter

-----Original Message-----
From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Tuesday, 5 April, 2016 01:18
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Improvements for CTC Enhanced (CTCE) Device,
incl. XCF Support, Now Available

Peter,

Not sure - but z/PDT probably has the ICF capability (which would allow
multiple z/OS hosts running under z/VM to run as a full blown sysplex using
a CF virtual machine) - But not necessarily to have multiple z/PDT systems
to run z/OS full blown sysplex (I guess it would then require a standalone
z/PDT to act as a CF).

Anyway, nice work on your work ! (I can't test it though).

I'd be curious to know if anyone managed to build a z/VM SSI system with
your enhancements (But you also need PVM I think - I'm not THAT familiar
with SSI - And yes - I know - I'm stuck with z/VM 5.3 too).

--Ivan

(PS : CTCE and CF are different beasts right ?)
Ivan Warren ivan@vmfacility.fr [hercules-390]
2016-04-05 09:35:36 UTC
Permalink
Post by 'Peter J. Jansen' ***@yahoo.com [hercules-390]
Ivan,
Thanks for your nice comments.
Yes, zPDT supports ICF as described in "SG24-7859-02, zPDT and Parallel
Sysplex", but this remains restricted to a single PC as I understand it. And
yes, CTCE's emulation of CTC's now supporting XCF only allows BASE Sysplex.
The full blown PARALLEL Sysplex would require Coupling Facility (CF)
emulation to support XES, and this is totally impossible to implement
without its detailed specifications being available. Even with such
specifications I think it would be a gigantic task if not impossible; the
CTC specifications are, and you won't believe how many times I had to
re-read those before I got the CTCE emulation to work correctly.
Peter
-----Original Message-----
Peter,

Actually the CF infrastructure has already been implemented ;) (but
never released) - because it requires using the ICF/CF LIC - and that we
cannot do - for legal reasons (unless someone wants to try
implementing/emulate the CF functionality)

Apparently the CF code (that runs on a standalone machine) and ICF code
(that run in a virtual machine) are actually identical !

--Ivan

(Believe it or not - I do have basic understanding of how a CTC works -
having gone many time through various CE manuals to try to understand
how it works).



[Non-text portions of this message have been removed]
Tony Harminc tharminc@gmail.com [hercules-390]
2016-04-05 18:23:05 UTC
Permalink
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Actually the CF infrastructure has already been implemented ;) (but
never released) - because it requires using the ICF/CF LIC - and that we
cannot do - for legal reasons (unless someone wants to try
implementing/emulate the CF functionality)
Remember way back when there was a guy (Peter Ward, iirc) from Funsoft
hanging out on this list making strange hints about how the Hercules
64-bit zSIE couldn't have been implemented using only IBM published
information? And of course it turned out that IBM *had* published the
information, but in an unexpected place...

I don't want to sound like that guy, but I do wonder how it is
possible to implement a CF using only published information?
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Apparently the CF code (that runs on a standalone machine) and ICF code
(that run in a virtual machine) are actually identical !
Indeed. The CF/ICF code is not distributed with z/VM, but is loaded on
the fly by some magic from the LIC ("microcode") storage on the
hardware. Presumably therefore it *is* distributed with the zPDT.

Tony H.
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-04-06 08:13:13 UTC
Permalink
If the CF specifications were ever published or discovered, then I would certainly love to help implementing them in the Hercules emulator.



I suspect additional requirements could emerge, e.g. the CF facility also needing access to ETR / STP timing facilities. (Again with no detailed specifications available, right ? I thought to have read somewhere that zPDT emulates STP ? z/VM’s ICF may not need that, using SIMETRID ? Questions, questions 
)



In case anyone wonders, a Base Sysplex using CTCE – XCF can circumvent these by (1) ensuring sufficiently identical time between the Hercules hosting PC’s, e.g. NTP (for Windows I use the free Meinberg NTP client), and (2) giving each Hercules instance the same emulated 390 serial number but different LPAR numbers. As a result, SIMETRID in PARMLIB’s CLOCKxx works just fine.



Peter J.



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Tuesday, 5 April, 2016 20:23
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Improvements for CTC Enhanced (CTCE) Device, incl. XCF Support, Now Available
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Actually the CF infrastructure has already been implemented ;) (but
never released) - because it requires using the ICF/CF LIC - and that we
cannot do - for legal reasons (unless someone wants to try
implementing/emulate the CF functionality)
Remember way back when there was a guy (Peter Ward, iirc) from Funsoft
hanging out on this list making strange hints about how the Hercules
64-bit zSIE couldn't have been implemented using only IBM published
information? And of course it turned out that IBM *had* published the
information, but in an unexpected place...

I don't want to sound like that guy, but I do wonder how it is
possible to implement a CF using only published information?
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Apparently the CF code (that runs on a standalone machine) and ICF code
(that run in a virtual machine) are actually identical !
Indeed. The CF/ICF code is not distributed with z/VM, but is loaded on
the fly by some magic from the LIC ("microcode") storage on the
hardware. Presumably therefore it *is* distributed with the zPDT.

Tony H.
stephen.orso@yahoo.com [hercules-390]
2016-04-07 12:33:28 UTC
Permalink
Peter:

Does your VS2015 support work with the Win 8.1 SDK, the Win 10 SDK, or both--or neither? VS2015 doesn't appear support anything earlier than 8.1, and I'm using VS2015 IDE with the VS2008 C++ compiler and the Win7.1 SDK.


If you're using the 8.1 or 10 SDK, is there a change in the C Runtime level needed?


I'll test on DOS/DOSVS/MVT.


Steve Orso


---In hercules-***@yahoogroups.com, <***@...> wrote :

<...>
This development started under SuSE SLES 12 and Windows 7 VS2010 and SDK 7, but the latter was later upgraded to Windows 10 and VS2015 (community edition, update 1 of December 2015).
<...>
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-04-07 14:53:59 UTC
Permalink
Steve,



I only tested VS2015 Community Edition on Windows 10, I skipped 8 / 8.1 altogether. I started prior to the VS2105 December 2105 update 1, but later applied this update as well. I did this on an regular updated Windows 10 system, but on a different PC I installed windows 10 from scratch, and then installed VS2015 Community Edition Update 1. On this latter system, neither a MS VS2010 (or other version), nor any SDK, was ever present. The simplification of not having to install any additional SDK’s surprised me, but I like it much better this way. I must admit I’m not deeply into MS VS nor it’s SDK’s, perhaps this VS2015 has it included, together with the C compiler etc. ?



The only small difficulty I had to overcome was the total absence of the “Win32.Mak” file. After some Internet searches I got the impression this is how it now is. I solved this by copying that file from the VS2010 SDK into the include path (I actually just copied it in the Hercules source directory). This latter may need a more professional fix, perhaps Herculeans with a better and deeper knowledge of MS VS201x may improve on this (like Fish).



I did not make any changes to the C Runtime level.



In short, on Windows all one needs to build Hercules is MS VS2015 Community Edition (apart from ZLIB 1.2.5, BZIP2 1.0.6, and PCRE 8.20, if one wants to add these – which I suspect most Hercules users would want.)



Regards,



Peter J. Jansen



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, 7 April, 2016 14:33
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Improvements for CTC Enhanced (CTCE) Device, incl. XCF Support, Now Available





Peter:



Does your VS2015 support work with the Win 8.1 SDK, the Win 10 SDK, or both--or neither? VS2015 doesn't appear support anything earlier than 8.1, and I'm using VS2015 IDE with the VS2008 C++ compiler and the Win7.1 SDK.



If you're using the 8.1 or 10 SDK, is there a change in the C Runtime level needed?



I'll test on DOS/DOSVS/MVT.



Steve Orso



---In <mailto:hercules-***@yahoogroups.com> hercules-***@yahoogroups.com, < <mailto:***@...> ***@...> wrote :

<...>

This development started under SuSE SLES 12 and Windows 7 VS2010 and SDK 7, but the latter was later upgraded to Windows 10 and VS2015 (community edition, update 1 of December 2015).

<...>
stephen.orso@yahoo.com [hercules-390]
2016-04-08 14:29:49 UTC
Permalink
This post might be inappropriate. Click to display it.
Tony Harminc tharminc@gmail.com [hercules-390]
2016-04-08 21:16:28 UTC
Permalink
Post by ***@yahoo.com [hercules-390]
VS2008 (the last free VS/IDE before VS2015) requires a license key that is
no longer available from Microsoft. Without the key, one gets nagged every
so often to provide it. A registry hack is available......
I know nothing about this, but note that on MSDN the VS2008 versions
(standard, express, professional) are all available with "no license key
required". Which would lead me to think that they must be out there all
over the net if MS is no longer tracking them by license key. Are you
saying these versions all nag? Or is it just some special "free" version
they stopped distributing the keys for?

Tony H.
stephen.orso@yahoo.com [hercules-390]
2016-04-08 22:26:47 UTC
Permalink
This post might be inappropriate. Click to display it.
rgschmi@execpc.com [hercules-390]
2016-04-09 04:17:26 UTC
Permalink
This is awesome! I have just been playing with sysplex distributor using two tcpip stacks on the same O/S and four TN3270 stacks, two with affinity to each tcpip stack. Sysplex distributor works, but TN3270 LUNS gets confused with everything on the same O/S image and only 'sorta' works.

Now I can set up a 'real' base sysplex and get sysplex distributor and LUNS working the way they would in the real world. I just have to get my IODF and sysplex friend to help me configure CTCs and XCF as I'm just a network guy. Sounds like VTAM XCF should work as well!

Thanks for making this happen!
rgschmi@execpc.com [hercules-390]
2016-04-10 17:33:08 UTC
Permalink
I'm having trouble making XCF work. I get a 'not all sockets connected' message. I also noticed the example in the online manual for CTCE is for CTCT's and I believe is wrong for CTCT as the addresses have to be cross-connected.

Do you have an example of a configuration that works?

I have also tested this with a stand-alone diagnostic tool used to check connectivity on real CTC's and it also fails.

I'm hoping it is something I am doing wrong as I'd really like to make it work.

Interestingly, the version command doesn't show the version!
George George@shedlock.org [hercules-390]
2016-05-11 22:14:36 UTC
Permalink
I have been testing with Hercules on my Debian 8 system with all of the
latest patches applied. I installed the Herc version from the standard
repository, along with Herc Studio. I copies a full set of files from my
Windows laptop where everything runs fine. The only change I made to the
config file was to change the path names to the disk images. This is a
z/VM 5.2 system. I load the config file and do a power on and it comes
up fine. I then start a x3270 session and get the Herc logo. I then IPL,
put in the cons=0700 into the screen that is displayed, hit the F10 key
and get a 9029 hard wait. There has been a lot of discussion regarding
this wait code, but no resolution or hints on how to fix it.

Anyone have a suggestion?
George George@shedlock.org [hercules-390]
2016-05-12 00:41:38 UTC
Permalink
After re-reading what I put in below, I realized that I made a typo on
the hard wait code. It is actually 9046 which from my reading seems to
be related to STFLE. I will try to install Spinhawk for a test to see if
that fixes the problem.

George
Post by George ***@shedlock.org [hercules-390]
I have been testing with Hercules on my Debian 8 system with all of the
latest patches applied. I installed the Herc version from the standard
repository, along with Herc Studio. I copies a full set of files from my
Windows laptop where everything runs fine. The only change I made to the
config file was to change the path names to the disk images. This is a
z/VM 5.2 system. I load the config file and do a power on and it comes
up fine. I then start a x3270 session and get the Herc logo. I then IPL,
put in the cons=0700 into the screen that is displayed, hit the F10 key
and get a 9029 hard wait. There has been a lot of discussion regarding
this wait code, but no resolution or hints on how to fix it.
Anyone have a suggestion?
Ivan Warren ivan@vmfacility.fr [hercules-390]
2016-05-13 11:03:58 UTC
Permalink
Post by George ***@shedlock.org [hercules-390]
After re-reading what I put in below, I realized that I made a typo on
the hard wait code. It is actually 9046 which from my reading seems to
be related to STFLE. I will try to install Spinhawk for a test to see
if that fixes the problem.
George
George,

There are reports of z/VM 5.3 working on spinhawk and hyperion... It's
quite possible debian 8 ships with Hercules 3.07 which may not have the
necessary facilities.

There are also reports of people managing to run up to z/VM 6.3 (but it
requires some tweaking - especially the right choice of compiler for
IAF2 support).

Of course this requires having your own build environment.

--Ivan


[Non-text portions of this message have been removed]
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-05-13 11:51:50 UTC
Permalink
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
George,
There are reports of z/VM 5.3 working on spinhawk and hyperion...
[...]
There are also reports of people managing to run up to z/VM 6.3 (but it
requires some tweaking - especially the right choice of compiler for
IAF2 support).
Of course this requires having your own build environment.
-> -Ivan

Ivan,

I can confirm that z/VM 5.3 works fine on both Hyperion and Spinhawk.

Also z/VM 6.3 works just fine, and is actually the z/VM version I'm using to
test CTC connections for the SSI ISCF links (already working now). So far
I did this only using Spinhawk, and thus without IAF2 support. As soon as
RSCS CTC links have been tested as well, I will repeat the process under
Hyperion (and when all is fine, release my CTCE updates). I use Windows 10
and SuSE SLES 12 SP1 (*).

I (re-)build Hercules whenever needed, so I can't vote for z/VM support
under older Hercules versions.

Peter J.

P.S.: (*) I also have/had z/VM 5.3 running on a Raspberry Pi 2.
rgschmi@execpc.com [hercules-390]
2016-04-10 18:28:50 UTC
Permalink
I'm having problems getting CTCE to work. If it connects at all I usually get a 'not all sockets connected' message. I'm running under OpenSUsE linux. I tried the 'version' command under Hercules, but it doesn't show the version, but I downloaded the source dated 4-8-2016, so I believe I have the latest code.

I also tested the connectivity using a stand-alone diagnostic used to test CTC's on real mainframes. It failed also. Do you have an example configuration that I can use as a sample in case I'm doing something wrong? I noticed the CTCT sample in the online manual is for CTT's and I believe is wrong for CTCE's as the ports should be cross-connected (my send is your receive).

I'd be happy to run any tests you might want and send you more info via email.
rgschmi@execpc.com [hercules-390]
2016-04-11 14:21:01 UTC
Permalink
It's working now! A lot of user errors on my part in addition to not really knowing much about sysplex configuration. Also, the stand-alone utility was sending a 0E4 extended sense command that I see you don't support (nor is it needed) that led us astray.

I tried to cross connect the CTC addresses so I could use the same COUPLExx member in both images. Sometimes it worked, but for whatever reason it seems more stable when I used the same address on both images and separate COUPLExx members. Not sure why.

Now on to my windows machines. Hopefully there will be some pre-built binaries soon.

Really nice job! I'm impressed.
'John P. Hartmann' jphartmann@gmail.com [hercules-390]
2016-04-11 14:50:30 UTC
Permalink
For a 3088, E4 sense is a must.
Post by ***@execpc.com [hercules-390]
E4 extended sense command that I see you don't support (nor is it needed)
mcisho@yahoo.com [hercules-390]
2016-04-11 15:31:06 UTC
Permalink
The code suggests that CTCE does support E4 (Sense ID). The only thing it doesn't do is return the definition of the Read Configuration Data command, but that probably doesn't matter.
'John P. Hartmann' jphartmann@gmail.com [hercules-390]
2016-04-11 16:19:31 UTC
Permalink
Certainly doesn't. A 3088 doesn't know of such a beast.
Post by ***@yahoo.com [hercules-390]
The code suggests that CTCE does support E4 (Sense ID). The only thing
it doesn't do is return the definition of the Read Configuration Data
command, but that probably doesn't matter.
mcisho@yahoo.com [hercules-390]
2016-04-11 16:56:09 UTC
Permalink
< Certainly doesn't. A 3088 doesn't know of such a beast. >

I disagree. The original CTCA may not have known about Sense ID, and maybe even the very first 3088's, but most 3088's certainly did. The 'Channel-to-Channel Adapter for the System/360 and System/370 I/O Interface' manual (SA22-7091-01, October 1991) lists Sense ID (0xE4) as an adapter command, with a note that says 'Those models that do not provide the sense-ID command interpret it as the sense-command-byte command.' ESCON and FICON CTCA, which still describe themselves as 3088's, always support Sense ID.
'John P. Hartmann' jphartmann@gmail.com [hercules-390]
2016-04-11 17:06:52 UTC
Permalink
A 3088 is rather a lot more complex that what you relate, but what I
thought I said was that E4 sense is a requirement, but it does not do
read configuration or any other of the newfangled commands for DASD.
Post by ***@yahoo.com [hercules-390]
< Certainly doesn't. A 3088 doesn't know of such a beast. >
I disagree. The original CTCA may not have known about Sense ID, and
maybe even the very first 3088's, but most 3088's certainly did. The
'Channel-to-Channel Adapter for the System/360 and System/370 I/O
Interface' manual (SA22-7091-01, October 1991) lists Sense ID (0xE4) as
an adapter command, with a note that says 'Those models that do not
provide the sense-ID command interpret it as the sense-command-byte
command.' ESCON and FICON CTCA, which still describe themselves as
3088's, always support Sense ID.
mcisho@yahoo.com [hercules-390]
2016-04-11 17:59:02 UTC
Permalink
It certainly is and was complicated, especially 30-years later. I used to have a manual that described the original CTCA (which wasn't calledf a 3088, 3088's were the second generation), but sadly it got lost in a house move. I referred to that manual, and the later 3088 manual (SA22-7091), a lot back then while writing code to drive CTC's. All I have these days is SA22-7091-02 (and the ESCON CTCA manual), which says Read Configuration Data is available, model dependent, and Sense ID and Read Configuration Data are described in the same section.
rgschmi@execpc.com [hercules-390]
2016-04-20 16:07:55 UTC
Permalink
I'm having trouble buiulding Hercules for Windows. I've downloaded VS2015 and ZLIB and BZIP2. At first I got an error message that amd64 wasn't supported so I managed to build a 32 bit binary. Then Visual Studio did an update and now it get a little further but I get errors on both 32 and 64 bit builds. I've never used Visual Studio before, so I'm probably doing something wrong, I just can't fugure out what. It also dows a 'one way conversion' before starting the build. Here is the log I managed to find. What's with the win32.mak?

Visual Studio 2015 detected
Hercules version number is \"4.00.0\" (4.00.0.0)
Makefile will assume VS14 or VS2015 Express (MSVC version 20)
Target processor type is 64-bit AMD64

VERSION = \"4.00.0\" (4.00.0.0)

ZLIB support will be included from "c:\ZLIB\x64"
BZIP2 support will be included from "c:\BZIP2\x64"
PCRE support will not be generated
REGINA REXX support will be included from "C:\Program Files\rexx.org\Regina"
makefile-dllmod.msvc(28): fatal error U1052: file 'win32.mak' not found
Stop.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.MakeFile.Targets(42,5): error MSB3073: The command "makefile.bat RETAIL-X64 makefile.msvc 32 -a" exited with code 2.


Any suggestions?

Thanks
'Peter J. Jansen' peter_j_jansen@yahoo.com [hercules-390]
2016-04-20 16:29:18 UTC
Permalink
The „Win32.Mak“ file was part of Microsoft earlier VS versions, like VS2010, or, more precisely, the SDK that went with it (SDK 7.1 if I remember correctly). You will need to copy that file in the include path of VS2015 in order to build Hercules correctly (using the CLI method, which as explained in this thread is no longer possible otherwise with VS2015).



I also think only 64 bit builds are now possible, at least for Hyperion 4.00. (I never tried 32 bit builds.)



Cheers,



Peter J.



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, 20 April, 2016 18:08
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Improvements for CTC Enhanced (CTCE) Device, incl. XCF Support, Now Available





I'm having trouble buiulding Hercules for Windows. I've downloaded VS2015 and ZLIB and BZIP2. At first I got an error message that amd64 wasn't supported so I managed to build a 32 bit binary. Then Visual Studio did an update and now it get a little further but I get errors on both 32 and 64 bit builds. I've never used Visual Studio before, so I'm probably doing something wrong, I just can't fugure out what. It also dows a 'one way conversion' before starting the build. Here is the log I managed to find. What's with the win32.mak?

Visual Studio 2015 detected
Hercules version number is \"4.00.0\" (4.00.0.0)
Makefile will assume VS14 or VS2015 Express (MSVC version 20)
Target processor type is 64-bit AMD64

VERSION = \"4.00.0\" (4.00.0.0)

ZLIB support will be included from "c:\ZLIB\x64"
BZIP2 support will be included from "c:\BZIP2\x64"
PCRE support will not be generated
REGINA REXX support will be included from "C:\Program Files\rexx.org\Regina"
makefile-dllmod.msvc(28): fatal error U1052: file 'win32.mak' not found
Stop.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.MakeFile.Targets(42,5): error MSB3073: The command "makefile.bat RETAIL-X64 makefile.msvc 32 -a" exited with code 2.


Any suggestions?

Thanks
rgschmi@execpc.com [hercules-390]
2016-04-20 22:57:45 UTC
Permalink
Well, I got further, but still having problems. It seems strange to me to get win32 messages when I'm trying to build 64bit binaries, but I have never used Visual Studio before. I am using the zip file source for Hercules dated 4/8/2016 if that matters. I set the VS2015 pull-downs to release and x64.

Here is the latest:

Visual Studio 2015 detected
Hercules version number is \"4.00.0\" (4.00.0.0)
Makefile will assume VS14 or VS2015 Express (MSVC version 20)
Target processor type is 64-bit AMD64

VERSION = \"4.00.0\" (4.00.0.0)

ZLIB support will be included from "c:\ZLIB\x64"
BZIP2 support will be included from "c:\BZIP2\x64"
PCRE support will not be generated
REGINA REXX support will be included from "C:\Program Files\rexx.org\Regina"
REGINA REXX FLAGS /D ENABLE_REGINA_REXX /I"C:\Program Files\rexx.org\Regina\include" /D HAVE_REXXSAA_H
IPV6 FLAGS /D ENABLE_IPV6
build_pch.c
Target platform = _WIN32_WINNT 0x0502
C:\Program Files (x86)\Windows Kits\8.1\include\um\dbghelp.h(1544): error C2220: warning treated as error - no 'object' file generated
C:\Program Files (x86)\Windows Kits\8.1\include\um\dbghelp.h(1544): warning C4091: 'typedef ': ignored on left of '' when no variable is declared
C:\Program Files (x86)\Windows Kits\8.1\include\um\dbghelp.h(3190): warning C4091: 'typedef ': ignored on left of '' when no variable is declared
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\x86_amd64\cl.EXE"' : return code '0x2'
Stop.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.MakeFile.Targets(37,5): error MSB3073: The command "makefile.bat RETAIL-X64 makefile.msvc 32" exited with code 2.
'\'Fish\' (David B. Trout)' david.b.trout@gmail.com [hercules-390]
2016-04-21 02:53:55 UTC
Permalink
***@execpc.com wrote:

[...]
Post by ***@execpc.com [hercules-390]
warning C4091: 'typedef ': ignored on left of '' when no variable is
declared
warning C4091: 'typedef ': ignored on left of '' when no variable is
declared
You're missing a recent fix(*).

Download the latest version of Hyperion and try again.
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: ***@softdevlabs.com

(*) Specifically, commit 105b9b532503c0acd8ea41e59d465fc003c55b13, which added Warning C4091 to the list of warnings to be ignored for VS2015:

!IF $(vsversion) >= $(vers_vs2015)
cflags = $(cflags) /wd4996
cflags = $(cflags) /wd4312
cflags = $(cflags) /wd4477
cflags = $(cflags) /wd4172
cflags = $(cflags) /wd4776
cflags = $(cflags) /wd4091 <=== this on was added
!ENDIF
rgschmi@execpc.com [hercules-390]
2016-04-21 16:38:46 UTC
Permalink
I'm much further now. I found a win32.mak that seems to work, but now I get three errors in winioctl.h, missing ':' before 'constant' on lines 5394, 5395, 5396. If I could find winioctl in VS2015 I could probably fix it, but I checked all the header files I could find and didn't see it. It's in the unzipped Hercules folder, but I don;'t have an editor that numbers the lines, so pretty hard to find.
stephen.orso@yahoo.com [hercules-390]
2016-04-20 23:27:34 UTC
Permalink
Hi Peter et al,

My Hyperion builds have all been 32-bit builds. I'm embarrassed to share how many I've done. No issues apart from my mistakes.


I haven't figured out how to use my machine to build 3.12, so I haven't started bothering Roger yet.


To rgschmi: See my post dated 8-April in this thread for additional details on my setup.


Best Regards,
Steve Orso

---In hercules-***@yahoogroups.com, <***@...> wrote :


<...>
I also think only 64 bit builds are now possible, at least for Hyperion 4.00. (I never tried 32 bit builds.)

<...>
'\'Fish\' (David B. Trout)' david.b.trout@gmail.com [hercules-390]
2016-04-21 01:31:44 UTC
Permalink
I'm having trouble building Hercules for Windows.
I've downloaded VS2015 and ZLIB and BZIP2.
VS2015 support is still under development. VS2015 Community Edition Update 1 has issues as does Update 2 as well. They are being looked into. I'll post more information as it becomes available.


[...]
Any suggestions?
Yes: hang loose for a while. It's being worked on.

In the mean time, if you can find a copy of VS2008, use that instead.
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: ***@softdevlabs.com
rgschmi@execpc.com [hercules-390]
2016-04-21 01:56:37 UTC
Permalink
Thanks. Will do.
'George' George@shedlock.org [hercules-390]
2016-05-13 12:46:54 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
</head>







<body style="background-color: #fff;">
<span style="display:none">&nbsp;</span>

<!--~-|**|PrettyHtmlStartT|**|-~-->
<div id="ygrp-mlmsg" style="position:relative;">
<div id="ygrp-msg" style="z-index: 1;">
<!--~-|**|PrettyHtmlEndT|**|-~-->

<div id="ygrp-text" >


<p>


<span style="font-size:10pt;"><p style="margin-top:0;margin-bottom:0;">Is there a set of pre-built binaries for the debian platform?</p><p style="margin-top:0;margin-bottom:0;">&nbsp;</p><dev3>Sent from my Sprint phone.</dev3><br><br>------ Original message ------<br><b>From:&nbsp;</b>Ivan Warren ***@vmfacility.fr [her...<hercules><br><b>Date:&nbsp;</b>5/13/2016 7:04 AM<br><b>To:&nbsp;</b>hercules-***@yahoogroups.com;<br><b>Subject:</b>Re: [hercules-390] Installing Hercules on Debian 8<br><br>


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<span>&nbsp;</span>



<div id="ygrp-text">


<p><br>
<br>
Le 12/05/2016 &agrave; 02:41, George ***@shedlock.org [hercules-390] a &eacute;crit :<br>
&gt;<br>
&gt;<br>
&gt; After re-reading what I put in below, I realized that I made a typo on <br>
&gt; the hard wait code. It is actually 9046 which from my reading seems to <br>
&gt; be related to STFLE. I will try to install Spinhawk for a test to see <br>
&gt; if that fixes the problem.<br>
&gt;<br>
&gt; George<br>
<br>
George,<br>
<br>
There are reports of z/VM 5.3 working on spinhawk and hyperion... It's <br>
quite possible debian 8 ships with Hercules 3.07 which may not have the <br>
necessary facilities.<br>
<br>
There are also reports of people managing to run up to z/VM 6.3 (but it <br>
requires some tweaking - especially the right choice of compiler for <br>
IAF2 support).<br>
<br>
Of course this requires having your own build environment.<br>
<br>
--Ivan<br>
<br>
[Non-text portions of this message have been removed]<br>
<br>
</p>

</div>





<!-- end group email -->


</span>
</p>

</div>


<!--~-|**|PrettyHtmlStart|**|-~-->
<div style="color: #fff; height: 0;">__._,_.___</div>






<div style="clear:both"> </div>

<div id="fromDMARC" style="margin-top: 10px;">
<hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
Posted by: &quot;George&quot; &lt;***@shedlock.org&gt; <hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
</div>
<div style="clear:both"> </div>

<table cellspacing=4px style="margin-top: 10px; margin-bottom: 10px; color: #2D50FD;">
<tbody>
<tr>
<td style="font-size: 12px; font-family: arial; font-weight: bold; padding: 7px 5px 5px;" >
<a style="text-decoration: none; color: #2D50FD" href="https://groups.yahoo.com/neo/groups/hercules-390/conversations/messages/79150;_ylc=X3oDMTJwNHYwbzlrBF9TAzk3MzU5NzE0BGdycElkAzM0MjA2NARncnBzcElkAzE3MDcyODE5NDIEbXNnSWQDNzkxNTAEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxNDYzMTQzNjIx?act=reply&messageNum=79150">Reply via web post</a>
</td>
<td>&bull;</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;" >
<a href="mailto:***@shedlock.org?subject=Re%3A%20%5Bhercules-390%5D%20Installing%20Hercules%20on%20Debian%208" style="text-decoration: none; color: #2D50FD;">
Reply to sender </a>
</td>
<td>&bull;</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;">
<a href="mailto:hercules-***@yahoogroups.com?subject=Re%3A%20%5Bhercules-390%5D%20Installing%20Hercules%20on%20Debian%208" style="text-decoration: none; color: #2D50FD">
Reply to group </a>
</td>
<td>&bull;</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;" >
<a href="https://groups.yahoo.com/neo/groups/hercules-390/conversations/newtopic;_ylc=X3oDMTJka2EwZWRvBF9TAzk3MzU5NzE0BGdycElkAzM0MjA2NARncnBzcElkAzE3MDcyODE5NDIEc2VjA2Z0cgRzbGsDbnRwYwRzdGltZQMxNDYzMTQzNjIx" style="text-decoration: none; color: #2D50FD">Start a New Topic</a>
</td>
<td>&bull;</td>
<td style="font-size: 12px; font-family: arial; padding: 7px 5px 5px;color: #2D50FD;" >
<a href="https://groups.yahoo.com/neo/groups/hercules-390/conversations/topics/79146;_ylc=X3oDMTM1bTA0ZnVzBF9TAzk3MzU5NzE0BGdycElkAzM0MjA2NARncnBzcElkAzE3MDcyODE5NDIEbXNnSWQDNzkxNTAEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxNDYzMTQzNjIxBHRwY0lkAzc5MTQ2" style="text-decoration: none; color: #2D50FD;">Messages in this topic</a>
(5)
</td>
</tr>
</tbody>
</table>


<div id="megaphoneModule">
<hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
<div>
<div class="stream" style="margin-bottom:10px;">
<div style="background-color:white;">
<div class="sn-img" style="display:inline;"><img name="tn_file" style="padding:0px 10px;vertical-align:top;margin-top:5px;" src="https://s.yimg.com/ru/static/images/yg/img/megaphone/1462984467_php0t2tHG" height="82" width="82"></div>
<div class="mod-txt" style="display:inline-block;">
<a rel="nofollow" name="sub_url" target="_blank" href="https://yho.com/1wwmgg" style="color:#0000FF;display:block;margin-left:5px;text-decoration:none;"><span style="font-size:15px;">Upgrade your account with the latest Yahoo Mail app</span></a>
<div style="max-width:530px;padding:2px 5px;">Get organized with the fast and easy-to-use Yahoo Mail app. Upgrade today!</div>
</div>
</div>
</div> </div>

<hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
</div>

<!------- Start Nav Bar ------>
<!-- |**|begin egp html banner|**| -->
<!-- |**|end egp html banner|**| -->


<div id="ygrp-grfd" style="font-family: Verdana; font-size: 12px; padding: 15px 0;">

<!-- |**|begin egp html banner|**| -->

Community email addresses:<BR>
&nbsp; Post message: hercules-***@yahoogroups.com<BR>
&nbsp; Subscribe:&nbsp;&nbsp;&nbsp; hercules-390-***@yahoogroups.com<BR>
&nbsp; Unsubscribe:&nbsp; hercules-390-***@yahoogroups.com<BR>
&nbsp; List owner:&nbsp;&nbsp; hercules-390-***@yahoogroups.com<BR>
<BR>
Files and archives at:<BR>
&nbsp; <a href="http://groups.yahoo.com/group/hercules-390">http://groups.yahoo.com/group/hercules-390</a><BR>
<BR>
Get the latest version of Hercules from:<BR>
&nbsp; <a href="http://www.hercules-390.org">http://www.hercules-390.org</a><BR>
<BR>

<!-- |**|end egp html banner|**| -->

</div>




<!-- |**|begin egp html banner|**| -->
<div id="ygrp-vital" style="background-color: #f2f2f2; font-family: Verdana; font-size: 10px; margin-bottom: 10px; padding: 10px;">

<span id="vithd" style="font-weight: bold; color: #333; text-transform: uppercase; "><a href="https://groups.yahoo.com/neo/groups/hercules-390/info;_ylc=X3oDMTJkbnFlbnVsBF9TAzk3MzU5NzE0BGdycElkAzM0MjA2NARncnBzcElkAzE3MDcyODE5NDIEc2VjA3Z0bARzbGsDdmdocARzdGltZQMxNDYzMTQzNjIx" style="text-decoration: none;">Visit Your Group</a></span>

<ul style="list-style-type: none; margin: 0; padding: 0; display: inline;">
<li style="border-right: 1px solid #000; font-weight: 700; display: inline; padding: 0 5px; margin-left: 0;">
<span class="cat"><a href="https://groups.yahoo.com/neo/groups/hercules-390/members/all;_ylc=X3oDMTJlN2JuazA3BF9TAzk3MzU5NzE0BGdycElkAzM0MjA2NARncnBzcElkAzE3MDcyODE5NDIEc2VjA3Z0bARzbGsDdm1icnMEc3RpbWUDMTQ2MzE0MzYyMQ--" style="text-decoration: none;">New Members</a></span>
<span class="ct" style="color: #ff7900;">4</span>
</li>
</ul>
</div>


<div id="ft" style="font-family: Arial; font-size: 11px; margin-top: 5px; padding: 0 2px 0 0; clear: both;">
<a href="https://groups.yahoo.com/neo;_ylc=X3oDMTJjaWlqY2UwBF9TAzk3NDc2NTkwBGdycElkAzM0MjA2NARncnBzcElkAzE3MDcyODE5NDIEc2VjA2Z0cgRzbGsDZ2ZwBHN0aW1lAzE0NjMxNDM2MjI-" style="float: left;"><img src="Loading Image..." height="15" width="137" alt="Yahoo! Groups" style="border: 0;"/></a>
<div style="color: #747575; float: right;"> &bull; <a href="https://info.yahoo.com/privacy/us/yahoo/groups/details.html" style="text-decoration: none;">Privacy</a> &bull; <a href="mailto:hercules-390-***@yahoogroups.com?subject=Unsubscribe" style="text-decoration: none;">Unsubscribe</a> &bull; <a href="https://info.yahoo.com/legal/us/yahoo/utos/terms/" style="text-decoration: none;">Terms of Use</a> </div>
</div>
<br>

<!-- |**|end egp html banner|**| -->

</div> <!-- ygrp-msg -->


<!-- Sponsor -->
<!-- |**|begin egp html banner|**| -->
<div id="ygrp-sponsor" style="width:160px; float:right; clear:none; margin:0 0 25px 0; background: #fff;">

<!-- Start Recommendations -->
<div id="ygrp-reco">
</div>
<!-- End Recommendations -->



</div> <!-- |**|end egp html banner|**| -->

<div style="clear:both; color: #FFF; font-size:1px;">.</div>
</div>

<img src="http://geo.yahoo.com/serv?s=97359714/grpId=342064/grpspId=1707281942/msgId=79150/stime=1463143621" width="1" height="1"> <br>

<img src="http://y.analytics.yahoo.com/fpc.pl?ywarid=515FB27823A7407E&a=10001310322279&js=no&resp=img&cf12=CP" width="1" height="1">

<div style="color: #fff; height: 0;">__,_._,___</div>
<!--~-|**|PrettyHtmlEnd|**|-~-->

</body>

<!--~-|**|PrettyHtmlStart|**|-~-->
<head>
<style type="text/css">
<!--
#ygrp-mkp {
border: 1px solid #d8d8d8;
font-family: Arial;
margin: 10px 0;
padding: 0 10px;
}

#ygrp-mkp hr {
border: 1px solid #d8d8d8;
}

#ygrp-mkp #hd {
color: #628c2a;
font-size: 85%;
font-weight: 700;
line-height: 122%;
margin: 10px 0;
}

#ygrp-mkp #ads {
margin-bottom: 10px;
}

#ygrp-mkp .ad {
padding: 0 0;
}

#ygrp-mkp .ad p {
margin: 0;
}

#ygrp-mkp .ad a {
color: #0000ff;
text-decoration: none;
}
#ygrp-sponsor #ygrp-lc {
font-family: Arial;
}

#ygrp-sponsor #ygrp-lc #hd {
margin: 10px 0px;
font-weight: 700;
font-size: 78%;
line-height: 122%;
}

#ygrp-sponsor #ygrp-lc .ad {
margin-bottom: 10px;
padding: 0 0;
}

#actions {
font-family: Verdana;
font-size: 11px;
padding: 10px 0;
}

#activity {
background-color: #e0ecee;
float: left;
font-family: Verdana;
font-size: 10px;
padding: 10px;
}

#activity span {
font-weight: 700;
}

#activity span:first-child {
text-transform: uppercase;
}

#activity span a {
color: #5085b6;
text-decoration: none;
}

#activity span span {
color: #ff7900;
}

#activity span .underline {
text-decoration: underline;
}

.attach {
clear: both;
display: table;
font-family: Arial;
font-size: 12px;
padding: 10px 0;
width: 400px;
}

.attach div a {
text-decoration: none;
}

.attach img {
border: none;
padding-right: 5px;
}

.attach label {
display: block;
margin-bottom: 5px;
}

.attach label a {
text-decoration: none;
}

blockquote {
margin: 0 0 0 4px;
}

.bold {
font-family: Arial;
font-size: 13px;
font-weight: 700;
}

.bold a {
text-decoration: none;
}

dd.last p a {
font-family: Verdana;
font-weight: 700;
}

dd.last p span {
margin-right: 10px;
font-family: Verdana;
font-weight: 700;
}

dd.last p span.yshortcuts {
margin-right: 0;
}

div.attach-table div div a {
text-decoration: none;
}

div.attach-table {
width: 400px;
}

div.file-title a, div.file-title a:active, div.file-title a:hover, div.file-title a:visited {
text-decoration: none;
}

div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div.photo-title a:visited {
text-decoration: none;
}

div#ygrp-mlmsg #ygrp-msg p a span.yshortcuts {
font-family: Verdana;
font-size: 10px;
font-weight: normal;
}

.green {
color: #628c2a;
}

.MsoNormal {
margin: 0 0 0 0;
}

o {
font-size: 0;
}

#photos div {
float: left;
width: 72px;
}

#photos div div {
border: 1px solid #666666;
height: 62px;
overflow: hidden;
width: 62px;
}

#photos div label {
color: #666666;
font-size: 10px;
overflow: hidden;
text-align: center;
white-space: nowrap;
width: 64px;
}

#reco-category {
font-size: 77%;
}

#reco-desc {
font-size: 77%;
}

.replbq {
margin: 4px;
}

#ygrp-actbar div a:first-child {
/* border-right: 0px solid #000;*/
margin-right: 2px;
padding-right: 5px;
}

#ygrp-mlmsg {
font-size: 13px;
font-family: Arial, helvetica,clean, sans-serif;
*font-size: small;
*font: x-small;
}

#ygrp-mlmsg table {
font-size: inherit;
font: 100%;
}

#ygrp-mlmsg select, input, textarea {
font: 99% Arial, Helvetica, clean, sans-serif;
}

#ygrp-mlmsg pre, code {
font:115% monospace;
*font-size:100%;
}

#ygrp-mlmsg * {
line-height: 1.22em;
}

#ygrp-mlmsg #logo {
padding-bottom: 10px;
}


#ygrp-msg p a {
font-family: Verdana;
}

#ygrp-msg p#attach-count span {
color: #1E66AE;
font-weight: 700;
}

#ygrp-reco #reco-head {
color: #ff7900;
font-weight: 700;
}

#ygrp-reco {
margin-bottom: 20px;
padding: 0px;
}

#ygrp-sponsor #ov li a {
font-size: 130%;
text-decoration: none;
}

#ygrp-sponsor #ov li {
font-size: 77%;
list-style-type: square;
padding: 6px 0;
}

#ygrp-sponsor #ov ul {
margin: 0;
padding: 0 0 0 8px;
}

#ygrp-text {
font-family: Georgia;
}

#ygrp-text p {
margin: 0 0 1em 0;
}

#ygrp-text tt {
font-size: 120%;
}

#ygrp-vital ul li:last-child {
border-right: none !important;
}
-->
</style>
</head>

<!--~-|**|PrettyHtmlEnd|**|-~-->
</html>
<!-- end group email -->
George George@shedlock.org [hercules-390]
2016-05-13 22:48:46 UTC
Permalink
I have another question about this. What is the difference in Hercules
3.07 when run on Windoze and 3.07 when run on Debian? Is there something
that I need to add / delete from the config file to run on Debian? I run
the same config files (except for the path names to the files) and dasd
images on both systems and Windoze works, but Debian gets a hard wait.
Seems to me that Hercules should behave the same way on both systems at
the same software level.

George
Post by 'George' ***@shedlock.org [hercules-390]
Is there a set of pre-built binaries for the debian platform?
Sent from my Sprint phone.
------ Original message ------
*Date: *5/13/2016 7:04 AM
*Subject:*Re: [hercules-390] Installing Hercules on Debian 8
Post by George ***@shedlock.org [hercules-390]
After re-reading what I put in below, I realized that I made a typo on
the hard wait code. It is actually 9046 which from my reading seems to
be related to STFLE. I will try to install Spinhawk for a test to see
if that fixes the problem.
George
George,
There are reports of z/VM 5.3 working on spinhawk and hyperion... It's
quite possible debian 8 ships with Hercules 3.07 which may not have the
necessary facilities.
There are also reports of people managing to run up to z/VM 6.3 (but it
requires some tweaking - especially the right choice of compiler for
IAF2 support).
Of course this requires having your own build environment.
--Ivan
[Non-text portions of this message have been removed]
Loading...