Re: Differences in QP2TERM and SSH (pUTTY)

Pete Helgren wrote:

For example, java -version in QSH and QP2TERM
produce: java version "1.4.2". In pUTTY, nothing is output. Not
even an error.

If you used QP2SHELL (versus QSH or QP2TERM) to start sshd you can see this behavior. This is due to differences between the way QP2SHELL runs the specified program (sshd in this case) versus the way QSH and QP2TERM run the program.



Since QP2SHELL runs the program in the same process that is calling QP2SHELL, the program started by QP2SHELL inherits the ILE file descriptors for stdin, stdout and stderr that existed in the process calling QP2SHELL. These ILE descriptors can be unreliable when used in an environment that uses the fork() API (and sshd is such an environment).



Contrast with QSH or CALL QP2TERM -- these both will create a new process to run the specified program in and they both set up that new process with true IFS stream file descriptors for stdin, stdout and stderr. These IFS descriptors are "forkable".



So. Try something like this to start sshd and see if it doesn't improve things for you:

QSH CMD('/QOpenSys/usr/sbin/sshd')



-- Walt Madden