Jake (zpmain) wrote:

Right now I am using the below statement to define one OSA

0400.3 OSA CHPID F0 iface 192.168.1.2 ipaddr 192.168.1.5 netmask 255.255.255.0

If i want second OSA devices defined then how do I code?
Can I just repeat this line with another IP address for
secondary OSA?

What the best way to get second osa device defined for the
hercules?

Hi Jake!

I'm not sure what you mean by "secondary OSA" (did you mean: "a second OSA?", or "another OSA?"), but yes, that's all you need to do.

Just like any other device statement, such as a dasd device (where you repeat the statement but with a different device number and, of course, filename), for OSA, you simply repeat the statement, but with a different device number and, of course, ipaddr:


0404.3 OSA CHPID F0 iface 192.168.1.2 ipaddr 192.168.1.6 netmask 255.255.255.0


Notice the different device number (0404.3 instead of 0400.3) and ipaddr (192.168.1.6 instead of 192.168.1.5).

The only caveat is that the iface option -- being which host adapter the emulation is to use -- must remain the same.

On my own VM system for example (which works just fine), I have 3 OSA devices defined:


0600.3 OSA chpid F0 iface 192.168.0.107 ipaddr 192.168.0.73 netmask 255.255.0.0
0604.3 OSA chpid F0 iface 192.168.0.107 ipaddr 192.168.1.73 netmask 255.255.0.0
0608.3 OSA chpid F0 iface 192.168.0.107 ipaddr 192.168.2.73 netmask 255.255.0.0


It's that simple!

I'm actually quite surprised that the question was even asked! Is there something about our documentation or something else somewhere that was maybe confusing you or causing you to think that maybe it was done differently, thereby compelling you to ask such a question?

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

mail: fish@...

David wrote:

In my case, the second OSA would connect to an entirely
different network, on a different Ethernet switch. How
would that be configured?

Hi David!

Well, I haven't tried it myself (because I only have one network adapter), but I would think all you would have to do would be to specify a different 'iface' value. E.g.:

0400.3 OSA CHPID F0 iface 192.168.0.1 ipaddr 192.168.1.6 netmask 255.255.0.0
0404.3 OSA CHPID F0 iface 172.16.0.1 ipaddr 172.16.1.6 netmask 255.255.0.0

where 192.168.0.1 identifies the ip address of your HOST's first network adapter, and 172.16.0.1 of course would be the ip address of your HOST's *second* network adapter. The other ip addresses (specified for the 'ipaddr' option) would be the ip addresses of your z/OS or z/VM, etc, guest, running under Hercules.

Note: the above presumes you're running Hercules on Windows. If you're running it on Linux, the format (syntax) of your OSA device statement would be slightly different, as explained on our web page:

*

"iface device"

"Specifies, on Linux, the name of the host tunnel device to use.
On Windows, this required option identifies your Windows system's
actual network adapter. On Linux, the value should be specified
by name (e.g. /dev/net/tun). On Windows, the value should be
specified by either IP or MAC address."


Your question is an interesting one, David! I don't know of any user that has actually tried doing what you are wanting to do! Please DO let us know whether you are able to get it working!

Thanks!

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

mail: fish@...

CCKDDUMP / CCKDDU64 on z## z/OS,
CCKDLOAD / CCKDLO74 on Hercules.MVS



On Sat, Jan 11, 2025 at 1:39?AM Brian_Westerman via groups.io
<Brian_Westerman@...> wrote:

Fish,

Do you have any special TCPIP settings on the hercules side to go with changing to the OSA from LCS?

I find that OSA seems to be able to FTP at 3 times the speed of the old LCS, but unfortunately if I transfer more than a couple gigabytes, it tends to get lost somehow and times out. As long as I keep the files under 3 GB, it seems to work every time, but when I need to transfer a DASD volume (3390-54 or 3390-27), they tend to be between 5 to 15GB of data so I end up bringing up an older z/os that still supports LCS to do the transfer.

