On Wednesday, 03/18/2009 at 09:51 EDT, Shimon Lebowitz 
<[email protected]> wrote:
> As a result of a careless mistake (starting an ISLINK between systems
> running SFS servers by the same name), the servers got this message:
> DMS5DF3366W SEVER FROM *IDENT FOR RESOURCE YPOOL. REASON CODE 0 
> After correcting the problem (deactivating the link), is there any way 
short of 
> IPL CMS
> to reconnect the SFS server to the *Ident service, and allow access to 
the 
> filepool? 

No.  The filepool has to be restarted.

Alan Altmark
z/VM Development
IBM Endicott

Reply via email to