I'd forgotten about this. For the sake of anyone finding this in the future, the problem did not recur on the original (single DB2 instance) server. However, it did recur on another. What was spooky was that on the second server it happened with both instances that were running there. This makes...