开云体育

I've uploaded XNET version 1.4.1 to the files section.? This upload includes the full XNET package including the latest documentation.? For VM/CE V1.R1.2 users, note that this version is identical to the 1.4.0 version you have preinstalled on VM/CE (on the XNET userid).? The version change to 1.4.1 was simply to denote the difference between this version with its updated documentation versus the parts and pieces that are in VM/CE.? Again, 1.4.0 and 1.4.1 are functionally identical.

?

The materials are now in the Files section of this group, named "xnetv141.zip".

?

From the XNET documentation intro:

XNET connects together two or more S/370-based VM systems for the purposes of allowing remote logon.? XNET allows 3270 terminal users to log on to userids on other similar VM system(s) that are currently online to XNET.? Likewise, a user on one of the other VM system(s) would be able to log on to a userid on your system.? You still retain access control for your own systems via the system directory and passwords.

?

XNET provides the management and transport of 3270 data between systems in order to facilitate remote logons and connections to other VM systems.? XNET can support multiple users and multiple systems, and supports two types of data transport mechanisms.? XNET is a fully asynchronous mini-operating system that runs in a virtual machine.

?

Regards,

Bob

On Sat, Aug 3, 2024 at 07:56 AM, Bob Polmanter wrote:

XNET provides the management and transport of 3270 data between systems in order to facilitate remote logons and connections to other VM systems.? XNET can support multiple users and multiple systems, and supports two types of data transport mechanisms.? XNET is a fully asynchronous mini-operating system that runs in a virtual machine.

wow, just ... wow.

?

?... Mark S.

Double-Plus Wow!

Hi Gregg,

?

All of the information you need to set up XNET and the CTC device(s) (both in VM/370 and in Hercules) are in the documentation, including examples.

?

Also, you can set up two XNET servers on the same system (in two different userids) and connect them with a virtual CTCA.?? While this does not serve any practical purpose, it does allow one to get a feel for it and see that it is working, and validate that they set up the configuration correctly.? I'd recommend something like this before trying to connect with a separate host computer running Hercules+VM/370.

?

Regards,

Bob

On Sat, Aug 3, 2024 at 07:56 AM, Bob Polmanter wrote:

I've uploaded XNET version 1.4.1 to the files section.? This upload includes the full XNET package including the latest documentation.? For VM/CE V1.R1.2 users, note that this version is identical to the 1.4.0 version you have preinstalled on VM/CE (on the XNET userid).? The version change to 1.4.1 was simply to denote the difference between this version with its updated documentation versus the parts and pieces that are in VM/CE.? Again, 1.4.0 and 1.4.1 are functionally identical.

I will work on getting this in place on my fork of CE in preparation for the next release. It won't happen overnight, though ... unless I have trouble sleeping again.

?

?... Mark S.

?

On Sun, Aug 4, 2024 at 07:02 AM, Bob Polmanter wrote:

All of the information you need to set up XNET and the CTC device(s) (both in VM/370 and in Hercules) are in the documentation, including examples.

Bob,

?

I've set up two VM/370 CE 1.1.2 systems in qemu KVMs on a Linux system. I have configured Hercules to make use of two CTCE channels (500 and 600) and using 500 to connect the two systems together. I added the lport/rport to the firewalls for each of the KVMs to allow traffic through. I have setcap for Hercules on both systems. I used x3270 to connect from the Linux host to the KVMs.

I am using the default DMKRIO rchannel/rdevice/... configurations for both VM systems. I have two additional systems for future adds, and an indication that there is no connection.

?

