Neal This is what the error code X'8010302C' means, found by precisely following the explanation of the EZZ4310I message:
X'80' Permanent error Explanation: Request rejected due to failure of either a system or network function. X'10' LLC layer local error Explanation: A primitive was processed and an error was found by the local VTAM. X'302C' Enable Incoming connections for Port failed Explanation: A QDIO device rejected an attempt to allow connections to be enabled on this device. I was going to ask "What is your reason for suspecting that the port name is incorrect?" but then I Googled 8010302c and came up with the following as the first "hit": <quote> TCP/IP message EZZ4310I CODE 8010302C when starting OSA QDIO device Problem(Abstract) The following error appears when starting TCP/IP QDIO (OSA) device: EZZ0060I PROCESSING COMMAND: VARY TCPIP,,START,OSAD900 EZZ0053I COMMAND VARY START COMPLETED SUCCESSFULLY EZZ4310I ERROR: CODE=8010302C REPORTED ON DEVICE OSAD900. DIAGNOSTIC CODE: xx Cause This error occurs when there is a mismatch in VTAM and TCP/IP definitions. The device_name specified in the TCP/IP DEVICE and LINK statements must match the PORTNAME specified in the VTAM TRLE statement for the OSA- Express QDIO PORT. Also, all LPARs using the OSA PORT on a CEC must use the same PORTNAME. The OSA will remember the first PORTNAME that is used to activate the OSA PORT. All subsequent users must use this same PORTNAME. If an incorrect name is used and is remembered by the OSA, the OSA can be reset using the VARY OFFLINE command for all CHPIDs that used that OSA PORT. Resolving the problem Use the same PORTNAME (device_name in TCP/IP DEVICE and LINK statements) in all VTAM and TCP/IP definitions that use an OSA PORT. </quote> Note that an OSA feature is like an elephant, it never forgets - unless you take a massive gun to it and "VARY OFFLINE command for all CHPIDs that used that OSA PORT." If you want to update a TRLE definition use V NET,ACT,UPDATE=ALL,ID=trl- major-node-name but make sure that IP has "stopped" the DEVICE. You should be able to discover your DEVICE names with the output from the NETSTAT DEVLINKS command. There is no need to stop VTAM. There is a very helpful guide to changing DEVICE and LINK statements entitled "Modifying DEVICE and LINK statements" under "Summary of DEVICE and LINK statements" under Chapter 2, "TCP/IP profile (PROFILE.TCPIP) and configuration statements" in the z/OS Communications Server IP Configuration Reference manual. However, you are on V1R4 and I checked V1R10 so I made sure something similar was available in V1R4 and here it is: <quote> Modifying DEVICE and LINK statements: To modify any DEVICE and LINK statement values, follow these steps: Stop the device. Use a VARY TCP/IP command with an OBEYFILE that contains: A new HOME statement that does not contain the home IP address or addresses of the LINK or LINKs involved in the DELETE DELETE linkname and DELETE devicename statements Use a VARY TCPIP command with an OBEYFILE that contains: The changed DEVICE and LINK statements A new HOME statement that includes the home IP address or addresses of the LINK or LINKs being added Start the device. Note: To dynamically change a value on a LINK statement only, do not perform the DELETE devicename and redefine DEVICE steps in the above list. </quote> Anyhow, thanks for "suggesting" I should look this up. I hadn't realised/remembered it was so complicated! Chris Mason On Mon, 15 Jun 2009 08:48:25 -0500, Chris Mason <[email protected]> wrote: >Neal > >By some sort of pure coincidence I have just answered a query on the >IBMTCP-L list regarding changing TRLE definitions. IBMTCP-L is in fact your >best bet for problems involving z/OS Communications Server. > >What does D NET,TRL,TRLE=trle-name show for each of the TRLE resources >you are trying to change at the time you are trying to change them? Perhaps >you should use the D NET,TRL command first in order to be sure what your >current TRL and TRLE names are! > >Meantime I'll have a look at your post in more detail. > >Chris Mason > >On Mon, 15 Jun 2009 09:34:05 -0400, Neal Eckhardt ><[email protected]> wrote: > >>Ok, I tried to get our new OSA adapter going on our z9. I have it working >>perfectly on our test LPAR. When trying to bring it up on our production >>LPAR I get the following message for both interfaces: >> >>EZZ4310I ERROR: CODE=8010302C REPORTED ON DEVICE GIGPORP2. >DIAGNOSTIC >>CODE: 00 >>EZZ4309I ATTEMPTING TO RECOVER DEVICE GIGPORP2 >> >>I believe this is due to the PORTNAME being different on the two LPARS >>(though at least one of the two was correct at one time. These messages >>keep coming out even if I stop the device. >> >>I cannot seem to update the TRLE to utilize the correct PORTNAME. I get >>the following error when truing to update it with UPDATE=ALL in the VARY >>ACT. >> >>V NET,ACT,ID=TRL400P,UPDATE=ALL, >>IST097I VARY ACCEPTED, >>IST886I VARY ACT ISTTRL CHANGE TRLE400P FAILED 736, >>IST523I REASON = INVALID RESOURCE CURRENT STATE, >>IST314I END, >>IST886I VARY ACT ISTTRL DELETE IUTW0106 FROM ISTTRL FAILED 737, >>IST523I REASON = INVALID RESOURCE CURRENT STATE, >>IST314I END, >>IST886I VARY ACT ISTTRL DELETE IUTW0102 FROM ISTTRL FAILED 738, >>IST523I REASON = INVALID RESOURCE CURRENT STATE, >>IST314I END, >>IST886I VARY ACT ISTTRL DELETE TRLE600P FROM ISTTRL FAILED 739, >>IST523I REASON = INVALID RESOURCE CURRENT STATE, >>IST314I END, >>IST093I,ISTTRL,ACTIVE, >> >>How can I get this changes without bringing VTAM down. >> >>Also, I tried to update the DEVICE and LINK definitions in TCPIP with an >>obeyfile. The new devices were defined, but the links stayed defined with >>the old DEVICE, with this error message: >> >>LINK NAME GIGP1 ON LINE 3 IS ALREADY DEFINED >>LINK NAME GIGP2 ON LINE 6 IS ALREADY DEFINED >> >>How can I get around this or do I just create a new LINK? >> >>And the V TCPIP stop and start commands do not recognize either the old, >>or new device names. >> >>And of course I saved the best for last, we are still running z/OS 1.4. >> >>Thanks for any insight. >> >>Neal ---------------------------------------------------------------------- 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
