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

304 Chapter3
Command Interpreter
(CIERR) 1901-12256
START has been done using the modified configuration
file.
10906 MESSAGE NO SPUSO NAME FOR THIS SYSTEM. (CIERR 10906)
CAUSE An :SPUCONTROL SHOWSPU was entered, but the
system has not been given an SPU Switch Over system
name yet.
ACTION Enter an SPU Switch Over name via the ASYSTEM
command in the SPU subsystem of SYSGEN.
10907 MESSAGE SYSTEM !sysname NOT RESPONDING. THE ALTERNATE
SYSTEM MUST BE UP
BEFORE THIS COMMAND CAN SUCCEED. (CIERR
10907)
CAUSE Communication between systems was attempted by the
:SPUCONTROL SETUP command, but the partner
system did not respond.
ACTION Check the partner system to be sure it is up. Also check
the connections between the two systems.
10908 MESSAGE SYSTEM !sysname NOT RESPONDING, SPUCONTROL
START CONTINUED. (CIWARN 10908)
CAUSE Communication between systems was attempted by the
:SPUCONTROL STARTcommand,butthepartnersystem
did not respond. Although the communication attempt
failed, the command continued to execute.
ACTION Check partner system to see if it is up. Also check the
connections between the two system. If the system is not
up, a :SWITCHOVER, or :SWITCHBACK can be executed
based on the state of the switchable volume sets.
10909 MESSAGE OPEN FAILED ON SPUSO CONFIGURATION FILE.
(CIERR 10909)
CAUSE Each of the SPUSO commands must open the
configuration file. Apparently, the file does not exist, or is
empty.
ACTION Configure the SPU Switch Over environment through
SYSGEN, and the necessary information will be added to
the configuration file.
10910 MESSAGE ERROR OCCURRED WHILE ACCESSING SPUSO
CONFIGURATION FILE. (CIERR 10910)
CAUSE Each of the SPUSO commands must read the information
in the configuration file. An error occurred while reading
information from the configuration file.
ACTION Run SYSGEN; get into the SPU subsytem and do a SHOW
to see the configuration file information. Make sure the