RE: Disk failure procedure

Pete -

You mean ADDSRVTBLE SERVICE('as-sts') PORT(3000) PROTOCOL(TCP)
TEXT('Service Tools 
Server') ALIAS('AS-STS')  I would recommend adding this entry anyway, as
someday you're sure to need it and it does require TCP to be restarted
before it will take effect.  This entry is needed for iNav to do
anything that requires an SST ID.  If you add it now it will be
activated at your next IPL and those functions will be available for
use.     

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group
                                   

-----Original Message-----
date: Mon, 16 Oct 2006 09:02:29 -0600
from: Pete Helgren <Pete@xxxxxxxxxx>
subject: Re: Disk failure procedure

Scott,

The Infocenter only gives the iNav directions.  At least, I couldn't
find any command line stuff before everyone came back on line this
morning.  Anyway, I tried it through iNav and it told me that "No
Service Tools Server found at address 10.0.10.200"  I found a reference
that said I needed to add a entry and restart TCP, which I didn't have
the interest to do will the drive failure looming in the background.

So, Justin gets the prize.  I did use the "Concurrent Maintenance" 
option.  I was never able to get the LED to blink to confirm that I had
the correct drive but, based on Justin's information, I pulled the drive
in slot 5, replaced it, rebuilt it and all is now well.  I didn't have
to shut down the 270.  Just did a hot replacement on the drive itself.

Thanks to all who weighed in. 

Pete Helgren




DISCLAIMER:
This message and accompanying documents are covered by the Electronic 
Communications Privacy Act, 18 U.S.C. 2510-2521, and contains information 
intended for the specified individual(s) only. This information is 
confidential. If you are not the intended recipient or an agent responsible for 
delivering it to the intended recipient, you are hereby notified that you have 
received this document in error and that any review, dissemination, copying, or 
the taking of any action based on the contents of this information is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by e-mail, and delete the original message.