>The case in point today was a user on UBVMS*; relevant tries were:
>* PMDF said UBVMSC, which matched the "To:" line (surprise!) but that
>  didn't work,
>* Cluster name UBVMS didn't work either.
>
>The only "apparent" workaround is to GET the list, look for something
>similar (it was UBVMSD), delete it, and LSVPUT it back.  Time consuming,
>awkward, and annoying.  In my opinion PMDF is at fault, but we know how
>that goes.  Anyone have any good suggestions to get around this mess?
 
Since these clustsers usually have a common prefix in the name, maybe
wildcards would help.  Then you could
 
               DEL userid@UBVMS*
 
and get the userid on UBVMSA through UBVMSZ.
 
Actually, it sounds like a dreadful hack and you'd get 25 error notices back
 
Somebody who knows, tell me:
All these Vax clusters that cause so many problems--is there a right way
to set them up?  Is there a configuration and software that will prevent
these problems?  I've forwarded a couple of stupid delivery error notes
to postmasters (never gotten a reply, though) and flamed at people to
get smarter software.  Question is, does this smarter software exist?
 
stm