Discussion:
Cannot connect to Hercules with telnet or x3270 via port 3270 on Ubuntu 16.04
(too old to reply)
anerlich@yahoo.com [hercules-390]
2017-09-30 07:39:11 UTC
Permalink
I have installed Hercules 3.12 and am attempting to install OS/360 MVT 21.8f per Jay Maynard's instructions at http://www.conmicro.com/hercos360/ http://www.conmicro.com/hercos360/.


I was able to use the makedasd script successfully.


I am unable to successfully connect to Hercules via either telnet or x3270 to run the IPL.


telnet gives me the introductory


Hercules version 3.12 built on Jan 4 2016 05:12:27
running on andrew-Inspiron-555 (Linux-4.4.0-83-generic.#106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 MP=4)

Connected to device 0:0009


But then remains both deaf and mute. No response to any commands.


X3270 gives me the introductory Hercules screen, but after clearing and resetting the screen goes into a permanent wait state after any input.


I can connect via port 8081.


I have made sure port 3270 is open listening and not blocked by any firewall.


Can anyone advise me on next steps to try? Is this a workable OS or should I be trying something else?


Should I try Hyperion instead?


Many thanks


Andrew Nerlich
Martin Truebner Martin@pi-sysprog.de [hercules-390]
2017-09-30 09:09:28 UTC
Permalink
Andrew,

have you started (IPLed) MVS yet?

Hercules is plain hardware (-simulation). Without any software handling
whatever comes in and producing an answer..everything (including a 3270
screen) will remain deaf+dead

Martin
anerlich@yahoo.com [hercules-390]
2017-10-01 05:45:21 UTC
Permalink
I'm not using MVS, I'm trying to install OS/360. instructions say I need to connect a console via the 3270 port to be able to enter the IPL command,

I thikn I'm going to try the MVS turnkey system instead. I'm brand new to this and sort of lumbering around in the dark.
'Dave Wade' dave.g4ugm@gmail.com [hercules-390]
2017-10-01 07:24:05 UTC
Permalink
Yes you need a terminal connected ready for the OS to use when the OS IPLs, but you enter the IPL command into the session running Hercules. That’s the HARDWARE console where you IPL Hercules.

The same applies to all Operating Systems.

The thread messages occur because Hercules is multi-threaded and doesn’t have sufficient rights to adjust the thread priorities. It will still run. You can I think run as ROOT but I wouldn’t recommend it.



Dave





From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: 01 October 2017 06:45
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Cannot connect to Hercules with telnet or x3270 via port 3270 on Ubuntu 16.04





I'm not using MVS, I'm trying to install OS/360. instructions say I need to connect a console via the 3270 port to be able to enter the IPL command,



I thikn I'm going to try the MVS turnkey system instead. I'm brand new to this and sort of lumbering around in the dark.
Giuseppe Vitillaro giuseppe@vitillaro.org [hercules-390]
2017-10-01 09:40:51 UTC
Permalink
Post by 'Dave Wade' ***@gmail.com [hercules-390]
Yes you need a terminal connected ready for the OS to use when the OS
IPLs, but you enter the IPL command into the session running Hercules.
Thatÿÿs the HARDWARE console where you IPL Hercules.
The same applies to all Operating Systems.
The thread messages occur because Hercules is multi-threaded and
doesnÿÿt have sufficient rights to adjust the thread priorities. It will
still run. You can I think run as ROOT but I wouldnÿÿt recommend it.
Not sure if the topic question is for Linux, but hercules emulator
has a really nice alternative to raise its privileges without
actually running as "root user", in linux distros.

If configured, under Linux, with "--enable-capabilities" and with
libcap, libcap-devel installed, a couple of simple commands,
not provided by "make install", let the emulator to gain at runtime,
for what I may understand, the privileges it needs to control
thread priorities and networking:

setcap cap_sys_nice+ep $PATH_HERCULES_BIN/hercules
setcap cap_net_admin+ep $PATH_HERCULES_BIN/hercifc

These "setcap" commands have to be issued as root, at emulator
installation time, after "make install", but, beside that,
the emulator may run as an unprivileged user, with the bare
minimum privileges it needs for its functions.

In a multiuser environment, the right to execute the "setcap"
binaries "hercules/hercifc" may be further restricted to a "group"
of users acting with chown/chmod on that files.

Just tested once again with the last 3.13 version, under
Gentoo, it still works for what I may see.

To the hercules developers: please, keep this feature
in future versions. It is really a nice feature ;-)

Peppe.



[Non-text portions of this message have been removed]
Dan Kalmar kalda0912@gmail.com [hercules-390]
2017-09-30 09:26:52 UTC
Permalink
When you start Hercules you can also specify an RC script for performing
the IPL.
anerlich@yahoo.com [hercules-390]
2017-10-01 05:46:06 UTC
Permalink
Thanks. I'm going to try a different OS install now anyway.
'Dave Wade' dave.g4ugm@gmail.com [hercules-390]
2017-09-30 08:32:42 UTC
Permalink
If you get those messages you have connected. It sounds like you havn’t IPL’d your operating system.



