[hercules-390] No listener on Hercules on Ubuntu 16.04?

[VanVleet [e-mail] [hercules-390]]

I just installed Hercules on Ubuntu 16.04, using the cmake build
instructions on the website (hercules-390.github.io/html/CMake/index.html).
Everything seemed to have worked fine and Hercules starts up fine (as best
I can tell?) but when I try to connect via c3270, I get connection refused.
Looking at netstat, nothing is listening on 3270, and Hercules isn't
listening anywhere. My hercules.cnf (just the default one) has the line:

CNSLPORT 3270

Help?!?

Thanks!
-Andrew

[Gerhard Postpischil [e-mail] [hercules-390]]

Post by VanVleet ***@gmail.com [hercules-390]
I just installed Hercules on Ubuntu 16.04, using the cmake build
instructions on the website
(hercules-390.github.io/html/CMake/index.html
<http://hercules-390.github.io/html/CMake/index.html>). Everything
seemed to have worked fine and Hercules starts up fine (as best I can
tell?) but when I try to connect via c3270, I get connection refused.
Looking at netstat, nothing is listening on 3270, and Hercules isn't
CNSLPORT 3270

My understanding is that you need a device definition for each I/O
device, and you may need additional ones for flavor (370 vs. 390 vs.
zOS), amount of memory, and max and desired number of CPUs.

Gerhard Postpischil
Bradford, VT

---
This email has been checked for viruses by AVG.
http://www.avg.com

[Ivan Warren [e-mail] [hercules-390]]

Post by VanVleet ***@gmail.com [hercules-390]
I just installed Hercules on Ubuntu 16.04, using the cmake build
instructions on the website
(hercules-390.github.io/html/CMake/index.html
<http://hercules-390.github.io/html/CMake/index.html>). Everything
seemed to have worked fine and Hercules starts up fine (as best I can
tell?) but when I try to connect via c3270, I get connection refused.
Looking at netstat, nothing is listening on 3270, and Hercules isn't
CNSLPORT 3270

Maybe showing us the log of hercules startup would help ! Maybe
something prevents hercules from listening on port 3270 ? (SELinux maybe ?)

If the listen (or rather the bind(2) system call didn't work - and it
would show in the log)

--Ivan


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

[Mike Stramba [e-mail] [hercules-390]]

Post by VanVleet ***@gmail.com [hercules-390]
I just installed Hercules on Ubuntu 16.04, using the cmake build
instructions on the website (hercules-390.github.io/html/CMake/index.html).
Everything seemed to have worked fine and Hercules starts up fine (as best
I can tell?) but when I try to connect via c3270, I get connection refused.
Looking at netstat, nothing is listening on 3270, and Hercules isn't
CNSLPORT 3270

What's in the rest of the hercules.cnf ?

What version of Hercules are your running (type the 'version' command).

You need at least one 3270 device definition e.g. :

# address devtype
0010 3270

What O.S, (if any) are you planning on running?

Mike

Post by VanVleet ***@gmail.com [hercules-390]
Help?!?
Thanks!
-Andrew

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

[...]

Post by VanVleet ***@gmail.com [hercules-390]
Help?!?

Gremlins?

[Gregg Levine [e-mail] [hercules-390]]

Hello!
No actually Fish those gremlins arranged for it to snow all over where you are.

Seriously though,.to best assist you, we need more information. What
are you planning on running, and what did you do besides building it
using those instructions.

And incidentally we know that Vanya had absolutely nothing to with
your problems. However those same gremlins are arranging one where you
are though.
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."


On Wed, Dec 27, 2017 at 9:25 PM, ''Fish' (David B. Trout)'

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
[...]

Post by VanVleet ***@gmail.com [hercules-390]
Help?!?

Gremlins?
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
------------------------------------
------------------------------------

[Harold Grovesteen [e-mail] [hercules-390]]

Post by VanVleet ***@gmail.com [hercules-390]
I just installed Hercules on Ubuntu 16.04, using the cmake build
instructions on the website (hercules-
390.github.io/html/CMake/index.html). Everything seemed to have
worked fine and Hercules starts up fine (as best I can tell?) but
when I try to connect via c3270, I get connection refused. Looking at
netstat, nothing is listening on 3270, and Hercules isn't listening
CNSLPORT 3270
Help?!?
Thanks!
-Andrew 
 

The CNSLPORT command identifies the TCP port on which the built-in
TN3270 server will listen.  It does not actually cause the TN3270
server to be started.  One or more 3270 device definitions in the
configuration file actually triggers the starting of the server.

See Mike Stramba's post.

Harold Grovesteen

[VanVleet [e-mail] [hercules-390]]

Thanks for all the responses! I'll try to sum up here:

Ivan: What's the default startup log file? I'll pull it and see if there's
some hint there.

Mike/Harold: I'm starting with baby steps... I haven't worried about which
OS I'll run yet, because I couldn't get Herc up and running yet. ;o) I'm
literally using the default .cnf file from Github:
https://github.com/hercules-390/hyperion/blob/master/hercules.cnf. By
default, it looks like it's z/Arch, so let's just start with that? (I am
aware that I'll have to pick an OS soon and that there are licensing issues
with some.) I do see the line "001F 3270" to define one 3270 device (at
line 101 in the github file). I am running v4.0.0 of Hercules (I just
cloned the github repo, so it should be the latest committed version).

Thank you!
Andrew

Post by Harold Grovesteen ***@tx.rr.com [hercules-390]

Post by VanVleet ***@gmail.com [hercules-390]
I just installed Hercules on Ubuntu 16.04, using the cmake build
instructions on the website (hercules-
390.github.io/html/CMake/index.html). Everything seemed to have
worked fine and Hercules starts up fine (as best I can tell?) but
when I try to connect via c3270, I get connection refused. Looking at
netstat, nothing is listening on 3270, and Hercules isn't listening
CNSLPORT 3270
Help?!?
Thanks!
-Andrew

The CNSLPORT command identifies the TCP port on which the built-in
TN3270 server will listen. It does not actually cause the TN3270
server to be started. One or more 3270 device definitions in the
configuration file actually triggers the starting of the server.
See Mike Stramba's post.
Harold Grovesteen

[Ivan Warren [e-mail] [hercules-390]]

Post by VanVleet ***@gmail.com [hercules-390]
Ivan: What's the default startup log file? I'll pull it and see if
there's some hint there.

Andrew,

Just redirect output (hercules > log.txt). This will redirect a copy of
the log to the specified file which you can then examine afterwards.
For any other use (for example if you need to get the log past a certain
point, you can use the 'log' command (log filename).

One of the side effect of having the log file sent to a file is that the
console logger will not drop messages (at the possible expense of
slowing down hercules during operations which can be quite verbose
especially with "ostailor none" since it will show all program
exceptions - even those that are expected such as page faults).

--Ivan


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

[VanVleet [e-mail] [hercules-390]]

Here's the startup log and netstat results.

Post by Ivan Warren ***@vmfacility.fr [hercules-390]

Post by VanVleet ***@gmail.com [hercules-390]
Ivan: What's the default startup log file? I'll pull it and see if
there's some hint there.

Andrew,
Just redirect output (hercules > log.txt). This will redirect a copy of
the log to the specified file which you can then examine afterwards.
For any other use (for example if you need to get the log past a certain
point, you can use the 'log' command (log filename).
One of the side effect of having the log file sent to a file is that the
console logger will not drop messages (at the possible expense of
slowing down hercules during operations which can be quite verbose
especially with "ostailor none" since it will show all program
exceptions - even those that are expected such as page faults).
--Ivan
[Non-text portions of this message have been removed]

----------

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:51413 *:* LISTEN 6036/transmission-g
tcp 0 0 MWZ64LIN1:domain *:* LISTEN 980/dnsmasq
tcp 0 0 localhost:ipp *:* LISTEN 7390/cupsd
tcp 0 0 192.168.20.200:46562 151.101.1.147:http ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:51522 iad30s08-in-f131.:https ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:39682 iad30s08-in-f133.:https ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:58976 iad30s07-in-f4.1e:https ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:56092 iad30s08-in-f13.1:https ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:46560 151.101.1.147:http ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:39436 iad30s08-in-f142.1:http TIME_WAIT -
tcp 0 85 192.168.20.200:53865 96-18-173-96.cpe.:33574 ESTABLISHED 6036/transmission-g
tcp 0 0 192.168.20.200:39430 iad30s08-in-f142.1:http TIME_WAIT -
tcp 0 0 192.168.20.200:53352 server-52-84-85-2:https ESTABLISHED 5847/firefox
tcp 0 203 192.168.20.200:56790 ec2-52-25-153-217:https ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:39428 iad30s08-in-f142.1:http TIME_WAIT -
tcp 0 544 192.168.20.200:43011 this-is-hosted-by:61864 ESTABLISHED 6036/transmission-g
tcp 0 0 192.168.20.200:39432 iad30s08-in-f142.1:http TIME_WAIT -
tcp 0 0 192.168.20.200:46558 151.101.1.147:http TIME_WAIT -
tcp 0 0 192.168.20.200:39434 iad30s08-in-f142.1:http TIME_WAIT -
tcp 0 0 192.168.20.200:46556 151.101.1.147:http TIME_WAIT -
tcp 0 0 192.168.20.200:46248 iad30s14-in-f3.1e:https ESTABLISHED 5847/firefox
tcp 0 0 192.168.20.200:50982 iad30s14-in-f14.1:https ESTABLISHED 5847/firefox
tcp 0 612 192.168.20.200:53025 ns520378.ip-198-2:51413 ESTABLISHED 6036/transmission-g
tcp6 0 0 [::]:51413 [::]:* LISTEN 6036/transmission-g
tcp6 0 0 ip6-localhost:ipp [::]:* LISTEN 7390/cupsd
udp 0 0 *:ipp *:* 7391/cups-browsed
udp 0 0 *:50918 *:* 827/avahi-daemon: r
udp 0 0 192.168.20.200:60152 192.168.20.1:5351 ESTABLISHED 6036/transmission-g
udp 0 0 *:36646 *:* 980/dnsmasq
udp 0 0 MWZ64LIN1:domain *:* 980/dnsmasq
udp 0 0 *:51413 *:* 6036/transmission-g
udp 0 0 *:mdns *:* 827/avahi-daemon: r
udp6 0 0 [::]:48141 [::]:* 827/avahi-daemon: r
udp6 0 0 [::]:mdns [::]:* 827/avahi-daemon: r
raw6 0 0 [::]:ipv6-icmp [::]:* 7 822/NetworkManager


----------

09:41:27 HHC01413I Hercules version 4.0.0 (4.0.0.8806)
09:41:27 HHC01414I (C) Copyright 1999-2016 by Roger Bowler, Jan Jaeger, and others
09:41:27 HHC01414I Commit 438faa9.
09:41:27 HHC01414I After commit: 0 added/modified/deleted files. 0 untracked files.
09:41:27 HHC01415I Build date: Dec 27 2017 at 11:21:14
09:41:27 HHC01417I Built with: GCC 5.4.0 20160609
09:41:27 HHC01417I Build type: GNU/Linux x86_64 host architecture build
09:41:27 HHC01417I Modes: S/370 ESA/390 z/Arch
09:41:27 HHC01417I Max CPU Engines: 128
09:41:27 HHC01417I Using setresuid() for setting privileges
09:41:27 HHC01417I Using POSIX threads Threading Model
09:41:27 HHC01417I Using Error-Checking Mutex Locking Model
09:41:27 HHC01417I With Syncio support
09:41:27 HHC01417I With Shared Devices support
09:41:27 HHC01417I With Dynamic loading support
09:41:27 HHC01417I Using shared libraries
09:41:27 HHC01417I With External GUI support
09:41:27 HHC01417I With IPV6 support
09:41:27 HHC01417I With HTTP Server support
09:41:27 HHC01417I With IEEE 754 binary floating point support
09:41:27 HHC01417I With SIGABEND handler
09:41:27 HHC01417I Without CCKD BZIP2 support
09:41:27 HHC01417I Without HET BZIP2 support
09:41:27 HHC01417I Without ZLIB support
09:41:27 HHC01417I With Regular Expressions support
09:41:27 HHC01417I Without Object REXX support
09:41:27 HHC01417I With Regina REXX support
09:41:27 HHC01417I With Automatic Operator support
09:41:27 HHC01417I Without National Language Support
09:41:27 HHC01417I Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8 hatomics=C11
09:41:27 HHC01417I Running on: MWZ64LIN1 (Linux-4.10.0-28-generic x86_64) MP=2
09:41:27 HHC01508I HDL: loadable module directory is /usr/local/bin
09:41:27 HHC00150I Crypto module loaded (c) Copyright 2003-2016 by Bernard van der Helm
09:41:27 HHC00151I Activated facility: Message Security Assist
09:41:27 HHC00151I Activated facility: Message Security Assist Extension 1, 2, 3 and 4
09:41:27 HHC00100I Thread id 00007fb24fbd1700, prio 2147483647, name Processor CP00 started
09:41:27 HHC00100I Thread id 00007fb24fad0700, prio 2147483647, name Timer started
09:41:27 HHC00811I Processor CP00: architecture mode z/Arch
09:41:27 HHC00100I Thread id 00007fb256523740, prio 2147483647, name Control panel started


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

[Mike Stramba [e-mail] [hercules-390]]

Post by VanVleet ***@gmail.com [hercules-390]
Here's the startup log and netstat results.
09:41:27 HHC01413I Hercules version 4.0.0 (4.0.0.8806)
09:41:27 HHC01414I (C) Copyright 1999-2016 by Roger Bowler, Jan Jaeger, and others
09:41:27 HHC01414I Commit 438faa9.

<snip>

You are running version 4.00 / Hyperion branch.

(versus the "official" version 3.13 Spinhawk).

I suspect you have Hercules in your path, but you are starting it from
a directory that does NOT contain the hercules.cnf file ?

Hyperion 4.0 will happily start WITHOUT a hercules.cnf, while 3.13 /
Spinhawk will issue an error message and quit.

But the hercules.cnf file is only used FROM THE DIRECTORY THAT YOU
START HERCULES FROM .

Second possiblity is that you ARE starting Hercules in the same
directory as the hercules.cnf file but all device definitions have
been commented out. Again Hyperion 4.0 will start, 3.13 / Spinhawk
will issue an error message ("HHCCF004S No device records in file
hercules.cnf).

Issue a DEVLIST command (or you can put it in a "hercules.rc" file ..
in the same directory that you start Hercules from. Hercules will
run any commands found in the herucles,rc

**Hyperion 4.0 will run commands found in the *hercules.cnf* file as well

So you could put a DEVLIST (or) DEVLIST DSP in your hercules.cnf
(or hercules.rc file)
( 3.13. / Spinhawak does NOT allow *commands* in the hercules.cnf file)


Mike

[Mike Stramba [e-mail] [hercules-390]]

On 12/28/17, VanVleet ***@gmail.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:

(I am aware that I'll have to pick an OS soon and that there are
licensing issues
with some.)

Well you don't *have* to pick ANY O.S ;)

Depending on your interest / background, you might just start with the
IBM Principles of Operation manual (good idea to get them even if you
are running an OS, and plan to do any Assembler programming), and run
some "bare metal" ("hardware only") programs.

The P.O.P manuals can be found here :

390 PrinOps
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/download/dz9ar006.pdf?ACTION=SAVE&DT=19990630131355

370 PrinOps
http://bitsavers.org/pdf/ibm/370/princOps/GA22-7000-10_370_Principles_of_Operation_Sep87.pdf

zarch prinops
http://linuxmain.blogspot.ca/2012/09/zarchitecture-principles-of-operation.html

Harold Grovesteen has a very nice product called SATK ("Stand-Alone Took Kit"):
https://github.com/s390guy/SATK

Tommy Sprinkle has a site showing how to write your own 370 based O.S. :
http://www.txxos.com/

If you are as "patient" / (crazy) as me, you can even use the
hercules "r" (alter storage) command to "poke" in raw hex opcodes.
For a *slightly* less primitive approach, you could put them in a
file, and execute them using the SCRIPT command.

Here's a "hello world" to a 3215 / 1052 device (

---- hercules.cnf -----
PANTITLE "IPL 370"
CNSLPORT 370

# ---- minimum entries for Hercules 3.13 (works on Hyperion as well)
ARCHMODE S/370
NUMCPU 1 # Number of CPUs

0009 3215
------------------------------

load the following script with SCRIPT hello-world.sc (at hercules
console or hercules.rc)

----- hello-world.sc----
r 00=0008000000000200 #370 RESTART enhanced PSW address=0200
r 10=000A00000000BEEF #370 wait psw
#
r 200=41200270 # LA 2,624(0,0) get the CCW address
r 204=50200048 # ST 2,72(0,0) store it in the CAW
r 208=9C000009 # SIO 9(0) start the I/O
r 20c=82000010 # LPSW 16(0) load a wait psw
#
# CCW for write to 3215 / 1052 device
r 270=0900029000000050
#
r 290=C8C5D3D3D6 # HELLO
r 295=40E6D6D9D3C4 # WORLD

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

Mike

[VanVleet [e-mail] [hercules-390]]

Thank you, Mike! You nailed it. I was running Hercules from the default
install directory, and didn't realize it would happily start up without a
config file. When I specified a config file, everything is working great.
The giveaway was that my startup log didn't show it was parsing a config.
Hurray!

And thanks for the resources to start learning! Really appreciate it!
Time to get started on the good stuff!


Take care,

-Andrew

Post by Mike Stramba ***@gmail.com [hercules-390]
(I am aware that I'll have to pick an OS soon and that there are
licensing issues
with some.)
Well you don't *have* to pick ANY O.S ;)
Depending on your interest / background, you might just start with the
IBM Principles of Operation manual (good idea to get them even if you
are running an OS, and plan to do any Assembler programming), and run
some "bare metal" ("hardware only") programs.
390 PrinOps
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/download/dz9ar006.pdf?ACTION=SAVE&DT=19990630131355
370 PrinOps
http://bitsavers.org/pdf/ibm/370/princOps/GA22-7000-10_370_Principles_of_Operation_Sep87.pdf
zarch prinops
http://linuxmain.blogspot.ca/2012/09/zarchitecture-principles-of-operation.html
https://github.com/s390guy/SATK
http://www.txxos.com/
If you are as "patient" / (crazy) as me, you can even use the
hercules "r" (alter storage) command to "poke" in raw hex opcodes.
For a *slightly* less primitive approach, you could put them in a
file, and execute them using the SCRIPT command.
Here's a "hello world" to a 3215 / 1052 device (
---- hercules.cnf -----
PANTITLE "IPL 370"
CNSLPORT 370
# ---- minimum entries for Hercules 3.13 (works on Hyperion as well)
ARCHMODE S/370
NUMCPU 1 # Number of CPUs
0009 3215
------------------------------
load the following script with SCRIPT hello-world.sc (at hercules
console or hercules.rc)
----- hello-world.sc----
r 00=0008000000000200 #370 RESTART enhanced PSW address=0200
r 10=000A00000000BEEF #370 wait psw
#
r 200=41200270 # LA 2,624(0,0) get the CCW address
r 204=50200048 # ST 2,72(0,0) store it in the CAW
r 208=9C000009 # SIO 9(0) start the I/O
r 20c=82000010 # LPSW 16(0) load a wait psw
#
# CCW for write to 3215 / 1052 device
r 270=0900029000000050
#
r 290=C8C5D3D3D6 # HELLO
r 295=40E6D6D9D3C4 # WORLD
-----------------------
Mike

[Mike Stramba [e-mail] [hercules-390]]

Post by VanVleet ***@gmail.com [hercules-390]
Thank you, Mike! You nailed it. I was running Hercules from the default
install directory, and didn't realize it would happily start up without a
config file. When I specified a config file, everything is working great.
The giveaway was that my startup log didn't show it was parsing a config.
Hurray!

Great !

Post by VanVleet ***@gmail.com [hercules-390]
But the hercules.cnf file is only used FROM THE DIRECTORY THAT YOU
START HERCULES FROM .

You can actually start Hercules from *any* directory (even if there is
NOT a "hercules.cnf" in that directory), with the "-f <config file"
option. And the file doesn't even need to be called "hercules.cnf',
if using the -f option.

I forgot about that option ... because I never use it ;) (I always
start Hercules from the directory where the hercules.cnf is located.

Maybe you are already using that ? ,, since you wrote "when I
specified a config file"

Mike

Happy New Year ;)

Post by VanVleet ***@gmail.com [hercules-390]
And thanks for the resources to start learning! Really appreciate it!
Time to get started on the good stuff!
Take care,
-Andrew

Post by Mike Stramba ***@gmail.com [hercules-390]
(I am aware that I'll have to pick an OS soon and that there are
licensing issues
with some.)
Well you don't *have* to pick ANY O.S ;)
Depending on your interest / background, you might just start with the
IBM Principles of Operation manual (good idea to get them even if you
are running an OS, and plan to do any Assembler programming), and run
some "bare metal" ("hardware only") programs.
390 PrinOps
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/download/dz9ar006.pdf?ACTION=SAVE&DT=19990630131355
370 PrinOps
http://bitsavers.org/pdf/ibm/370/princOps/GA22-7000-10_370_Principles_of_Operation_Sep87.pdf
zarch prinops
http://linuxmain.blogspot.ca/2012/09/zarchitecture-principles-of-operation.html
https://github.com/s390guy/SATK
http://www.txxos.com/
If you are as "patient" / (crazy) as me, you can even use the
hercules "r" (alter storage) command to "poke" in raw hex opcodes.
For a *slightly* less primitive approach, you could put them in a
file, and execute them using the SCRIPT command.
Here's a "hello world" to a 3215 / 1052 device (
---- hercules.cnf -----
PANTITLE "IPL 370"
CNSLPORT 370
# ---- minimum entries for Hercules 3.13 (works on Hyperion as well)
ARCHMODE S/370
NUMCPU 1 # Number of CPUs
0009 3215
------------------------------
load the following script with SCRIPT hello-world.sc (at hercules
console or hercules.rc)
----- hello-world.sc----
r 00=0008000000000200 #370 RESTART enhanced PSW address=0200
r 10=000A00000000BEEF #370 wait psw
#
r 200=41200270 # LA 2,624(0,0) get the CCW address
r 204=50200048 # ST 2,72(0,0) store it in the CAW
r 208=9C000009 # SIO 9(0) start the I/O
r 20c=82000010 # LPSW 16(0) load a wait psw
#
# CCW for write to 3215 / 1052 device
r 270=0900029000000050
#
r 290=C8C5D3D3D6 # HELLO
r 295=40E6D6D9D3C4 # WORLD
-----------------------
Mike

[Rahim Azizarab [e-mail] [hercules-390]]

 (x3270 -model 3279-2-E -once 127.0.0.1:3270&)
 you may want to try the above command to see if it resolves the problem. 
regards;

Rahim Azizarab