Re: CHPID TYPE OSE Port 1 of OSA Express3
We have not resolved the problem yet - waiting for change control process. We do now understand the problem. The problem is because the OSA cards do not come with a default OAT that includes port 1. To use PORT 1 for LCS you must use OSA/SF to complete the configuration. There are 2 changes required: 1 - to the CONFIG we need to add a port name and use that same port name in the TCPIP LINK statements in our PROFILE, 2 - modify the OAT to include definitions for port 1. The hardware definitions I modifed on Monday, it appears, will work. Adding the device with UA of FE and type OSAD was needed to use the OSA/SF facility. With the OSA/SF I was able to do a GET_CONFIG and GET_OAT for each of the CHPIDs. The required changes are staged and ready to be loaded. As soon as change control is approved and an approriate time for the change agreed upon, I think it will work. We previously had never needed to use OSA/SF and that is why our initial configuration didn't include a device with UA of FE and type OSAD. Thank you all for your input. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
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 lists...@vm.marist.edu with the message: INFO IBMTCP-L Chris Mason On Mon, 3 Dec 2012 09:54:39 -0600, Rebecca Martin rebecca.mar...@tgslc.org 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
Yes Chris I did state this wrong 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. Good thing I am not the communication person here :) The bottom line (for us) was that to use port 1 on a OSA with a CHPID type of OSE and LCS in the TCPIP definitions, we need to use OSA/SF to load the ODAT for port 1 and set the portname in the config. When we only had 1 port per CHPID, OSA/SF was not required. For our z114 installation/implementation there is another hardware vendor that we have been working with. The CE is from IBM but our other support during the installation/implementation is not. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
Thank you Dale. I am going to try that now. Just getting in. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
Dale, I replied too soon. After looking further at your recommendation, I can't do this. The CHPID is type OSE and OSE can not have more than 1 CU. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
Please excuse all the replies. I'll go get some coffee now and will report back after I try the suggestion. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
The changes did not work. We have a copy of that Share document and have actually read it several times :( Here is the new definitions from IOCP: CHPID PATH=(CSS(0),00),SHARED,* PARTITION=((MVSD,MVSM,MVSP,MVSZ),(=)),PCHID=200,TYPE=OSE CHPID PATH=(CSS(0),04),SHARED,* PARTITION=((MVSD,MVSM,MVSP,MVSZ),(=)),PCHID=210,TYPE=OSE CHPID PATH=(CSS(0),05),SHARED, CNTLUNIT CUNUMBR=FC00,PATH=((CSS(0),00)),UNIT=OSA IODEVICE ADDRESS=(FC00,032),CUNUMBR=(FC00),UNIT=OSA IODEVICE ADDRESS=(FCFE,001),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 After dynamic activate and IPL, FC10 and FC40 paths are still not operational. Do you see what we missed? Here are some displays: D M=CHP(04) IEE174I 13.23.06 DISPLAY M 113 CHPID 04: TYPE=10, DESC=OSA EXPRESS, ONLINE DEVICE STATUS FOR CHANNEL PATH 04 0 1 2 3 4 5 6 7 8 9 A B C D E F 0FC2 + + $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ 0FC4 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ 0FCF . . . . . . . . . . . . . . . + SWITCH DEVICE NUMBER = NONE PHYSICAL CHANNEL ID = 0210 SYMBOL EXPLANATIONS + ONLINE@ PATH NOT VALIDATED - OFFLINE. DOES NOT EXIST * PHYSICALLY ONLINE $ PATH NOT OPERATIONAL -D M=DEV(FC40) IEE174I 13.23.57 DISPLAY M 119 DEVICE 0FC40 STATUS=OFFLINE CHP 04 ENTRY LINK ADDRESS.. DEST LINK ADDRESS 0D PATH ONLINE Y CHP PHYSICALLY ONLINE Y PATH OPERATIONAL N PATHS NOT VALIDATED V PATH(FC40,04),ONLINE IEE386I PATH(FC40,04) NOT BROUGHT ONLINE IEE763I NAME= IECVIOPM CODE= 0004 IOS552I PATH NOT PHYSICALLY AVAILABLE IEE764I END OF IEE386IRELATED MESSAGES D M=DEV(FCFE) IEE174I 13.36.12 DISPLAY M 156 DEVICE 0FCFE STATUS=ONLINE CHP 00 ENTRY LINK ADDRESS.. DEST LINK ADDRESS 0D PATH ONLINE Y CHP PHYSICALLY ONLINE Y PATH OPERATIONAL Y MANAGED N CU NUMBER FC00 MAXIMUM MANAGED CHPID(S) ALLOWED: 0 DESTINATION CU LOGICAL ADDRESS = 00 D M=DEV(FCFF) IEE174I 13.36.30 DISPLAY M 158 DEVICE 0FCFF STATUS=ONLINE CHP 04 ENTRY LINK ADDRESS.. DEST LINK ADDRESS 0D PATH ONLINE Y CHP PHYSICALLY ONLINE Y PATH OPERATIONAL Y MANAGED N CU NUMBER FC20 MAXIMUM MANAGED CHPID(S) ALLOWED: 0 DESTINATION CU LOGICAL ADDRESS = 00 Thanks Rebecca -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message:
Re: CHPID TYPE OSE Port 1 of OSA Express3
Guess I'd ask the CE to do wrap test on second port. Back when I was doing this SG24-5948 OSA-Express Implementation Guide was a really good reference. In a message dated 12/3/2012 2:12:23 P.M. Central Standard Time, rebecca.mar...@tgslc.org writes: After dynamic activate and IPL, FC10 and FC40 paths are still not operational. Do you see what we missed? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
Thank you, Ed. I'll ask the CE about that test. We also have been reading the implementation guide. The guide and the Share presentation give you a lot of information and examples for QDIO but not so much for non-QDIO, type OSE. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: CHPID TYPE OSE Port 1 of OSA Express3
Ed- Just a quick question- - - Have you queried the OSA using OSASF? If you have not, checking the Config for each LPAR in OSASF may give you some indication. Cheryl -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Finnell Sent: Monday, December 03, 2012 3:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CHPID TYPE OSE Port 1 of OSA Express3 Guess I'd ask the CE to do wrap test on second port. Back when I was doing this SG24-5948 OSA-Express Implementation Guide was a really good reference. In a message dated 12/3/2012 2:12:23 P.M. Central Standard Time, rebecca.mar...@tgslc.org writes: After dynamic activate and IPL, FC10 and FC40 paths are still not operational. Do you see what we missed? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
