On 1/23/09 11:02 AM, "Alan Altmark" <[email protected]> wrote:
> On Friday, 01/23/2009 at 12:20 EST, "Martin, Terry R. (CMS/CTR) (CTR)" > <[email protected]> wrote: > >> Is anyone running FTP on z/VM connecting to FTP server on z/OS over a >> HiperSockets network? If so can you share with me the steps to take to > get this >> working? > > The general sequence is: > 1. Define a HiperSocket chpid and subchannels. Give the z/VM partition > access to three of them (at least) and bring them online. > 2. Add DEDICATE statements for the three subchannels to TCPIP's directory > entry. > 3. Add DEVICE/LINK/HOME/START statements to PROFILE TCPIP. The IFCONFIG > command can assist you if you're uncertain about the statements you need. > > But don't take my word for it! Take a gander at the often-ignored and > always-overlooked z/VM Connectivity book in the z/VM library. ;-) > > Please note that there is an error on p.82 > IODEVICE ...,UNIT=IDQ USERPRM=(parmname,OS_num) > is incorrect. It should read > IODEVICE ...,UNIT=IDQ,CHPARM=(code) > where (code) has the "OS" values in the table. You should also consider using a Linux guest as a firewall/NAT router between the physical hipersocket and a VSWITCH or guest LAN instead of dedicating the connection to the VM stack. Since the number of hipersockets are limited, and setting them up is a royal PITA, a setup like that allows more guest systems to take advantage of the connection w/o reinventing the wheel every time, and provides significant traffic shaping and management capabilities. It will cost you some cycles, but it's worth considering if you need a managed path between the guests and don't want to use an external switch path for network performance or security reasons.
