Re: Bypass sign-on screen (ODBC connections and QAQQINI)

Hello Jim,

Am 10.09.2024 um 16:02 schrieb Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>:

What example code would you like? If I have it I'll pass it along.

If only knew. :-)

I have a loose heap of puzzle pieces left to the complete picture being recognizable for me. Pretty sure there are some extra-pieces in there which might be "alternative pieces". This makes it hard to decide what individual piece I might actually miss.

The overall picture should be: How to connect with any 5250 client — with a specific device name configured — to my machine, so the "incoming terminal request" gets directly "connected" to a *PGM, maybe using the ACQ technique mentioned by Rob Behrend? There shall be no signon screen, the *PGM is to be run with e. g. the default user profile, such as QUSER.

I know how to use workstation entries in subsystems, but I fail to see how I can bypass the sign-on screen but instead call a *PGM object. I also fail to see how to reasonably automate the this with the ACQ mentioned by Rob: I don't know a dynamic device name from e. g. a telnet connection beforehand. AFAIK device names from clients need to be unique, but I assume they become numbered, once a second client connects with the same device name?

As to the unique device name routed to a specific subsystem, that's all workstation entries.

Yap, that part is reasonably clear to me for now.

Unless you use some of the advanced techniques I used to teach at COMMON by using a routing program, maybe that's what you were looking for?

Sounds like it. If you have some pointers to your COMMON presentations, that would be awesome. And a starting point for me, maybe.

More importantly it's the initial program that's called for the device log in that counts as how the screen is handled. That is also a user issue.

Ah, an interesting remark. But how to set or pass an initial program when there is no sign-on screen with a field to be filled? Or do you suggest that a certain user profile contains an initial program and *that* makes my "kiosk like" application appear? 🤔

So it's maybe really boiling down to your routing program technique being applied?

In short, there are lots of options

Yes, that's my issue. Can't see the forest because too many trees.

and I'm not sure one is any better than any other except maybe in complexity to set up and maintain.

Well, the less complex, the better. Right?

Thank you for helping me!

:wq! PoC