Well, there it is then. We'll see if TSM support comes back with this bit of information on their next attempt to "resolve" this issue. Their first attempt was to tell me that I couldn't move nodedata from a copy storage pool to another storage pool. I guess they didn't read the entire ESR. Anyway, I agree... a note about volume access being readwrite or readonly most certainly could be added to the "help move nodedata" text, as well.
Thanks, Richard. ps. The Technical Guide redbook now has a direct link on my desktop. Thanks. >Shouldn't it use primary storage volumes to get the data, just like a >reclamation or a move data for acc=offsite volumes? Again, I urge reading the Technical Guide redbook to fully understand TSM functions before trying to use them. It's particularly important to do so because the command reference manual ends up getting just a fraction of the information presented in the TG - often omitting important facts, such as: "The volumes added to this list have to have an access of READWRITE or READONLY." That obviously precludes Access=Offsite. And wouldn't it be nice if the programmers put out some kind of message when the function ends up copying none of the data that the customer requested? (Come on, IBM - that's not "enterprise" level programming.) Richard Sims, BU
