开云体育

VM/ESA 2.4 definitely does support OSA. (we're running two OSAs in an S/390 at LSSM) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

Tony Harminc wrote: As far as VM operating systems go, I can confirm that VM/ESA 2.4.0 supports LCS, as do all modern z/VMs. Modern z/VM supports OSA as well (in either mode too: Layer 2 mode -or-

Jay Maynard wrote: Thirded. Unless VM/ESA supports OSA? Does anyone know? I don't recall having ever tried it myself. I have two separate VM/ESA 2.4.0 configurations -- one CTCI, the other LCS -- and

What guest OSs still support LCS? Tony H.

Seconded. I wound up going this route myself, and after figuring out how to do it (I wound up using a bridge device and running it to the Ethernet and tap devices), it works really well. -- Jay

Start using LCS. It is much easier, because you can bridge tap0 and not worry about routing.

You might have a look here: https://sdl-hercules-390.github.io/html/hercconf.html#CTCI Joe wrote:

Many thanks.. While testing, yes, I did force/xautolog TCPIP often.. I suspect the tun device, its routing, and the iptables firewall that might be involved. I tweaked with a lot of the parameters but

Have your started the TCPIP virtual machine ? There might be an AUTOLG EXEC on the OPERATOR machine called from it's PROFILE EXEC. The default in the AUTOLG EXEC is to have all the XAUTOLOG commands

Hello Mark, I have sent you a PDF with some words on PER usage in program debugging. Please let me know that you have received it. Regards, Martin.

Hi there. I am unable to get routing working between the Linux host and the VM/ESA running.. The 192.168.200.1 cannot be pinged from the linux, and the 192.168.200.2 cannot be pinged from the VM. Here

I think having someone write about PER, who has used it would be of benefit to ALL of us. Please do so at your pace. ... Mark S.

I remember hearing about PER, but when last debugging years ago, I got my problem solved with DEBUG, so I didn't look into it. So the VM/370 CE V1R1.2 contains help for CP PER, and I can use that, and

What Dave says is true but its worth looking st CP PER function as it can assist the debugging process no end.

Mark, One issuette is that PER which is definitely the way to go is a user add-on so isn't in the R6 manuals. It's way more sophisticated than the CMS debug facilites. Dave [email protected]> wrote:

Hello Mark, I tried to use the DEBUG function but never got the hang of it. Using CP to do the debugging was the way to go. I can put together a guide outlining my method if this would be of use to

Since the program is a user program, rather than CMS, I had not thought to try the CP debugging commands. That will be new ground for me. Thank you. ... Mark S.

I've been using LOADMOD, then set up the CMS DEBUG commands, and then issue START with the parameters I would normally pass when I just entered the module name. I don't know if I have multiple bugs,

Hello Mark, I did a lot of program debugging back in the day and recently with the VM/370 system. I used the ADSTOP to set a stop point and the use the CP PER and DISPLAY commands to look at storage

[...] I haven't debugged on VM of any flavour for a long time, but it seems to me you should be able to use the START assembler directive (instead of CSECT) to get your listings to match loaded