Re: Telnet server multiple instances?

As Jim mentioned this has a lot of potential and actually works remarkably well. Once Jim posts the code you'll see a number of options in there to route to various subsystems, put up 'maintenance in progress' screens, and even provide the option to kick admins to QCTL.

The session was originally done by Paul and Jim. Over the years I took Paul's place (on the 'Tall Side' of the session :-) ) then we stopped doing it for a time.

It was brought back though because with EVERYONE connecting via TCP/IP now named sessions are not so useful as back in the Twinax days. Recently there is SO much new content at COMMON Conferences that we pulled this one primarily because while still useful it hasn't changed in many years.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 5/11/2020 8:22 PM, Jim Oberholtzer wrote:

Yes, you can achieve your goal with a routing program and multiple subsystems. I don’t believe you can run multiple telnet servers but you really don’t need to. Even at V4R5.

I have samples that both Larry and I ( and another fellow named Paul Weyer) used at Common conferences called Advanced Work Management.

You will need to identify the user somehow, and we usually used the accounting code in the user profile for that purpose.

If I get time tomorrow I’ll post it in the wiki, or if you have a COMMON membership you might find it in one of the session lists, although it’s been awhile since either of us taught that class.

Each subsystem can be set up to use a different language if they are installed on the system.

Contact me privately and I can send you all the code which will compile at V4.

Jim Oberholtzer
Agile Technology Architects

On May 11, 2020, at 4:28 PM, Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello,

is it possible to have multiple instances of the telnet service, on different ports? Maybe even under ancient OS like V4R5?

Why? I'm searching for a way to differ job routing depending on how the client connects, so the session gets routed to a separate SBS (maybe QINTER2) with a non-system-default (secondary) language, and a different signon-screen.

Hard coding the LU name in the client-connection for routing-decision is a no-go, because this is error prone for unexperienced users. Also, users connecting via vt100 cannot provide a LU name. I'm searching for a fool-proof solution.

Also, since I don't know about any free, browser-based 5250 client, I guess this way is also a no-go.

Ideas, anyone?

:wq! PoC

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com