Hitman FAQ 3
Hitman is stopping unexpectedly
1. Verify that you can list both the prime and nonprime data files
$ hitman /list /file=both
If you are unable to list both data files you may need to convert the one that fails following the instructions in FAQ 1
. A data file problem is usually responsible for this if Hitman is stopping at the same time everyday.
2. Inspect the hitman_dat:hitman_audit_file.node to see if a privileged user is actually stopping it. Anytime the Hitman/stop command is issued there will be an audit record written to record the time and username.
3. Inspect the hitman_dat:hitman_error_file.node to see if an error message has been written out at the time Hitman stopped working. If there is an error message fixing the problem may allow Hitman to run normally.
4. Start Hitman and make a note of the process id. After it has stopped inspect the OpenVMS accounting record for that process - the final status message text may indicate why Hitman is stopping.
Assuming the process id was 0200AC12
$ accounting /full /ident=0200AC12
Be sure to page through until you obtain a screen of information for that process ID that has the current date.