How to setup Threshold for closed & corrupted file on HP NonStop
We have Prognosis 10.2. I would like to set up the alarm with threshold for the files, that are NOT opened (closed files, so EXCEPT records are not usable) and are corrupted. - I have some example files for testing - I added those files in the DISC configuration: MONITOR ( $DATA04.IGOR.* ) - I can see those files in the NonStopFileDeatil records table (my own display), the corrupted files have FileFlag = C
there is no column that will show if file is closed or opened, it could appear as "O" in the FileFlag column, but it looks like this field has only one possible flag . is it possible to have FileFlag = "OC" (open and corrupted)???
In the "OPENS" column there are always "****", no numbers, even though if I open the edit sample files many times (I use EDIT for opening not corrupted edit sample files in that subvolume). Why is that? How can force Prognosis to show some numbers in "OPENS" field?
is there any other way to setup threshold for closed & corrupted files?
Re: How to setup Threshold for closed & corrupted file on HP NonStop
Thanks for your query.
The FLAGS field in the FILEDET record can show multiple flags, so it would be possible to have 'OC' in there for an open, corrupt file. Thus if you wanted to alert on closed corrupt files, you could use a where clause of FLAGS CONTAINS "C" AND FLAGS NOT CONTAINS "O".
There's only a slight limitation with this approach; the FILEDET record is collected progressively over the DISC interval, and there's no way of telling at which point in that interval any particular file will be sampled. So it's possible that the file could be opened when sampled (and so would show the O flag) but closed by the end of the interval. Conversely, it could be closed when sampled, but opened before or after the sampling - but it would show without the O flag.
Depending on the nature of the files and the problem you are detecting, then this is perhaps not an issue, but it's something to keep in mind.