Re: Automate OnLine Archive on Windows NT

zsun@b500dbss.med.osd.mil wrote: > > Hi all, > > Has anyone successfully used "at" command on Windows NT 3.51 to schedule > "ontape -s" to run at a specified time? We keep get " Must be dbsa to run this > program.", and Informix Tech Support said they don't really support batch backup > on either NT or Unix platform. We would like to know how other NT users handle > Online archive. And if you are able to use "at" to do "ontape -s", is your > ODS installation configuration "Domain Install" or "Local install"? > > Operating System: Windows NT 3.51 > Informix OnLine: 7.20.TC2 > Installation Configuration: Domain Install > (we know this is not supported, just want to give it a try) > The user who schedule "at" is informix, and is a local administrators > group member, also a member of Informix-Admin ( because of Domain Install, > this is a global group). > > Thanks for any help, > > Zhenling Sun > zsun@b500dbss.med.osd.mil Hi Zhenling ! The main problem is to make the interactive program ontape run in batch. Under Unix you can solve this problem by creating a shell script, which contains something like the following: $INFORMIXDIR/bin/ontape -s -L 0 <<EOF EOF I have found no way to make this in Windows batch programming. So, we use a software called MKS Toolkit, which gives you a korn shell under NT. This is of course not a smart solution. Perhaps you or someone else is more familiar with windows batch programming and knows the trick. I am very much interested in a solution to this problem (email replies are appreciated). To activate ontape with the at command you have to type: at 19:00 /every:M,T,W,Th,F "c:\\mks\\sh.exe -c \\"c:/temp/save.sh\\"" This will start ontape every working day at 7 p.m. Hope this helps a bit ! Tschuess, Dirk -- --------------------------------------------------- Dirk Schmidtpott S I E M E N S EMail: schmidtpott.pad@sni.de ============= Phone: 0049-5251-8-14922 N I X D O R F Fax : 0049-5251-8-27905 The above statements and opinions are my own and do not necessarily represent those of my employer. ---------------------------------------------------