|
Anyone else have problems with the V5R1 telnet server? A spinoff company has a 270 that had the problem on two mornings in about two months, but they weren't on the latest cum at the time. This morning our 720 was not accessible via telnet, so only the dumb terminals were up. We were on the latest cum, but I see one was just released 2 days ago.... Simple fix - just end the telnet server then start it. But you can't just start it because it half-way starts. There are QTVDEVICE jobs running but no QTVTELNET that I could see. Neither port 23 nor 992 would answer. VERY frustrating way to get forced into an early morning start! I'm going to order the latest cum/group/hipers, but I don't know if that will help. We've been on V5R1 for 3 weeks and this is the first time with this problem. We power down every Sunday night (old habit, keeps everything happy) and ENDSBS *ALL every night before backup (again, old habit to help the other sysop sleep better!) Any suggestions other than get the cum? TIA!
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.