DIVER System Utility
The DIVER program is used to stop a processor, causing all processes and all lines to switch to the backup. The program was created so programmers can down a single CPU to test their NonStop programs. DIVER is never used under normal circumstances.
RISK DIVER is a dangerous program. Forcing the system to use the backup processor for any affected devices or programs may affect the performance of the backup processor, particularly if it is already being heavily used when the command is issued.
RISK Processes that are not non-stop and are running in the CPU will terminate abruptly.
AP-ADVICE-DIVER-01 DIVER can be used in emergency circumstances to down a CPU that has programmatically locked up. However, it is better to attempt to stop the suspect processes that may be causing the lock up, rather than downing the CPU.
Securing DIVER
BP-FILE-DIVER-01 DIVER should be secured "- - - -".
BP-OPSYS-LICENSE-01 DIVER must be LICENSED.
BP-OPSYS-OWNER-01 DIVER should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-01 DIVER must reside in $SYSTEM.SYSnn.
If available, use Safeguard software or a third party object security product to grant access to DIVER object files only to users who require access in order to perform their jobs.
BP-SAFE-DIVER-01 Add a Safeguard Protection Record to grant appropriate access to the DIVER object file.
| Discovery Questions | Look here: | |
|---|---|---|
| OPSYS-OWNER-01 | Who owns the DIVER object file? | Fileinfo |
| OPSYS-LICENSE-01 | Is the DIVER object file licensed? | Fileinfo |
| FILE-POLICY | Who is allowed to execute DIVER on the system? | Policy |
| FILE-DIVER-01 | Is the DIVER object file correctly secured with the Guardian or Safeguard system? | Fileinfo Safecom |
