Rebecca > For the OSE cards, when TCP/IP is started, it uses the information in the > TCP/IP profile to load the port with IP address, etc, that the port needs to > connect to the network.
No. You or your "hardware vendor" - wouldn't that be IBM or has the world become more complicated with more people skimming the milk since I retreated from the grindstone? - are confusing QDIO and non-QDIO. Try this section from the zEnterprise 196, System z10, System z9 and eServer zSeries Open Systems Adapter-Express Customer's Guide and Reference: 1.1.8.1 ARP Takeover http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ioa2z180/1.1.8.1 - Well, I'm glad you have got your OSA-Express3 feature working. When I last worked with OSE 12 years ago with OSA-2 features, setting up OSA/SF and then configuring with OSA/SF appeared to be mandatory - but maybe that's because I was concentrating on SNA use. Even since then when I have concentrated on OSD (QDIO) I have emphasised setting up OSA/SF in order to be able to "see" the OSA Address Table. - Incidentally, when you finally start using OSD rather than OSE, you should use the IBMTCP-L list for any topic related to z/OS Communications Server and neighbouring topics such as OSA features: For IBMTCP-L subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBMTCP-L Chris Mason On Mon, 3 Dec 2012 09:54:39 -0600, Rebecca Martin <[email protected]> wrote: >FYI - Looks like our hardware vendor has found the answer (I'll know for sure >a bit later on): > >After spending a while researching and thinking about the OSA problem, here's >what I think it is. >For the OSE cards, when TCP/IP is started, it uses the information in the >TCP/IP profile to load the port with IP address, etc, that the port needs to >connect to the network. The default configuration that gets loaded onto the >OSE chpids during POR has entries for unitadd 00 and 01, which makes the port >0 connections work. For port 1 the definitions are unitadd 10 and 11 for FC40 >and FC10. Those unitadds do not get set up right in the card's default >configuration. > >Here's the fix : >In HCD, add a device definition for a device type OSAD at unitadd FE to each >of the OSE chpids, like the following: > CNTLUNIT CUNUMBR=FC00,PATH=((CSS(0),00)),UNIT=OSA > IODEVICE ADDRESS=(FC00,032),CUNUMBR=(FC00),UNIT=OSA > IODEVICE ADDRESS=FCFE,UNITADD=FE,CUNUMBR=FC00),UNIT=OSAD <-- > > CNTLUNIT CUNUMBR=FC20,PATH=((CSS(0),04)),UNIT=OSA > IODEVICE ADDRESS=(FC20,016),UNITADD=00,CUNUMBR=(FC20),UNIT=OSA > IODEVICE ADDRESS=(FC40,016),UNITADD=10,CUNUMBR=(FC20),UNIT=OSA > IODEVICE ADDRESS=FCFF,UNITADD=FE,CUNUMBR=FC20),UNIT=OSAD ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
