I had already done all of these troubleshooting steps (as well as some others), but here are the particulars:
q sched f=d: Policy Domain Name: SERVER_SEVEN_DAY_POOL_1 Schedule Name: NORMAL_DAILY Description: Default Backup schedule for Tivoli clients Action: Incremental Options: Objects: Priority: 3 Start Date/Time: 02/15/2001 19:00:00 Duration: 4 Hour(s) Schedule Style: Classic Period: 1 Day(s) Day of Week: Any Month: Day of Month: Week of Month: Expiration: Last Update by (administrator): XXXXXXXXXX Last Update Date/Time: 05/22/2008 10:42:05 Q event SERVER_SEVEN_DAY_POOL_1 NORMAL_DAILY Scheduled Start Actual Start Schedule Name Node Name Status -------------------- -------------------- ------------- ------------- --------- 06/03/2013 19:00:00 NORMAL_DAILY WVVNFSERV2 Future 06/03/2013 19:00:00 NORMAL_DAILY WVVNFSERV4 Future 06/03/2013 19:00:00 NORMAL_DAILY WVVNFSERV3 Future The schedule has not expired. There are two other clients using the same schedule, and they are working correctly. The association between the problem node and the schedule does exist. I tried deleting it and defining it again. Same result. Here are the complete contents of the error log for the scheduled backup that was attempted on 6/1. 06/01/2013 19:23:18 ANS1814E Unable to start the scheduled event 'NORMAL_DAILY' 06/01/2013 19:23:18 ANS1815E Either the window has elapsed or the schedule has been deleted Here are the contents for the schedule log: 06/01/2013 19:23:18 Executing scheduled command now. 06/01/2013 19:23:18 Node Name: WVVNFSERV2 06/01/2013 19:23:18 Session established with server SERVER1: MVS 06/01/2013 19:23:18 Server Version 5, Release 5, Level 4.2 06/01/2013 19:23:18 Server date/time: 06/01/2013 19:23:37 Last access: 06/01/2013 19:11:17 06/01/2013 19:23:18 ANS1814E Unable to start the scheduled event 'NORMAL_DAILY' 06/01/2013 19:23:18 ANS1815E Either the window has elapsed or the schedule has been deleted 06/01/2013 19:23:18 ANS1483I Schedule log pruning started. 06/01/2013 19:23:18 ANS1484I Schedule log pruning finished successfully. 06/01/2013 19:23:18 TSM Backup-Archive Client Version 5, Release 5, Level 1.0 06/01/2013 19:23:18 Querying server for next scheduled event. 06/01/2013 19:23:18 Node Name: WVVNFSERV2 06/01/2013 19:23:18 Session established with server SERVER1: MVS 06/01/2013 19:23:18 Server Version 5, Release 5, Level 4.2 06/01/2013 19:23:18 Server date/time: 06/01/2013 19:23:37 Last access: 06/01/2013 19:23:37 06/01/2013 19:23:18 --- SCHEDULEREC QUERY BEGIN 06/01/2013 19:23:18 --- SCHEDULEREC QUERY END 06/01/2013 19:23:18 Next operation scheduled: 06/01/2013 19:23:18 ------------------------------------------------------------ 06/01/2013 19:23:18 Schedule Name: NORMAL_DAILY 06/01/2013 19:23:18 Action: Incremental 06/01/2013 19:23:18 Objects: 06/01/2013 19:23:18 Options: 06/01/2013 19:23:18 Server Window Start: 19:00:00 on 06/02/2013 06/01/2013 19:23:18 ------------------------------------------------------------ 06/01/2013 19:23:18 Schedule will be refreshed in 4 hours. The boot path error does not show up when a scheduled backup is attempted. It only appears when I start or query the TSM client. At those times, I see: 06/03/2013 10:39:08 ANS1577I The Windows console event handler received a 'Close' console event. 06/03/2013 10:39:25 Boot path was not found. Assumed boot path as C:\ Those are the only two lines in the error log. I am pretty sure the two are related to the rebuild of the server, but I agree that they don't seem to be directly related to each other. Thanks again for all the help. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Andrew Raibeck Sent: Friday, May 31, 2013 3:08 PM To: [email protected] Subject: Re: [ADSM-L] Boot Path Not Found Hi Kevin, For the scheduler issue: Check the schedule on the TSM server using QUERY SCHEDULE with the F=D parameter. Make sure it has not expired and that the node still has an association for it. Use QUERY EVENT for that schedule to see if there is indeed a pending event for the node. Also, if you are using the client QUIET option, switch to VERBOSE while troubleshooting. Maybe there are other related messages that are being suppressed. And what exactly is in the dsmsched.log file and dsmerror.log file when this schedule is attempted? More info makes it easier to try to help on this forum... :-) For the boot path error: there should be more in the dsmerror.log than just the one message... I would expect at least one message with more specific info preceding the "Boot path not found" message. - Andy
