Eric, who ought to know after all, says:
> The MOVE command wasn't designed for "direct" use by list owners. It is a
> kind of tool used by the EXPLODE command: EXPLODE returns a job with MOVE
> statements that  you can submit to  LISTSERV to perform the  move. So you
> could try:
 
> EXPLODE listname (WITHOUT oldpeer PREFER newpeer
 
Well, I tried that, but there's obviously something I'm missing.
We're not trying to "peer" the list - we're trying to physically move
it from site a to site B, preferably without entering each
subscriber's data by hand.  We've got too many subscribers for that.
 
I'm working on getting back the ability to send/receive net.data
files, but at this point I can't do that so I can't just GET the list
membership from Site A and PUT it to Site B.
 
This looked so simple when I first analyzed it... *sigh*
 
Additional help gratefully accepted...
 
Here's what I got with my attempt to use Eric's suggestion - like I
said, I must be missing something important...
 
From: BITNET list server at UNCCVM <[log in to unmask]> (1.7f)
Subject: Output of your job "JAE"
To: Jae Walker <[log in to unmask]>
 
> EXPLODE arcana (WITHOUT arcana@unccvm PREFER [log in to unmask]
There is no peer on list ARCANA besides the local node.
 
Summary of resource utilization
-------------------------------
 CPU time:        0.241 sec                Device I/O:    13
 Overhead CPU:    0.015 sec                Paging I/O:    11
 CPU model:        4381                    DASD model:  3380