The POSTSCHEDULECMD should not run until the scheduled operation has completed. Of course, if the scheduled operation launches a process that runs in the background (asynchronously), then you are likely to see the situation you describe since the client has no means of monitoring background processes.
Do you have a dsmsched.log file that illustrates this problem? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. rh <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/17/2004 10:49 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject POSTSCHEDULECMD Timing Hi ITSM'rs I'm running backups out of schedules for clients that have resourceutilization set to >1. I have noticed that the postschedulecmd runs before all of the associated sessions that have been started are finished, ie. before the schedule has completely finished. Since I use the pre/post to cycle down/up my applications and database I certainly don't want this to happen. Has anyone else seen this behavior? I'm running 5.2. Thanks, Rod Hroblak __________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com