They 'see' each other, but DIAL fails to connect. Some information is below. What else would you need from me to offer suggestions (apart from 'go fly a kite!) ;-)

VM370DEV Hercules definitions (line number are from vim)
?182 # Hercules PC Host vm370dev with IP address 192.168.122.240 connecting to
?183 # Hercules PC Host vm370-01 with IP address 192.168.122.246
?184 # ldevnum ?CTCE ?[lport] ?[rdevnum=] raddress ? rport ?[[mtu] ?sml] ?[ATTNDELAY delay] ?[FICON]
?185 0500 ? ? ? CTCE ?30880 ? ?0500=192.168.122.246 ?30880 ?62552 ? 16
?186 #
?187 # Hercules PC Host vm370dev with IP address 192.168.122.240 connecting to
?188 # Hercules PC Host vm370-02 with IP address 192.168.122.154
?189 # ldevnum ?CTCE ?[lport] ?[rdevnum=] raddress ? rport ?[[mtu] ?sml] ?[ATTNDELAY delay] ?[FICON]
?190 #
?191 0600 ? ? ? CTCE ?30880 ? ?0600=192.168.122.154 ?30880 ?62552 ? 16
?192 ?

VM370-01 Hercules definitions

?

?183 # Hercules PC Host vm370-01 with IP address 192.168.122.246 connecting to
?184 # Hercules PC Host vm370dev with IP address 192.168.122.240
?185 # ldevnum ?CTCE ?[lport] ?[rdevnum=] raddress ? rport ?[[mtu] ?sml] ?[ATTNDELAY delay] ?[FICON]
?186 0500 ? ? ? CTCE ?30880 ? ?0500=192.168.122.240 ?30880 ?62552 ? 16
?187 #
?188 # Hercules PC Host vm370-02 with IP address 192.168.122.154 connecting to
?189 # Hercules PC Host vm370dev with IP address 192.168.122.240
?190 # ldevnum ?CTCE ?[lport] ?[rdevnum=] raddress ? rport ?[[mtu] ?sml] ?[ATTNDELAY delay] ?[FICON]
?191 #
?192 0600 ? ? ? CTCE ?30880 ? ?0600=192.168.122.154 ?30880 ?62552 ? 16
?193?

?

VM370DEV XNET Console 'screen shot'

?

?

VM370-01 XNET 'screen shot'

?

?

This is the result of trying to dial from VM370DEV to VM370-01

?

?

I can dial to the local system VM370DEV -> VM370DEV, and VM370-01 -> VM370-01 and log in.? Any suggestions?

?

?... Mark S.

Mark,

?

It looks like the two systems are connected ok.? You might verify that by using the M command from the XNET virtual machine console.? This just sends a message across the CTC to the other side, and the message should show up on the other side's XNET virtual machine console.? Use the M command like you would if you were on CMS using the M command (the MSG command).? Specify:

?

M nodename MESSAGE_TEXT HERE

?

So in your case, from the VM370DEV XNET console, type in:

m VM370-01 This is a test.

?

On the VM370-01 XNET console you should see:

@VM370DEV This is a test.

?

You should also be able to send it the other direction as well.? If you are not receiving a test message then this would be why the 3270s are not connecting.? If the message does go through ok, then there is probably something else wrong.? Can you paste your XNET CONFIG file (from both sides) for reference??

?

Depending on your results, I may ask you later to obtain some diagnostic information.

?

Regards,

Bob

On Mon, Aug 12, 2024 at 05:35 PM, Bob Polmanter wrote:

You should also be able to send it the other direction as well.? If you are not receiving a test message then this would be why the 3270s are not connecting.? If the message does go through ok, then there is probably something else wrong.? Can you paste your XNET CONFIG file (from both sides) for reference??

It seems I can message VM370-01 to VM370DEV, but not the other way.

?

VM370DEV Console

?

?

VM370-01 Console

?

?

VM370DEV XMASVMCE CONFIG

?

?

VM370-01 XMASVMCE CONFIG

?

?

?... Mark S.

?

Hi Mark,

?

If you are not already, I'd recommend that you have the CTCE device defined in the Hercules configuration for both systems, so that they will establish their TCPIP connection when Hercules starts up, and allow VM/370 CP to contact them and issue SIOs to them at system start up so they properly initialize. When both systems are up, then logon to the XNET machines and start XNET.? I often have trouble if I define CTCEs dynamically when Hercules is already up.? I don't think this is a CTCE problem per se; but CP is not initializing the device which helps to establish the TCPIP connection.

?

I just brought things up and had no difficulties.? I used VM/CE 1.1.2 as node1 and a VM Sixpack system as node2.? I connected them via CTCE at address 500 on both systems; dev 500 attached to XNET as 500.? Here are the results.? I was able to send messages back and forth and connect a terminal (via dial) to each XNET and connect to the remote system.

?

VMCE:

xnet ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
XNET010 Cross System Net - V1.4.0 ? 07/15/22 10.42 ? ? ??
XNET002 XNET using configuration file XNET ? ? CONFIG ? *
XNET020 VMCE ? ? active ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
XNET016 CTCA 500 initialization in progress... ? ? ? ? ??
XNET017 CTCA 500 is X-side ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
XNET019 CTCA 500 connected to node SIXPACK ?(NETID= ?2) ?
XNET020 SIXPACK ?active ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
@SIXPACK test from sixpa ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
m sixpack test from vmce ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
XNET012 Device 0C8 connected ? ? ? ? ? ? ? ? ? ? ? ? ? ??
XNET028 GRAF 0C8 associated with SIXPACK ?L000 ? ? ? ? ??
XNET029 GRAF 0C8 disassociated with SIXPACK ?L000 ? ? ? ?
XNET013 Device 0C8 disconnected ? ? ? ? ? ? ? ? ? ? ? ? ?
XNET021 LDEV L000 associated with SIXPACK ?0C8 ? ? ? ? ??
XNET015 LDEV L000 disassociated with SIXPACK ?0C8 ? ? ? ?

?

SIXPACK:

xnet ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
XNET010 Cross System Net - V1.4.1 ? 08/03/24 12.46 ? ? ? ?
XNET002 XNET using configuration file XNET ? ? CONFIG ? *?
XNET020 SIXPACK ?active ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
XNET016 CTCA 500 initialization in progress... ? ? ? ? ? ?
XNET017 CTCA 500 is Y-side ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
XNET019 CTCA 500 connected to node VMCE ? ? (NETID= ?1) ??
XNET020 VMCE ? ? active ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
m vmce test from sixpack? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
@VMCE test from vmce? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
XNET021 LDEV L000 associated with VMCE ? ? 0C8 ? ? ? ? ? ?
XNET015 LDEV L000 disassociated with VMCE ? ? 0C8 ? ? ? ??
XNET012 Device 0C8 connected ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
XNET028 GRAF 0C8 associated with VMCE ? ? L000 ? ? ? ? ? ?
XNET029 GRAF 0C8 disassociated with VMCE ? ? L000 ? ? ? ??
XNET013 Device 0C8 disconnected ? ? ? ? ? ? ? ? ? ? ? ? ??

?

Note: there is a small bug in XNET where the last 1 or 2 characters is chopped off the message text if the node id is a longer one, as you may notice above.? It doesnt hurt the operation but you should be aware of it.

?

And here was the XNET CONFIGs that I used:

?

VMCE:

* ? ? ? nodename ?netid ? ? ? ? ? ? ? ??
* ? ? ? -------- ?----- ? ? ? ? ? ? ? ??
?LOCAL ?VMCE ? ? ? ?1 ? ? ? ? ? ? ? ? ??
* ? ? ? ? ? ? ? ? ? ? ? ? via ? ? ? ? ??
* ? ? ? nodename ?netid ?netid ? ? ? ? ?
* ? ? ? -------- ?----- ?----- ? ? ? ? ?
?NODE ? SIXPACK ? ? 2 ? ? ?2 ? ? ? ? ? ?
* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
* ? ? ? ? ? ? to ? ? ? ? START/ ? ? ? ??
* ? ? ?cuu ? netid ? ? ?NOSTART ? ? ? ??
* ? ? ?--- ? ----- ? ? ?------- ? ? ? ??
?CTCA ?500 ? ? 2 ? ? ? ? ?START ? ? ? ??
* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
* ? ? ? ? ?PFKey to exit from session ??
* ? ? ? ? ?---- ? ? ? ? ? ? ? ? ? ? ? ??
?EXITPFK ? PF24 ? ? ? ? ? ? ? ? ? ? ? ??

?

?

SIXPACK:

* ? ? ? nodename ?netid ? ? ? ? ? ? ? ?
* ? ? ? -------- ?----- ? ? ? ? ? ? ? ?
?LOCAL ?SiXPACK ? ? 2 ? ? ? ? ? ? ? ? ?
* ? ? ? ? ? ? ? ? ? ? ? ? via ? ? ? ? ?
* ? ? ? nodename ?netid ?netid ? ? ? ??
* ? ? ? -------- ?----- ?----- ? ? ? ??
?NODE ? VMCE ? ? ? 1 ? ? ?1 ? ? ? ? ? ?

*

* ? ? ? ? ? ? to ? ? ? ? start/ ? ? ? ?
* ? ? ?cuu ? netid ? ? ?nostart ? ? ? ?
* ? ? ?--- ? ----- ? ? ?------- ? ? ? ?
?CTCA ?500 ? ?1 ? ? ? ? ? START ? ? ? ?
* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
* ? ? ? ? ?PFKey to exit from session ?
* ? ? ? ? ?---- ? ? ? ? ? ? ? ? ? ? ? ?
?EXITPFK ? PF24 ? ? ? ? ? ? ? ? ? ? ? ?

?

Regards,

Bob

On Tue, Aug 13, 2024 at 07:23 AM, Bob Polmanter wrote:

If you are not already, I'd recommend that you have the CTCE device defined in the Hercules configuration for both systems, so that they will establish their TCPIP connection when Hercules starts up, and allow VM/370 CP to contact them and issue SIOs to them at system start up so they properly initialize. When both systems are up, then logon to the XNET machines and start XNET.? I often have trouble if I define CTCEs dynamically when Hercules is already up.? I don't think this is a CTCE problem per se; but CP is not initializing the device which helps to establish the TCPIP connection.

?

?

Note: there is a small bug in XNET where the last 1 or 2 characters is chopped off the message text if the node id is a longer one, as you may notice above.? It doesnt hurt the operation but you should be aware of it.

?

Hi Bob,

?

Sorry for the delayed response.

?

I have the CTCE connections defined in the configuration file, so they are present at IPL, I have been logging in to XNET while I get this running. I plan to use AUTOLOG from AUTOLOG1 eventually. In trying to properly grok this CTCE/CTCA documentation, I am trying to follow the SDL (4.7) description. What hasn't been clear to me is if I am using an even/odd pair of ports to connect the hosts to each other.

?

Here are the Hercules configuration entries. First for VM370DEV (line numbers are due to cut & paste from vim)

?

?

?

Here is the Hercules configuratino for VM370-01 (line numbers are are due to cut & paste from vim)

?

?

I would not be surprised if anything related to VM/370 did not chop off characters after character #8. I haven't been able to find out if I can actually use a minus sign (-) in a node name or host id.

?

?... Mark S

?

On Tue, Aug 13, 2024 at 07:23 AM, Bob Polmanter wrote:

?

If you are not already, I'd recommend that you have the CTCE device defined in the Hercules configuration for both systems, so that they will establish their TCPIP connection when Hercules starts up, and allow VM/370 CP to contact them and issue SIOs to them at system start up so they properly initialize. When both systems are up, then logon to the XNET machines and start XNET.? I often have trouble if I define CTCEs dynamically when Hercules is already up.? I don't think this is a CTCE problem per se; but CP is not initializing the device which helps to establish the TCPIP connection.

?

Bob,

?

Additionally, while looking at the log files, these are the last few lines for VM370DEV

?

Starting with:

?

?

and ending with:

20:09:20 HHC01313I 0:00CF CHAN: sense 40000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
20:09:20 HHC01314I 0:00CF CHAN: sense INTREQ?
20:09:37 HHC05070I 0:0500 CTCE: Accepted inbound connection :30880 <- 0:0500=192.168.122.246:33559 (bufsize=62552,16)
20:09:37 HHC05054I 0:0500 CTCE: Started outbound connection :41559 -> 0:0500=192.168.122.246:30880

?

I do not see similar lines in the log file for VM370-01

?

Starting with:

?

?

and ending with:

?

?

If I need to rebuild SDL on both systems, fine. I just need to know.

?

?... Mark S.

Hi Mark,

?

Ok, I think I see the problem.? You are reusing the same port numbers on your CTCE definitions in your Hercules configuration.? They need to be unique, by CTCE device.

?

For example, you have port 30880 on the CTCE at 500 and at 600.? They need to be different ports, on both sides of the CTCE definition.? So, I'd suggest using 30880 for address 500 and something like 30890 for address 600.? This isnt XNET's rules; rather, this is required by CTCE to function properly.

?

Also, I'd suggest simplicity.? You have a lot of extra definitions of CTCEs as well as nodes and CTC devices in your configurations that are not actually in use. When you are just trying to get something to work, just define two hosts and try to get them to work.? Then you can expand as you need to.? In a two node setup, you only need a single CTCE defined in each Hercules instance.

?

Regards,

Bob

On Thu, Aug 15, 2024 at 07:50 AM, Bob Polmanter wrote:

For example, you have port 30880 on the CTCE at 500 and at 600.? They need to be different ports, on both sides of the CTCE definition.? So, I'd suggest using 30880 for address 500 and something like 30890 for address 600.? This isnt XNET's rules; rather, this is required by CTCE to function properly.

?

Also, I'd suggest simplicity.? You have a lot of extra definitions of CTCEs as well as nodes and CTC devices in your configurations that are not actually in use. When you are just trying to get something to work, just define two hosts and try to get them to work.? Then you can expand as you need to.? In a two node setup, you only need a single CTCE defined in each Hercules instance.

?

I rebuilt Hercules on both systems via hercules-helper, removing any prior versions of 3.x or 4.x leaving only the most recent 4.7.

?

?

I have pared down the Hercules configuration file to just one CTCA, the second one is commented out.

?

VM370DEV configuration

?

?

VM370-01 configuration

?

?

I also have commented out the extra lines in XMASVMCE CONFIG on each machine.

?

VM370DEV XMASVMCE CONFIG A

?

?

VM370-01 XMASVMCE CONFIG A

?

?

An interesting result from asking Hercules about device 500. One response has a single line (minus) and the other has two lines (equals) between the 'arrows'. Not sure what that means.

?

VM370DEV web console

?

HHC01603I devlist 500 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
HHC02279I 0:0500 CTCE CTCE 30880/37589 <-> 0:0500=192.168.122.246:30880/44447 IO[8] open ?? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

?

VM370-01 web console

?

?

and still no communication from VM370DEV to VM370-01 via message. There is communication from VM370-01 to VM370DEV.

?

VM370DEV console

?

?

VM370-01 console

?

L XNET
ENTER PASSWORD:
?
DMKLOG090E DEV 09E NOT DEFINED; DEV 09E NOT AVAILABLE
DMKLOG090E DEV 09F NOT DEFINED; DEV 09F NOT AVAILABLE
LOGON AT 19:33:47 GMT FRIDAY 08/16/24
VM Community Edition V1 R1.2
?
Y (19E) R/O
Segment GCCLIB is not loaded because virtual machine memory is in use.
U (19D) R/O
XNET010 Cross System Net - V1.4.0 ? 07/15/22 10.42
XNET002 XNET using configuration file XMASVMCE CONFIG ? *
XNET020 VM370-01 active
XNET016 CTCA 500 initialization in progress...
XNET017 CTCA 500 is X-side
XNET019 CTCA 500 connected to node VM370DEV (NETID= ?1)
XNET020 VM370DEV active

m VM370DEV This is a test from VM370-01

?

?

I am as confused as I can be.

?

?... Mark S.

?

?

On Thu, Aug 15, 2024 at 07:50 AM, Bob Polmanter wrote:

Ok, I think I see the problem.? You are reusing the same port numbers on your CTCE definitions in your Hercules configuration.? They need to be unique, by CTCE device.

Does the SYSID in DMKSYS have to match the NODE value?

?

?... Mark S.

Hi Mark,

?

I found the problem.? It is in your XNET configuration.? I completely missed it before.? Here is the problem, and it is in the CONFIG file for VM370DEV only.? The CONFIG for VM370-01 is correct.? The adjacent node number is incorrect.? Here is what you show you have coded in earlier messages:

?

FSVIEW: XMASVMCE CONFIG C1 ? ? ? ? ? ? ? Lines 1-31/31 V80[1-79] ?FSVIEW V1.2.5
* ? ? ? nodename ?netid
* ? ? ? -------- ?-----
?LOCAL ?VM370DEV ? ?1
* ? ? ? ? ? ? ? ? ? ? ? ? ????????????????via
* ? ? ? nodename ?netid ?netid
* ? ? ? -------- ?----- ?-----
?NODE ? VM370-01 ? ?2 ? ? ?1

?

The ‘via’ netid should be a 2 in this case.? To get to node 2, you have to get there via the link-up to node 2.? Hence 2 is the adjacent node.? Your config for the VM370-01 is correct and correctly says adjacent to 1.

?

So I think if you fix adjacent node in the CONFIG file in VM370DEV, then restart XNET on both sides with a fresh IPL 190 first, you will be good to go.

?

Regards,

Bob

On Sat, Aug 17, 2024 at 02:56 PM, Bob Polmanter wrote:

So I think if you fix adjacent node in the CONFIG file in VM370DEV, then restart XNET on both sides with a fresh IPL 190 first, you will be good to go.

Bob,

?

Thank you so much for your patience! I now have a two node XNET working!!

?

I also rebuilt CP so the SYSID name matches the NODE name. I'll need that (and fixing SYSTEM NETID) for RSCS.

?

?... Mark S.

Bob,

I added XNET to AUTOLOG1 and it is running disconnected. I can dial XNET and get the menu, and choose a system, but it does not connect.

?

On Sat, Aug 17, 2024 at 07:11 PM, Gregg Levine wrote:

I see that Mark. There's a good reason waiting for it. What say that
when all of this is settled, and you've got the two systems seeing
each other, can you present all of this as a good example of
documentation?

I can present it as an example of documentation, a HOW-TO. Good will be in the eye of the beholder.

?

?... Mark S.