It is worse than previously stated. It is an intermittant problem. Usually it fails trying to determine the shell type, but ocassiona +lly it gets past that point only to fail later timingout waiting for stdout. Looking at this with debu +g, shows that it fails to determine what shell type it is because the output from the echo;echo bsherrno=$? command is never seen on stdout. I do see the echo of the command being entered, but not the outpu +t. I.e. I am not seeing bsherrno=0 on the stdout. The few times that it does get past this point in th +e code, I do see the bsherrno=0 in stdout. I did determine that if I remove my .profile, it does not fail to determine the shell type as often +. Another clarifying point. I am using ksh as my shell. I am assuming that since bsh and ksh both u +se $? to show the return code of the previous command, this should not cause me a problem. The bottom line here is that I have not been able to get this module to successfully work yet.