Re: Spec for New V7R1 Development Machine/Remotely Racked

[rob@xxxxxxxxx]

I always use the shared key route.  I have never used the dedicated key 
route.  Well at least not since the guy walked over to me at the IBM lab 
and slapped me because he could no longer remotely access the console 
session.

Imagine this:
Bubba is working his shift for downtime.  He's doing the save or something 
while you relax before you come in and do the OS upgrade.  He hates 
touching the HMC directly because it's not ergonomically placed in the 
rack, and, if he uses it remotely from the PC (located on a desk right 
next to the rack) he can copy and paste the appropriate save commands and 
whatnot from a script from a word document.  Save aborts.  Bubba is a good 
programmer but OS type issues are not his strong suit.  So he calls you 
up.  You pounce on your laptop at home and use that shared session to look 
at the joblog (remember, he is doing his save in a dedicated state with 
all subsystems down and comm disabled).  You resolve the issue remotely, 
are able to continue on from where you left off, and only lost about 20 
minutes of time.

Real life situation.  Happens all the time.

Screw dedicated session, shared session is the only way to go.  I did have 
one person here who ran into about this exact situation and he started a 
dedicated session instead when he accidentally closed the session.  I had 
to drive in and I was not happy.  DSPJOBLOG OUTPUT(*PRINT), SIGNOFF *LIST, 
close session, restart session shared, now I'll work on your problem.  And 
don't do it again.


Rob Berendt