Re: Telnet server multiple instances?

Hello Jim,

Am 12.05.2020 um 16:43 schrieb <midrangel@xxxxxxxxxxxxxxxxx> <midrangel@xxxxxxxxxxxxxxxxx>:

Thinking yet a bit further, I think one of the originally stated goals was to present the sign on screen in the appropriate language for that specific user.

Yes. My goal is to have the standard complete german signon screen when I connect from my inside network, with (standard qpadev*) LU names. Connections from elsewhere should show a modified signon, with only user and password with no further possible modifications, in english language.

If I connect internally, I'll get my standard signon screen. If I connect externally, I see the modified signon screen in english language.

There will be two classes of user profiles. Standard (like mine), and special with LMTCPB(*YES), and a dedicated INLMNU, with just a subset of applications available.

I don't know enough about the SBS and job routing stuff yet to predict what would happen, if I sign on externally, though. :-)

These are the basic building blocks, I've come up so far. I found documentation on the IBM website how to change the default language for an user profile, and now I learned a way how to do the same for the signon screen.

How can the exit program assist in presenting the appropriate panel in the correct language when the user profile/IP address is presented to the exit BEFORE it runs? Where did it get that information?

From nowhere. See above.

Presuming that the concept of a named device (generic naming for instance "FR*", "US*, "EE*" for France, USA, and Estonia) is reasonable then just set the dang terminal emulations up, put them in a shared folder, and let the user choose the one that's right for them.

Again, my intention is not thought for a closed, commercial, company environment, so your proposal doesn't fit.

Why fuddle around with it more than that. Complicated = broken more than you want.

See my previous mail for further explanation.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc