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@...
