George As I said at the end of my last post, you need to explain better what precisely your problem is. The more I look at the "Signon" and "Signoff" records you posted the less I understand about what is supposed to be going on. We - because, who knows?, maybe someone else has some ideas what could be wrong - need a description of the whole scenario, preferably with real messages from the program which you think is giving trouble, TN3270E.
Also I hope you noticed that I asked for the full PROFILE data set used for the TN3270E program, that is, the contents of member OMVS.PROD.TCPIP.PARMLIB (TN32&SYSNAME) - with the appropriate substitution for the &SYSNAME variable, of course! > Here's another thing I found that doesn't match the result you're expecting. I did the NETSTAT DEVLINKS command and this is what it showed: > EZZ2826I IPv4 LAN Group Summary > EZZ2827I LanGroup: 00001 > EZZ2828I LnkName LnkStatus ArpOwner VipaOwner > EZZ2829I ------- --------- -------- --------- > EZZ2771I OSA0402LNK Active OSA0402LNK No > EZZ2771I OSA0602LNK Active OSA0602LNK Yes > ... > The VipaOwner is set to yes on OSA0602LNK. and what I posted was >> EZZ2826I IPv4 LAN Group Summary >> EZZ2827I LanGroup: 00001 >> EZZ2828I LnkName LnkStatus ArpOwner VipaOwner >> EZZ2829I ------- --------- -------- --------- >> EZZ2771I OSA0402LNK Active OSA0402LNK Yes >> EZZ2771I OSA0602LNK Active OSA0602LNK No The only difference is that I assumed/guessed that of the two interfaces, OSA0402LNK would be chosen as the "VIPA owner" by the OSA feature logic while, in the event - today - the OSA logic has in fact chosen OSA0602LNK. Sometimes Google is better than searching in the IBM manual[1]! In this case I entered "vipaowner" and the first "hit" was the following: "The wrong network device (OSA) is listed as the VipaOwner" http://www-01.ibm.com/support/docview.wss?uid=swg21430261 This is better than a Googlewhack! The explanation given in this Technote so perfectly and precisely says what I would be obliged to say in answer to your observation that I will just let you read it. The key point is the following: <quote> The VipaOwner is determined at device startup. </quote> This explains why I added "today" to my preamble. > In my last post to you I executed the command: D TCPIP,TN3270E,TELNET,CONN and it displayed under the LOGMODE the entry SNX32702, but when I look at the TELNETDEVICE I have as the LOGMODE entry NSX32702. Is this a simple transposition of letters and as a result, it's using the default value of SNX32702? There is very strong evidence from this comment that you have not yet managed to work through the TELNETDEVICE tutorial I also posted yesterday which was specifically to deal with this sort of confusion. I can tell from your mode table entry names that the code decided during negotiation at the start of the TELNET connection is IBM-3278-2-E - which you could have confirmed in your response - actually it would have been better to post the relevant part of the output from the command. What you specify in your TELNETDEVICE statement is "TELNETDEVICE 3278-2- E NSX32702" as given in an earlier post. All you have done is specify the default mode table entry name for column 2, the column used when "TN3270" protocols are agreed during TELNET negotiation - see the first example in RFC 2355 13.4. Because, during TELNET negotiation, the use of "TN3270E" protocols is agreed - see all the other examples in RFC 2355 13.4 - the mode table entry name is selected from column 3. The default entry taken from the famous Table 33 in the Communications Server Configuration Reference manual is as follows: IBM-3278-2-E NSX32702 SNX32702 What more can I say? If - having read through the "tutorial" - there is some part of it you do not understand, please reply to that post and indicate in the body of the quoted text what it is you do not understand. It's only 283 lines long so you shouldn't have any difficulty with the "line count". Chris Mason [1] Which *didn't* have the answer, by the way! On Wed, 19 Jan 2011 09:46:32 -0500, George Rodriguez <[email protected]> wrote: >Hi Chris, > >I couldn't use your last post to respond since the 1,000 line limit was >exceeded. > >Here's another thing I found that doesn't match the result you're expecting. >I did the NETSTAT DEVLINKS command and this is what it showed: > >EZZ2826I IPv4 LAN Group Summary >EZZ2827I LanGroup: 00001 >EZZ2828I LnkName LnkStatus ArpOwner VipaOwner >EZZ2829I ------- --------- -------- --------- >EZZ2771I OSA0402LNK Active OSA0402LNK No >EZZ2771I OSA0602LNK Active OSA0602LNK Yes > >EZZ2639I OSA-Express Network Traffic Analyzer Information: >EZZ2664I No OSA-Express Network Traffic Analyzer interfaces are defined >* >* >The VipaOwner is set to yes on OSA0602LNK. > >In my last post to you I executed the command: > >D TCPIP,TN3270E,TELNET,CONN > >and it displayed under the LOGMODE the entry SNX32702, but when I look at >the TELNETDEVICE I have as the LOGMODE entry NSX32702. Is this a simple >transposition of letters and as a result, it's using the default value of >SNX32702? > >Once again thanks... >* >* >*George Rodriguez* ---------------------------------------------------------------------- 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
