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
