> > you will need to create a > >file called route-hsi0 > to be created also in /etc/sysconfig/network-scripts ?
Yes, that's one method. > is fine, I can do that in any case. > > Is it also necessary if the applications (we plan to implement) use the > IP-address the HSI interface of z/os directly, and not the VIPA-Address of > z/OS? So that every conversation > from-Linux-to-z/os and back explicitly uses the HSI-Address? Unless you defined a specific VIPA for two hipersocket interfaces, then yes. Another tip: PLEASE set up DNS entries for the different interfaces and make the applications refer to the names, not the addresses. It's worth the effort, even if you have to run a local DNS server (a great use for another Linux guest, by the way -- DNS is a lot easier to set up on Linux than z/OS). If you have to reorganize your network at some point, changing the DNS server once is a LOT easier than hunting down a bunch of hard-coded addresses in applications. I'd suggest one name per interface, consisting of the base name of the system, a dash (-) and the interface name, eg snamvs-hsi0.example.com, snamvs-eth0.example.com, etc. That way you can explicitly reference a interface if you need to, but use a more generic name like snamvs.example.com to refer to things like the VIPA. -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
