Today we’ve found that one of out servers can make backups manually and works fine with polling mode, but when it is switched to prompting mode then schedule never run. After some investigation we’ve found http://www.tsmblog.org/tag/tcpclientport/ because we thought we have a problem with port of CAD. We’ve found that TSM scheduler does not operate with data from NODES table, which contain correct names and IP addresses, but instead it uses SCHEDULE_NODE_ADDRESSES table, which only contains host names and ports. Problem server was in different AD forest and TSM sever did not have correct DNS search suffixes. After fixing DNS issues all Pending schedules disappeared.