I'm wondering if I have missed something in my definitions. I have offload turned off for the physical windows TCPIP adapter, and in my zos TCPIP parms I also have nochecksumoffload specified, but no other TCPIP config parms relating to the OSA adapter, I just let them all default.

Maybe there is another way to transfer the dasd than using ADRDSSU on both sides. I had heard that some people use CCKDDASD but have not tried that.

Brian

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

Brian_Westerman wrote:

Fish,

Do you have any special TCPIP settings on the hercules side
to go with changing to the OSA from LCS?

Nope. Just what's in our documentation.

I find that OSA seems to be able to FTP at 3 times the speed
of the old LCS,

Interesting. I hadn't really noticed that myself. Of course, I never bothered to time it either, so I'll have to take your word for it.

but unfortunately if I transfer more than a couple gigabytes,
it tends to get lost somehow and times out.

Also interesting! As a programmer, that sounds very much like a possible memory leak somewhere. I wonder whether the leak (if it is a leak! I'm just guessing that it is!) is in z/OS or Hercules?

Question: do you notice an increase in memory use in your host (Windows, Linux, etc) when this happens? On Windows, you can use Process Explorer. On Linux, I don't know what you would use. On z/OS, I don't know what you would use either!


[...]

I'm wondering if I have missed something in my definitions.

I doubt it.

I have offload turned off for the physical windows TCPIP
adapter, and in my zos TCPIP parms I also have nochecksumoffload
specified, but no other TCPIP config parms relating to the OSA
adapter, I just let them all default.

Which is fine. The checksum offload setting would only affect the speed of the transfer (not having it enabled slows things down a wee bit), but should not affect the memory leak issue (IF, that is, that is indeed what the problem really is! I'm only speculating (guessing) at this point!).

Although I suppose it's possible that the leak (if that's what it is!) could be in the checksum offloading handling logic of whoever's got the leak (host or guest).

In any case, this *is* somewhat interesting.

I'm not going to waste any of my own time/effort digging into this issue myself, but if it becomes a serious problem, I would report it (either to IBM or Hercules, whoever's at fault) so it can be investigated and fixed.

Maybe there is another way to transfer the dasd than using ADRDSSU
on both sides. I had heard that some people use CCKDDASD but have
not tried that.

I believe you mean CCKDDUMP/CCKDLOAD, not CCKDDASD. :)

