Hélio In case you didn't see precisely what Luke was asking you to do - and I'll admit it was only when I noticed that the TELNET flavour of the VARY command did *not* include the CONN option - he is saying that it was incorrect of you to be using the TN3270E program address space name but that you should be using the name of the main Communications Server (CS) address space. As I noted, there is no such thing as a VARY TCPIP,<n>,TELNET,CONN command but there is a VARY TCPIP,<n>,CONN command where "n" has to be the name of the main CS IP address space.
I wondered whether the "connection identifier" which you have derived from a DISPLAY TCPIP,<n>,TELNET,CONN command might be different from those obtained by a DISPLAY TCPIP,<n>,NETSTAT,CONN command but there are lots of reasons why the "connection identifier" should be the same entity. It depends on your release of z/OS, but, with the later releases, the "TELNET" in the TN3270E commands is optional. This "flexibility" can add to possible confusion - as we see! You should not be using the TN3270E INACT option in this context since that is all about making the name of what is or could become an APPL statement - acting as a secondary LU - unavailable. What I started out saying until I noticed that Luke had "nailed" it, was the following which still makes a useful point - although reveals a problem: A configuration supported by the z/OS Communications Server TN3270E program consists of an SNA session which the TN3270E program acting as a TN3270 server concatenates to a TN3270 TCP connection. The fact that there is no name under APPLID in the DISPLAY TCPIP,<tn3270servername>,CONN command may indicate that the SNA session part of the configuration no longer exists. However, the "A" under "TSP PTR" indicates that there should be an application - so that's a mystery! However, depending on your TN3270E PROFILE specifications, once the SNA session is no longer there, the connection may still exist. In fact, checking your post, I see that the connection persists even after CICS has "stopped", presumed to be shut down. Thus making sure that the SNA session is terminated with a VTAM VARY INACT may not achieve your objective which is to terminate the TN3270 TCP connection. Chris Mason On Mon, 28 Feb 2011 15:33:17 -0600, Rabbe, Luke <[email protected]> wrote: >What happens if you try V TCPIP,tcpip_procname,DROP,CONN=000EECA5? > >Luke >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of HELIO >Sent: Monday, February 28, 2011 3:09 PM >To: [email protected] >Subject: Connection locked > >All list, > > >I have the following situation: A conection was locked and could not >drop it, we have to stop the tcpip profile. >A connection is terminal the CICS, > >D TCPIP,TN3270U,TELNET,CONN,PORT=23,IPA=172.18.35.2 >EZZ6064I TELNET CONNECTION DISPLAY 812 > EN TSP >CONN TY IPADDR..PORT LUNAME APPLID PTR LOGMODE >-------- -- ---------------------- -------- -------- --- -------- >001742F7 172.18.35.2..3483 RURI0359 CICSREL TAE SNX32702 >001742F8 172.18.35.2..3484 RURI0350 CICSREL TAE SNX32702 >001742F3 172.18.35.2..3479 RURI0354 CICSREL TAE SNX32702 >001742F2 172.18.35.2..3478 RURI0355 CICSREL TAE SNX32702 >001742F1 172.18.35.2..3477 RURI0353 CICSREL TAE SNX32702 >001742F0 172.18.35.2..3476 RURI0352 CICSREL TAE SNX32702 >*000EECA5 172.18.35.2..3696 RURI0351 TAE >SNX32702* > >----- PORT: 23 ACTIVE PROF: CURR CONNS: 289 >------------------------------------------------------------ > >I used the follow commands: > >V TCPIP,TN3270U,TELNET,INACT,RURI0351 >V NET,INACT,ID=RURI0351,F > >V TCPIP,TN3270U,DROP,CONN=000EECA5 > > >After the command issued, the following message issued EZZ0059I >INCORRECT CONNECTION NUMBER 00EECA5 > >I can't drop the connection. >I stoped the CICS and the connection was active. > >Anyone know how I can drop (force) the connection without stop tcpip >profile. > >-- > >Hélio. ---------------------------------------------------------------------- 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
