Just some notes from the day that DATAMOVR wouldn't do anything.           
There was a lot for DATAMOVR to do (about 8 CLEANs and 2 COPYs),                
and I made sure that it had write links to all its disks (it didn't             
originally, I had to do some mucking around), but DATAMOVR still                
wouldn't do anything.  It would start itself, query DIRMAINT for                
things to do, and then sit there like a bump on the log and do nothing.         
                                                                                
     I learned some interesting things though, looking at it.  DATAMOVR         
works by calling PROFILE EXEC, which invokes XEDIT to edit the                  
DIRMAINT DATA file with a stacked call to the DVHDMX XEDIT macro.               
DVHDMX XEDIT gets control, loads a bunch of stuff at X'40000' and sends         
two requests to DIRMAINT.  The first is                                         
        "CP SMSG DIRMAINT DIRM PASSWORD SETOPTN SMSG ON"                        
PASSWORD is a phony-ed up password, DATAMOVR doesn't need to specify            
         his password.                                                          
SETOPTN is an undocumented DIRMAINT command (it doesn't even have a help        
        function for it if you say "DIRM ? SETOPTN").  It is documented         
        in the DVHSOP ASSEMBLE file on DIRMAINT's 107 disk.                     
                                                                                
The second DIRMAINT command that DATAMOVR was executing was                     
        "CP SMSG DIRMAINT DIRM PASSWORD QRY COPY"                               
The result from that command was coming back to the screen, not via SMSG.       
                                                                                
     What I think was happening was that DIRMAINT wasn't setting some bit       
of his somewhere telling him to send stuff back to DATAMOVR via SMSG, not       
normal MSGNOH.  Unfortunately, I got it working by forcing off DIRMAINT         
and logging him on again, so I couldn't verify if this was so.  If this         
should happen again, log on as DATAMOVR and when he's in a wait state,          
waiting for his 15 minute timer pop to see if there's anything new to do,       
issue this CP command                                                           
        "CP SMSG DIRMAINT DIRM PASSWORD SETOPTN"                                
The reply from DIRMAINT should say that SMSG is on.  I suspect it'll say        
it's still off.