I've used the DELETE FILESPACE NodeName * command with the WAIT=YES parm
with great success many times before.  With the wait parm, it will start
one process and won't return control of the command prompt until it has
finished.  I have this as part of a rexx script that reads from a list of
servers, does a few checks to make sure it really has been removed, issues
the del filespace command, and goes on to the next server once it's
finished.  When I was doing mass deletions from the GUI, I would routinely
cause the ADSM server to lockup, mostly because I would have multiple
processes open for different filespaces and nodes.

John Johnson
IBM Global Services - WMI
Enterprise Architecture Design