HP 3000 Manuals HP 3000 Manuals
Subsystem 143) (contd.)
121 MESSAGE The account name specified exceeds the maximum
legal length. (FILE SYSTEM ERROR -121)
CAUSE An illegal account name was specified.
ACTION Supply a legal account name.
---------------------------------------------------------------
122 MESSAGE The remote environment specification is invalid.
(FILE SYSTEM ERROR -122)
CAUSE The remote environment specification is invalid.
ACTION Supply a legal remote environment.
---------------------------------------------------------------
123 MESSAGE NS3000 is not present on the system. (FILE
SYSTEM ERROR -123)
CAUSE NS3000 has not been installed on the system.
ACTION Install NS3000, or do not attempt a remote file
specification.
---------------------------------------------------------------
124 MESSAGE The remote environment specification is missing.
(FILE SYSTEM ERROR -124)
CAUSE The remote environment specification is missing.
ACTION Supply a remote environment, or remove the trailing
colon.
---------------------------------------------------------------
125 MESSAGE The remote environment exceeded the maximum legal
length. (FILE SYSTEM ERROR -125)
CAUSE The remote environment specification was too long.
ACTION Supply a legal remote envirionment.
---------------------------------------------------------------
126 MESSAGE A component of an HFS path exceeds the maximum
legal length. (FILE SYSTEM ERROR -126)
CAUSE A HFS path component is too long.
ACTION Supply legal names in each component of the HFS
pathname.
---------------------------------------------------------------
127 MESSAGE The HFS path specification exceeds the maximum
legal length. (FILE SYSTEM ERROR (-127)
CAUSE The HFS path name is too long.
ACTION Change the CWD to a lower point in the path name
and use relative naming to specify the path name.
---------------------------------------------------------------
128 MESSAGE The HFS path name exceeded the number of levels
supported. (FILE SYSTEM ERROR -128)
CAUSE There are too many directory levels in the path
name.
ACTION File an SR.
---------------------------------------------------------------
129 MESSAGE A component of the HFS path name started with a
hyphen (-). (FILE SYSTEM ERROR -129)
CAUSE An invalid HFS component name was specified.
ACTION Supply legal HFS component names.
---------------------------------------------------------------
130 MESSAGE The HFS path name specified began with two
slashes (//). (FILE SYSTEM ERROR -130)
CAUSE The path name began with two slashes.
ACTION Use only one leading slash.
---------------------------------------------------------------
131 MESSAGE Lower case characters were detected and are not
allowed. (FILE SYSTEM ERROR -131)
CAUSE While parsing the name, the system was not allowing
lower case characters in this case and it found
some.
ACTION Upshift the lowercase characters.
---------------------------------------------------------------
132 MESSAGE The wildcarded name provided may match an
incorrect syntax. (FILE SYSTEM WARNING 132)
CAUSE Wildcard character expansion may match names not in
the specified syntax.
ACTION No action necessary.
---------------------------------------------------------------
133 MESSAGE The syntax of the specified name cannot be
determined. (FILE SYSTEM ERROR -133)
CAUSE The system could not determine the syntax of the
name specified.
ACTION Specify a syntax parameter value, or express the
name more clearly.
---------------------------------------------------------------
134 MESSAGE A lockword specification was attempted, but it is
not allowed. (FILE SYSTEM ERROR -134)
CAUSE A lockword was present, but the system does not
allow them in this case.
ACTION Remove the lockword specification.
---------------------------------------------------------------
135 MESSAGE An illegal attempt was made to escape to HFS
syntax from an MPE only syntax name. (FILE SYSTEM
ERROR -135)
CAUSE The name illegally started with either a dot (.)
or a slash (/).
ACTION Use either MPE escaped syntax, or HFS syntax.
---------------------------------------------------------------
136 MESSAGE An illegal character was found in the HFS path
name. (FILE SYSTEM ERROR -136)
CAUSE An invalid character was in the HFS path name.
ACTION Remove the invalid character from the path name.
---------------------------------------------------------------
137 MESSAGE Incompatible version of the file.
CAUSE An error occurred while trying to access afile
label extension.
ACTION Call your HP Support Representative.
---------------------------------------------------------------
140 MESSAGE Internal ACD corruption (equivalent to
HOP_INTERNAL_ACD_ERROR.)
---------------------------------------------------------------
165 MESSAGE Inserting a directory entry failed due to the
system's directory limit.
CAUSE Inserting a directory entry failed because the
directory size would exceed the system's limit for
directory files.
ACTION Delete/purge some entries from the current
directory or increase thedirectory limit.
---------------------------------------------------------------
173 MESSAGE The caller lacks sufficient privilege to specify
this read format option. (FILE SYSTEM ERROR -173)
CAUSE The caller is not privileged enough to be granted
the requested read format option.
ACTION Do not request this option, or become sufficiently
privileged.
---------------------------------------------------------------
174 MESSAGE The Multiple Build Environment Facility has
encountered an internal error. (FILE SYSTEM ERROR
-174)
CAUSE An internal error was encountered by the MBE code.
ACTION Contact the appropriate HP personnel.
---------------------------------------------------------------
175 MESSAGE A component of the path name specified is not a
directory. (FILE SYSTEM ERROR -175)
CAUSE One of the intermediate path name components is not
a directory.
ACTION Correct the invalid path name component.
---------------------------------------------------------------
176 MESSAGE A name in the MPE namespace is required. (FILE
SYSTEM ERROR -176)
CAUSE The name specified lies outside of the MPE
namespace.
ACTION Make sure that the name provided is within the MPE
namespace.
---------------------------------------------------------------
177 MESSAGE The maximum number of hard links to the file has
been exceeded. (FILE SYSTEM ERROR -177)
CAUSE There are too many pre-existing links to this file.
ACTION Remove some of the existing links, or use a
different file.
---------------------------------------------------------------
178 MESSAGE The user lacks the ability to purge this object.
(FILE SYSTEM ERROR -178)
CAUSE The system security will not allow this user to
purge the object.
ACTION Have the system manager grant the user the
necessary access rights.
---------------------------------------------------------------
179 MESSAGE The user lacks the ability to create an object.
(FILE SYSTEM ERROR -179)
CAUSE The system security will not allow this user to
create the object.
ACTION Have the system manager grant the user the
necessary access rights.
---------------------------------------------------------------
180 MESSAGE The user lacks the ability to traverse through a
directory in the specified path. (FILE SYSTEM
ERROR -180)
CAUSE The system security will not allow this user to
traverse through a directory in the path.
ACTION Have the system manager grant the user the
necessary access rights.
---------------------------------------------------------------
181 MESSAGE The read format option contained an illegal
value. (FILE SYSTEM ERROR -181)
CAUSE The value passed in with the read format option was
not in the valid range.
ACTION Consult the Intrinsics Manual for valid values for
this item.
---------------------------------------------------------------
182 MESSAGE The length of the collating sequence table is too
long. (FILE SYSTEM ERROR -182)
CAUSE The length of the collating sequence table is too
long.
ACTION Reduce the size of the collating sequence table.
---------------------------------------------------------------
183 MESSAGE HOP_KSM_MISSING_KSAMPARAM: There was no ksamparam
array passed in for the creation of the KSAM file.
Therefore, the open of the KSAM file failed.
CAUSE No ksamparam array was passed in.
ACTION Specify the ksamparam array when openning a new
KSAM file.
---------------------------------------------------------------
184 MESSAGE HOP_KSM_INVALID_KEY_LOC: An invalid key location
was specified in the ksamparam array. Therefore,
the open of the KSAM file failed.
CAUSE Either the key location specified is less than one
or another key starts at the same location.
ACTION Change the key location so it is greater than zero
and does not start at the same location as another
key.
---------------------------------------------------------------
185 MESSAGE HOP_KSM_INVALID_KEY_LEN: An invalid key length
was specified in the ksamparam array. Therefore,
the open of the KSAM file failed.
CAUSE Either the key length specified is invalid for the
key type or the key length combined with the
starting key location would extend the particular
key beyond the record length.
ACTION Change the key length so it is valid for the key
type or reduce the key length so that the
particular key does not extend beyond the record
length.
---------------------------------------------------------------
186 MESSAGE HOP_KSM_INVALID_KEY_TYPE: An invalid key type was
specified in the ksamparam array. Therefore, the
open of the KSAM file failed.
CAUSE An invalid key type was specified in the ksamparam
array.
ACTION Change the key type so that it is valid.
---------------------------------------------------------------
187 MESSAGE HOP_KSM_OUT_OF_INDEX_SPACE: The space reserved
for the index area in the file is full and has
reached the start of the data area.
CAUSE This error should never occur during the open of a
file. If this error occurs, then there is some
internal error in the operating system.
ACTION Record the parameter values passed to FOPEN or
HPFOPEN. Call your HP Support Representative.
---------------------------------------------------------------
188 MESSAGE HOP_KSM_INVALID_KEY_COUNT: An invalid key count
was passed in the ksamparam array. Therefore, the
open of the KSAM file failed.
CAUSE The key count specified in the ksamparam array was
not between 1 and 16.
ACTION Change the key count to be between 1 and 16.
---------------------------------------------------------------
189 MESSAGE HOP_KSM_ATTACH_FAILED:The call to Transaction
Management (XM) to attach a file for logging
failed. Therefore, the open of the KSAM file
failed.
CAUSE An internal MPE/iX error occurred.
ACTION Take a memory dump and call your HP Support
Representative.
---------------------------------------------------------------
190 MESSAGE HOP_KSM_UNSUPPORTED_LANGUAGE: An invalid language
id was specified in the ksamparam array.
Therefore, the open of the KSAM file failed.
CAUSE The language specified in the ksamparam array is
not supported on MPE/iX.
ACTION Change the language to a supported language.
---------------------------------------------------------------
191 MESSAGE HOP_KSM_NLS_ERROR: NLS detected an error while
verifying that the language specified in the
ksamparam is supported. Therefore, the open of the
KSAM file failed.
CAUSE An internal NLS error occurred.
ACTION Record the parameter values passed to FOPEN and
HPFOPEN. Call your HP Support Representative.
---------------------------------------------------------------
192 MESSAGE HOP_KSM_XM_START_TRAN_FAILED: Transaction
Management (XM) detected an error while starting a
transaction. Therefore, the open of the KSAM file
failed.
CAUSE An internal error occurred in MPE/iX.
ACTION Record the parameter values passed to FOPEN and
HPFOPEN. Call your HP Support Representative.
---------------------------------------------------------------
193 MESSAGE HOP_KSM_XM_END_TRAN_FAILED: Transaction
Management (XM) detected an error while ending a
transaction.
CAUSE An internal error occurred in MPE/iX.
ACTION Record the parameter values passed to FOPEN and
HPFOPEN. Call your HP Support Representative.
---------------------------------------------------------------
194 MESSAGE HOP_KSM_XM_TRAVERSE_TREE_ERROR: There was an
error in the index pages detected while searching
for the lowest primary key. Therefore, the open of
the KSAM file failed.
CAUSE The KSAM file is corrupted.
ACTION Close the KSAM file, store it to tape, and call
your HP Support Representative.
---------------------------------------------------------------
195 MESSAGE HOP_KSM_INDEX_ERROR:There was an error in the
index header for the index blocks. Therefore, the
open of the KSAM file failed.
CAUSE The KSAM file is corrupted.
ACTION Close the KSAM file, store it to tape, and call
your HP Support Representative.
---------------------------------------------------------------
196 MESSAGE HOP_KSM_INVALID_DATA_PTR_CALCULATED: The
calculation of the pointed to, lowest primary key,
resulted in an invalid offset into the file.
Therefore, the open of the KSAM file failed.
CAUSE The KSAM file is corrupted.
ACTION Close the KSAM file, store it to tape, and call
your HP Support Representative.
---------------------------------------------------------------
198 MESSAGE An item is present in the parameters passed to
HPFOPEN, but the associated item number is missing;
the item was ignored. (FILE OPEN WARNING 198)
CAUSE An item number is missing in the parameters passed
to HPFOPEN. Usually, this is caused by two commas
in a row ",,".
ACTION Always specify an item number when passing an item
to HPFOPEN.
---------------------------------------------------------------
199 MESSAGE An ITEMNUMBER is present in the parameters passed
to HPFOPEN, but the associated item is missing; the
ITEMNUMBER was ignored. (FILE OPEN WARNING 199)
CAUSE The item associated with an item number was not
passed to HPFOPEN. The usual cause is two commas in
a row ",,".''
ACTION Except for item number zero, you must specify an
item with all item numbers.
---------------------------------------------------------------
200 MESSAGE The DOMAIN OPTION (item# 3) does not match the
DOMAIN of the file, or two specified options
conflict regarding the file's DOMAIN. (FILE OPEN
WARNING 200).
CAUSE Usually, this is caused by specifing a NEW domain
for a non-sharable device or by specifying two
conflicting domains at the same time.
ACTION In general, this warning can be ignored. It's
purpose is to indicate that HPFOPEN had to override
one or more domain specifications.
---------------------------------------------------------------
201 MESSAGE Two or more ITEMNUMS conflict. (FILE OPEN
WARNING 201)
CAUSE This is usually caused by specifying a device name
or device class and a volume name or volume class.
Or, by specifying the same item number more than
once.
ACTION Do not specify the same item number more than once.
For the options that can be specified by more that
one item number use only of the item numbers.
---------------------------------------------------------------
202 MESSAGE The FORMALDESIGNATOR OPTION (item# 2) is invalid,
or a bounds violation occurred on this option.
(FILE OPEN ERROR 202)
CAUSE The formal designator contains invalid characters
or the variable passed to the file system is not
accessible by the caller.
ACTION Specify the formal designator correctly.
---------------------------------------------------------------
203 MESSAGE The FILE DOMAIN OPTION (item# 3) is not valid, or
a bounds violation occurred on this option. (FILE
OPEN ERROR 203)
CAUSE The domain is not one of the valid domain values or
the variable passed to the file system is not
accessible by the caller.
ACTION Specify the domain correctly.
---------------------------------------------------------------
204 MESSAGE The ASCII/BINARY OPTION (item# 53) is not valid,
or a bounds violation occurred on this option.
(FILE OPEN ERROR 204)
CAUSE The data type is not one of the valid data types or
the variable passed to the file system is not
accessible by the caller.
ACTION Specify the data type correctly.
---------------------------------------------------------------
205 MESSAGE The RECORD FORMAT OPTION (item# 6) is not valid,
or a bounds violation occurred on this option.
(FILE OPEN ERROR 205)
CAUSE The record format is not one of the valid record
formats or the variable passed to the file is not
accessible by the caller.
ACTION Specify the record format correctly.
---------------------------------------------------------------
206 MESSAGE The CARRIAGE CONTROL OPTION (item# 7) is not
valid, or a bounds violation occurred on this
option. (FILE OPEN ERROR 206)
CAUSE The carriage control is not a valid carriage
control or the variable passed to the file system
is not accessible by the caller.
ACTION Specify the carriage control correctly.
---------------------------------------------------------------
207 MESSAGE The LABELED TAPE LABEL OPTION (item# 8) is not
valid, or a bounds violation occurred on this
option. (FILE OPEN ERROR 207)
CAUSE The tape label is not specified correctly or the
variable passed to the file system is not
accessible by the caller.
ACTION Specify the tape label correctly.
---------------------------------------------------------------
208 MESSAGE The DISALLOW FILE EQUATION OPTION (item# 9) is
not valid, or a bounds violation occurred on this
option. (FILE OPEN ERROR 208)
CAUSE The DISALLOW FILE EQUATION OPTION is not specified
correctly or the variable passed to the file system
is not accessible by the caller.
ACTION Specify the DISALLOW FILE EQUATION OPTION
correctly.
---------------------------------------------------------------
209 MESSAGE The FILE TYPE OPTION (item# 10) is not valid, or
a bounds violation occurred on this option. (FILE
OPEN ERROR 209)
CAUSE The file type is not one of the valid file types or
the variable passed to the file system is not
accessible by the caller.
ACTION Specify the file type correctly.
---------------------------------------------------------------