Dave



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: 30 September 2017 08:39
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Cannot connect to Hercules with telnet or x3270 via port 3270 on Ubuntu 16.04








I have installed Hercules 3.12 and am attempting to install OS/360 MVT 21.8f per Jay Maynard's instructions at http://www.conmicro.com/hercos360/.





I was able to use the makedasd script successfully.





I am unable to successfully connect to Hercules via either telnet or x3270 to run the IPL.





telnet gives me the introductory





Hercules version 3.12 built on Jan 4 2016 05:12:27

running on andrew-Inspiron-555 (Linux-4.4.0-83-generic.#106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 MP=4)

Connected to device 0:0009



But then remains both deaf and mute. No response to any commands.



X3270 gives me the introductory Hercules screen, but after clearing and resetting the screen goes into a permanent wait state after any input.



I can connect via port 8081.



I have made sure port 3270 is open listening and not blocked by any firewall.



Can anyone advise me on next steps to try? Is this a workable OS or should I be trying something else?



Should I try Hyperion instead?



Many thanks



Andrew Nerlich
anerlich@yahoo.com [hercules-390]
2017-10-01 05:43:42 UTC
Permalink
My understanding and the install instructions indicated I need to connect via 3270 after creating the DASDs to IPL the system. If I try to enter the IPL command direct into the Hercules window, it fails with an error.
Jon Perryman jperryma@pacbell.net [hercules-390]
2017-09-30 15:39:32 UTC
Permalink
Forget about telnet. Use x3270 or whatever TN3270 (3270 telnet) you desire. For the starter system, I believe you connect to 009. If you have a blank screen, you might need to press enter.
What messages do you get in the hercules screen? Also, look at the bottom line for the PSW. Does it have a small number which we call a wait state code?
I don't use the starter system. Alternatively, you could download the prebuilt TK4 system at http://wotho.ethz.ch/tk4-/ which saves you time and is more current. Be sure to look at the bottom of the page for the newest source. Since you are running under Unix, you will use the hercules you downloaded for your system.
Regards, Jon.



On Saturday, September 30, 2017 12:39 AM, "***@yahoo.com [hercules-390]" <hercules-***@yahoogroups.com> wrote:


  I have installed Hercules 3.12 and am attempting to install  OS/360 MVT 21.8f per Jay Maynard's instructions at http://www.conmicro.com/hercos360/.
I was able to use the makedasd script successfully.
I am unable to successfully connect to Hercules via either telnet or x3270 to run the IPL.
telnet gives me the introductory
Hercules version 3.12 built on Jan  4 2016 05:12:27running on andrew-Inspiron-555 (Linux-4.4.0-83-generic.#106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 MP=4)Connected to device 0:0009
But then remains both deaf and mute. No response to any commands.
X3270 gives me the introductory Hercules screen, but after clearing and resetting the screen goes into a permanent wait state after any input.
I can connect via port 8081.
I have made sure port 3270 is open listening and not blocked by any firewall.
Can anyone advise me on next steps to try? Is this a workable OS or should I be trying something else?
Should I try Hyperion instead?
Many thanks
Andrew Nerlich


  #yiv8905331462 #yiv8905331462 -- #yiv8905331462ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv8905331462 #yiv8905331462ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv8905331462 #yiv8905331462ygrp-mkp #yiv8905331462hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv8905331462 #yiv8905331462ygrp-mkp #yiv8905331462ads {margin-bottom:10px;}#yiv8905331462 #yiv8905331462ygrp-mkp .yiv8905331462ad {padding:0 0;}#yiv8905331462 #yiv8905331462ygrp-mkp .yiv8905331462ad p {margin:0;}#yiv8905331462 #yiv8905331462ygrp-mkp .yiv8905331462ad a {color:#0000ff;text-decoration:none;}#yiv8905331462 #yiv8905331462ygrp-sponsor #yiv8905331462ygrp-lc {font-family:Arial;}#yiv8905331462 #yiv8905331462ygrp-sponsor #yiv8905331462ygrp-lc #yiv8905331462hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv8905331462 #yiv8905331462ygrp-sponsor #yiv8905331462ygrp-lc .yiv8905331462ad {margin-bottom:10px;padding:0 0;}#yiv8905331462 #yiv8905331462actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv8905331462 #yiv8905331462activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv8905331462 #yiv8905331462activity span {font-weight:700;}#yiv8905331462 #yiv8905331462activity span:first-child {text-transform:uppercase;}#yiv8905331462 #yiv8905331462activity span a {color:#5085b6;text-decoration:none;}#yiv8905331462 #yiv8905331462activity span span {color:#ff7900;}#yiv8905331462 #yiv8905331462activity span .yiv8905331462underline {text-decoration:underline;}#yiv8905331462 .yiv8905331462attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv8905331462 .yiv8905331462attach div a {text-decoration:none;}#yiv8905331462 .yiv8905331462attach img {border:none;padding-right:5px;}#yiv8905331462 .yiv8905331462attach label {display:block;margin-bottom:5px;}#yiv8905331462 .yiv8905331462attach label a {text-decoration:none;}#yiv8905331462 blockquote {margin:0 0 0 4px;}#yiv8905331462 .yiv8905331462bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv8905331462 .yiv8905331462bold a {text-decoration:none;}#yiv8905331462 dd.yiv8905331462last p a {font-family:Verdana;font-weight:700;}#yiv8905331462 dd.yiv8905331462last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv8905331462 dd.yiv8905331462last p span.yiv8905331462yshortcuts {margin-right:0;}#yiv8905331462 div.yiv8905331462attach-table div div a {text-decoration:none;}#yiv8905331462 div.yiv8905331462attach-table {width:400px;}#yiv8905331462 div.yiv8905331462file-title a, #yiv8905331462 div.yiv8905331462file-title a:active, #yiv8905331462 div.yiv8905331462file-title a:hover, #yiv8905331462 div.yiv8905331462file-title a:visited {text-decoration:none;}#yiv8905331462 div.yiv8905331462photo-title a, #yiv8905331462 div.yiv8905331462photo-title a:active, #yiv8905331462 div.yiv8905331462photo-title a:hover, #yiv8905331462 div.yiv8905331462photo-title a:visited {text-decoration:none;}#yiv8905331462 div#yiv8905331462ygrp-mlmsg #yiv8905331462ygrp-msg p a span.yiv8905331462yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv8905331462 .yiv8905331462green {color:#628c2a;}#yiv8905331462 .yiv8905331462MsoNormal {margin:0 0 0 0;}#yiv8905331462 o {font-size:0;}#yiv8905331462 #yiv8905331462photos div {float:left;width:72px;}#yiv8905331462 #yiv8905331462photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv8905331462 #yiv8905331462photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv8905331462 #yiv8905331462reco-category {font-size:77%;}#yiv8905331462 #yiv8905331462reco-desc {font-size:77%;}#yiv8905331462 .yiv8905331462replbq {margin:4px;}#yiv8905331462 #yiv8905331462ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv8905331462 #yiv8905331462ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv8905331462 #yiv8905331462ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv8905331462 #yiv8905331462ygrp-mlmsg select, #yiv8905331462 input, #yiv8905331462 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv8905331462 #yiv8905331462ygrp-mlmsg pre, #yiv8905331462 code {font:115% monospace;}#yiv8905331462 #yiv8905331462ygrp-mlmsg * {line-height:1.22em;}#yiv8905331462 #yiv8905331462ygrp-mlmsg #yiv8905331462logo {padding-bottom:10px;}#yiv8905331462 #yiv8905331462ygrp-msg p a {font-family:Verdana;}#yiv8905331462 #yiv8905331462ygrp-msg p#yiv8905331462attach-count span {color:#1E66AE;font-weight:700;}#yiv8905331462 #yiv8905331462ygrp-reco #yiv8905331462reco-head {color:#ff7900;font-weight:700;}#yiv8905331462 #yiv8905331462ygrp-reco {margin-bottom:20px;padding:0px;}#yiv8905331462 #yiv8905331462ygrp-sponsor #yiv8905331462ov li a {font-size:130%;text-decoration:none;}#yiv8905331462 #yiv8905331462ygrp-sponsor #yiv8905331462ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv8905331462 #yiv8905331462ygrp-sponsor #yiv8905331462ov ul {margin:0;padding:0 0 0 8px;}#yiv8905331462 #yiv8905331462ygrp-text {font-family:Georgia;}#yiv8905331462 #yiv8905331462ygrp-text p {margin:0 0 1em 0;}#yiv8905331462 #yiv8905331462ygrp-text tt {font-size:120%;}#yiv8905331462 #yiv8905331462ygrp-vital ul li:last-child {border-right:none !important;}#yiv8905331462
anerlich@yahoo.com [hercules-390]
2017-10-01 05:36:44 UTC
Permalink
Pressing enter doesn't seem to do either the on-screen keypad with x3270 or the Enter key on my keyboard.

I get no on-screen messages that indicate any problem. The connection appears to be successful, and the connection aappares in the Hercules startup window.


If by the PSW, you mean the hex numerals in the extreme lower left, they are 4A. If that is a wait code, it indicates a problem with the TOD clock.


I noticed that I am getting the following messages during Hercules startup:


HHCTT001W Timer thread set priority -20 failed: Permission denied
HHCTT002I Timer thread started: tid=7F8CFB9F0700, pid=23911, priority=0


Maybe I need to sort that out.


I think I'll follow for your suggestion and try the Turnkey MVS system. I haven't worked on mainframes since the early 1990s and was never a systems programmer. If I'm still having connection problems then, maybe I'll try Windows instead.


Thanks for the reply!


Andrew
Joe Monk joemonk64@gmail.com [hercules-390]
2017-10-01 11:52:39 UTC
Permalink
Andrew,

Let me clear up something for you.

Connecting to Hercules is NOT connecting to the OS!!!

Hercules is the hardware ... just like you have a terminal connected to a
CU, until you IPL the OS there will be no response from the terminal, but
the terminal will still show "connected" to the hardware.

Since you stated that you are running OS/360, the way to IPL that OS on
real hardware was to set the IPL address on the console dials and then
press the IPL button...

In hercules you simulate that action by typing "IPL XXX" into the hercules
shell window, where XXX = the address your SYSRES volume. If you were using
Kevin Leonard's prebuilt OS/360, the correct address is 150. So you would
type IPL 150 into the hercules shell in order to bring up OS/360.

However, OS/360 has a requirement that the operators console be connected
BEFORE IPL. So, to do that, you telnet 127.0.0.1 to port 3270 (instead of
the normal 23). This connects your telnet session to the hercules HARDWARE.

Once you IPL the hardware, then your telnet session will come to life, as
you expect.

Joe
Post by ***@yahoo.com [hercules-390]
Pressing enter doesn't seem to do either the on-screen keypad with x3270
or the Enter key on my keyboard.
I get no on-screen messages that indicate any problem. The connection
appears to be successful, and the connection aappares in the Hercules
startup window.
If by the PSW, you mean the hex numerals in the extreme lower left, they
are 4A. If that is a wait code, it indicates a problem with the TOD clock.
HHCTT001W Timer thread set priority -20 failed: Permission denied
HHCTT002I Timer thread started: tid=7F8CFB9F0700, pid=23911, priority=0
Maybe I need to sort that out.
I think I'll follow for your suggestion and try the Turnkey MVS system. I
haven't worked on mainframes since the early 1990s and was never a systems
programmer. If I'm still having connection problems then, maybe I'll try
Windows instead.
Thanks for the reply!
Andrew
Mike Schwab Mike.A.Schwab@gmail.com [hercules-390]
2017-10-02 11:59:43 UTC
Permalink
As part of building the volumes, you should have created a script file
which includes the DASD, other devices, and you IPL command. You need to
run that script with administrator rights
Post by Martin Truebner ***@pi-sysprog.de [hercules-390]
Andrew,
Let me clear up something for you.
Connecting to Hercules is NOT connecting to the OS!!!
Hercules is the hardware ... just like you have a terminal connected to a
CU, until you IPL the OS there will be no response from the terminal, but
the terminal will still show "connected" to the hardware.
Since you stated that you are running OS/360, the way to IPL that OS on
real hardware was to set the IPL address on the console dials and then
press the IPL button...
In hercules you simulate that action by typing "IPL XXX" into the hercules
shell window, where XXX = the address your SYSRES volume. If you were using
Kevin Leonard's prebuilt OS/360, the correct address is 150. So you would
type IPL 150 into the hercules shell in order to bring up OS/360.
However, OS/360 has a requirement that the operators console be connected
BEFORE IPL. So, to do that, you telnet 127.0.0.1 to port 3270 (instead of
the normal 23). This connects your telnet session to the hercules HARDWARE.
Once you IPL the hardware, then your telnet session will come to life, as
you expect.
Joe
Post by ***@yahoo.com [hercules-390]
Pressing enter doesn't seem to do either the on-screen keypad with x3270
or the Enter key on my keyboard.
I get no on-screen messages that indicate any problem. The connection
appears to be successful, and the connection aappares in the Hercules
startup window.
If by the PSW, you mean the hex numerals in the extreme lower left, they
are 4A. If that is a wait code, it indicates a problem with the TOD clock.
HHCTT001W Timer thread set priority -20 failed: Permission denied
HHCTT002I Timer thread started: tid=7F8CFB9F0700, pid=23911, priority=0
Maybe I need to sort that out.
I think I'll follow for your suggestion and try the Turnkey MVS system. I
haven't worked on mainframes since the early 1990s and was never a systems
programmer. If I'm still having connection problems then, maybe I'll try
Windows instead.
Thanks for the reply!
Andrew
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
anerlich@yahoo.com [hercules-390]
2017-10-03 06:29:24 UTC
Permalink
Thanks all. I decided to cut my losses and installed the MVS turnkey system. No problems whatsoever.
Continue reading on narkive:
Loading...