Tim,
INV-NAME is quite clearly in the TN3270E RFC, RFC 2355. The explanation is
the following:
<quote>
7.1.5 REJECT Command
If the server wishes to deny the request, it sends back the DEVICE-
TYPE REJECT command with one of the following reason-codes:
Reason code name Explanation
---------------- -----------------------------------
...
INV-NAME The resource-name or device-name
specified in the CONNECT or ASSOCIATE
command is not known to the server.
...
</quote>
If you now take a look at the examples in section 13.4, you will see
examples of the CONNECT command in use. From 7.1.5 we can see that the
REJECT command is sent by the server and results from a use of the CONNECT
command by the client. The first example in which the client uses the
CONNECT command is the following:
<quote>
The following example shows a TN3270E-capable server and a TN3270E-
capable client establishing a terminal session where the client
requests a specific device-name:
Server: IAC DO TN3270E
Client: IAC WILL TN3270E
Server: IAC SB TN3270E SEND DEVICE-TYPE IAC SE
Client: IAC SB TN3270E DEVICE-TYPE REQUEST IBM-3278-5-E
CONNECT myterm IAC SE
Server: IAC SB TN3270E DEVICE-TYPE IS IBM-3278-5-E CONNECT
myterm IAC SE
Client: IAC SB TN3270E FUNCTIONS REQUEST RESPONSES
BIND-IMAGE IAC SE
Server: IAC SB TN3270E FUNCTIONS IS RESPONSES BIND-IMAGE
IAC SE
(3270 data stream is exchanged)
</quote>
This means the client actually specified the name of a "device" when trying
to set up the TELNET connection. You should be able to see something like
this if you trace your exchange.
I expect that the failing emulator somehow has a specification for a
"device" name, perhaps coded as an example or coded by you thinking the name
had another purpose.
I see from Google that CLI ET2000 specifications include the following:
<quote>
TN3270 Features
. IBM 3278-2-E or 3278-5-E color terminal emulation
. Device naming
...
</quote>
I wanted to bring your attention here to "device naming" which is where you
are getting into trouble. However my attention was taken by the first
so-called "feature" which holes the credibility of CLI ET2000 well below the
water-line so I included it as well. <g>
Having so closely defined the problem, I decided to go the extra kilometer
and see if I could spot the specification that is very probably getting you
into trouble. I downloaded the CLI ET2000 user manual and there it was,
under the "SESSIONx CONFIGURATION MENU": "DEVICE NAME". This is described as
the "Name the host session" but a better description might have been "Name
the host SNA logical unit".
Turning again to RFC 2355, you'll see what I mean in the following paragraph
found under 7.1.1 Device Pools:
<quote>
The terms "device-name", "LU name" and "network name" can be
considered interchangeable in this document. They refer to a
specific terminal or printer device.
</quote>
Note: LU = "logical unit".
Incidentally "A blank entry will cause the host to create a virtual device
name." is nonsense. What a blank entry very probably means is simply that
the server will select the name of the logical unit as in the example in RFC
2355 immediately before the one I quoted above.
Chris Mason
----- Original Message -----
From: "Tim Pinkawa" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Monday, 05 June, 2006 7:24 AM
Subject: What could cause INV-NAME?
> I have a few special purpose emulator devices (CLI ET2000s with the
> latest firmware) connecting over TN3270 and when they try to connect I
> get a "REJECT REASON: INV-NAME" response. I'm able to connect with a
> variety of PC-based emulators like Vista tn3270 and x3270. I did some
> looking and it appears to be in the TN3270 RFC, although there was not
> much explanation on it and I can't find anything in IBM TCP/IP
> documentation.
>
> Thanks!
----------------------------------------------------------------------
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
