I had something like this happen once. In my case, java.exe also hung and drove up CPU. RDi 7.1 had the fix for the actual hang, however, my root cause with QShell not working was a firewall situation in our I/T area.

A Verify Connection operation <http://archive.midrange.com/wdsci-l/200803/msg00206.html#>, or trying to run STRRSESVR from your i5/OS command line might confirm if you have a firewall situation concerning server callbacks to the RSE daemon. When I authenticated to my firewall environment, then the QShell subsystem worked OK for me - there is a callback from i5/OS to the PC running WDSC involved
with the QShell subsystem/view.

In my case, when the TCP/IP
<http://archive.midrange.com/wdsci-l/200803/msg00206.html#> interface on i5/OS is restarted, I needed to re-authenticate with our firewall. The OS upgrade would have restarted your TCP/IP interface. It took a while to figure out what was going on in our environment, because QShell had worked before, and I couldn't figure out why it stopped working.

After upgrading to OS 6.1, the shell in WDSCi 7.0 doesn't seem to work. For instance, I usually compile java source from WDSC 7.0.0.8, but now the shell opens but none of the commands issued are processed. There isn't a prompt either. I think it used to be a> (in qshell through the green screen it's a $).

I'm wondering if maybe something isn't turned on.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.