Nancy -- You don't really need to run mupip integ every time you shut down, especially if you have just done a clean rundown. Running mupip integ is like a man needing to check the zipper on his trousers occasionally, but not obsessively often. You can schedule a database integ every once in a while (e.g., weekly), and you can do it on a comprehensive backup in order to allow a production database to continue operating uninterruptedly.
If you are running a production database, if you just happen to like powering down your PC on a whim, or you happen to live as I do in Malvern, PA, where the electricity company likes to regularly remind its customers just who has the power, you can run journaling. Assuming you don't have any scratch regions, you can turn on journaling for all regions with something like (you will need to have $gtm_dist and $gtmgbldir set correctly): mupip set -journal="enable,on,before" -region "*" When you boot up your PC (whether or not you shut down cleanly), just run the command: mupip journal -recover -backward "*" Periodically (every time you successfully backup your database), you can get rid of older generation journal files (there is a minor caveat if you are running logical dual site operation). Also, if your PC has more than one disk, you should put the journal files on a different disk from the database, and if the PC has more than one disk controller, then put the journal file and database files on separate controllers. More information is in the chapter on journaling in the GT.M Admin and Ops Guide. Regards -- Bhaskar P.S. Yes, Nancy, you really should go through the Acculturation CD! On Mon, 2005-08-01 at 15:22 -0500, Nancy Anthracite wrote: > I add this rundown alias to my shell environment variables and I love > it. > > alias rundown="$gtm_dist/mupip rundown -r \"*\"" > > If I am am not just playing around, I do a "rundown" each time I halt > VistA > and go one step further if I am REALLY serious and run a mupip integ. > If you > have had a disorderly exit from gtm, you will usually need to run it > down or > if there are any processes still running, you will need to stop them > and then > do a rundown. Try ps aux|grep mumps to look for persistent > processes. All > seems well with my demo by GTM standards as seen below. > > Now one of these days when it doesn't check out, I am going to just > replace > mumps.dat because I have a BU copy, but if it were a production > system, it > would be being journaled and backed up so I could get someone to help > bail me > out of trouble. > > [EMAIL PROTECTED]: ~$ ps aux|grep mumps > nancy 9685 0.0 0.0 1836 588 pts/2 R+ 15:44 0:00 grep > mumps > > > [EMAIL PROTECTED]: ~$ rundown > %GTM-I-MUFILRNDWNSUC, File /home/nancy/VADemo/g/mumps.dat successfully > rundown > > [EMAIL PROTECTED]: ~$ mupip integ > File or Region: /home/nancy/VADemo/g/mumps.dat > No errors detected by integ. > > Type Blocks Records % Used Adjacent > > Directory 4 444 32.897 NA > Index 1165 168737 57.633 24 > Data 168013 27089086 94.658 165387 > Free 4818 NA NA NA > Total 174000 27258267 NA 165411 > > What you really need to do is go through Bhaskar's Acculturation CD > that you > can download from the Sourceforge > > http://sourceforge.net/projects/sanchez-gtm/ > > Having said that, did I go through it yet? - No. That is on that "To > Do" > list, too. ;-( > > Now, virtually 100% of the time, I foul up something I say about what > to do, > so let's see what Bhaskar says this time. I have to stick my neck out > like > this to gain. It's that pain and gain thing. > > On Monday 01 August 2005 03:02 pm, Michael Zacharias wrote: > > mupip rundown -reg "*" > > > > have a look at the gtm administration manual under the mupip > section... > > > > > > michael > > > > --- [EMAIL PROTECTED] wrote: > > > What does this error mean? > > > > > > %GTM-E-REQRUNDOWN, Error accessing > database /vista/dat/g/mumps.dat. Must > > > be run > > > down on cluster node vista2. > > > > > > And how does one "rundown" a GTM database (running on linux)? > > > > > > John > > > > Michael Zacharias > > Technical Consultant > > cell: (250) 920-8613 > > email: [EMAIL PROTECTED] > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > > from IBM. Find simple to follow Roadmaps, straightforward articles, > > informative Webcasts and more! Get everything you need to get up to > > speed, fast. > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > _______________________________________________ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > -- > Nancy Anthracite > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
