Installation and User's Guide

Client defined options are defined in the dsm.opt file. The Tivoli Storage Managerserver can also define some options in a client options set, or as part of the optionsparameter of the schedule definition. The Tivoli Storage Manager server can alsoset some options globally for all clients. By default, the client setting for theseoptions is honored. If the global override on the Tivoli Storage Manager server isset, the client setting for the option is ignored. Defining client options as part ofthe schedule definition is useful if you want to use specific options for a scheduledaction that differ from the option settings normally used by the client node, or aredifferent for each schedule the node executes.The schedmode option controls the communication interaction between the TivoliStorage Manager client and server. There are two variations on the schedule mode:client polling and server prompted.Return codes from preschedulecmd and postschedulecmdscriptsThis topic lists the return codes that you might see when you use thepreschedulecmd and postschedulecmd options.vvIf the command specified by the preschedulecmd option ends with a nonzeroreturn code, Tivoli Storage Manager considers the command to have failed. Inthis case, neither the scheduled event nor any postschedulecmd orpostnschedulecmd command runs. The administrative query event commandwith format=detailed option shows that the event failed with return code 12.If the command specified by the postschedulecmd option ends with a nonzeroreturn code, Tivoli Storage Manager considers the command to have failed. Theadministrative query event command with format=detailed option shows that theevent completed with return code 8, unless the scheduled operation completedwith a higher return code, in which case the higher return code takesprecedence. Therefore, if the scheduled operation completes with return code 0or 4 and the postschedulecmd command fails, the administrative query eventcommand shows that the event completed with return code 8. If the scheduledoperation completes with return code 12, that return code takes precedence, andquery event shows that the event failed with return code 12.When interpreting the return code from a command, Tivoli Storage Managerconsiders 0 to mean success, and anything else to mean failure. While this behavioris widely accepted in the industry, it is not 100% guaranteed. For example, thedeveloper of the widget.exe command might exit with return code 3, if widget.exeran successfully. Therefore, it is possible that the preschedulecmd orpostschedulecmd command might end with a nonzero return code and besuccessful. To prevent Tivoli Storage Manager from treating such commands asfailed, you should wrap these commands in a script, and code the script so that itinterprets the command return codes correctly. The script should exit with returncode 0 if the command was successful; otherwise it should exit with a nonzeroreturn code. The logic for a script running widget.exe might look like this:run ’widget.exe’if lastcc == 3exit 0elseexit 1220 IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide