If you insist upon writing your own root level script I think you need to source ~db2<sid>/.cshrc to get your environment setup. As an alternative what about using SAP transaction DB13 to set-up a planning calendar, and choose "full backup with TSM" as your backup method. If you have TSM client installed and operating it "works out of the box". For a more definative description of backing up DB2 in a TSM environment I found the following IBM redbook invaluable: Backing Up DB2 UDB Using Tivoli Storage Manager http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246247.html?Open
Note: Someone else suggested using brbackup. Brbackup is the SAP on Oracle backup tool. It doesn't exist on SAP on DB2 (although brarchive does). The SAP/DB2 supported backup method IS DB13 which eventually calls "db2 backup ...". Good luck! Ken Chamberlain University of Toronto Phone:(416) 978-1582 Fax: (416) 971-2085 E-mail: [EMAIL PROTECTED] ----- Original Message ----- > > Date: Wed, 28 Apr 2004 02:52:34 +0800 > From: Roslind Kaur <[EMAIL PROTECTED]> > Subject: Re: Antwort: Re: AIX - backup SAP DB2 > > --0__=C7BBE410DFF658148f9e8a93df938690918cC7BBE410DFF65814 > Content-type: text/plain; charset=ISO-8859-1 > Content-transfer-encoding: quoted-printable > > > > Hi, > > I am not sure whether this will help, but if you are able to run the sc= > ript > via crontab but not via TSM Scheduler, then try putting this in the > scheduler objects field: > > "your full path"/backupon.sh > "your log file" 2>&1 < /dev/null > > Basically you have to redirect the STDIN to /dev/null. > Hope it helps! > > Best Regards, > > Roslind Kaur > > > > = > > Sabine = > > Rettenberger = > > <Sabine.Rettenber = > To > [EMAIL PROTECTED] [EMAIL PROTECTED] = > > NIK.DE> = > cc > Sent by: "ADSM: = > > Dist Stor Subj= > ect > Manager" Antwort: Re: AIX - backup SAP DB= > 2 > <[EMAIL PROTECTED] = > > .EDU> = > > = > > = > > 04/27/2004 11:09 = > > PM = > > = > > = > > Please respond to = > > "ADSM: Dist Stor = > > Manager" = > > = > > = > > > > > > Hey Tomas, > > i use the root - crontab to start the DB2-Backup on AIX. > It works fine. > > mfg > Sabine Rettenberger > > Wolf GmbH | \ _ , , , - - - , , _ > > Abt. Z-IR ZZZzz / , ` . - ' ` ' - . ; - ; ; = > , _ > Industriestra=DFe 1 | , 4 - ) ) - , _ . , \ ( ` '= > - ' > > 84048 Mainburg ' - - - ' ' ( _ / - - ' ` - ' \ _ ) > > Tel.: 08751/74-1780 > Fax: 08751/744-1780 > E-Mail: [EMAIL PROTECTED] > > No trees were killed in the sending of this message. > However a largenumber of electrons were terribly inconvenienced. > > > > > Steve Harris > > <[EMAIL PROTECTED] An: > [EMAIL PROTECTED] > > QLD.GOV.AU> Kopie: > > Gesendet von: "ADSM: Thema: Re: AIX - > backup SAP DB2 > Dist Stor Manager" > > <[EMAIL PROTECTED] > > > > > > > 27.04.2004 00:18 > > Bitte antworten an > > "ADSM: Dist Stor > > Manager" > > > > > > > > Tomas > > Shoudn't you be running the SAP brbackup utility? > This is a bunch of generic scripts and, yes, at the end of it all it bo= > ils > down to a db2 backup command, but it is the SAP way to do things. > > Steve. > > > >>> [EMAIL PROTECTED] 23/04/2004 18:20:46 >>> > Hi all, > > I have problem with running backup of DB2 backup database of SAp system= > on > AIX. I am not AIX guru so, please, dont shoot me :-)). I have shell scr= > ipt, > backupon.sh for online backup of database with this contens: > > #!/bin/sh > su - devadm "-c db2 backup db DEV online use tsm" > > Backup works fine, when I run script on foreground. At least backup wor= > ks > fine when I run "dsmc sched" on foreground (under root user) and make > schedule on TSM server to run this script. But backup don't work, when = > I > run > scheduler on background with "nohup dsmc schedule 2> /dev/null &" as > described in TSM client user's guide. Script ends with return code 127.= > > Running script with cron aends with error return code too. > > Any advice for one poor, miserable, devasted and bleeding AIX > non-specialist > and cookie-eater? > > Thanks > Tomas > > > > ***********************************************************************= > ************ > > > This email, including any attachments sent with it, is confidential and= > for > the sole use of the intended recipient(s). This confidentiality is not= > > waived or lost, if you receive it and you are not the intended > recipient(s), or if it is transmitted/received in error. > > Any unauthorised use, alteration, disclosure, distribution or review of= > > this email is prohibited. It may be subject to a statutory duty of > confidentiality if it relates to health service matters. > > If you are not the intended recipient(s), or if you have received this > email in error, you are asked to immediately notify the sender by > telephone or by return email. You should also delete this email and > destroy any hard copies produced. > > ***********************************************************************= > ************ > > > >