Stuart Thanks for getting back to us. As well as missing that the LINK statement name in the EZZ0331I message was IUTSAMEH rather than EZASAMEMVS, also missed that the message arose from the entry of the START command rather than being in a log as the messages in your second post. So that's one mystery replaced with another!
Just to be sure you know how you should define an IUTSAMEH interface in the absence of the DYNAMICXCF parameter, here's what is stated in the section "Step 1: Prepare your TCP/IP configuration" in Chapter 6, "Using Enterprise Extender (EE)" in the z/OS Communications Server (CS) Network Implementation Guide manual: <quote> To manually configure IUTSAMEH definitions, do the following: - For IPv4, define and start IUTSAMEH using the DEVICE, LINK, HOME, and START statements. ... Following is an example of a manual configuration: ;******************************* ; VTAM to TCPIP Stack, IPv4 ;******************************* DEVICE IUTSAMEH MPCPTP LINK EELINK MPCPTP IUTSAMEH HOME 93.1.1.1 EELINK START IUTSAMEH </quote> In fact, the only part of the example which is flexible is the actual IPv4 address of course and the name used within the LINK statement and, hence, the HOME statement list. - Now to the "port name" problem: This refers to the TRLE statements which define your OSA feature port in QDIO mode. There is a PORTNAME operand which must specify the same value on all TRLE statements which refer to the same OSA port. If you define multiple OSA feature ports in any one LPAR, the names specified by the PORTNAME operand must be different. I'm afraid I don't have experience with VM so I can't help with any matters peculiar to VM. Here are a couple of relevant paragraphs taken from the description of the PORTNAME operand in the z/OS CS SNA Resource Definition Reference manual. I know, you'd expect them to be in a CS IP manual but TRLEs are defined in the CS SNA manuals because VTAM developers are responsible for all the more recent IP component I/O. <quote> Specifies the Open Systems Adapter (OSA) port name. The name must be unique in one logical partition and it must be unique for an OSA port shared by multiple logical partitions. Some OSA-Express3 features provide support for multiple ports per network interface card (NIC). The port name assigned to each port on a specific NIC must also be unique. In general, each defined port name should be unique within your network. The maximum length for the port_name value is 8 characters. For an Open Systems Adapter-Express (OSA-Express) port operating in QDIO mode, the name specified for the port_name value is downloaded into the OSA- Express when the first TCP/IP device for this OSA-Express port is activated. For OSA-Express QDIO connections, this name must be defined as the device name in the TCP/IP profile DEVICE statement or as the port name in the TCP/IP profile INTERFACE statement for any TCP/IP stack that will use this OSA-Express feature. This name must also be defined as the port name on a VARY TCPIP,,OSAENTA command or the port name on an OSAENTA profile statement if a TCP/IP stack will start an OSA-Express network traffic analyzer trace on this OSA feature. </quote> I see your DEVICE name in the definitions you posted is OSA400 which you also describe as your "port name" so, in principle, that's all correct. I hope you haven't been confused by the Enterprise Extender XCA major node PORT statement. That also has a name but it has nothing to do with OSA feature port QDIO definitions. If you are still confused or it still doesn't work, please post again with relevant definitions. Also I'm sure we'd all appreciate full stops and capital letters where appropriate. I had to annotate you last post before - thinking - I had understood it! Chris Mason On Tue, 24 Feb 2009 14:27:08 -0000, Stuart Willis <[email protected]> wrote: >Hi All > >Sorry for the delay in getting back but I'm now back on the task of >setting up my sysplex. > >I seem to have opened a can of worms here! > >I'm a one man band as it were and do all the sysproging here, VM Z/OS >VTAM TCPIP etc so I get it to work and leave it as not having the time >to full understand the internals of how it work and what's happening >under the covers. > >This is what I did > >In my original TCPIP PROFILE I had the Link and device statements for >the OSA, Enterprise Extender, and IUSAMEH use by E/E and the 2 home >addresses. > > >DEVICE OSA400 MPCIPA NONROUTER <= the OSA I was having the problem with > >LINK LNKOSA40 IPAQGNET OSA400 > >DEVICE EEVIPAD VIRTUAL 0 <= Enterprise Extender >LINK EEVIPAL VIRTUAL 0 EEVIPAD > >DEVICE IUTSAMEH MPCPTP AUTORESTART <= required for E/E >LINK IUTSAMEH MPCPTP IUTSAMEH > >HOME > > 10.5.1.110 LNKOSA40 <= Home address for OSA > 10.5.1.151 EEVIPAL <= Home address for E/E > >I then did a V,TCPIP,,START,OSA400 which for some reason issues the >EZZ0331I message always has. I also get this if I do an OBEYFILE that >alters any of the devices in the TCPIP profile. > >At this point I did not have any DYNAMICXCF statements active in My >TCPIP profile I know that DYNAMICXCF dynamically create IUSAMEH >statement for you if you have it allocated you get a duplicate IUSAMEH >error message when you bring TCPIP up. > >Hope this has cleared this up Let me know of not. > >One question I have 2 OSA cards with 64 address defined to each port. > >The devices are attached to ZOS systems under VM of on 1st OSA I have >1600-1603 attached to ZPLEX1 as 400-403 with a port name of OSA400, I >have 1604-1607 attached to ZPLEX2 400-403 with a port name of OSA400 >and all subsequent systems that use the 16nn OSA range this is what it >seems to imply by the 3150 error. > > >X'3150' Wrong Portname > Explanation: An attempt was made to activate > an OSA-Express port in QDIO mode. The Portname > for this activation attempt did not match the Portname > already assigned to this port by a previous user. > All z/OS users of that port must activate with > the same Portname. > > >Best Regards > >Stuart > > > > > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Chris Mason >Sent: 21 February 2009 09:29 >To: [email protected] >Subject: Re: OSA's Error codes > >Stuart > >Would you know how it came about that there the following message >appeared in the log in your first post but did *not* appear in the two >logs in >your second post? > >EZZ0331I NO HOME ADDRESS ASSIGNED TO LINK IUTSAMEH > >Did you have explicitly defined a pair of DEVICE and LINK statements in >essence if not completely as follows: > >DEVICE IUTSAMEH MPCPTP >LINK IUTSAMEH MPCPTP IUTSAMEH > >which you removed? > >It would be surprising if you had removed that DEVICE and LINK pair and >then >performed your tests in answer to Ed Finnell's post since it was >precisely that >interface definition to which Ed was referring! > >Chris Mason > >On Thu, 19 Feb 2009 15:22:29 -0000, Stuart Willis ><[email protected]> wrote: > >>Hi >> >>I have proved (I think) that the OSA dose have a Home address. >> >>Output from the TCPIP proc with a Home address all I get is the >EZZ4310I >> >>----------------------------------------------------------------------- >- >> >> >> >>---- THURSDAY, 19 FEB 2009 ---- >> >> IEF695I START TCPIP WITH JOBNAME TCPIP IS ASSIGNED TO USER >TCPIP >>, GRO >> $HASP373 TCPIP STARTED >> >> IEF403I TCPIP - STARTED - TIME=09.03.46 >> >> IEE252I MEMBER CTIEZB00 FOUND IN ADCD.Z110.PARMLIB >> >> IEE252I MEMBER CTIIDS00 FOUND IN SYS1.PARMLIB >> >> IEE252I MEMBER CTINTA00 FOUND IN SYS1.PARMLIB >> >> EZZ7450I FFST SUBSYSTEM IS NOT INSTALLED >> >> EZZ0162I HOST NAME FOR TCPIP IS ZOS10 >> >> EZZ0300I OPENED PROFILE FILE DD:PROFILE >> >> EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE >> >> EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE >> >> EZZ0334I IP FORWARDING IS DISABLED >> >> EZZ0335I ICMP WILL IGNORE REDIRECTS >> >> EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED >> >> EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED >> >> EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP >> >> EZZ4310I ERROR: CODE=80103150 REPORTED ON DEVICE OSA400. >DIAGNOSTIC >>CODE: 03 >> EZZ4315I DEACTIVATION COMPLETE FOR DEVICE OSA400 >> >> EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE. >> >> EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE. >> >> EZD1176I TCPIP HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GROUP >>EZBTCPCS >> S FTPD >> >> S PORTMAP >> >>EZZ0162I HOST NAME FOR TCPIP IS ZOS10 >>EZZ0300I OPENED PROFILE FILE DD:PROFILE >>EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE >>EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE >>EZZ0334I IP FORWARDING IS DISABLED >>EZZ0335I ICMP WILL IGNORE REDIRECTS >>EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED >>EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED >> >> >> >>Remove the Host entry I get the EZZ4310I error and an EZZ0331I no Home >>---------------------------------------------------------------------- >>address >>------- >> >> >>---- THURSDAY, 19 FEB 2009 ---- >> >> IEF695I START TCPIP WITH JOBNAME TCPIP IS ASSIGNED TO USER >TCPIP >>, GROU >> $HASP373 TCPIP STARTED >> >> IEF403I TCPIP - STARTED - TIME=09.12.40 >> >> IEE252I MEMBER CTIEZB00 FOUND IN ADCD.Z110.PARMLIB >> >> IEE252I MEMBER CTIIDS00 FOUND IN SYS1.PARMLIB >> >> IEE252I MEMBER CTINTA00 FOUND IN SYS1.PARMLIB >> >> EZZ7450I FFST SUBSYSTEM IS NOT INSTALLED >> >> EZZ0162I HOST NAME FOR TCPIP IS ZOS10 >> >> EZZ0300I OPENED PROFILE FILE DD:PROFILE >> >> EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE >> >> EZZ0323I HOME STATEMENT ON LINE 136 HAD NO ENTRIES >> >> EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE >> >> EZZ0334I IP FORWARDING IS DISABLED >> >> EZZ0335I ICMP WILL IGNORE REDIRECTS >> >> EZZ0331I NO HOME ADDRESS ASSIGNED TO LINK LNKOSA40 <======= >> >> EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED >> >> EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED >> >> EZZ4202I Z/OS UNIX - TCP/IP CONNECTION ESTABLISHED FOR TCPIP >> >> EZZ4310I ERROR: CODE=80103150 REPORTED ON DEVICE OSA400. >DIAGNOSTIC >>CODE: 03 >> EZZ4315I DEACTIVATION COMPLETE FOR DEVICE OSA400 >> >> EZB6473I TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE. >> >> EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE. >> >> EZD1176I TCPIP HAS SUCCESSFULLY JOINED THE TCP/IP SYSPLEX GROUP >>EZBTCPCS >> S FTPD >> >> S PORTMAP >> >> >> >>EZZ0162I HOST NAME FOR TCPIP IS ZOS10 >>EZZ0300I OPENED PROFILE FILE DD:PROFILE >>EZZ0309I PROFILE PROCESSING BEGINNING FOR DD:PROFILE >>EZZ0323I HOME STATEMENT ON LINE 136 HAD NO ENTRIES >>EZZ0316I PROFILE PROCESSING COMPLETE FOR FILE DD:PROFILE >>EZZ0334I IP FORWARDING IS DISABLED >>EZZ0335I ICMP WILL IGNORE REDIRECTS >>EZZ0331I NO HOME ADDRESS ASSIGNED TO LINK LNKOSA40 >><======================= >>EZZ0338I TCP PORTS 1 THRU 1023 ARE RESERVED >>EZZ0338I UDP PORTS 1 THRU 1023 ARE RESERVED >> >> >>Regards, >>Stuart >> >> >> >>-----Original Message----- >>From: IBM Mainframe Discussion List [mailto:[email protected]] On >>Behalf Of Ed Finnell >>Sent: 19 February 2009 14:15 >>To: [email protected] >>Subject: Re: OSA's Error codes >> >> >>In a message dated 2/19/2009 5:02:31 A.M. Central Standard Time, >>[email protected] writes: >> >>error Code I can find in any manual I have looked in the Data link >>control >>(DLC) >>status codes I can find 30nn and 32nn but no 31nn ? >>>> >>I plugged it into LOOKAT and got the expected answer? >> >> >>EZZ0331I No home address assigned to link linkname >> >> >>Explanation: The link was defined but no home address was given for >it. >>No >>TCP/IP traffic can flow over this link. >>System Action: TCP/IP continues. >>Operator Response: Assign a home address for the link using the HOME >>statement. Rerun the profile. >>System Programmer Response: None. >>Module: EZACFMS1 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
