Good Morning. I setup in the DSM.OPT file a preschedulecmd with a batch file that I've tested and it worked well outside of TSM. When the backup kicked off(serverinitiated) it failed. In the dsmerror.log I'm receiving the following error. ------------------------------------------------------------ 02/16/2005 19:01:25 ANS1902E The PRESCHEDULECMD command failed. The scheduled event will not be executed. 02/16/2005 19:01:25 ANS1512E Scheduled event 'CAGE_DEV_INTEL' failed. Return code = 12. -------------------------------------------------------------- It looked like I only needed quotes arount the command if blanks were present which none are. The line in the DSM.OPT file is preschedulecmd d:\NTBACKUP\SYSTEMSTATE_Backup.bat
The backup in TSM ran fine until I added the preschedulecmd. Nothing ran in the batch file. Do I need to add/change anything in the DSM.OPT file preschedulecmd? It's running on a win2K machine with SP4 and TSM 5.2.2 The server is AIX 5.2 with TSM 5.2.2 Thanks for the help, Eric -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Jurjen Oskam Sent: Friday, January 21, 2005 8:06 AM To: [email protected] Subject: Re: Questions concerning file/user exits On Fri, Jan 21, 2005 at 09:34:52AM -0000, Davis Adrian wrote: [ passing filetextexit output to a script ] > I presume that this has already been thought of - So I was wondering if > anybody has tried it? If so are there any problems? This is exactly what I'm doing, and it works quite well. I created a named pipe, and let the TSM server use that as a filetextexit (use the APPEND option). On the other end of the pipe a Perl-script is running, which reads from the pipe and takes actions depending on the messages it receives. Beware that such a setup could result in unwanted signals to the TSM server (SIGPIPE). Test this well. -- Jurjen Oskam "E-mail has just erupted like a weed, and instead of considering what to say when they write, people now just let thoughts drool out onto the screen." - R. Craig Hogan
