开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

[hercules-390] HIM Support for Hercules 4.8


 

开云体育

I just submitted a pull request for the HIM code. I'm sure there will be issues with it. I'll fix them as soon as I can, but note that I will be out of town with limited network access from this Monday (Oct 28) through November 17.

The source branch for the pull is MTS-HIM-device on my fork at git@...:mtalexander/SDL-hyperion.git.

Mike

On 30 Sep 2024, at 10:39, John Palmer wrote:

Just wondering about the status of the code merge for Hercules.?
?
Are there still unresolved issues with getting the HIM code to work with modern Hercules???
?
If the current code with HIM support is available in a GIT repository somewhere, I'd be willing to take a look at it.? I've done C/C++ programming in the past
?
John
(also posted to H390-MTS)


 

Thanks for your effort on this,? Mike.? I'm sure just about everything else takes precedence over this.?
?
John


 

Looks like your pull request has been committed to the development branch of Hercules.
?
It looks like the d6.0 distribution has support for TCP/IP. The Telnet manager is running (*TCM file job).??
?
Do you have the proper settings for the hercules.cnf to activate the HIM code for d6.0???
?
I know the? TCP/IP support in d6.0 is primitive, but I'd like to play around with it.
?
Thanks


 

John Palmer wrote:

[...]
Do you have the proper settings for the hercules.cnf to activate
the HIM code for d6.0?
Hi John!

While Mike would certainly be the person to provide a definitive answer to that, I believe I might be able to help you, having reviewed his code before having approved it for inclusion into Hercules.

If you take a look at "Supported Device Types" table on our Configuration File web page (), you will see there are three new device types that are now supported: TLNT, TCPH and UDPH.

While I have no idea what the difference is between the three (since I know absolutely *nothing* about MTS!), if you click on the link provided in the "Emulated by" column, it should take you to:

*

where it states:

"These device types emulate the Host Interface Machine (HIM)
devices that are used to connect a host running The Michigan
Terminal System (MTS) to the Internet. The device type (TLNT,
TCPH, or UDPH) should match the device type configured into MTS."

"The only parameter is the IP address the emulated interface
should bind to."


So simply defining one or more of those devices in your Hercules configuration files looks like all you need to activate the new HIM code. Herc's sample configuration even lists three examples:

621-62B UDPH 10.0.0.46
62C-643 TLNT 10.0.0.46
644-64F TCPH 10.0.0.46

As I said, I don't know the particulars regarding which type to use nor how many of them you need to define (since that's an MTS thing), I suspect anyone familiar with MTS, such as you, would know.

Hope that helps!


I know the TCP/IP support in d6.0 is primitive, but I'd like to
play around with it.
So would I! But I know absolutely NOTHING about MTS, and unfortunately don't really have the time to learn it. :(

(That's the drawback of being a Hercules developer: you spend all your time working on Hercules with no free time left over to actually PLAY with Hercules! It's you Hercules users that get to have all the fun.)

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...


 

开云体育

Fish's description is correct, but unfortunately it's only half the story. It wxplains how to configure HIM support in Hercules, but you also have to configure it in MTS. The D6.0 MTS device configuration doesn't contain any HIM devices. This is because we (perhaps incorrectly) didn't think that the D6 version of MTS supported them. I was surprised to discover recently that there is a version of the HIM code on the D6 tapes, but I don't know to what extent it works. We could, of corse, find out, but I'd rather spend my time working on getting the 1996 system out than tweaking D6.0.

The three types of HIM devices are all the same in Hercules. TheMTS device type is used to select the appropriate DSP for the connection (Telnet, TCP, or UDP). While you can use the MTS Mount command to allocate one of these, this is not usually necessary since the command you are using allocates them implicitly. For example the FTP command allocates various TCP and Telnet devices as appropriate.

Mike

On 29 Jan 2025, at 22:38, Fish Fish via groups.io wrote:

John Palmer wrote:

[...]

Do you have the proper settings for the hercules.cnf to activate
the HIM code for d6.0?

Hi John!

While Mike would certainly be the person to provide a definitive answer to that, I believe I might be able to help you, having reviewed his code before having approved it for inclusion into Hercules.

If you take a look at "Supported Device Types" table on our Configuration File web page (), you will see there are three new device types that are now supported: TLNT, TCPH and UDPH.

While I have no idea what the difference is between the three (since I know absolutely nothing about MTS!), if you click on the link provided in the "Emulated by" column, it should take you to:

where it states:

"These device types emulate the Host Interface Machine (HIM)
devices that are used to connect a host running The Michigan
Terminal System (MTS) to the Internet. The device type (TLNT,
TCPH, or UDPH) should match the device type configured into MTS."

"The only parameter is the IP address the emulated interface
should bind to."

So simply defining one or more of those devices in your Hercules configuration files looks like all you need to activate the new HIM code. Herc's sample configuration even lists three examples:

621-62B   UDPH     10.0.0.46
62C-643   TLNT     10.0.0.46
644-64F   TCPH     10.0.0.46

As I said, I don't know the particulars regarding which type to use nor how many of them you need to define (since that's an MTS thing), I suspect anyone familiar with MTS, such as you, would know.

Hope that helps!

I know the TCP/IP support in d6.0 is primitive, but I'd like to
play around with it.

So would I! But I know absolutely NOTHING about MTS, and unfortunately don't really have the time to learn it. :(

(That's the drawback of being a Hercules developer: you spend all your time working on Hercules with no free time left over to actually PLAY with Hercules! It's you Hercules users that get to have all the fun.)

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...