The trick for getting a "clean" store is to subtract out the files that show
up in the open for writing mode via an indirect store file. For static files
this is quite easy. For others it might mean negating an entire sequence of
files. For example system log file numbers vary from backup to backup, thus
to eliminate this file you can
 LOG####.PUB.SYS.

WARNING: Subtracting files from a "full backup" is a dangerous proposition
and should only be done by competent system administrators! It is not the
intention of this method to subtract out files that would have otherwise
been written to tape other than system log files.

The reason I mentioned this is that using this method it is very easy to
subtract out entire groups and accounts. While this may speed up the backup
process it also means that you no longer have a single full backup set.

An indirect store file might look like this (YMMV):

@[log in to unmask]@
-DSTLGTAB.PUB.SYS
-DSTLID.PUB.SYS
-DSTRINS.PUB.SYS
-DSTWELC1.PUB.SYS
-DSTWELC2.PUB.SYS
-FPROTECT.PUB.SYS
-HPGID.PUB.SYS
-HPGIDNX.PUB.SYS
-HPUID.PUB.SYS
-HPUIDNX.PUB.SYS
-JMATFILE.PUB.SYS
-LOADLIST.PUB.SYS
-LOG####.PUB.SYS
-LOG4ONLN.PUB.SYS
-MEMLOG.PUB.SYS
-NMLG####.PUB.SYS
-RUNOR.PUB.SYS
-SLORE.PUB.SYS
-TURBODBS.PUB.SYS
-TURBOLKT.PUB.SYS
;PROGRESS;SHOW=DATES;DIRECTORY;ONVS=MPEXL_SYSTEM_VOLUME_SET

Mike Hornsby
[log in to unmask]

-----Original Message-----
From: Stigers, Greg ~ AND <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Thursday, September 17, 1998 11:16 AM
Subject: Re: clean running STORE jobs


>I'm telling myself that due to the repeated postings of old messages,
>this got only one response, and if I repost, someone can offer
>suggestions for how to do this, off list or on.
>
>I am looking for some way to have either the daily differential STORE
>job, or another job determine whether or not the results of the daily
>differential were "normal" - everything got backed up except for the
>normal set of files that are "OPEN FOR WRITING". Hacks welcome. I also
>realize that this could be very prone to getting broken by normal
>changes to the box. But even that would be better than nothing, because
>nothing is what we have right now. None of the staff available at 3AMish
>will manually check the STDList, but we can code to TELLOP or ESCAPE so
>that our scheduler (Nobix JobPak) will process an aborted job, and that
>will get checked and responded to.
>
>> -----Original Message-----
>> From: Stigers, Greg  ~ AND
>> Sent: Tuesday, September 08, 1998 2:27 PM
>> To:   HP3K-L (E-mail)
>> Subject:      clean running STORE jobs
>>
>> I would like to get our daily differential STORE job to 'run clean' on
>> a normal day, and abort on an abnormal day. Then the aborted job will
>> be handled with Nobix JobPak, because timely, intelligent human
>> intervention is apparently not an option. I am pretty sure that I'm
>> not the first list member to want to do this, but I don't find any
>> traffic on this subject.
>>
>> One of the obstacles I know about is that some number of files will be
>> "OPEN FOR WRITING". Now, some of these, I could have excluded in an
>> indirect file, but others are for instance the various logs that
>> remain open. I can think of ways to hack up such a list, but none that
>> I care for. What other challenges does this offer?
>>
>> Since there has not been much traffic on this, I assume it would be
>> best to send to me off list, and I can compile and repost the results.
>> Thanks.