MPE/iX Error Messages Manual Vol 1 (32650-90878)

306 Chapter3
Command Interpreter
(CIERR) 1901-12256
is required.
10915 MESSAGE SPUCONTROL SETUP MUST BE EXECUTED BEFORE
EXECUTING THIS COMMAND. (CIERR 10915)
CAUSE An :SPUCONTROL START was entered, but the SPUSO
configuration file had been modified since the last
:SPUCONTROL SETUP.
ACTION Enter an :SPUCONTROL SETUP first.
10916 MESSAGE UNABLE TO WRITE INFORMATION TO THE SPUSO
CONFIGURATION FILE ON SYSTEM !sysname. (CIERR
10916)
CAUSE An :SPUCONTROL SETUP was entered, but the
configuration file on the system indicated in the message
could not be updated with "setup complete" information.
ACTION Check the configuration file on the system indicated via
SYSGEN. If the failure occurred on the partner system,
check the connections. Re-enter the :SPUCONTROL
SETUP command.
10917 MESSAGE SPUCONTROL START WAS ALREADY DONE, COMMAND
CONTINUED. (CIERR 10917)
CAUSE Both systems were up and an :SPUCONTROL START was
entered. Both systems think that an :SPUCONTROL
START was already done. This is just a warning. The
command will continue and start the heartbeat signal.
ACTION No action required.
10918 MESSAGE SPUCONTROL START WAS ALREADY EXECUTED. (CIERR
10918)
CAUSE Only one system was up and an :SPUCONTROL START
was entered. SPUSO had already been started through a
previous execution of the command.
ACTION The command should not have been entered a second time;
no action required.
10919 MESSAGE SPUCONTROL START MUST BE EXECUTED ON SYSTEM
!sysname BEFORE EXECUTING THIS COMMAND.
(CIERR 10919)
CAUSE An :SPUCONTROL STOP, STATUS, SWITCHOVER, or
SWITCHBACK was entered, but an :SPUCONTROL
START was not previously executed on the system
indicated in the message. SPU Switch Over is not active.
ACTION Execute :SPUCONTROL START before entering the
attempted command. If :SPUCONTROL STOP was
attempted, there is no need to do a :SPUCONTROL
START.