HP 3000 Manuals HP 3000 Manuals
Manager Program Error Messages
The following error messages are concerned with the Silhouette Manager
Program (MP).
0004 MESSAGE Unknown Silhouette Command. (MPERR4)
CAUSE Silhouette did not recognize the command specified.
ACTION Check the spelling of the command specified and correct if
necessary.
--------------------------------------------------------------------------------------
0005 MESSAGE The commandname command has not yet been implemented.
(MPERR 5)
CAUSE The specified command will not work in this version of
Silhouette.
ACTION Do not use the specified command; enter an appropriate
command.
--------------------------------------------------------------------------------------
0006 MESSAGE MPE command error error , parm . (MPERR 6)
CAUSE This message shows the MPE COMMAND intrinsic returns 'error'
and 'parm'.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0007 MESSAGE The commandname command expects a file name. (MPERR 7)
CAUSE The specified command must be followed by the name of the
configuration file.
ACTION Supply the name of the configuration file following the
specified command.
--------------------------------------------------------------------------------------
(cont.)
0008 MESSAGE The commandname command expects a DS line number or class.
(MPERR 8)
CAUSE The specified command must be followed by a DS line number
or class.
ACTION Supply a DS line number or class following the specified
command.
--------------------------------------------------------------------------------------
0010 MESSAGE File System Error nnnopening configuration file filename .
(MPERR 10)
CAUSE An MPE file system error was encountered in the FOPEN of the
specified configuration file.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0011 MESSAGE File System Error nnn opening RESPONSES file. (MPERR 11)
CAUSE An MPE file system error was encountered in the FOPEN of the
file.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0039 MESSAGE There are no DS lines available. (MPWARN 39)
CAUSE All DS lines are unavailable.
ACTION Silhouette continues trying until a DS line becomes
available.
--------------------------------------------------------------------------------------
0040 MESSAGE DS line dsline can not be found in the configuration file.
(MPERR 40)
CAUSE The specified DS line is not in the current system
configuration file.
ACTION Specify a different DS line or use an editor to modify the
configuration file.
--------------------------------------------------------------------------------------
(cont.)
0042 MESSAGE No configuration is currently active. (MPWARN 42)
CAUSE The >START command was not issued specifying a configuration
file.
ACTION Enter a >START command and specify the configuration file.
--------------------------------------------------------------------------------------
0043 MESSAGE This configuration is NOT currently active. (MPWARN 43)
CAUSE The >START command has not been issued specifying the
configuration.
ACTION Enter a >START command specifying the configuration file.
--------------------------------------------------------------------------------------
0044 MESSAGE The CP is present but does not respond. (MPWARN 44)
CAUSE The Communications Process is busy elsewhere and did not
respond.
ACTION This situation normally corrects itself.
--------------------------------------------------------------------------------------
0045 MESSAGE This system is currently being controlled by another
Silhouette Manager Program. (MPWARN 45)
CAUSE You are not allowed to run more than one Manager Program
(MP) on a given configuration.
ACTION No action is required.
--------------------------------------------------------------------------------------
0046 MESSAGE File System Error opening COMMANDS file to the CP job.
(MPERR 46)
CAUSE An MPE file system error occurred in the FOPEN of the
COMMANDS file.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
(cont.)
0050 MESSAGE The CP or RP process does not respond or is not present.
(MPERR 50)
CAUSE This error occurs due to a DS line error, a connect timeout,
or because the Communications Process job could not start
up.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0051 MESSAGE This Silhouette system is currently active. (MPWARN 51)
CAUSE The Manager Program referred to a configuration that has
already been started.
ACTION Do not specify an active configuration.
--------------------------------------------------------------------------------------
0052 MESSAGE This Silhouette system was started with a different
configuration file. Use the CONFIG command. (MPWARN 52)
CAUSE The Manager Program is attempting to control the system with
a configuration file other than the one used to start it.
ACTION Use the configuration file that was used to start the
system.
--------------------------------------------------------------------------------------
0053 MESSAGE The CP or RP did not supply the expected response to the
Manager Program. Try again. (MPERR 53)
CAUSE A previous error may have caused an abort leaving corrupted
messages in the COMMANDS or RESPONSES pipe files.
ACTION Try again.
--------------------------------------------------------------------------------------
0054 MESSAGE The specified system was NOT started. Check $STDLIST or the
CP job for any errors and try again. (MPERR 54)
CAUSE Many errors will appear on the terminal screen but some will
only appear on $STDLIST.
ACTION Check $STDLIST for any errors which may not have appeared on
the terminal screen.
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
0055 MESSAGE The Silhouette system was started successfully. (MPMSG 55)
CAUSE This message appears after a successful START has occurred.
ACTION No action is required.
--------------------------------------------------------------------------------------
0058 MESSAGE The commandname command is invalid on an active Silhouette
recovery system. (MPERR 58)
CAUSE The specified command is not permitted on the secondary
system.
ACTION Determine if command used is proper for current mode.
--------------------------------------------------------------------------------------
0059 MESSAGE This system is NOT suspended for BACKUP. Any pending
requests for either STOP or BACKUP were cleared. (MPWARN
59)
CAUSE This message appears after a successful RESUME when the RP
has not yet released the databases for backup.
ACTION No action is required.
--------------------------------------------------------------------------------------
0060 MESSAGE The commandname command is invalid on the main system.
(MPERR 60)
CAUSE The specified command is not allowed on the primary system.
ACTION Do not specify this command on the primary system.
--------------------------------------------------------------------------------------
0062 MESSAGE Cannot RECOVER an active Silhouette system. (MPERR 62)
CAUSE If databases are active they do not need to be recovered.
ACTION Do not attempt to recover active databases.
--------------------------------------------------------------------------------------
(cont.)
0063 MESSAGE The recovery job was not started. (MPERR 63)
CAUSE Either the Recovery Process could not be started, the
databases could not be opened, or the logfile does not
exist.
ACTION Assuming the RP was started, examine the job stream for more
information.
--------------------------------------------------------------------------------------
0064 MESSAGE There is no answer from the recovery job. (MPERR 64)
CAUSE The Recovery Process started but did not complete possibly
opening pipe files.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0065 MESSAGE All databases were not opened, see RP job $STDLIST. (MPERR
65)
CAUSE All the specified databases in the configuration file could
not be opened.
ACTION Check the RP job $STDLIST to determine the problem.
--------------------------------------------------------------------------------------
0066 MESSAGE The recovery job could not continue. (MPERR 66)
CAUSE The Recovery Process aborted because of an error.
ACTION Check the job stream for more information.
--------------------------------------------------------------------------------------
0067 MESSAGE The recovery was started successfully for filename .
(MPMSG 67)
CAUSE This message appears when a stand-alone recovery has been
started successfully. It identifies the configuration file
name.
ACTION If the configuration file name is correct, no action is
necessary.
--------------------------------------------------------------------------------------
(cont.)
0068 MESSAGE Bad option specified. (MPERR 68)
CAUSE The option supplied with the last command is invalid,
incorrect, or misspelled.
ACTION Correct or modify the option supplied with the last command.
--------------------------------------------------------------------------------------
0069 MESSAGE The recovery job was not scheduled. (MPERR 69)
CAUSE The >STREAM command for the recovery job failed.
ACTION Verify the >STREAM command syntax was correct, and try
again.
--------------------------------------------------------------------------------------
0070 MESSAGE filename is not enabled for logging. (MPWARN 70)
CAUSE The Silhouette software will not work unless the database is
enabled for logging.
ACTION Enable logging for the database.
--------------------------------------------------------------------------------------
0071 MESSAGE filename is not using the correct logid. (MPWARN 71)
CAUSE The logid for the configuration file and root file do not
match.
ACTION Ensure the logid for the configuration file and root file
are he same.
--------------------------------------------------------------------------------------
0073 MESSAGE File System Error opening root file for filename . (MPERR
73)
CAUSE An MPE file system error occurred in the FOPEN for the root
file of the specified database.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
(cont.)
0074 MESSAGE File System Error nnn reading root file for filename .
(MPERR 74)
CAUSE An MPE file system error occurred in an FREAD of the root
file for the specified database.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0075 MESSAGE Stream file open failure# FSERR# nnn . (MPERR 75)
CAUSE An MPE error occurred in FOPEN for the job stream file on
the primary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0076 MESSAGE Stream of CP job failed. Error = nnn . (MPERR 76)
CAUSE An MPE error occurred in the COMMAND intrinsic to stream the
Communications Process job.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0077 MESSAGE filename is enabled for Silhouette Recovery. his database
may not be used as a primary system. (MPERR 77)
CAUSE User is trying to use a secondary database as a primary
database without entering a >SWITCH or >MODE command.
ACTION This message is not currently in use.
--------------------------------------------------------------------------------------
0078 MESSAGE This Silhouette system is stopping or has stopped. (MPWARN
78)
CAUSE This messages appears in response to any command entered
after a >STOP command.
ACTION If you want to continue, enter a >START command.
--------------------------------------------------------------------------------------
(cont.)
0079 MESSAGE There is no Recovery Process on the secondary system.
Examine the error message(s) above or check the Job listing
on the secondary printer for more information. (MPERR 79)
CAUSE The remote recovery process has logged off due to abnormal
conditions.
ACTION Check the job listing on the secondary printer for
additional information.
--------------------------------------------------------------------------------------
0080 MESSAGE Please be patient, this may take a minute or two to execute.
(MPMSG 80)
CAUSE This informs the user that a wait of several minutes may be
normal for both the >START and >USE command.
ACTION Wait for execute to complete, and then continue.
--------------------------------------------------------------------------------------
0081 MESSAGE No errors found in Silhouette configuration file. (MPMSG
81)
CAUSE This is the response to a >VERIFY command when there are no
errors.
ACTION No action is required.
--------------------------------------------------------------------------------------
0085 MESSAGE Silhouette program versions are mismatched. (MPERR 85)
n.nn.nn versus n.nn.nn .
CAUSE Either the CP, RP, or MP have unmatched program versions.
The first version given is for the MP; then either RP or CP.
ACTION Ensure that the Silhouette program version matches for the
MP, RP, and CP.
--------------------------------------------------------------------------------------
(cont.)
0086 MESSAGE Cannot start Silhouette subsystem. Verify installation.
(MPERR 86)
CAUSE Silhouette is not properly installed on the system.
ACTION Install the product again to ensure all versions match.
--------------------------------------------------------------------------------------
0087 MESSAGE Warning from STREAM command starting CP. CIWARN= nnn .
(MPWARN 87)
CAUSE Non-fatal error in LOCAL definition in configuration file.
ACTION Examine CI errors and configuration file to determine cause.
--------------------------------------------------------------------------------------
0088 MESSAGE No configuration has been specified. (MPWARN 88)
CAUSE Use of the >STATUS command, before specifying a
configuration file name with either the >CONFIG, >SYSTEM, or
>STATUS command, will result in this warning.
ACTION Specify a configuration file name with either the CONFIG,
>SYSTEM, or >STATUS command.
--------------------------------------------------------------------------------------