Telnet TerminalName / iSeries WorkstationID

Question

Hi,

I'm trying to create a TelnetTerminal session to our IBM iSeries. I've got the connection working (which was very easy, kudos to rebex!) but now I need to configure how it connects.

For example, connecting through our usual emulators we specify a 'WorkstationID' which will configure how the screen appears based on the name (eg. if the WorkstationID has 'scan' in it, the screen will be configured for viewing on a scanner).

I thought the property TerminalName for the TelnetTerminalControl would do it, but it doesn't seem to be working.

Does anybody have any advice?

Thanks, Tom

Comments

Have you set the TelnetTerminalControl.Options.TerminalName before you call Connect method? It is necessary, because terminal name is reported to the remote end shortly after the connection is established and only if the remote end asks for it.

---

Hi, thanks for the reply.

Yup, I'm setting the properties before calling Connect():

TelnetTerminalControl1.ServerName = "ourservername"
TelnetTerminalControl1.Options.TerminalName = "scan"
TelnetTerminalControl1.Connect()

Perhaps it's something at our server end that's the problem, though having said that all the clients I've tested with all behave correctly when I've set the name..hmmm...

---

Can you please create a communication log of the TelnetTerminalControl and also of your usual emulator and send it to support@rebex.net for comparison? Maybe we can spot some important difference.

Communication log of the Rebex control can be done like this:

TelnetTerminalControl1.LogWriter = new Rebex.FileLogWriter("C:\temp\telnet.log", Rebex.LogLevel.Verbose)

---

Hi, As it turns out we are using the telnet session in a different way now, so I have no need to set the terminal name.

Thanks for your help anyway. Tom

Answer 1

In case anyone else runs into the same issue - please try creating two Wireshark logs:

• One log showing a Rebex Telnet connection with the terminal name set.
• Another log showing a connection from one of your usual emulators that works as excpected.

By comparing the two logs, we should be able to determine what went wrong and how to solve it.