×
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.
Hello John,
Am 01.04.2024 um 21:31 schrieb John Yeung <gallium.arsenide@xxxxxxxxx>:
No job logs for QP0ZSPWP.
The history does show that job QP0SZYSC starts and ends immediately, followed by job SSHD starting and ending immediately.
There aren't any other messages. The completion messages say the end code was 0 and that the job ended after 1 routing step with secondary end code 0.
Does that give any clues?
No. :-)
Sshd on Unix logs to syslog. I know OS/400 has no syslog. I don't know if newer releases IBM i have this library call. I don't know whereto sshd on IBM i logs to. But this is the crucial thing to know.
Another option would be to call sshd "by hand", in debug mode, from a shell.
-d Debug mode. The server sends verbose debug output to standard
error, and does not put itself in the background. The server
also will not fork and will only process one connection. This
option is only intended for debugging for the server. Multiple
-d options increase the debugging level. Maximum is 3.
I hope this might lead you to a probable solution.
:wq! PoC
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
