Hi,

? I've downloaded and successfully run CE1.2.? I would like to get it Internet connected.

? I've found some advice () that involves routing through virtual networks within the host machine.? I've also found a comment somewhere (that I cannot find again) that seemed to say using QETH in bridge mode (Layer2) could be made to work.? I'm perhaps jumping to a conclusion here but I'm wondering if that meant that this configuration would permit the VM "host" to appear as a secondary IP on the Linux host system's ethernet adapter (with a 2nd MAC address, I'm also guessing).? Maybe I'm misunderstanding what was meant about that comment.

? Is this possible?? Has anyone done it?? Are there any written instructions?? ?I've searched the various mail groups to no avail.

? I understand UNIX/Networking but I'm a VM newbie.

Thanks!
Rob

Hi Bob,?

? ?That makes perfect sense.? I seem to have missed that part of the document I referenced that lists: VSE, VM/ESA, and LinuxS/390 as the Hercules guests that you might want to configure networking for.

Thanks!
Rob

On 1/11/23 18:00, robballantyne3@... wrote:

? ?That makes perfect sense.? I seem to have missed that part of the document I referenced that lists: VSE, VM/ESA, and LinuxS/390 as the Hercules guests that you might want to configure networking for.

But if you DO end up needing to configure TCP/IP under VM/ESA, I have done that several times, and can assist if needed. It's also the same IP stack as is used under OS/390, and the configuration is very much the same.

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA

Rob wrote:

I've downloaded and successfully run CE1.2. I would like to
get it Internet connected.

I've found some advice ()
that involves routing through virtual networks within the host
machine. I've also found a comment somewhere (that I cannot find
again) that seemed to say using QETH in bridge mode (Layer2)
could be made to work.

I don't know what you saw and where (some IBM documentation perhaps?), but if it was VM related, it was more than likely referring to z/VM, a much more modern z/Architecture version of VM which does indeed support networking with QETH (i.e. OSA) devices in Layer 2 (or Layer 3!) mode.

As Bob pointed out in his reply however, the VM that is usually discussed here in this group is VM/CE ("Community Edition"), which is a community modified/enhanced/supported version of VM/370, a very old version of VM that does not have any TCP/IP support at all as far a I know.

HTH

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

mail: fish@...

FWIW:

the original VM TCP/IP was written in IBMs Pascal/VS, AFAIK.

If the source code of this product could be found somewhere, I could imagine it would be possible
to compile it with my current version of New Stanford Pascal without or with minor changes.
If someone out there has access to the original TCP/IP source code for VM and wants to test this,
feel free to contact me offline for discussion and support.

New Stanford Pascal compiler website:

Thank you, kind regards

Bernd


Am 12.01.2023 um 03:57 schrieb Fish Fish:

On Thu, 12 Jan 2023 at 01:24, Bernd Oppolzer via groups.io
<berndoppolzer@...> wrote:

the original VM TCP/IP was written in IBMs Pascal/VS, AFAIK.

If the source code of this product could be found somewhere, I could
imagine it would be possible
to compile it with my current version of New Stanford Pascal without or
with minor changes.
If someone out there has access to the original TCP/IP source code for
VM and wants to test this,
feel free to contact me offline for discussion and support.

I doubt the source code was ever published. The original VM TCP/IP
("FAL") was at a time after IBM's Object Code Only (OCO) policy was
already established, and although a lot of the VM assembler code
remained available in source, virtually everything written in high
level languages (PL/X, C, and Pascal) was never shipped with source.

I would be happy to be proven wrong!

Tony H.

On Wed, Jan 11, 2023 at 01:33 PM, Bob Bolch wrote:

VMCE is based on nearly 50 year old code. IBM introduced TCPIP support years later. That IBM TCPIP code depends on facilities that were not added to VM until much later.?

VM/370 R6 PLC 17 is ~ 1980 code; TCP/IP was running at (for example) at Clarkson University in 1986.? That's not?a huge?gap; I think the primary thing missing was IUCV, but you might be to use VMCF if IUCV has not been backported to VM/CE.

On Wed, Jan 11, 2023 at 10:24 PM, Bernd Oppolzer wrote:

the original VM TCP/IP was written in IBMs Pascal/VS, AFAIK.

If the source code of this product could be found somewhere, I could?imagine it would be possible?to compile it with my current version of New Stanford Pascal without or?with minor changes.
If someone out there has access to the original TCP/IP source code for?VM and wants to test this,?feel free to contact me offline for discussion and support.

Any IBM TCP/IP program is a Licensed Program Product and can't be blithely redistributed in source or object. Same for the header files. So don't bother.

Three legal alternatives one could consider:

• IBM TCP/IP originally was based on WISCNET (); is there a pre-PP of WISCNET archive out there?
• Look for BSD network kernels, especially those ported to foreign platforms.
  VM specific network adapter and client VMCF/IUCV support would have to be written.
• KNET was a TCP/IP competitor from Spartacus/Fibronics. Perhaps they released their code to the public domain.

-ahd-

开云体育

On Thu, Jan 12, 2023 at 03:05 PM, Dave Wade wrote:

.. transporting non-vm code to vm does not always end happily ….

*snicker*

"Transporting X code to Y does not always end happily."?

(It's simpler)

OTOH, the BSD code has ranged far and wide …

(It's simpler)