1) The very FIRST time you run HSHDSK, it will create your 'base'
file listing. Since there is not another file on your system
to COMPARE, you will need to run HSHDSH again - either the
next day/hour/whenever - BEFORE you run HASHCK. The sample
HSHDSK command file has this information in it in case you
forget.
2) You should not use HSHDSK and HASHCK on P,PNs that are
extemely 'active' - the main purpose of these two files are to
check somewhat 'static' P,PNs: DSK0:[1,4],[7,6], etc. I use
them to check most of DSK0: and the Network P,PNs. The reason
for this warning is because HASHCK will report hash total
differences (changes to file contents). Data files, letter
files and the like don't need to be checked as much as your
system .LIT files etc. Examining very dynamic files makes for
a 'messy' report (although it still works!).
3) The two files that contain 'last time' hash totals and 'this
time' hash totals could be quite large. Make sure you have
room on DSK0: to contain these two files (these two files are
called HASHCK.OLD and HASHCK.NEW respectively).
4) The run time action of HASHCK looks very similar to DSKANA. It
reports the DSK and P,PN that it is checking, and any
differences within a particular P,PN is NOT reported to the
screen, but to a file titled HASHCK.RPT (see HSHDSK for more
details). HASHCK.RPT is the final result file to examine.
