|
Douglas Handy <dhandy@xxxxxxxxx> wrote:
It this is for inactivity timeouts, beware the MAXRCD method is only effective while your application is active.If a user has access to other displays (eg spool file displays or whatever), you have lost control.
Fortunately, that isn't the case with the application in question: the terminal sessions in question quite literally have everybody but the 3 relevant public accounts locked out of them, and those three public accounts are locked into an absurdly simple (in terms of user interface, not in terms of back-end) "authorization code on demand" application we're just about to roll out, using auto-login to sign them on, a CL program to make sure that even if the device is newly autoconfigured, it's got all other accounts locked out, only one screen, and (with initial menu set to *SIGNOFF, and both ATTN and SysRq disabled) no way out of that screen that doesn't involve an immediate signoff.
In other words, from that particular entire series of TN5250 devices, it's the Code on Demand application, or nothing.
-- JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
