Patrick Thanks for the clarification.
>I started doing the hex to decimal conversion and received the message: >EZZ6057I NO QUALIFYING MATCHES I think this is saying that you tried the command I suggested without the "T" and in principle it worked but, with a converted version of the "connection identifier" and not a valid one, you got the EZZ6057I message. It would be interesting if you confirmed that use of the command - without the "T" - on your V1R11 system but with a "connection identifier" which would match works - just to tie it up neatly. Unfortunately, George not only included the "T" on his V1R9 system but also took my suggestion to try the LUNAME parameter in place of the CONN parameter, so his test wasn't quite the confirmation I had hoped for either! Chris Mason On Thu, 27 Jan 2011 14:24:03 -0600, Patrick Lyon <ptl...@midamerican.com> wrote: >On Wed, 26 Jan 2011 13:35:19 -0600, Chris Mason ><chrisma...@belgacom.net> wrote: > >>George >> >>I scanned the IP System Administrators Commands manual in order to check >>on this matter of the CONN operand. There's no actual explanation but it's >>suspicious that, when entered as a command operand, the value is always >>decimal in the examples whereas the CONN column in output is clearly >>hexadecimal. It's not at all "user-friendly" that the number would need to be >>converted - particularly when very large as yours are! >> >>If this is correct your 38B37 needs to be entered as 232247. This is clearly >>useless operationally. There's a faint chance that you can enter the number >in >>any C format so you could try 0x38B37. That is just a wild guess but it's >worth >>a try. >> >>Chris Mason >> > >My apologies Chris. This post is where I went awry. > >I started doing the hex to decimal conversion and received the message: >EZZ6057I NO QUALIFYING MATCHES > >So I then inadvertantly issued the following command and got the "error" >which I mentioned in my previous post, which was due to my own accord of >not having the second "CONN" in the command: >D TCPIP,TN3270,TELNET,CONN=nnnnnn > >It was apparently then when I went scrounging into the manuals and found >the TELNET option, which also works on my 1.11 system. > >So that mention of the error was purely my mistake. > >Sorry for the inconvenience. > >Regards, >Pat L. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
