ASAP 3.2 Messages Manual

HP NonStop Messages Manual Page 50 of 414
cpu
is the CPU where the SGP process was not started in.
Cause. The ASAPMON process could not start the SGP because a process with the
same name exists.
Effect. The SGP is not started.
Recovery. Shut down ASAP. Select a different NSS ID Restart ASAP.
1060
ASAPACT script file missing error
error
file-system error number
Cause. The ASAP Action server file ASAPACT is missing. This file is always
installed, this error indicates ASAP was not properly installed.
Effect. The Action server cannot be started. Actions will not occur.
Recovery. Reinstall ASAP and verify that file ASAPACT is present.
1061
ACTION Server not started as SUPER.SUPER
Cause. The ASAP Action Server was not started under the SUPER.SUPER user ID.
Effect. The Action Server might not be able to perform certain actions.
Recovery. Restart ASAP using the SUPER.SUPER user ID or PROGID the
ASAPMON object file.
1062
Unable to save ASAP control file, FE: error
error
file-system error number
Cause. The ASAPMON process could not save the ASAP control file into the
subvolume where its object file resides.
Effect. The ASAP command interpreter cannot discover configuration settings from
the running ASAP copy.
Recovery. Correct the problem indicated by the file system error number.