Neal There's something wrong with your manner of posting. I detected your last - maybe - post only in the Google Groups digest. The post did not and does not appear in the archives:
http://bama.ua.edu/cgi-bin/wa?A1=ind0906&L=ibm-main&O=D&H=0&D=1&T=0 which is where I keep a look out during the day rather than be swamped by e- mails. The same applies to your prompt post where you provide the D NET,TRL,TRLE= output. I'm going to have to post this as a "reply" to my previous post". - So I'm glad you think you've worked out your problem. Regarding the D NET,TRL,TRLE= messages, going by the examples in the Communications Server SNA Operations manual, I believe the OSA feature was "in use" because the IST1577I and IST1221I messages are there. You can "delete" a TRL only when it is not "in use". Presumably it was still "in use" because you couldn't quite pin down what name to use in the STOP device- name command! Chris Mason - Lost post 1: D NET,TRL,TRLE=TRLE400P, IST097I DISPLAY ACCEPTED, IST075I NAME = TRLE400P, TYPE = TRLE 156, IST486I STATUS= ACTIV----E, DESIRED STATE= ACTIV, IST087I TYPE = LEASED , CONTROL = MPC , HPDT = YES, IST1715I MPCLEVEL = QDIO MPCUSAGE = SHARE, IST1716I PORTNAME = GIGPORP1 LINKNUM = 0 OSA CODE LEVEL = 0892 IST1577I HEADER SIZE = 4096 DATA SIZE = 0 STORAGE = ***NA***, IST1221I WRITE DEV = 0401 STATUS = ACTIVE STATE = ONLINE, IST1577I HEADER SIZE = 4092 DATA SIZE = 0 STORAGE = ***NA***, IST1221I READ DEV = 0400 STATUS = ACTIVE STATE = ONLINE, IST1221I DATA DEV = 0402 STATUS = RESET STATE = N/A, IST1724I I/O TRACE = OFF TRACE LENGTH = *NA*, IST314I END, - Lost post 2: Thanks Chris, I got a good education about OSA adapters outta this, as I finally pieced together what happened. My test system was running fine with the following TRLE definitions: Addresses (portname): 400-402(gigport2) 600-602(gigport1) I entered these in error originally since I thought the 400 addresses were gigport1 and the 600 address were gigport2. That is what I logically would have done. When I created the TRLE entries on the production system, I had both address ranges with the same PORTNAME and got those recovery errors. Not realizing that the PORTNAMES had to be the same across the LPARS, I changed them. That did not fix the error, so Google being my friend eventually got me to the fact that they had to have the same name, and I vaguely remembered reading that in the manual. Unfortunately, I was never able to get the TRLEs to be updated, but when I bought down my test system, it grabbed the ports, and renamed the portname, so them the test system quit working. I think, a reIPL is the best solution now, I stopped the TRL and devices from auto starting on both sustems so I can do a "controlled" start after the IPL. Thanks for your help. All of the pieces eventually came together. It's not often anymore that I get to fight new installation problems like this. 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
