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

Chapter 3 305
Command Interpreter
(CIERR) 1901-12256
information is correct. If it is not, re-configure the SPU
Switch Over environment through SYSGEN.
10911 MESSAGE VALIDATION FAILED ON THE SPUSO CONFIGURATION
FILE ON SYSTEM !sysname. (CIERR 10911)
CAUSE One of the SPUSO commands was entered, but the
SPUSO configuration file information was not valid. The
file might not have any system names, system pairs, or
volume sets listed.
ACTION Do SYSGEN SPU> SHOW to see the configuration file
information. Do this on both systems making sure the
information is the same. If it is not, re-configure the SPU
Switch Over environment through SYSGEN on one of the
systems. Next, execute an SPUCONTROL SETUP on the
system with the correct configuration file.
10912 MESSAGE FAILURE TO TRANSFER SPUSO CONFIGURATION FILE
TO SYSTEM !sysname. (CIERR 10912)
CAUSE :SPUCONTROL SETUP was entered, but there was an
error while transferring the SPUSO configuration file to
the alternate system.
ACTION Make sure the alternate system is up. Run SYSGEN; get
into the SPU subsytem and do a SHOW to see the
configuration file information. Make sure the systems
listed are correct. If it is not, re-configure the SPU Switch
Over environment through SYSGEN.
10913 MESSAGE THE SPUSO CONFIGURATION FILES ON BOTH SYSTEMS
MUST BE IDENTICAL. (CIERR 10913)
CAUSE :SPUCONTROL START, :SWITCHBACK, or
:SWITCHOVER was entered, and the SPUSO
configuration file on the home and alternate systems were
compared. The comparison failed.
ACTION Run SYSGEN, get into the SPU subsytem and do a SHOW
to see the configuration file information on both systems.
On the system that has the correct version of the
configuration file, perform an :SPUCONTROL SETUP.
10914 MESSAGE SPUCONTROL SETUP WAS ALREADY EXECUTED. (CIERR
10914)
CAUSE An :SPUCONTROL SETUP was entered, but the SPUSO
configuration file had not been changed since the last
:SPUCONTROL SETUP.
ACTION If there has been a configuration file change, this
command must be executed on the system with the
modified configuration file. Otherwise, it was an
inappropriate context for entering the command; no action