Summary
The new algorithm to find the destination path (introduced in v 36a) caused problems for T2 sites that did not have schedconfig.setokens set. When the pilot can not use the setokens list (i.e. when it does not have the same length as the destination path list) it will switch back to the old algorithm which required a destination path containing the space token in lower case.
Version info
Switching to original algorithm when setokens list is not the same length as the seprodpath list (SiteMover)
No comments:
Post a Comment