.nr Hu 1
.SK
.HU "APPENDIX H"
.SP 2P
.ce
.B
\s16Testing Miscellany\s0
.R
.SP 2P
.BL 2
.LI
The absence of a required data file will be reported by \f(CWsetaccess\fP.
.LI
If you execute \f(CWverify\fP before \f7setaccess\fP,
data files may be inadvertantly created, modified, or deleted.
The tester should repeat the test procedures starting at Step <1>.
.LI
When modules are recompiled after \f(CW./bin/setaccess\fP has been run,
some implementations may fail to load specific modules.
To avoid this possibility, execute \f(CW./bin/clraccess\fP prior
to recompilation.
.LI
Although the \*(Np is designed to continue if a test FAILs,
a failure of a test may cause a later test in the same module
to FAIL that should have PASSed.
Tests are not necessarily executed in ascending order.
The Raw Journal Report provides the order of testing.
FAILures should be resolved in the order in which they were tested.
.LI
A failure or an abort
of an assertion which make use of the general terminal interface 
devices may cause the implementation's driver for that device to \f1hang\fP.
If rerun of prior assertions, which use the general terminal interface
devices, now FAIL where they were previously reporting PASS
a reboot of the operating system may be necessary to clear the driver.
.LI
If assertion results are grossly inconsistent with prior results, a process
of a prior PCTS run may be still active.
Perform a process report on currently active processes
and delete any old PCTS active processes that are found.
.LI
For failure of assertions associated with permission bits, ensure the
command \f(CWumask 0\fP was in affect when the test was processed.
.LE
