×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hell Jim,
Am 09.11.2022 um 18:39 schrieb MidrangeL <midrangel@xxxxxxxxxxxxxxxxx>:
Easy is in the way of the beholder. You've actually gotten a couple of good ideas to set this up.
I plead guilty. :-) Apparently it wasn't enough to just mention UNIX motd in general to get people the idea about my goal and desired implementation details.
On Unix, motd is a text while which is read by the login authentication/authorization system on modern Linux, called PAM (Pluggable Authentication Modules). After authenticating and authorizing access to the individual user, *the system* prints this file's contents and launches the user's configured login shell. There is no interaction necessary for the user and also no user specific configuration for the system administrator. The user has a shell window with the message being displayed for his convenience and it will scroll out of sight when the user starts work. Each and every logon yields the same behavior.
To map this idea into the 5250 world, my thoughts were:
- The message is to be displayed *after* signon. You probably know by yourself that you don't really perceive the contents of a signon screen when running on low caffeine levels in the morning?
- No change to individual user profiles *beside* those needed anyway, such as a non-generic INLMNU. This is a break with the "true" motd which isn't dependent on e. g. a certain login shell to be used, etc. I have not found some "good" exit in WRKREGINF for my ancient V4R5 system, though, which somewhat naturally seems to be an appropriate place. Having a substitute for the routing program with a proper code seems equally appropriate.
- No separate screen popping up and needing confirmation. Imagine you need to confirm such a nagging screen each and every signon. Unnerving. :-)
- Behavior might be like the copyright message being emit on the system provided MAIN menu. It's shown when the menu is displayed or redisplayed (by pressing F3 when already at the first call stack entry) and vanishes when doing other things.
Using a routing program is one I had not thought of but it would work. In any of the cases it requires a minimum of screen/panel changes and/or a CL to send the messages. Additionally some minor work management, but this is all fairly minor stuff in the end.
As time passes, I like the idea more and more.
:wq! PoC
midrange.com
