×
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.
2009/7/2 <rob@xxxxxxxxx>:
Well, you could turn Autoreconnect on for the session properties.
That's a good idea but I'm not sure how practical it would be to
communicate that to all our users. Funnily enough the group that's
complaining loudest is the techies who have just taken over
responsibility for hosting our servers. I think they would be the most
resistant to that idea.
We have a similar command. Very useful for ending telnet. Can also be
used as a replacement for ENDPASTHR. Get's users used to the same command
as they transition from Pass Thru to telnet. BOFH did not like my
abbreviation of FO so I had to make it ET (for End Telnet or "ET go
home!").
Computing "top level" can be a bit of work. Is it worth it?
Probably not. What we've done is to change the cloned command so that
the default is now ENDCNN(*NO). In the command processing program we
look at this parameter, and if it is *NO we blindly attempt ENDPASTHR.
If it's *YES, or the ENDPASTHR fails, we pass the parameters unchanged
to QSYS/SIGNOFF. This is nicer than before in one way but it doesn't
automatically end TELNET sessions which was the joy of the previous
version.
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
