HP 3000 Manuals HP 3000 Manuals
(CIERR) (contd.)
9036 MESSAGE THE ESCAPE COMMAND FAILED SETTING HPCIERR.
(CIERR9036)
---------------------------------------------------------------
9037 MESSAGE THE ESCAPE COMMAND FAILED SETTING CIERROR. (CIERR
9037)
---------------------------------------------------------------
9038 MESSAGE A directory name cannot reference a file
equation. (CIERR 9038)
CAUSE User tried to back-reference a file equation using
the MPE syntax.
ACTION File equations are not permitted. Remove the
back-reference specification.
---------------------------------------------------------------
9039 MESSAGE Non-existent directory. (CIERR 9039)
CAUSE One or more directory name components does not
exist.
ACTION Use LISTFILE to find the correct directory
pathname. Note: the missing directory name may be
on a user volume that is either not mounted or not
the HOMEVS volume of an MPE group.
---------------------------------------------------------------
9041 MESSAGE NOTREE option overrides directory name ending in
"/". (CIWARN 9041)
CAUSE The ;NOTREE option was specified and the HFS-named
directory ends in a "/" (implying mulit-level).
Multi-level is ignored.
ACTION Either remove the trailing "/" in the directory
name, or remove the NOTREE option.
---------------------------------------------------------------
9042 MESSAGE No PURGEDIR was done. (CIERR 9042)
CAUSE User replied "NO" to the prompt asking if is was OK
to purge the directory.
ACTION Respond "YES" or "ALL" to this prompt, or use the
;YES option to acknowledge the purge and suppress
the prompt.
---------------------------------------------------------------
9043 MESSAGE No match found for the pathname. (CIWARN 9043)
CAUSE A wildcarded dirname was specified, but no
directories match the pattern.
ACTION Use LISTFILE and/or choose a different wildcard
pattern.
---------------------------------------------------------------
9044 MESSAGE Trailing slash at end of filename was ignored.
(CIWARN 9044)
CAUSE A syntax error was detected in the pathname.
ACTION Re-enter a legal pathname.
---------------------------------------------------------------
9049 MESSAGE MUST HAVE SM CAPABILITY TO SPECIFY A PARM LESS
THAN 0. PARM = 0 USED. (CIWARN 9049)
CAUSE System Manager (SM) capability is required to
specify a parameter value less than zero (0) when
running the CI without the PARM=value option.
ACTION None. The CI was executed with a PARM=0.
---------------------------------------------------------------
9051 MESSAGE PH CAPABILITY IS REQUIRED FOR PROGRAM EXECUTION.
(CIERR 9051)
CAUSE Evidently, you do not have PH capability which is
required to execute a program from inside another
program.
ACTION If you are not at the root CI, use the EXIT command
to return to it. Then, reenter the command. If
this problem persists, consult with your account
manager or system manager about acquiring PH
capability.
---------------------------------------------------------------
9052 MESSAGE CREATEPROCESS FAILED ON IMPLIED RUN COMMAND.
(CIERR 9052)
CAUSE The CREATEPROCESS intrinsic failed.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9054 MESSAGE THE COMMAND FILE CANNOT BE CLOSED. (CIERR 9054)
CAUSE The CREATEPROCESS intrinsic failed.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9055 MESSAGE A component of the pathname is not a directory.
(CIWARN 9055)
CAUSE One or more of the components of the pathname is
not a directory object - it is probably a filename.
ACTION Use LISTFILE to verify your pathname.
---------------------------------------------------------------
9056 MESSAGE ILLEGAL FILE CODE FOR COMMAND FILE, EXPECTED 0
THROUGH 1023. (CIERR 9056)
CAUSE The file code for the command file was not within
the valid range of 0 through 1023.
ACTION Recreate the command file with a valid file code
(the default file code is 0.
---------------------------------------------------------------
9057 MESSAGE IMPLIED RUN COMMAND FAILED DUE TO PARSER ERROR.
(CIERR 9057)
CAUSE Unknown.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9060 MESSAGE FPARSE ERROR - THE FILENAME CANNOT BE PARSED.
(CIERR 9060)
CAUSE Unknown.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9063 MESSAGE THIS COMMAND CAN ONLY BE EXECUTED FROM THE ROOT
CI. (CIERR 9063)
CAUSE An attempt was made to execute a command from a
command interpreter (CI) level other than level
one.
ACTION Use the EXIT command to return to the root CI.
Then, reenter the command.
---------------------------------------------------------------
9064 MESSAGE THIS COMMAND CAN ONLY BE EXECUTED INTERACTIVELY.
(CIERR 9064)
CAUSE An attempt was made to execute a command from a
job, and the command can only be executed
interactively.
ACTION Do not attempt to execute the command from a job.
---------------------------------------------------------------
9065 MESSAGE COMMAND NOT ALLOWED FROM USER COMMAND IN BREAK.
(CIERR 9065)
CAUSE While in break mode, you entered a user command
(either a UDC or a command file) that contains a
command which cannot be executed in break mode.
Since this command is within a user command, you
cannot be prompted to abort the broken process.
Several commands cannot be issued after the break
key is pressed. Refer to the MPE/iX Commands
Reference Manual, (32650-90003) for a list of these
commands. See also CIERR 986.
ACTION You may enter the ABORT the user command to
terminate the break mode, and reenter the command.
However, you will not be able to continue the
activities from the point the break key was
pressed.
---------------------------------------------------------------
9066 MESSAGE COMMAND NOT ALLOWED PROGRAMMATICALLY IN BREAK.
(CIERR 9066)
CAUSE While in break mode (from a process), you executed
a command that cannot be executed programmatically
from break mode. For example, you may have been
using the editor, then pressed BREAK to run debug.
ACTION ABORT the process to terminate the break mode, and
reenter the command. However, you will not be able
to continue the activities from the point the break
key was pressed.
---------------------------------------------------------------
9067 MESSAGE THE CI CANNOT CONFIGURE BREAK : INFO = !, SUBSYS
= ! (CIWARN 9067)
CAUSE The CONFIGURE_BREAK system call failed. This is
part of the root CI initialization.
ACTION Submit an SR (service request) explaining the
situation.
---------------------------------------------------------------
9070 MESSAGE REDO, DO AND LISTREDO ARE DISABLED. (CIERR 9070)
CAUSE These commands have been disabled because the redo
stack size was set to 0. This was done with the
command SETVAR HPREDOSIZE 0.
ACTION Use the SETVAR command to reset the redo stack size
to a larger, positive number.
---------------------------------------------------------------
9071 MESSAGE POSSIBLE INFINITE LOOP IN REDO STACK. (CIERR
9071)
CAUSE Unknown.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9072 MESSAGE THERE ARE NO COMMANDS AVAILABLE TO REDO. (CIERR
9072)
CAUSE The REDO or DO command was issued and the redo
stack is empty.
ACTION Use the LISTREDO command to check the contents of
the redo stack. Only use the REDO command when
there are commands in the redo stack to execute.
---------------------------------------------------------------
9073 MESSAGE INVALID NUMERIC INDEX INTO THE REDO STACK. (CIERR
9073)
CAUSE The DO or REDO command was entered with a numeric
value not in the range of the redo stack.
ACTION Use the LISTREDO command to check the redo stack.
---------------------------------------------------------------
9074 MESSAGE THE REDO STACK SIZE CANNOT BE ADJUSTED. (CIERR
9074)
CAUSE The p_getheap Pascal routine failed.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative, or use less heap space in your
application.
---------------------------------------------------------------
9075 MESSAGE THE COMMAND SEARCH STRING CANNOT BE FOUND IN THE
REDO STACK. (CIERR 9075)
CAUSE The string pattern you supplied with either DO or
REDO was not found in the command history stack.
ACTION Look for misspellings in the line you entered or
use LISTREDO to get a listing of all commands
available on the command history stack. Then,
reenter the command.
---------------------------------------------------------------
9076 MESSAGE THE REDO SUBSTITUTION EDIT IS MISSING A
DELIMITER. (CIERR 9076)
CAUSE The CHANGE (C) command used with REDO is missing
the terminating delimeter.
ACTION Consult with online Help facility or the MPE/iX
Commands Reference Manual, (32650-90003) for
information on REDO's edit string. Then, reenter
the command.
---------------------------------------------------------------
9077 MESSAGE AN INVALID REDO STACK RANGE WAS SPECIFIED. (CIERR
9077)
CAUSE The LISTREDO command was entered with a numeric
value not in the range of the redo stack.
ACTION Reenter the LISTREDO command with a valid range, or
with no range. Entering no range will cause the
system to use the default value of ALL commands in
the redo stack.
---------------------------------------------------------------
9078 MESSAGE COMMAND FILES CANNOT HAVE VARIABLE RECORD
FORMATS. (CIERR 9078)
CAUSE The command file you tried to execute does not have
fixed length records.
ACTION Recreate the command file using a fixed length
record format. You may build a file that has fixed
length records and FCOPY the original command file
into it. Do not use the COPY command.
---------------------------------------------------------------
9079 MESSAGE THE LISTREDO COMMAND FAILED. (CIERR 9079)
CAUSE A file system error occurred and this message is
necessary to insure that CIERROR is set.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9080 MESSAGE THE PRINT COMMAND FAILED. (CIERR 9080)
CAUSE A file system error occurred and this message is
necessary to insure that CIERROR JCW is set to an
error in set 2 of the catalog.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9083 MESSAGE AN INVALID STARTING RECORD NUMBER WAS SPECIFIED.
(CIERR 9083)
CAUSE The record number you supplied to start printing at
is either zero or larger than the length of the
file.
ACTION Reenter the command and supply a starting record
number that is not larger than the maximum number
of records in the file. Consult with online Help
facility and the MPE/iX Commands Reference Manual,
(32650-90003) for information on the PRINT command.
---------------------------------------------------------------
9084 MESSAGE AN INVALID ENDING RECORD NUMBER WAS SPECIFIED.
(CIERR 9084)
CAUSE Evidently, you specified zero as the record number
to stop printing at.
ACTION Reenter the command and supply a record number that
is not zero. Consult with online Help facility and
the MPE/iX Commands Reference Manual, (32650-90003)
for information on the PRINT command.
---------------------------------------------------------------
9085 MESSAGE THE PAGE PARAMETER MUST BE NON-NEGATIVE. (CIERR
9085)
CAUSE A negative value was entered for the PAGE
parameter.
ACTION Reenter the command using a positive value for the
PAGE parameter of the PRINT command. Consult with
online Help facility and the MPE/iX Commands
Reference Manual, (32650-90003) for information on
the PRINT command.
---------------------------------------------------------------
9086 MESSAGE THE COMMAND NAME EXCEEDS 36 CHARACTERS. (CIERR
9086)
CAUSE An MPE/iX command or file name exceeded the
allowable number of characters. UDC and built-in
command names cannot exceed 16 characters. File
names cannot exceed 36 characters.
ACTION Look for a missing delimiter between the command
and its parameters. Then reenter the command.
---------------------------------------------------------------
9087 MESSAGE THE COMMAND "!" EXCEEDS 36 CHARACTERS. (CIERR
9087)
CAUSE The command qualified by the HPPATH variable
exceeded 36 characters. The qualified command is
inserted in the error message.
ACTION Look for a missing delimiter between the command
and its parameters. Then, reenter the command.
---------------------------------------------------------------
9090 MESSAGE THE FIRST CHARACTER IN THE COMMAND NAME MUST BE
ALPHABETIC. (CIERR 9090)
CAUSE The first character in the user command is not
alphabetic. User commands cannot begin with
non-alphabetic characters.
ACTION Retype your command using a valid name.
---------------------------------------------------------------
9091 MESSAGE THE COMMAND NAME IS MISSING. (CIERR 9091)
CAUSE This message is usually caused by the COMMAND or
HPICOMMAND intrinsic (nothing was provided in the
"cmdrange" buffer.
ACTION Supply a command in the "cmdrange" buffer.
---------------------------------------------------------------
9095 MESSAGE THE COMMAND FILE IS EMPTY. (CIERR 9095)
CAUSE The file you tried to execute as a command file
does not contain any commands.
ACTION Reenter the command and supply a command file that
is not empty.
---------------------------------------------------------------
9096 MESSAGE THE CI CANNOT WRITE TO OUTPUT FILE. (CIERR 9096)
CAUSE An FWRITE to $STDLIST failed. It's possible that
the file to which data is redirected is full.
ACTION If CI output is redirected to a file, make that
file larger, and make sure that write access is
legal.
---------------------------------------------------------------
9098 MESSAGE NAME DOES NOT FIT INTO A LOCAL VARIABLE -
INTERNAL ERROR. (CIERR 9098)
CAUSE Unknown.
ACTION Reenter the command. If it fails consistently,
contact your system manager or support
representative.
---------------------------------------------------------------
9103 MESSAGE THIS COMMAND IS NO LONGER SUPPORTED IN MPE/iX.
(CIERR 9103)
CAUSE The command entered is no longer supported in the
MPE/iX system.
ACTION Consult the MPE/iX Commands Reference Manual,
(32650-90003) for a complete list of available
commands.
---------------------------------------------------------------
9110 MESSAGE THE HPRESULT VARIABLE COULD NOT BE MODIFIED.
(CIERR 9110)
CAUSE The CALC command could not modify the HPRESULT
variable value due to variable management error
already displayed. Typically, the variable value
exceeds 255 characters.
ACTION Reenter the command. The HPRESULT variable value
must be legitimate (less than 255 characters).
---------------------------------------------------------------
9111 MESSAGE THE INPUT VARIABLE COULD NOT BE ADDED/MODIFIED.
(CIERR 9111)
CAUSE The INPUT command could not modify the HPRESULT
variable value due to variable management error
already displayed. Typically, the variable value
exceeds 255 characters.
ACTION Reenter the command. The HPRESULT variable value
must be legitimate (less than 255 characters).
---------------------------------------------------------------
9113 MESSAGE NO COPY WAS DONE. (CIERR 9113)
CAUSE You did not confirm the purging of the destination
file before copying.
ACTION Reenter the command and supply either a different
destination file name or confirm the deletion of
the destination file.
---------------------------------------------------------------
9115 MESSAGE FILE BLOCK SIZE CANNOT EXCEED 32767 BYTES. (CIERR
9115)
CAUSE The file block size specified exceeds the maximum
size of 32,767 bytes.
ACTION Reenter the command and specify a block size less
than 32,767.
---------------------------------------------------------------
9116 MESSAGE ONLY LOCAL, PERMANENT, NON-SPOOLED DISK FILES MAY
BE COPIED. (CIERR 9116)
CAUSE Evidently, the file you are trying to copy does not
meet the restrictions mentioned above.
ACTION Check for misspelling in the file name. Reenter
the command and supply a file name that meets the
above restrictions.
---------------------------------------------------------------
9118 MESSAGE TARGET FILE COULD NOT BE PURGED. (CIERR 9118)
CAUSE The target file in the COPY command is protected
and cannot be purged.
ACTION Contact the creator of the file or your account
manager.
---------------------------------------------------------------
9120 MESSAGE SYSTEM FILE NAMES CANNOT BE USED IN THE COPY
COMMAND. (CIERR 9120)
CAUSE The file name entered with the COPY command is
reserved for system use.
ACTION Do not specify system-defined files ($ prefix) with
the COPY command.
---------------------------------------------------------------
9121 MESSAGE A FILE WHOSE FILE CODE IS ! CANNOT BE COPIED.
(CIERR 9121)
CAUSE Evidently, you have specified a file that is of a
special type and cannot be copied.
ACTION Use FCOPY to copy the file. If it also fails,
consult with the online Help facility or the MPE/iX
Commands Reference Manual, (32650-90003) for
information on copying files of this type.
---------------------------------------------------------------