IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

||commands when performing scheduled image snapshot backup operations. See“Srvprepostsnapdisabled” on page 355 for more information.Client return codesThe backup-archive command line interface and the scheduler exit with returncodes that accurately reflect the success or failure of the client operation. Scripts,batch files, and other automation facilities can use the return code from thecommand line interface. For operations that use Tivoli Storage Manager’sscheduler, the return codes are shown in the output of the QUERY EVENTadministrative command. See the IBM Tivoli Storage Manager Administrator’sReference for your operating system for more information about QUERY EVENT.In general, the return code is related to the highest severity message during theclient operation.v If the highest severity message is informational (ANSnnnnI), then the returncode will be 0.v If the highest severity message is a warning (ANSnnnnW), then the return codewill be 8.v If the highest severity message is an error (ANSnnnnE or ANSnnnnS), then thereturn code will be 12.The exception to the above rules is warning or error messages that individual filescould not be processed. For such a skipped file, the return code will be 4. For caseswhere the return code is not 0, you can examine the dsmerror.log file (and, forscheduled events, the dsmsched.log file).For a description of the return codes and their meanings, see Table 46Table 46. Client return codes and their meaningsCodeExplanation0 All operations completed successfully.4 The operation completed successfully, but some files were not processed.There were no other errors or warnings. This return code is very common.Files are not processed for various reasons. The most common reasons are:v The file satisfies an entry in an exclude list.v The file was in use by another application and could not be accessed bythe client.v The file changed during the operation to an extent prohibited by the copyserialization attribute. See “Copy serialization” on page 161.8 The operation completed with at least one warning message. For scheduledevents, the status will be Completed. Review dsmerror.log (and dsmsched.logfor scheduled events) to determine what warning messages were issued andto assess their impact on the operation.12 The operation completed with at least one error message (except for errormessages for skipped files). For scheduled events, the status will be Failed.Review the dsmerror.log file (and dsmsched.log file for scheduled events) todetermine what error messages were issued and to assess their impact on theoperation. As a general rule, this return code means that the error was severeenough to prevent the successful completion of the operation. For example,an error that prevents an entire file system from being processed yields returncode 12. When a file is not found the operation yields return code 12.Chapter 7. Automating tasks 155