12.07.2015 Views

Installation and User's Guide

Installation and User's Guide

Installation and User's Guide

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 34. Sample enhanced query schedule outputSchedule Name: QUARTERLY_FULLDescription: Quarterly full backupSchedule Style: EnhancedAction: SelectiveOptions: subdir=yesObjects: \* \volumes\fs2\*Priority: 5Next Execution: 1744 Hours <strong>and</strong> 26 MinutesDuration: 1 DayPeriod:Day of Week: FridayMonth: March, June, September, DecemberDay of Month: AnyWeek of Month: LastExpire: NeverDisplay information about completed workWhen you run the schedule comm<strong>and</strong> in the foreground, your screen displaysoutput from the scheduled comm<strong>and</strong>s.Output is also directed to the dsmsched.log file in the installation directory unlessyou change the directory <strong>and</strong> file name using the schedlogname option.Note: On Mac OS X, by default the log can be found in one of these locations:~/Library/Logs/tivoli/tsm/Library/Logs/tivoli/tsmWhen you run the schedule comm<strong>and</strong> as a service, output from scheduledcomm<strong>and</strong>s displays in the application event log. Output is also directed to thedsmsched.log file in the current directory unless you change the path <strong>and</strong> filename using the schedlogname option. The amount of detail is determined bywhether verbose or quiet is set in the dsm.opt file. The scheduler service also postsmessages to the Windows event log.After scheduled work is performed, check the schedule log to verify that all workcompleted successfully.When a scheduled comm<strong>and</strong> is processed the schedule log contains the followingentry:Scheduled event eventname completed successfullyIf the scheduled event does not complete successfully, you receive a messagesimilar to the following:ANS1512E Scheduled event eventname failed. Return code = code.The client indicates whether Tivoli Storage Manager successfully issued thescheduled comm<strong>and</strong> associated with the eventname (action=comm<strong>and</strong>). No attemptis made to determine the success or failure of the comm<strong>and</strong>. You can assess thestatus of the comm<strong>and</strong> by evaluating the return code from the scheduledcomm<strong>and</strong> in the schedule log. The schedule log entry for the return code of thecomm<strong>and</strong> is prefaced with the following text:Finished comm<strong>and</strong>. Return code is:Chapter 7. Tivoli Storage Manager scheduler overview 225

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!