Safeguard Reference Manual (G06.29+, H06.08+, J06.03+)

Table Of Contents
SAFECOM Error and Warning Messages
Safeguard Reference Manual 520618-030
A - 10
Recovery. Report the problem to your system manager. Wait a while and try to use
SAFECOM again.
Cause. The command failed for either of two reasons:
No SMP is running on your system or on the system of a remote object that you
tried to manage with a SAFECOM command.
The SMP running on your system or on a remote system was not started with the
correct process name, $ZSMP.
Effect. The command is not executed for users or objects managed by the SMP for
which the open failed.
Recovery. Report the problem to your system manager. If it is a local problem, your
system manager can create a SMP with the correct name. If the problem is on a
remote system, your system manager can ask the system manager on that system to
correct the problem.
Cause. The SMP encountered the indicated file-system error while attempting to
execute a STOP command.
Effect. The command is not executed.
Recovery. Report the problem to your system manager. Your system manager should
ensure that the Safeguard software has been installed properly. If your system
manager cannot solve the problem, report the error to your HP representative. (The
System Messages Manual describes file-system errors.)
Cause. The command failed because you lack the authority required to perform the
command.
Effect. The command is not executed.
Recovery. Ask someone with the required authority to execute the command.
Cause. The SMP encountered an internal error while attempting to execute the ST
OP
command.
Effect. The command is not executed.
* ERROR * CANNOT OPEN $ZSMP: $smp-name NOT FOUND
* ERROR * COMMAND FAILED : FILE ERROR = ###
* ERROR * COMMAND FAILED : SECURITY VIOLATION
* ERROR * COMMAND FAILED : SMP ERROR = ####