Re: [Veritas-bu] Netbackup SAP backup script
> Are there any naming convention rules on scripts created to > backup the archive logs? > > I've come across the following problem: > > - When initiating a backup it fails with error 29 > (failed trying to execute a command). > > - The script it calls is named: brarchive_svc.cmd > (brarchive being a command) > > - When you rename this script to test.cmd it works > perfectly. > > Has anyone come across a similar problem, where the script > name contains a command? Monique, is this on a PC? It _used_ to be (past tense since I just tested this and it no longer works this way on XP PC, at least) that the shell in DOS and DOS-based Windows releases didn't pay attention to the filename extension. Whether you typed "foo" or "foo.bat," the current directory, then the PATH, were searched for foo.com, foo.exe and foo.bat in that order, so typing foo.bat would execute foo.com if foo.com were present. Maybe that's all changed now, but I still avoid giving an OS or shell more than one piece of code with the same basename regardless of extension. In your case, maybe there's something else also doing the command interpreting. Printing out the environment from your test.cmd might show who called it. If this really is your issue, and you're wedded to brarchive* naming, setting up an explicit search path in the order you want things found might be useful. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup SAP backup script
Whenever you execute a command within a script, it's usually best to specify the complete path to the executable you want to run, so there is no ambiguity. ie, if you want to run /opt/myscript/bin/test, rather than /usr/bin/test, then be specific. Paul -- > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of bob944 > Sent: June 1, 2007 9:24 AM > To: veritas-bu@mailman.eng.auburn.edu > Cc: [EMAIL PROTECTED] > Subject: Re: [Veritas-bu] Netbackup SAP backup script > > > > Are there any naming convention rules on scripts created to > > backup the archive logs? > > > > I've come across the following problem: > > > > - When initiating a backup it fails with error 29 > > (failed trying to execute a command). > > > > - The script it calls is named: brarchive_svc.cmd > > (brarchive being a command) > > > > - When you rename this script to test.cmd it works > > perfectly. > > > > Has anyone come across a similar problem, where the script > > name contains a command? > > Monique, is this on a PC? It _used_ to be (past tense since I just > tested this and it no longer works this way on XP PC, at > least) that the > shell in DOS and DOS-based Windows releases didn't pay > attention to the > filename extension. Whether you typed "foo" or "foo.bat," the current > directory, then the PATH, were searched for foo.com, foo.exe > and foo.bat > in that order, so typing foo.bat would execute foo.com if foo.com were > present. Maybe that's all changed now, but I still avoid giving an OS > or shell more than one piece of code with the same basename regardless > of extension. In your case, maybe there's something else > also doing the > command interpreting. Printing out the environment from your test.cmd > might show who called it. > > If this really is your issue, and you're wedded to brarchive* naming, > setting up an explicit search path in the order you want things found > might be useful. > > > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Netbackup SAP backup script
Hi Are there any naming convention rules on scripts created to backup the archive logs? I've come across the following problem: - When initiating a backup it fails with error 29 (failed trying to execute a command). - The script it calls is named: brarchive_svc.cmd (brarchive being a command) - When you rename this script to test.cmd it works perfectly. Has anyone come across a similar problem, where the script name contains a command? Kind regards DISCLAIMER: This message may contain information which is confidential, private or privileged in nature. If you are not the intended recipient, you may not peruse, use, disseminate, distribute or copy this message or file which is attached to this message. If you have received this message in error, please notify the sender immediately by e-mail, facsimile or telephone and thereafter return and/or destroy the original message. Any views of this communication are those of the sender except where the sender specifically states them to be those of Faritec (Holdings) Limited (Faritec) and/or any of its subsidiaries including (but not limited to) Faritec Enterprise Solutions (Proprietary) Limited, Faritec Strategic IT Services (Proprietary) Limited, Faritec Contracting (Proprietary) Limited, Ebis and/or any of its subsidiaries. Please note that the recipient must scan this e-mail and any attached files for viruses and the like. While we do everything possible to protect information from viruses, Faritec accepts no liability of whatever nature for any loss, liability, damage or expense resulting directly or indirectly from the access and/or downloading of any files which are attached to this e-mail message. -- This e-mail was checked by the e-Sweeper Service. For more information visit our website, Clearswift Corporation e-Sweeper : http://www.mimesweeper.com/products/esweeper/ -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
