Safeguard Reference Manual (G06.24+, H06.03+ )

SAFECOM Error and Warning Messages
Safeguard Reference Manual—520618-013
A-8
Cause. You lack the authority required to access the SMP. For example, your
command requested an operation on a remote object, and you have not been granted
access to the remote object’s system. You can also get this warning if your system
manager has created an ACL for the SMP process name, and the ACL does not grant
you READ or WRITE access authority to the SMP process.
Effect. The command is not executed.
Recovery. Ask your system manager to grant you the authority you need to access
the SMP.
Cause. The command failed because the SMP has already been opened by the
maximum number of SAFECOM processes it allows. (Too many people are using
SAFECOM at the same time.)
Effect. The command is not executed.
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.
* ERROR * CANNOT OPEN $ZSMP : SECURITY VIOLATION
* ERROR * CANNOT OPEN $ZSMP: $smp-name IN USE
* ERROR * CANNOT OPEN $ZSMP: $smp-name NOT FOUND
* ERROR * COMMAND FAILED : FILE ERROR = ###