Yes, there is the CCKDDUMP/CCKDLOAD(*) technique that Mike Schwab mentioned in his reply to you that can offload (dump) a dasd on z/OS to a very large dataset (which can then be xfer'ed to your Hercules host using whatever means desired) and then turned into a Hercules CCKD (or CCKD64) dasd using Hercules's CCKDLOAD utility, but I personally have very little knowledge of it or experience with it.

Hope that helps!

---------------------
(*) CCKDDUMP/CCKDLOAD for legacy 32-bit CCKD dasd, or CCKDDU64/CCKDLO64 for 64-bit CCKD64 dasd. I think there's a .zip file in our 'util' directory. I believe the late great Greg Smith originally wrote it, followed by me and then someone else who made (or tried to make!) changes needed to support 64-bit CCKD64 dasds, but that's about all I know about it. I've never actually ever tried to use it myself.

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

mail: fish@...

Fish wrote:

Brian_Westerman wrote:

[...]

but unfortunately if I transfer more than a couple gigabytes,
it tends to get lost somehow and times out.

Also interesting! As a programmer, that sounds very much like a
possible memory leak somewhere. I wonder whether the leak (if it
is a leak! I'm just guessing that it is!) is in z/OS or Hercules?

Question: do you notice an increase in memory use in your host
(Windows, Linux, etc) when this happens? On Windows, you can use
Process Explorer.

Or maybe VMMap or RAMMap? ONE of those great SysInternals tools!

Memory leaks, like race conditions, are notoriously difficult to find.

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

mail: fish@...

Just an off topic
When i do ipconfig all.
The DNS shows as 8.8.8.8

I guess with this DNS value I can't connect zos from laptop right.

开云体育

So intrtnally to connect the zos running on hercules cannot be achieved with this DNS then?

开云体育

开云体育

Just an off topic
When i do ipconfig all.
The DNS shows as 8.8.8.8

I guess with this DNS value I can't connect zos from laptop right.

Not enough info given. Not sure about MVS et al but normally the hosts file over-rides the DNS so by manipulating the hosts file you can connect.
If the system you are trying to connect to has an externally visible IP address, so not one of the reserved non-routable range, and you own a domain, you can create an entry pointing to it.
So I own g4ugm.me.uk. So I can create an "A" record mvs.g4ugm.me.uk that points to the MVS system.
When I send my DNS query to 8.8.8.8 it the DNS query could be sent to the root DNS, to the DNS for .uk, to the DNS for me.uk, then finally to the DNS for g4ugm.me.uk which would respond with the answer.?

On Sun, 12 Jan 2025, 04:33 Fish Fish via , <david.b.trout=[email protected]> wrote:

Fish wrote:
> Brian_Westerman wrote:

[...]
> > but unfortunately if I transfer more than a couple gigabytes,
> > it tends to get lost somehow and times out.
>

Which direction?? Sounds like it could be a filestore overflowing..

> Also interesting! As a programmer, that sounds very much like a
> possible memory leak somewhere. I wonder whether the leak (if it
> is a leak! I'm just guessing that it is!) is in z/OS or Hercules?
>
> Question: do you notice an increase in memory use in your host
> (Windows, Linux, etc) when this happens? On Windows, you can use
> Process Explorer.

Or maybe VMMap or RAMMap?? ONE of those great SysInternals tools!

Memory leaks, like race conditions, are notoriously difficult to find.

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

mail: fish@...

Dave
G4UGM

Ian Shorter wrote:

Brian, what version of Hercules are you using? There was
a fix to the develop branch at the end of August 2024
that corrected a problem in Hercules' QDIO code:

*

The issue was raised relating to a zLinux guest, but a
z/OS guest would presumably also be affected. The effect
on zLinux was an abend, perhaps the effect on z/OS is
confusion and giving up?

Good catch, Ian! I had forgotten about that fix.

So yeah: Brian? What version of Hercules are you using? Official 4.7? Or development 4.8?

You might want to try your large (ftp?) using QETH/OSA again, but using Herc 4.8 Development instead. It might work better due to the EQBS and SQBS instruction fixes. (And it would be a good confirmation test for us too!)

If you've never built Hercules for yourself before, use Bill Lewis's excellent Hercules Helper script. It makes building Hercules a breeze on both Linux or Windows.

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

mail: fish@...

After installing win ctci and connecting the LAPTOP if it doesn't connect with IP. I believe there is some testing exec which can help to troubleshoot
Is it tt64test ?

So here should I choose tun ? And first IP address of Laptop then next the IP address of zos ?
Is this how we do.?

I mean connecting it with lan cable.

Brian_Westerman wrote:

[...]

So far, the only issue I have is that 4.7 allowed me to have
10 CP's defined and this version 4.8.0.11371 only seems to
allow 8. Is that a new restriction? It may not make a difference,
but my 14900K has 24 cores, and I thought I might benefit from
allowing 10 of them to be used by Hercules. I'm not really
sure if Hercules makes use of 10, but I didn't expect to get
the error in the config file having MAXCPU=10 and NUMCPU=10.
It seems to work at 8 though.

Sounds like a bug in Bill's "Hercules Helper" script. He's passing "8" instead of "64" as the number of desired CPU engines in the 3rd option of the makefile.bat script:


makefile.bat {build-type} {makefile-name} {num-cpu-engines} \
[-asm] \
[-title "custom build title"] \
[-hqa {directory}] \
[-extpkg {directory}] \
[-a|clean] \
[{nmake-option}]


When I build my Hercules, I always specify 64, the maximum supported on Windows. His script *should* be doing the same. Just report it to him, and I'm sure he'll get it fixed it straightaway. He's a good guy.

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

mail: fish@...