As it turns out, the remote shell did start, and proceeded to suck up system usage. I didn't notice any system slowdown yesterday, but today the response time was atrocious. Went to find what was sucking down the system, and oh look, two remote shell jobs. I guess I just won't use remote shell until I get RDP (which will hopefully be soon). Waiting for the upgrade pains to subside before approaching management about it.
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Mervosh
Sent: Monday, August 23, 2010 7:23 PM
Subject: [WDSCI-L] Upgraded to OS 6.1, Shell not working
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
>, 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
with the QShell subsystem/view.
In my case, when the TCP/IP
> 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 220.127.116.11, 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.