The executor node had also lost the routing type (area), after the NCP PURGE, DEFINEs and reboot. If I execute a COPY command with "WITH PURGE", I get one "component in wrong state message, probably when the executor node data is going to be modified. This might explain it - do you see this message as well? On Tue, Feb 19, 2013 at 09:24:19AM +0100, G. wrote: On Tue, 19 Feb 2013 08:49:52 +0100, you wrote: NCP> copy known nodes from rullfs using permanent to volatile Would that also work from MIM? But other executor parameters would remain lost after a purge. Just out of curiosity, which executor parameters would you loose with 'copy known nodes'? We (Italian DECnet) usually do a 'copy known nodes from xxxxxx using permanent to both with purge' and never noticed any problems (as long as there are no "private" nodes locally defined and not registered into the node we consider the authoritative database for node names). The above works for VMS (at least down to V4.7); TOPS-10 has to be manually updated; RSTS too; I do not remember about TOPS-20 any more: too much time has passed since my last experiments with it. Bye, :) G.