×
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.
I just had to warm-IPL our V4R4 box, after the Telnet server hung.
Yesterday afternoon, it was very difficult to get a Telnet session on
the box; this morning, it was impossible. When I signed on from a Twinax
terminal, I found that my last session from yesterday, which should have
been long-gone, was still showing up as signed on.
The associated Telnet server job wouldn't go away, not with an ENDJOB
*IMMED; not with an ENDSBS *ALL *IMMED; even after that, the server job
and its subsystem just sat there indefinitely with a status of END, and
no "restricted condition" message in the QSYSOPR queue.
After a quick STRSST, to verify that I didn't have any crashed drives, I
finally did a GO POWER, option 4, and everything was happy when it came
back up. But I'm still puzzled.
Has anybody else seen this sort of thing happen?
--
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
