Path: utzoo!utgpu!CUNYVM!IBMTCP-L Date: Wed, 28 Feb 90 15:59:00 EST Reply-To: IBM TCP/IP For VM List Sender: IBM TCP/IP For VM List From: PMW1@PSUVM.bitnet Subject: HYPERchannel defs of TCP/IP For MVS To: UofToronto LAN redistribution Message-ID: <90Feb28.160911est.57390@ugw.utcs.utoronto.ca> Newsgroups: list.ibmtcp-l Distribution: ut Approved: devnull@gpu.utcs.toronto.edu I recently received these from an unnamed IBM source. Would anyone like to confirm/deny the accuracy of them at any/all PTF levels? -- Peter M. Weiss | (this line intentionally left blank) 31 Shields Bldg (the AIS people) | Don't FAX me, I'll FAX you! University Park, PA USA 16802 | Disclaimer :1 * applies herein ---------------------------clip here---------------------------------- You don't need any additional software to attach a Hyperchannel to MVS TCPIP. It requires definitions for A220 Hyperchannel and IO definitions for the host. The following is the set of recommended IOCP definition for MVS. CNTLUNIT: cunumber=xxx,path=(yy),protocl=d,shared=n,unit=3705, unitadd=((zz,8)) IODEVICE: unit=bsc1,address=(yzz,8)adapter=bsca,tcu=2701,cunumber=(xxx) Notes: a). 8 subchannels minimum can configure up to 64 subchannels. b). Address base has to be aligned on (00,40,80,c0) boundary.