HP 3000 Manuals HP 3000 Manuals
(CIERR) (contd)
10604 MESSAGE VOLUME SET WAS NOT PHYSICALLY MOUNTED ON SYSTEM.
(CIERR 10604)
CAUSE If the named volume set is on the system, possible
cause is that PARTVS=BACKUP was specified for a
nonsplit-volume set.
ACTION Repeat the VSOPEN or VSCLOSE command without the
PARTVS parameter.
---------------------------------------------------------------
10640 MESSAGE VOLUME SET WITH MISSING VOLUMES CANNOT BE SPLIT.
(CIERR 10640)
CAUSE The mirrored volume set to be split has suspended
or disabled volumes.
ACTION Replace all missing volumes with the VOLUTIL
REPLACEMIRRVOL command before retrying the split.
---------------------------------------------------------------
10641 MESSAGE VOLUME SET CANNOT BE SPLIT WHILE UNDER REPAIR.
(CIERR 10641)
CAUSE The mirrored volume set to be split was undergoing
a repair at the time.
ACTION Wait for repair to complete before trying the
split.
---------------------------------------------------------------
10642 MESSAGE VOLULME SET IN USE, VSCLOSE WITH ;SPLIT CANNOT BE
DONE. (CIERR 10642)
CAUSE The mirrored volume set to be split has files
opened on it.
ACTION Log off all users from the volume set and retry the
split.
---------------------------------------------------------------
10643 MESSAGE PARTVS=USER IS VALID ONLY FOR A SPLIT VOLULME
SET. (CIERR 10643)
CAUSE The PARTVS=USER parameter was used to VSOPEN or
VSCLOSE a volume set which is not split.
ACTION Repeat the VSOPEN or VSCLOSE command without the
PARTVS parameter.
---------------------------------------------------------------
10900 MESSAGE SPU SWITCH OVER PRODUCT NOT INSTALLED ON THIS
SYSTEM. (CIERR 10900)
CAUSE :SPUCONTROL, :SWITCHBACK, or :SWITCHOVER was
entered, but the SPU Switch Over product was not
installed on the system.
ACTION Install the SPU Switch Over product, and make sure
the SPUINFOP configuration file is in the correct
configuration group.
---------------------------------------------------------------
10901 MESSAGE BOTH PARTNERS IN THE MIRRORED VOLUME SET !volset
name MUST BE PRESENT ON SYSTEM !sysname. (CIWARN
10901)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
command was entered, but the mirrored volume set
indicated in the message is missing one of the
mirrored partners. Both partners in a mirrored
volume set must be present on the system before
volume sets can be switched.
ACTION Wait for the missing partner to mount on the
specified system, then re-issue the command. If
the user wishes to stop mirroring for the volume
set, enter the appropriate command to suspend
mirroring, close the volume set, and re-enter the
command.
---------------------------------------------------------------
10902 MESSAGE SYSTEM NAME GREATER THAT 8 CHARACTERS. (CIERR
10902)
CAUSE A :SWITCHOVER, or :SWITCHBACK was entered with a
system name that was greater that 8 characters
long. The maximum length allowed for system names
is 8 characters.
ACTION Re-enter the command with the correct system names.
To check for the correct system names, perform a
:SPUCONTROL SHOWSPU, or go to the SPU subsystem in
SYSGEN and do a SHOW.
---------------------------------------------------------------
10903 MESSAGE 'TOSYSNAME' MUST BE THE SYSTEM WHERE THIS COMMAND
IS ENTERED. (CIERR 10903)
CAUSE A :SWITCHOVER, or :SWITCHBACK was entered with a
system name that is incorrect. The 'TOSYSNAME'
must be the name of the system that the command is
being entered on. The :SWITCHOVER and :SWITCHBACK
commands alway switch the volume sets to the system
that the command is being executed on.
ACTION Be sure the :SWITCHBACK, or :SWITCHOVER commands
are executed on the system the volume sets need to
be switched to. Perform a :SPUCONTROL SHOWSPU to
find the correct name of the system, then re-issue
the attempted command with the correct system name.
---------------------------------------------------------------
10904 MESSAGE 'FROMSYSNAME' MUST BE THE PARTNER SYSTEM NAME.
(CIERR 10904)
CAUSE A :SWITCHBACK, or :SWITCHOVER was entered with a
system name that is incorrect. The 'FROMSYSNAME'
must be the name of the partner system. The
'FROMSYSNAME' is the name of the system that the
volume sets are being switched from.
ACTION Be sure the :SWITCHBACK, or :SWITCHOVER commands
are executed on the system the volume sets need to
be switched to. Perform a :SPUCONTROL STATUS to
find the names of the systems in the SPUSO
configuration. Re-issue the attempted command with
the correct system name.
---------------------------------------------------------------
10905 MESSAGE SYSTEMS SPECIFIED ARE NOT A HOME/ALTERNATE PAIR.
(CIERR 10905)
CAUSE A :SWITCHBACK, or :SWITCHOVER was entered, but the
systems specified were not listed in the
configuration file as partner systems. Otherwise,
the systems were not listed as equal partners,
(i.e. the "to" system may not be the alternate
system for the "from" system, but the "from" system
is the alternate for the "to" system.)
ACTION Check the configuration file via the SHOW command
in the SPU subsystem of SYSGEN. Make sure the
systems are listed as partners. If they are not,
perform an APAIR. If the partners need to be equal,
perform APAIR twice. :SWITCHBACK, or :SWITCHOVER
cannot be performed until an :SPUCONTROL SETUP and
:SPUCONTROL 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 START command, but the partner system
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 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 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.
---------------------------------------------------------------
10920 MESSAGE UNABLE TO START THE HEART BEAT SIGNAL. (CIERR
10920)
CAUSE An :SPUCONTROL START was entered, but the heart
beat signal on the system could not be started.
ACTION Check the connections. Then attempt the command
again.
---------------------------------------------------------------
10921 MESSAGE SPUCONTROL STOP MUST BE EXECUTED BEFORE EXECUTING
THIS COMMAND. (CIERR 10921)
CAUSE An :SPUCONTROL SETUP was entered, but the SPUSO
process was not stopped. The process must be
stopped on both systems before re-initializing.
ACTION Enter an :SPUCONTROL STOP command.
---------------------------------------------------------------
10922 MESSAGE VOLUME SET !volset name NOT CONNECTED TO SYSTEM
!sysname. (CIERR 10922)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered, but the volume set indicated in the
message is not mounted on the system indicated.
ACTION Do a SYSGEN SPU> SHOW to see the list of volume set
names. Perform a :DSTAT on the system indicated,
and compare the volume set name to those in the
configuration file. Check the disk drive
connections to the system.
---------------------------------------------------------------
10923 MESSAGE BOTH HALVES OF THE SPLIT VOLUME SET !volset name
MUST BE PRESENT ON SYSTEM !. (CIWARN 10923)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
command was entered, but the half of the split
volume set is missing. More specifically, the
backup half of the split volume set is missing, and
it must be present on the system before volume sets
can be switched.
ACTION Wait for the missing half to mount on the specified
system, and then re-issue the command.
---------------------------------------------------------------
10924 MESSAGE VOLUME SET !volset name IS NOT CLOSED ON SYSTEM
!sysname. (CIWARN 10924)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered, but the volume set indicated in the
message was not :VSCLOSEd on the system indicated.
Volume sets must be closed before being switched
between systems.
ACTION :VSCLOSE all volume sets that will be switched.
Then re-issue the original command.
---------------------------------------------------------------
10928 MESSAGE UNABLE TO SWITCH VOLUME SETS. (CIERR 10928)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. While switching the volume sets an
error occurred, and none of the volume sets will be
switched.
ACTION Perform a :DSTAT to make sure all the ldevs in the
indicated volume set are in "loner" or "locked"
state on the current system, and if possible the
alternate system. Make sure the ldevs are
connected to both systems. Re-enter the command.
---------------------------------------------------------------
10929 MESSAGE ONE OR MORE LDEVS IN VOLUME SET !volset name ARE
NOT RESPONDING. (CIWARN 10929)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. One of the LDEVS in the indicated
volume set was not responding. It may be powered
off. Since one or more of the LDEVS in the volume
set were not responding, none of the volume sets
could be switched.
ACTION Check of the LDEVS in the volume set. Make sure
they are powered on. Also check all of the
connections to both systems. Re-enter the command.
---------------------------------------------------------------
10932 MESSAGE VOLUME SET !volset name NOT CONNECTED TO THIS
SYSTEM. (CIWARN 10923)
CAUSE An :SPUCONTROL STATUS was entered, but the volume
set indicated in the message is not mounted on the
current system.
ACTION Do a SYSGEN SPU> SHOW to see the list of volume set
names. Perform a :DSTAT and compare the volume set
names to those in the configuration file. Check
the disk drive connections to the system.
---------------------------------------------------------------
10924 MESSAGE VOLUME SET !volset name IS NOT CLOSED ON SYSTEM
!sysname. (CIERR 10924)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered, but the volume set indicated in the
message was not :VSCLOSEd on the system indicated.
Volume sets must be closed before being switched
between systems.
ACTION :VSCLOSE all volume sets that will be switched.
---------------------------------------------------------------
10925 MESSAGE NO VOLUME SETS SPECIFIED IN THE SPUSO
CONFIGURATION FILE. (CIWARN 10925)
CAUSE An :SPUCONTROL STATUS was entered, but there were
no volume sets specified in the configuration file.
ACTION If there were supposed to be volume sets listed,
check the SPUSO configuration by doing a SYSGEN
SPU> SHOW.
---------------------------------------------------------------
10926 MESSAGE ALL VOLUME SETS HOME TO SYSTEM !sysname WERE
PREVIOUSLY MOUNTED. (CIWARN 10926)
CAUSE A :SWITCHBACK was entered, but the volume sets home
to the system are already mounted on that system.
ACTION Do an :SPUCONTROL STATUS to check where the SPUSO
volume sets are currently mounted, and their home
systems. If the volume sets desired are already
mounted on the current system, then no action is
required. If the volume sets needed are those that
are home to the alternate system, a :SWITCHOVER
command should be entered. Remember for the
:SWITCHBACK and :SWITCHOVER commands, volume sets
are always switched to the system that the command
is executed on.
---------------------------------------------------------------
10927 MESSAGE ALL VOLUME SETS HOME TO THE ALTERNATE SYSTEM
!sysname WERE PREVIOUSLY MOUNTED. (CIWARN 10927)
CAUSE A :SWITCHOVER was entered, but the volume sets home
to the alternate system were already mounted on the
current system.
ACTION Do an :SPUCONTROL STATUS to check where the SPUSO
volume sets are currently mounted, and their home
systems. If the volume sets desired are already
mounted on the current system, then no action is
required. Remember for the :SWITCHBACK and
:SWITCHOVER commands, volume sets are always
switched to the system that the command is executed
on.
---------------------------------------------------------------
10928 MESSAGE UNABLE TO SWITCH VOLUME SET !volset name TO
SYSTEM !sysname. (CIWARN 10928)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. While switching the volume set to the
specific system, an error occurred and the volume
set will not be switched. The command will
continue to switch the remaining volume sets to the
indicated system if possible. The volume sets that
were switched before the error occurred will remain
on the system they were switched to. An
:SPUCONTROL SETUP is not complete until all SPUSO
volume sets are mounted on their home systems.
ACTION Perform a :DSTAT to make sure all the ldevs in the
indicated volume set are in "loner" or "locked"
state on the current system, and if possible the
alternate system. Make sure the ldevs are
connected to both systems. Re-enter the command.
If it fails, reboot the current system and the
alternate system if possible.
---------------------------------------------------------------
10929 MESSAGE UNABLE TO RESTORE VOLUME SET !volset name TO ITS
ORIGINAL STATE ON SYSTEM !sysname. (CIWARN 10929)
CAUSE An :SPUCONTROL SETUP, :SWITCHBACK, or :SWITCHOVER
was entered. While switching the volume set, an
error occurred. The volume set will not be
switched, and it cannot be restored to its original
state. The command will continue to switch the
remaining volume sets if possible. The volume sets
that were switched before the error occurred will
remain on the system they were switched to. An
:SPUCONTROL SETUP is not complete until all SPUSO
volume sets are mounted on their home systems.
ACTION Reboot the current system and the alternate system,
and re-enter the command.
---------------------------------------------------------------
10930 MESSAGE UNABLE TO SEND INFORMATION ON VOLUME SET !volset
name TO SYSTEM !sysname. (CIERR 10930)
CAUSE An :SPUCONTROL SETUP was entered, but set
information for the indicated volume set mounted on
the current system could not be sent to the
alternate system. It is important that the
information is sent when adding new volumes that
will be in the SPUSO configuration to the system.
ACTION Check all connections to both system. Perform a
:DSTAT on both systems to see if corresponding
volumes in the volume set exist on both systems.
---------------------------------------------------------------
10931 MESSAGE VOLUME SET !volset name LOCKED BY BOTH SYSTEMS.
(CIERR 10931)
CAUSE A previous :SPUCONTROL SETUP failed. Due to a
communication error, the volume set was left in a
"locked" state on the current and alternate
systems. It should be in a "locked" state on one
system, and a "loner" state on the other. This,
and subsequent executions of :SPUCONTROL SETUP will
fail because of the volume set state.
ACTION Perform a :DSTAT on both systems to check the state
of the volume set. Reboot both systems and
re-enter the command.
---------------------------------------------------------------
11701 MESSAGE The NOW option requires SM capability. (CIERR
11701)
CAUSE The SETCLOCK command was issued with the ;NOW
option but without the user having SM capability.
ACTION Issue the SETCLOCK command without the ;NOW option,
or issue the command after obtaining SM capability.
---------------------------------------------------------------
11702 MESSAGE SETCLOCK requires DATE and TIME, CORRECTION, or
TIMEZONE. (CIERR 11702)
CAUSE The SETCLOCK command was issued with none of the
required parameters.
ACTION Issue this command with a DATE and TIME,
CORRECTION, or TIMEZONE parameter.
---------------------------------------------------------------
11703 MESSAGE Both DATE and TIME parameters must be supplied.
(CIERR 11703)
CAUSE The DATE or TIME parameter was provided without
also providing the other parameter. The SETCLOCK
command requires both parameters to uniquely define
a system time.
ACTION Issue the command with both DATE and TIME
parameters.
---------------------------------------------------------------
11704 MESSAGE SETCLOCK requires DI in addition to either SM or
OP capability. (CIERR 11704)
CAUSE The SETCLOCK command was attempted without DI and
either SM or OP capability.
ACTION Issue the command with DI and either SM or OP
capability.
---------------------------------------------------------------