Problem: The time limit expired before any of the selected for
events occurred or before the time limit expired.
CAUSE
The HPSELECT intrinsic could not select for any
of the specified events during the specified time limit.
ACTION
Increase the time limit, or don't pass it.
-91
MESSAGE
Problem: A soft interrupt occurred before any of the selected
for events occurred or before the time limit expired.
CAUSE
A soft interrupt occurred, while the process was
blocked on HPSELECT.
ACTION
None.
-99
MESSAGE
The requested information is larger than the return value can
express. (FILE SYSTEM ERROR -99)
CAUSE
A 16 ir 32-bit return value was passed into anintrinsic which
needs a larger return value (32 or 64bit) in order to return a correct
result.
ACTION
Call the intrinsic with a new item number that returns
the information in a larger return value.
-342
MESSAGE
HOP_OPTION_ACD was specified for an HPFOPEN for which this
option is not allowed such as for a device or OLD file.
-353
MESSAGE
Due to the size of this file, only the LARGE-MAPPED option (87)
can be used to open the file for user mapped access.
(FILE OPEN ERROR -353)
-588
MESSAGE
The ACD option is not valid. The ACD supplied in the
HOP_OPTION_ACD keyvalue is invalid or the user does not have access
to the buffer.
-589
MESSAGE
An error occurred while accessing an ACD. This error is
typically returned when the ACD for the file or device being accessed
is corrupted.
-591
MESSAGE
The creator of a linked spoolfile which was being created
"RAW" did not have access to the target device. The spoolfile was
created and DEFERred..
-658
MESSAGE
Problem: Failure in Creating the File IO State Semaphore
Table.
CAUSE
Procedure FS_INITIALIZE_FILE_SYSTEM failed to create
the File IO State Semaphore Table.
ACTION
Ask your system manager to investigate the problem
and reboot the system.
-659
MESSAGE
Problem: Failure in initializing The File IO State Semaphore
Table.
CAUSE
Procedure FS_INITIALIZE_FILE_SYSTEM failed to initialize
the File IO State Semaphore Table.
ACTION
Ask your system manager to investigate the problem
and reboot the system.
1
MESSAGE
Intrinsic layer; file number is not valid.
2
MESSAGE
Intrinsic layer; the operation could not be completed because
caller lacked the proper execution privilege level.
3
MESSAGE
Intrinsic layer; an access violation occurred.
4
MESSAGE
Intrinsic layer; record number is not valid.
5
MESSAGE
Intrinsic layer; number of records is not valid.
6
MESSAGE
Intrinsic layer; the process is out of PLFD's.
7
MESSAGE
Intrinsic layer; the maximum user label size was
exceeded.
8
MESSAGE
Intrinsic layer; device type is not valid.
9
MESSAGE
Intrinsic layer; this is an illegal parameter.
10
MESSAGE
Intrinsic layer; this is an unimplemented function.
11
MESSAGE
Intrinsic layer; FLOCK is unable to LOCK file.
12
MESSAGE
Intrinsic layer; the file is not LOCKED.
13
MESSAGE
Intrinsic layer; the file has no user labels.
14
MESSAGE
Intrinsic layer; no WAIT IO pending.
15
MESSAGE
Intrinsic layer; no NOWAIT IO for specific file.
16
MESSAGE
Intrinsic layer; an invalid operation for this device
type.
17
MESSAGE
Intrinsic layer; a privilege violation occurred.
18
MESSAGE
Intrinsic layer; a bounds violation occurred.
19
MESSAGE
Intrinsic layer; user does not have multiple RIN
capability.
20
MESSAGE
Intrinsic layer; user does not have SAVE
capability.
21
MESSAGE
Intrinsic layer; a SECURITY VIOLATION on file
occurred.
22
MESSAGE
Intrinsic layer; missing item number or return
variable.
23
MESSAGE
Intrinsic layer; a switch failure occurred.
24
MESSAGE
Intrinsic layer; an undefined error occurred.
25
MESSAGE
Intrinsic layer; an OVERFLOW trap occurred.
26
MESSAGE
Intrinsic layer; a CONDITIONAL TRAP occurred.
27
MESSAGE
Intrinsic layer; a FLOATING POINT TRAP occurred.
28
MESSAGE
Intrinsic layer; a data page fault has occurred.
29
MESSAGE
Intrinsic layer; a DATA MEMORY PROTECTION TRAP has
occurred.
30
MESSAGE
Intrinsic layer; the reference to this file in this context is
not vaild.
31
MESSAGE
Intrinsic layer; the item number passed was out of
range.
32
MESSAGE
Intrinsic layer; the operation could not be completed because
the file was not opened with exclusive access.
33
MESSAGE
Intrinsic layer; the user of the file must be the creator for
this operation.
34
MESSAGE
Intrinsic layer; the operation desired is not consistent with
the device type.
35
MESSAGE
Intrinsic layer; RENAME of a file across a volume set was
attempted; this is an invalid operation.
36
MESSAGE
Intrinsic layer; the operation was not completed because a
nonexistent group was specified.
37
MESSAGE
Intrinsic layer; the operation could not be completed because
a nonexistent account was specified.
38
MESSAGE
Intrinsic layer; the operation could not be completed because
a nonexistent file was specified.
39
MESSAGE
Intrinsic layer; the operation could not be completed because
a nonexistent temporary file was specified.
40
MESSAGE
Intrinsic layer; the operation could not be completed because
of insufficient disk space in the group.
41
MESSAGE
Intrinsic layer; the operation could not be completed because
of insufficient disk space in the account.
42
MESSAGE
Intrinsic layer; the operation could not be completed because
a duplicate permanent file name was specified.
43
MESSAGE
Intrinsic layer; the operation could not be completed because
a duplicate temporary file name was specified.
44
MESSAGE
Intrinsic layer; the operation could not be completed because
an I/O error occurred in the directory routines.
45
MESSAGE
Intrinsic layer; the operation could not be completed because
the file equation used was invalid.
46
MESSAGE
Intrinsic layer; the operation could not be completed because a
file equation is required but was not used.
47
MESSAGE
Intrinsic layer; STORGE MANAGEMENT control failed.
48
MESSAGE
The block size of the file is invalid.
(FILE SYSTEM ERROR -48)
CAUSE
The block size specified is not in the range of
valid block sizes.
ACTION
Specify a block size that is valid.
49
MESSAGE
No nowait I/O is outstanding for any file.
(FILE SYSTEM ERROR -49)
CAUSE
A nowait read or write was not initiated against
any file prior to calling IOWAIT.
ACTION
Initiate a nowait I/O prior to calling IOWAIT.
50
MESSAGE
A specified option value was invalid.
(FILE SYSTEM ERROR -50)
CAUSE
An improper value was passed into the intrinsic.
ACTION
Consult the Intrinsics Manual for valid option values.
51
MESSAGE
The character set number must be between 0 and 31.
(FILE SYSTEM ERROR -51)
CAUSE
An improper character set number was specified.
ACTION
Specify a valid character set number.
52
MESSAGE
The logical page number must be between 0 and 31.
(FILE SYSTEM ERROR -52)
CAUSE
An improper logical page number was specified.
ACTION
Specify a valid logical page number.
53
MESSAGE
The number of copies must be between 1 and 32767.
(FILE SYSTEM ERROR -53)
CAUSE
An invalid number of copies was specified.
ACTION
Specify a valid number of copies.
54
MESSAGE
The page length parm must be between 12 (=3") and 68 (=17").
(FILE SYSTEM ERROR -54)
CAUSE
An invalid page length was specified.
ACTION
Specify a valid page length.
55
MESSAGE
The form number must be between 0 and 31.
(FILE SYSTEM ERROR -55)
CAUSE
An invalid form number was specified.
ACTION
Specify a valid form number.
56
MESSAGE
The number of overlays must be between 1 and 8.
(FILE SYSTEM ERROR -56)
CAUSE
An invalid number of overlays was specified.
ACTION
Specify a valid number of overlays.
57
MESSAGE
The vertical format number must be between 0 and 31.
(FILE SYSTEM ERROR -57)
CAUSE
An invalid vertical format number was specified.
ACTION
Specify a valid vertical format number.
58
MESSAGE
The picture number must be between 0 and 31.
(FILE SYSTEM ERROR -58)
CAUSE
An invalid picture nubmer was specified.
ACTION
Specify a valid picture number.
59
MESSAGE
The extended capability parm must be 0 (off) or 1 (on).
(FILE SYSTEM ERROR -59)
CAUSE
An invalid value for the extended capability parm
was specified.
ACTION
Specify a valid value for the extended capability parm.
60
MESSAGE
The caller lacks sufficient capability to perform the requested
operation. (FILE SYSTEM ERROR -60)
CAUSE
A request was made to perform a privileged operation from
an process lacking the necessary capabilities.
ACTION
Acquire the necessary capabilities prior to calling
the function.
61
MESSAGE
A matching UFID could not be found among the opened files for
this process. (FILE SYSTEM ERROR -61)
CAUSE
The target UFID file is not opened by the process.
ACTION
No action is necessary.
62
MESSAGE
The specified file resides on a read-only volume.
(FILE SYSTEM ERROR -62)
CAUSE
An attempt was made to modify a file on a read-only volume.
ACTION
Do not attempt to modify a file on a read-only volume.
63
MESSAGE
The filename cannot be expressed using the specified syntax.
(FILE SYSTEM ERROR -63)
CAUSE
The syntax requested to return the filename cannot
name the file.
ACTION
Request the filename in a different syntax.
64
MESSAGE
Renaming a file of the given file type is not supported.
(FILE SYSTEM ERROR -64)
CAUSE
An attempt was made to rename a file type that cannot
be renamed.
ACTION
Do not attempt to rename this file.
65
MESSAGE
The UID/GID database could not be found.
(FILE SYSTEM ERROR -65)
CAUSE
The files HPUID.PUB.SYS and HPGID.PUB.SYS do not exist.
ACTION
Run PXUTIL.PUB.SYS to create the UID/GID database.
66
MESSAGE
User information was not found in the UID database.
(FILE SYSTEM ERROR -66)
CAUSE
There was no entry for this user in the UID database.
ACTION
Run PXUTIL.PUB.SYS, or add the user to the database.
67
MESSAGE
File group information was not found in the GID database.
(FILE SYSTEM ERROR -67)
CAUSE
There was no entry for the file group in the GID
database.
ACTION
Run PXUTIL.PUB.SYS, or add the file group to the database.
68
MESSAGE
The caller lacks RACD capability.
(FILE SYSTEM ERROR -68)
CAUSE
The caller has not been granted RACD access to the file.
ACTION
Have RACD access granted to the user.
69
MESSAGE
A component in the specified pathname is not a directory.
(FILE SYSTEM ERROR -69)
CAUSE
One of the intermediate components of a pathname
is not a directory.
ACTION
Supply a valid pathname.
74
MESSAGE
IS_END_OF_FILE: An instrinsic operation was attempted when the
EOF was encountered.
CAUSE
An instrinsic was called when the data pointer was pointing
to the EOF.
ACTION
Reposition the file data pointer to a valid record.
80
MESSAGE
An internal error occurred. (FILE SYSTEM ERROR -80)
CAUSE
Something that can not happen did.
ACTION
File an SR or contact an HP representative.
81
MESSAGE
The operation failed due to a lack of system resources.
(FILE SYSTEM ERROR -81)
CAUSE
One or more system resources were exhausted.
ACTION
File an SR or contact an HP representative.
82
MESSAGE
FOPTIONs cannot express the physical attributes of this file.
(FILE SYSTEM ERROR -82)
CAUSE
One or more of the physical attributes of the file
cannot be represented in the fields of the FOPTIONs.
ACTION
Retrieve information about each of the file attributes
with separate items.
83
MESSAGE
The operation cannot be completed due to the privilege level of
the file. (FILE SYSTEM ERROR -83)
CAUSE
An attempt has been made to create a file with a
privilege level other than 3 outside of an MPE group.
ACTION
Do not attempt this operation with a privileged file.
84
MESSAGE
The operation cannot be completed because the file is write
protected. (FILE SYSTEM ERROR -84)
CAUSE
This file has been protected from write access.
ACTION
Do not attempt to alter this file.
85
MESSAGE
The operation cannot be completed because the file has a
privileged file code. (FILE SYSTEM ERROR -85)
CAUSE
An attempt has been made to create a file with a privileged
file code outside of an MPE group.
ACTION
Do not attempt this operation with a privileged
file code file.
86
MESSAGE
The user lacks traverse access to one of the directory
components in the path. (FILE SYSTEM ERROR -86)
CAUSE
The security attributes of one of the directory
components does not allow this user the ability to traverse through
the directory.
ACTION
Have the system or account manager allow the user
TD access to the directory.
87
MESSAGE
The record type of this file is not recognized by the system.
(FILE SYSTEM ERROR -87)
CAUSE
A file has somehow been placed on the system that
the system does not recognize.
ACTION
Unlink the file to remove it.
88
MESSAGE
The file type of this file is not recognized by the system.
(FILE SYSTEM ERROR -88)
CAUSE
A file has somehow been placed on the system that
the system does not recognize.
ACTION
Unlink the file to remove it.
89
MESSAGE
The name of this file cannot be expressed in the requested
syntax. (FILE SYSTEM ERROR -89)
CAUSE
The name of this file is not expressable in the
syntax requested.
ACTION
Request the name in a different syntax.
90
MESSAGE
The operation completed due to a time-out.
(FILE SYSTEM ERROR -90)
CAUSE
The operation timed-out before it could be otherwise
completed.
ACTION
If necessary, retry the operation.
91
MESSAGE
The operation was halted due to an interrupt.
(FILE SYSTEM ERROR -91)
CAUSE
An interrupt occurred before the operation could complete.
ACTION
If necessary, retry the operation.
92
MESSAGE
Files of this file type must reside in the MPE namespace.
(FILE SYSTEM ERROR -92)
CAUSE
An attempt was made to move this file outside the
MPE namespace.
ACTION
Do not attempt to move this file outside the MPE namespace.
93
MESSAGE
A component of the pathname specified does not exist.
(FILE SYSTEM ERROR -93)
CAUSE
One of the components of the path name does not exist.
ACTION
Check the spelling of each component of the path.
94
MESSAGE
The user lacks create access (CD) to the directory in which a,
file is to be created. (FILE SYSTEM ERROR -94)
CAUSE
The security attributes of the directory node do
not allow the user to create an object in the directory.
ACTION
Have the appropriate person allow CD access to this user.
95
MESSAGE
The user lacks delete access (DD) to the directory in which a
file is to be removed. (FILE SYSTEM ERROR -95)
CAUSE
The security attributes of the directory node do
not allow the user to delete an object from the directory.
ACTION
Have the appropriate person allow DD access to this user.
96
MESSAGE
The Storage Management Subsystem could not open this file.
(FILE SYSTEM ERROR -96)
CAUSE
The directory UFID entry for this file is probably invalid.
ACTION
Run FSCHECK on the system.
97
MESSAGE
Files in the specified file domain must remain in the MPE
namespace. (FILE SYSTEM ERROR -97)
CAUSE
An attempt was made to place a file outside the MPE namespace in a
file domain that only supports the MPE namespace.
ACTION
Do not attempt to give this file a name outside
the MPE namespace.
100
MESSAGE
The name syntax that was specified is invalid.
(FILE SYSTEM ERROR -100)
CAUSE
An invalid name syntax was specified.
ACTION
Consult the Intrinsics Manual for valid syntax values.
101
MESSAGE
A system file name was specified that was not known to the
system. (FILE SYSTEM ERROR -101)
CAUSE
An invalid $xxxx name was specified.
ACTION
Consult the Intrinsics Manual for valid system file names.
102
MESSAGE
An invalid character was found in an MPE syntax name.
(FILE SYSTEM ERROR -102)
CAUSE
An invalid MPE name was specified.
ACTION
Make sure that the name contains only alphanumerics,
. , /, and :.
103
MESSAGE
A wildcard character was found in the name, and it was not
allowed. (FILE SYSTEM ERROR -103)
CAUSE
A wildcard character was present in the name when
it was not allowed.
ACTION
Remove wildcard characters from the name.
104
MESSAGE
A back-referenced file specification is not allowed here.
(FILE SYSTEM ERROR -104)
CAUSE
A leading * was found in the name when it was not allowed.
ACTION
Do not attempt to backreference the file to a file
equation.
105
MESSAGE
System files are not allowed to be specified here.
(FILE SYSTEM ERROR -105)
CAUSE
A system file was specified when it was not allowed.
ACTION
Do not attempt to specify a system file.
106
MESSAGE
A remote environment specification is not allowed here.
(FILE SYSTEM ERROR -106)
CAUSE
A remote environment was specified when it was not allowed.
ACTION
Do not attempt to specify a remote environment.
107
MESSAGE
An invalid usage of a character class was attempted.
(FILE SYSTEM ERROR -107)
CAUSE
A character class specification was done improperly.
ACTION
Refer to either the Intrinsics Manual or the Commands Reference
Manual for information on properly specifying a character
class.
108
MESSAGE
The name specified is missing the file name component.
(FILE SYSTEM ERROR -108)
CAUSE
The file name component of a name was not specified.
ACTION
Make sure to specify the file name of the file.
109
MESSAGE
The file name did not start with an alphabetic character.
(FILE SYSTEM ERROR -109)
CAUSE
An illegal file name was specified.
ACTION
Make sure the name specified conforms to the specified syntax
rules.
110
MESSAGE
The file name specified is exceeds the maximum legal length.
(FILE SYSTEM ERROR -110)
CAUSE
The file name is too long.
ACTION
Make sure the name conforms to the specified syntax rules.
111
MESSAGE
The lockword in the backreferenced file name is illegal.
(FILE SYSTEM ERROR -111)
CAUSE
The lockword in the backreferenced file name is illegal.
ACTION
Specify a legal lockword.
112
MESSAGE
Specifying a lockword in a wildcarded file name is illegal.
(FILE SYSTEM -112)
CAUSE
Specifying a lockword in a wildcarded file name is illegal.
ACTION
Do not specify a lockword in a wildcarded file name.
113
MESSAGE
The lockword specification is missing.
(FILE SYSTEM ERROR -113)
CAUSE
The lockword specification is missing.
ACTION
Supply a lockword.
114
MESSAGE
The lockword specified did not start with an alphabetic
character. (FILE SYSTEM ERROR -114)
CAUSE
An illegal lockword was specified.
ACTION
Specify a legal lockword.
115
MESSAGE
The lockword specified exceeds the maximum legal length.
(FILE SYSTEM ERROR -115)
CAUSE
The lockword is too long.
ACTION
Specify a legal lockword.
116
MESSAGE
The group name is missing. (FILE SYSTEM ERROR -116)
CAUSE
The group name is missing from the specified name.
ACTION
Supply a group name, or remove the trailing period.
117
MESSAGE
The group name provided did not start with an alphabetic
character. (FILE SYSTEM ERROR -117)
CAUSE
An illegal group name was specified.
ACTION
Supply a legal group name.
118
MESSAGE
The group name specified exceeds the maximum legal length.
(FILE SYSTEM ERROR -118)
CAUSE
The group name is too long.
ACTION
Supply a legal group name.
119
MESSAGE
The account name is missing.
(FILE SYSTEM ERROR -119)
CAUSE
The account name is missing.
ACTION
Supply an account name, or remove the trailing period.
120
MESSAGE
The account name specified did not start with an alphabetic
character. (FILE SYSTEM ERROR -120)
CAUSE
An illegal account name was specified.
ACTION
Supply a legal account name.
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.
CIERR 200 - 399
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.
210
MESSAGE
The ACCESS TYPE OPTION (item# 11) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 210)
CAUSE
The access type is not one of the valid access types or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify the access type correctly.
211
MESSAGE
The DYNAMIC LOCKING OPTION (item# 12) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 211)
CAUSE
An INVALID DYNAMIC LOCKING option was specified or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify the DYNAMIC LOCKING OPTION correctly.
212
MESSAGE
The EXCLUSIVE OPTION (item# 13) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 212)
CAUSE
The EXCLUSIVE OPTION specified is not a valid exclusive option or
the variable passed to the file system is not accessible by
the caller.
ACTION
Specify the EXCLUSIVE OPTION correctly.
213
MESSAGE
The MULTIRECORD OPTION (item# 15) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 213)
CAUSE
The MULTI-RECORD OPTION was not specified correctly or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify the MULTI-RECORD OPTION correctly.
214
MESSAGE
The MULTIACCESS OPTION (item# 14) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 214)
CAUSE
The MULTI-ACCESS OPTION was not specified correctly or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify the MULTI-ACCESS OPTION correctly.
215
MESSAGE
The NOWAIT I/O OPTION (item# 16) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 215)
CAUSE
The NOWAIT I/O OPTION was not specified correctly or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify the NOWAIT I/O OPTION correctly.
216
MESSAGE
The COPY MODE OPTION (item# 17) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 216)
CAUSE
The COPY MODE OPTION was not specified correctly or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify the COPY MODE OPTION correctly.
217
MESSAGE
The DESIGNATOR OPTION (item# 5) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 217)
CAUSE
The specified designator is not one of the valid designator types or
the variable passed to the file system is not accessible
by the caller.
ACTION
Specify a valid designator.
218
MESSAGE
Bounds violation occurred on either the SHORT MAPPED OPTION
(item# 18), or on the LONG MAPPED OPTION (item# 21).
(FILE OPEN ERROR 218)
CAUSE
The pointer variable passed to HPFOPEN is not accessible by
the caller.
ACTION
Use only program-local variables when calling HPFOPEN.
219
MESSAGE
The RECORD SIZE OPTION (item# 19) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 219)
CAUSE
The specified record size is not correct or the variable passed to
the file system is not accessible by the caller.
ACTION
Specify a valid record size.
220
MESSAGE
The DEVICE NAME OPTION (item# 20) is not valid, missing
delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 220)
CAUSE
The specified device name contains one of the following errors:
invalid characters, missing delimiters, invalid length, or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify a valid device name using valid delimiters.
221
MESSAGE
The VOLUME CLASS OPTION (item# 22) is either invalid, missing
delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 221)
CAUSE
The specified volume class name contains one or the following
errors: invalid characters, missing delimiters, invalid length, or the
variable passed to the file system is not accessible by
the caller.
ACTION
Specify a valid volume class name using valid delimiters.
222
MESSAGE
The VOLUME NAME OPTION (item# 23) is either invalid, missing
delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 222)
CAUSE
The specified volume name contains one of the following errors:
invalid characters, missing delimiters, invalid length or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify a valid volume name using valid delimiters.
223
MESSAGE
The TAPE DENSITY OPTION (item# 24) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 223)
CAUSE
The specified tape density is not a valid density or the variable
passed to the file system is not accessible by the caller.
ACTION
Specify the tape density correctly.
224
MESSAGE
The PRINTER ENVIRONMENT OPTION (item# 25) is either invalid,
missing delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 224)
CAUSE
The specified environment file name contains one of the following
errors: invalid characters, missing delimiters, invalid length or the
variable passed to the file system is not accessible by the
caller.
ACTION
Specify a valid environment file name using valid
delimiters.
225
MESSAGE
The REMOTE ENVIRONMENT OPTION (item# 26) is either invalid,
missing delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 225)
CAUSE
The specified remote environment name contains one of the following
errors: invalid characters, missing delimiters, invalid length of the
variable passed to the file system is not accessible by
the caller.
ACTION
Specify a valid remote environment name using valid
delimiters.
226
MESSAGE
The OUTPUT PRIORITY OPTION (item# 27) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 226)
CAUSE
The specified printer priority is not a valid priority or the
variable passed to the file system is not accessible by the
caller.
ACTION
Specify a valid printer priority.
227
MESSAGE
The SPOOLED MESSAGE OPTION (item# 28) is either invalid, missing
delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 227)
229
MESSAGE
The LABELED TAPE TYPE OPTION (item# 30) is either invalid,
missing delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 229)
230
MESSAGE
The LABELED TAPE EXPIRATION OPTION (item# 31) is either invalid,
missing delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 230)
231
MESSAGE
The LABELED TAPE SEQUENCE OPTION (item# 32) is either invalid,
missing delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 231)
232
MESSAGE
The USER LABELS OPTION (item# 33) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 232)
233
MESSAGE
The SPOOLER COPIES OPTION (item# 34) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 233)
234
MESSAGE
The FILESIZE OPTION (item# 35) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 234)
235
MESSAGE
The INITIAL ALLOCATION OPTION (item# 36) is not valid, or a
bounds violation occurred on this option.
(FILE OPEN ERROR 235)
236
MESSAGE
The FILECODE OPTION (item# 37) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 236)
238
MESSAGE
The WILL-ACCESS OPTION (item# 39) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 238)
239
MESSAGE
The BLOCK FACTOR OPTION (item# 40) is not valid, or a bounds
violation occurred on the option. (FILE OPEN ERROR 239)
240
MESSAGE
The FILE NAME SYNTAX OPTION (item# 41) is not valid, or a
bounds violation occurred on this option.
(FILE OPEN ERROR 240)
241
MESSAGE
The DEVICE CLASS OPTION (item# 42) is either invalid, missing
delimiters, or a bounds violation occurred on this option.
(FILE OPEN ERROR 241)
242
MESSAGE
A file equation is required, but a file equation for the file
does not exist. (FILE OPEN ERROR 242)
243
MESSAGE
An invalid (unsupported) ITEMNUMBER was passed to HPFOPEN.
(FILE OPEN ERROR 243)
244
MESSAGE
A bounds violation occurred on the pointer passed with the LONG
MAPPED OPTION (item# 21). (FILE OPEN ERROR 244)
245
MESSAGE
The FORMALDESIGNATOR OPTION (item# 2) does not represent a valid
MPE/iX file name. (FILE OPEN ERROR 245)
246
MESSAGE
Specifying REMOTE ACCESS with these options is not allowed.
(FILE OPEN ERROR 246)
247
MESSAGE
The file does not exist in specified domain; the file was not
found. (FILE OPEN ERROR 247)
248
MESSAGE
Access to this file is denied for the specified file access; a
security violation occurred. (FILE OPEN ERROR 248)
249
MESSAGE
This file may not be opened with these options and the current
user's privilege level; a priveleged file violation occurred.
(FILE OPEN ERROR 249)
250
MESSAGE
The number of files opened for this process exceeds the maximum
available. (FILE OPEN ERROR 250)
251
MESSAGE
An error occurred in FDEVICECONTROL while processing the
specified printer environment file.
(FILE SYSTEM ERROR -251)
CAUSE
A failure in the FDEVICECONTROL intrinsic.
ACTION
File an SR.
252
MESSAGE
The file may not be opened exclusively, because the file is
already open. (FILE OPEN ERROR 252)
253
MESSAGE
The requested functionality is not currently implemented.
(FILE OPEN ERROR 253)
254
MESSAGE
The file name is missing from the formal designator
specification. (FILE OPEN ERROR 254)
255
MESSAGE
The file name starts with a nonalphabetic character.
(FILE OPEN ERROR 255)
256
MESSAGE
The file name exceeds eight characters.
(FILE OPEN ERROR 256)
257
MESSAGE
The file name contains a nonalphanumeric character.
(FILE OPEN ERROR 257)
258
MESSAGE
The lockword starts with a nonalphabetic character.
(FILE OPEN ERROR 258)
259
MESSAGE
The lockword exceeds eight characters.
(FILE OPEN ERROR 259)
260
MESSAGE
The lockword contains a nonalphanumeric character.
(FILE OPEN ERROR 260)
261
MESSAGE
The group name is missing from formal designator specification.
(FILE OPEN ERROR 261)
262
MESSAGE
The group name starts with a nonalphabetic character.
(FILE OPEN ERROR 262)
263
MESSAGE
The group name exceeds eight characters.
(FILE OPEN ERROR 263)
264
MESSAGE
The group name contains a nonalphanumeric character.
(FILE OPEN ERROR 264)
265
MESSAGE
The account name is missing from the formal designator
specification. (FILE OPEN ERROR 265)
266
MESSAGE
The account name starts with a nonalphabetic character.
(FILE OPEN ERROR 266)
267
MESSAGE
The account name exceeds eight characters.
(FILE OPEN ERROR 267)
268
MESSAGE
The account name contains a nonalphanumeric character.
(FILE OPEN ERROR 268)
269
MESSAGE
The remote environment or node name specified within a formal
designator is null. (FILE OPEN ERROR 269)
270
MESSAGE
The node name or remote environment specification in the formal
designator exceeds 80 characters. (FILE OPEN ERROR 270)
271
MESSAGE
The volume name specified on an existing file does not match the
volume restrictions for that file. (HPFOPEN ERROR 271)
272
MESSAGE
The volume class specified does not match the volume
restrictions for the existing file. (FILE OPEN ERROR 272)
273
MESSAGE
The creation of a file failed because of a duplicate permanent
file. (FILE OPEN ERROR 273)
274
MESSAGE
The volume class does not reside in the volume set attached to
the group in which the file is being opened.
(FILE OPEN ERROR 274)
275
MESSAGE
The volume name does not reside in the volume class specified.
(FILE OPEN ERROR 275)
276
MESSAGE
The volume name specified does not reside in the volume set
attached to the group in which the file is being opened.
(FILE OPEN ERROR 276)
277
MESSAGE
The procedure failed to allocate a new GDPD; there are too
many multi-access files opened on the system.
(FILE OPEN ERROR 277)
278
MESSAGE
The base of the option can not specify the option
list.
279
MESSAGE
This message is reserved.
280
MESSAGE
Specifying the FORMALDESIGNATOR OPTION (item# 2) for this file
type is invalid. (FILE OPEN ERROR 280)
281
MESSAGE
Specifying the DOMAIN OPTION (item# 3) for this file type is
invalid. (FILE OPEN ERROR 281)
282
MESSAGE
To be provided.
283
MESSAGE
Specifying the DESIGNATOR OPTION (item# 5) for this file type is
invalid. (FILE OPEN ERROR 283)
284
MESSAGE
Specifying the RECORD FORMAT OPTION (item# 6) for this file type
is invalid. (FILE OPEN ERROR 284)
285
MESSAGE
Specifying the CARRIAGE CONTROL OPTION (item# 7) for this file
type is invalid. (FILE OPEN ERROR 285)
286
MESSAGE
Specifying the LABELED TAPE LABEL OPTION (item# 8) for this file
type is invalid. (FILE OPEN ERROR 286)
287
MESSAGE
Specifying the DISALLOW FILE EQUATION OPTION (item# 9) for this
file type is invalid. (FILE OPEN ERROR 287)
288
MESSAGE
Specifying the FILE TYPE OPTION (item# 10) for this type of
file is invalid; contact your SE. (FILE OPEN ERROR 288)
289
MESSAGE
Specifying the ACCESS TYPE OPTION (item# 11) for this file type
is invalid. (FILE OPEN ERROR 289)
290
MESSAGE
Specifying the DYNAMIC LOCKING OPTION (item#12) for this file
type is not valid. (FILE OPEN ERROR 290)
291
MESSAGE
Specifying the EXCLUSIVE OPTION (item# 13) for this file type is
invalid. (FILE OPEN ERROR 291)
292
MESSAGE
Specifying the MULTIACCESS OPTION (item# 14) for this file type
is invalid. (FILE OPEN ERROR 292)
293
MESSAGE
Specifying the MULTIRECORD OPTION (item# 15) for this file type
is not valid. (FILE OPEN ERROR 293)
294
MESSAGE
Specifying the NOWAIT I/O OPTION (item# 16) for this file type
is not valid. (FILE OPEN ERROR 294)
295
MESSAGE
Specifying the COPY MODE OPTION (item# 1) for this file type is
not valid. (FILE OPEN ERROR 295)
296
MESSAGE
Specifying the SHORT MAPPED OPTION (item# 18) for this file type
is not valid. (FILE OPEN ERROR 296)
297
MESSAGE
Specifying the RECORD SIZE OPTION (item# 19) for this file type
is invalid. (FILE OPEN ERROR 297)
298
MESSAGE
Specifying the DEVICE NAME OPTION (item# 20) for this file type
is invalid. (FILE OPEN ERROR 298)
299
MESSAGE
Specifying the LONG MAPPED OPTION (item# 21) for this file type
is invalid. (FILE OPEN ERROR 299)
300
MESSAGE
Specifying the VOLUME CLASS OPTION (item# 22) for this file type
is invalid. (FILE OPEN ERROR 300)
301
MESSAGE
Specifying the VOLUME NAME OPTION (item# 23) for this file type
is invalid. (FILE OPEN ERROR 301)
302
MESSAGE
Specifying the DENSITY OPTION (item# 24) for this file type is
invalid. (FILE OPEN ERROR 302)
303
MESSAGE
Specifying the PRINTER ENVIRONMENT OPTION (item# 25) for this
file type is invalid. (FILE OPEN ERROR 303)
304
MESSAGE
Specifying the REMOTE ENVIRONMENT OPTION (item# 26) for this
file type is invalid. (FILE OPEN ERROR 304)
305
MESSAGE
Specifying the OUTPUT PRIORITY OPTION (item# 27) for this file
type is invalid. (FILE OPEN ERROR 305)
306
MESSAGE
Specifying the SPOOLED MESSAGE OPTION (item# 28) for this file
type is invalid. (FILE OPEN ERROR 306)
307
MESSAGE
Specifying the PRIVILEGED ACCESS OPTION (item# 29) for this file
type is invalid. (FILE OPEN ERROR 307)
308
MESSAGE
Specifying the LABELED TAPE TYPE OPTION (item# 30) for this file
type is invalid. (FILE OPEN ERROR 308)
309
MESSAGE
Specifying the LABELED TAPE EXPIRATION OPTION (item# 31) for
this file is invalid. (FILE OPEN ERROR 309)
310
MESSAGE
Specifying the LABELED TAPE SEQUENCE OPTION (item# 32) for
this file type is invalid. (FILE OPEN ERROR 310)
311
MESSAGE
Specifying the USER LABELS OPTION (item# 33) for this file type
is invalid. (FILE OPEN ERROR 311)
312
MESSAGE
Specifying the SPOOLER COPIES OPTION (item# 34) for this file
type is invalid. (FILE OPEN ERROR 312)
313
MESSAGE
Specifying the FILESIZE OPTION (item# 35) for this file type
is invalid. (FILE OPEN ERROR 313)
314
MESSAGE
Specifying the INITIAL ALLOCATION OPTION (item# 36) for this
file type is invalid. (FILE OPEN ERROR 314)
315
MESSAGE
Specifying the FILECODE OPTION (item# 37) for this file type is
invalid. (FILE OPEN ERROR 315)
316
MESSAGE
Specifying the FILE PRIVILEGE OPTION (item# 38) for this file
type is invalid. (FILE OPEN ERROR 316)
317
MESSAGE
Specifying the WILL ACCESS OPTION (item# 39) for this file
type is invalid. (FILE OPEN ERROR 317)
318
MESSAGE
Specifying the BLOCK FACTOR OPTION (item# 40) for this file
type is invalid. (FILE OPEN ERROR 318)
319
MESSAGE
Specifying the NAME SYNTAX OPTION (item# 41) for this file type
is invalid. (FILE OPEN ERROR 319)
320
MESSAGE
Specifying the DEVICE CLASS OPTION (item# 42) for this file
type is invalid. (FILE OPEN ERROR 320)
321
MESSAGE
Specifying the UFID OPTION (item# 43) for this file type
is invalid. (FILE OPEN ERROR 321)
322
MESSAGE
Specifying the NUMBUFFERS OPTION (item# 44) for this file
type is invalid. (FILE OPEN ERROR 322)
323
MESSAGE
Specifying the FILL CHARACTER OPTION (item# 45) for this file
type is invalid. (FILE OPEN ERROR 323)
324
MESSAGE
Specifying the INHIBIT BUFFERING OPTION (item# 46) for this
file type is invalid. (FILE OPEN ERROR 324)
325
MESSAGE
Specifying the NUMEXTENTS OPTION (item# 47) for this file type
is invalid. (FILE OPEN ERROR 325)
326
MESSAGE
Specifying the REVERSE VT OPTION (item# 48) for this file type
is invalid. (FILE OPEN ERROR 326)
327
MESSAGE
Specifying the PIN OPTION (item# 49) for this file type is
invalid. (FILE OPEN ERROR 327)
328
MESSAGE
Specifying the FINAL DISPOSITION OPTION (item# 50) for this
file type is invalid. (FILE OPEN ERROR 328)
329
MESSAGE
Specifying the PASCAL XL STRING OPTION (item# 51) for this file
type is invalid. (FILE OPEN ERROR 329)
330
MESSAGE
Specifying the FILE EQUATION STRING OPTION (item# 52) for this
file type is invalid. (FILE OPEN ERROR 330)
331
MESSAGE
Specifying the ASCII/BINARY OPTION (item# 53) for this file
type is invalid. (FILE OPEN ERROR 331)
332
MESSAGE
Specifying the KSAM PARMS OPTION (item# 54) for this file type
is invalid. (FILE OPEN ERROR 332)
333
MESSAGE
Specifying the RAW OPTION (item# 55) for this file type
is invalid. (FILE OPEN ERROR 333)
334
MESSAGE
Specifying the OBJECT CLASS OPTION (item# 56) for this file
type is invalid. (FILE OPEN ERROR 334)
335
MESSAGE
Specifying the VARIABLE ACCESS RIGHTS OPTION (item# 57) for this
file type is invalid. (FILE OPEN ERROR 335)
336
MESSAGE
Specifying the UNPROTECTED OPTION (item# 58) for this file type
is invalid. (FILE OPEN ERROR 336)
337
MESSAGE
Specifying the SYSTEM OBJECT CLASS OPTION (item# 59) for this
file type is invalid. (FILE OPEN ERROR 337)
338
MESSAGE
Specifying the FILE PID OPTION (item# 60) for this file type
is invalid. (FILE OPEN ERROR 338)
339
MESSAGE
Specifying the ACCESS RIGHTS OPTION (item# 61) for this file
type is invalid. (FILE OPEN ERROR 339)
340
MESSAGE
Lockword on file being referenced cannot be
specified.
CAUSE
Specifying a lockword for a file accessed as a raw or referencing a
file with a lockword using POSIX name syntax is prohibited.
ACTION
In the case of raw mode access to a file, don't specify a lockword.
In the case of name syntax, use only MPE or MPE Escaped name syntax
when referencing a file with a lockword.
343
MESSAGE
It is illegal to specify the file close privilege option in
this context. (FILE SYSTEM ERROR -343)
CAUSE
The file close privilege option was specified in
an illegal context.
ACTION
Do not specify the file close privilege option.
344
MESSAGE
It is illegal to specify the raw open option in this context.
(FILE SYSTEM ERROR -344)
CAUSE
The raw open option was specified in an illegal context.
ACTION
Do not specify the raw open option.
345
MESSAGE
The caller lacks the necessary privilege level to call the raw
open option. (FILE SYSTEM ERROR -345)
CAUSE
The caller is not privileged enough to call the raw
open option.
ACTION
Acquire the necessary privileges before calling with
this option.
346
MESSAGE
The value passed in with the raw open option is not valid.
(FILE SYSTEM ERROR -346)
CAUSE
A bad file label image was passed to HPFOPEN.
ACTION
Ensure only valid file labels are passed to HPFOPEN.
350
MESSAGE
The VIRTUAL ADDRESS is nil.
360
MESSAGE
The GUFD PTR is nil.
361
MESSAGE
Both the LONG (item# 21) and SHORT MAPPED (item# 18) OPTIONS
were specified; this is a conflict. (FILE OPEN ERROR 361)
362
MESSAGE
The UFID OPTION (item# 43) is invalid, or a bounds violation
occurred on this option. (FILE OPEN ERROR 362)
363
MESSAGE
The file could not be found because insufficient options were
specified. (FILE OPEN ERROR 363)
364
MESSAGE
Opening a user-mapped, variable length file for write access
is not allowed. (FILE OPEN ERROR 364)
365
MESSAGE
An internal inconsistency was found within the file system data
structures; contact your HP Service Representative.
(FILE OPEN ERROR 365)
366
MESSAGE
The options specified can not be supplied to the COMPATIBILITY
MODE FILE SYSTEM. (FILE OPEN ERROR 366)
367
MESSAGE
A bounds violation occurred on the formal designator.
(FILE OPEN ERROR 367)
368
MESSAGE
The FILE TYPE OPTION in the options is not valid.
(FILE OPEN ERROR 368)
369
MESSAGE
The record format in the AOPTIONS is not valid.
(FILE OPEN ERROR 369)
370
MESSAGE
The DOMAIN is not valid. (FILE OPEN ERROR 370)
371
MESSAGE
The MULTIACCESS OPTION in the AOPTIONS is not valid.
(FILE OPEN ERROR 371)
372
MESSAGE
The EXCLUSIVE OPTION in the AOPTIONS is not valid.
(FILE OPEN ERROR 372)
373
MESSAGE
The ACCESS OPTION in the AOPTIONS is not valid.
(FILE OPEN ERROR 373)
374
MESSAGE
The RECORD SIZE PARAMETER is not valid.
(FILE OPEN ERROR 374)
375
MESSAGE
A bounds violation occurred on the DEVICE parameter.
(FILE OPEN ERROR 375)
376
MESSAGE
A bounds violation occurred on the FORMS MESSAGE parameter.
(FILE OPEN ERROR 376)
377
MESSAGE
The number of USER LABELS specified is invalid.
(FILE OPEN ERROR 377)
378
MESSAGE
The BLOCKFACTOR parameter is out of range.
(FILE OPEN ERROR 378)
379
MESSAGE
The PRICOPBUFS parameter is invalid.
(FILE OPEN ERROR 379)
380
MESSAGE
The FILE SIZE parameter is invalid.
(FILE OPEN ERROR 380)
381
MESSAGE
The EXTENT parameter is invalid.
(FILE OPEN ERROR 381)
382
MESSAGE
The FILECODE parameter is invalid.
(FILE OPEN ERROR 382)
383
MESSAGE
The DEVICE NAME parameter is invalid.
(FILE OPEN ERROR 383)
384
MESSAGE
Missing delimiter in DEVICE STRING after device options.
(FILE OPEN ERROR 384)
385
MESSAGE
The LDEV is ZERO; this is not valid.
(FILE OPEN ERROR 385)
386
MESSAGE
The DEVICE CLASS is invalid. (FILE OPEN ERROR 386)
387
MESSAGE
The DEVICE CLASS NAME exceeds eight characters in length.
(FILE OPEN ERROR 387)
388
MESSAGE
The DEVICE OPTIONS after the device name are invalid.
(FILE OPEN ERROR 388)
389
MESSAGE
The FORMS LENGTH is too large.
(FILE OPEN ERROR 389)
390
MESSAGE
The TAPE LABEL exceeds 16 characters.
(FILE OPEN ERROR 390)
391
MESSAGE
The EXPIRATION DATE for LABELED TAPES exceeds the maximum length
for dates. (FILE OPEN ERROR 391)
392
MESSAGE
The LABELED TAPE SEQUENCE parameter is too long.
(FILE OPEN ERROR 392)
393
MESSAGE
The TAPE TYPE is not one of IBM or ANS.
(FILE OPEN ERROR 393)
394
MESSAGE
The DELIMITER is missing in the FORMS message (after the
labelled tape information). (FILE OPEN ERROR 394)
395
MESSAGE
There is a comma missing in the DEVICE specification.
(FILE OPEN ERROR 395)
396
MESSAGE
The DENSITY OPTION is not valid.
(FILE OPEN ERROR 396)
397
MESSAGE
The number of buffers specified is invalid.
(FILE OPEN ERROR 397)
398
MESSAGE
The FILL CHARACTER OPTION (item# 45) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 398)
399
MESSAGE
The INHIBIT BUFFERING OPTION (item# 46) is not valid, or a
bounds violation occurred on this option.
(FILE OPEN ERROR 399)
CIERR 400 - 699
400
MESSAGE
The NUMEXTENTS OPTION (item# 47) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 400)
401
MESSAGE
New files may not be opened using the UFID OPTION (item# 43)
if the file has not been saved as a permanent file.
(FILE OPEN ERROR 401)
402
MESSAGE
File creation failed during directory insertion due to security
violations. (FILE OPEN ERROR 402)
403
MESSAGE
The PIN OPTION (item# 49) was specified by a caller executing
at an incorrect PRIVILEGE level. (FILE OPEN ERROR 403)
404
MESSAGE
The PIN parameter is invalid.
(FILE OPEN ERROR 404)
405
MESSAGE
The maximum BLOCK SIZE was exceeded for a file with variable
length records. (FILE OPEN ERROR 405)
406
MESSAGE
The file type specified in the FILE TYPE OPTION (item# 10) is
not supported. (FILE OPEN ERROR 406)
407
MESSAGE
No file exists at the PIN and file number specified.
(FILE BESTOW ERROR 407)
408
MESSAGE
Can not bestow a nonNATIVE MODE FILE.
(FILE BESTOW ERROR 408)
409
MESSAGE
The FROM file does not exist (is not opened).
(FILE BESTOW ERROR 409)
410
MESSAGE
Opening of a DIRECTORY file failed because allocation of a
PLFD failed. (PROCESS CREATION ERROR 410)
411
MESSAGE
The PLFD TABLE has been corrupted; contact your SE.
(PROCESS CREATION ERROR 411)
412
MESSAGE
Opening of a directory file failed.
(PROCESS CREATION ERROR 412)
413
MESSAGE
Redirection of STDIN and STDLIST is not supported.
(PROCESS CREATION ERROR 413)
414
MESSAGE
FCLOSE of a reserved file failed.
(PROCESS CREATION ERROR 414)
415
MESSAGE
Opening of $STDIN failed.
(PROCESS CREATION ERROR 415)
416
MESSAGE
Opening of $STDLIST failed.
(PROCESS CREATION ERROR 416)
417
MESSAGE
Opening of $STDERR failed.
(PROCESS CREATION ERROR 417)
418
MESSAGE
Opening of $PROGRAM failed.
(PROCESS CREATION ERROR 418)
419
MESSAGE
The file system failed to locate the FATHER'S ROOT GUFD.
(PROCESS CREATION ERROR 419)
420
MESSAGE
Opening the ROOT DIRECTORY file failed.
(PROCESS CREATION ERROR 420)
421
MESSAGE
The file system failed to locate the FATHER'S ACCOUNT
directory GUFD. (PROCESS CREATION ERROR 421)
422
MESSAGE
Opening of the ACCOUNT directory failed.
(PROCESS CREATION ERROR 422)
423
MESSAGE
The file system failed to locate the FATHER'S GROUP directory
GUFD. (PROCESS CREATION ERROR 423)
424
MESSAGE
Opening of the GROUP directory failed.
(PROCESS CREATION ERROR 424)
425
MESSAGE
The file system failed to locate the FATHER'S TEMPORARY
directory GUFD. (PROCESS CREATION ERROR 425)
426
MESSAGE
Opening of the TEMPORARY directory failed.
(PROCESS CREATION ERROR 426)
427
MESSAGE
Upon closing a reserved file and reopening the system file,
the file number returned from the OPEN operation does not match the
reserved file number. (PROCESS CREATION ERROR 427)
428
MESSAGE
The FATHER'S directory file is not a NATIVE MODE file.
(PROCESS CREATION ERROR 428)
429
MESSAGE
Dynamic LOCKING was specified, yet the previous OPEN of the
file did not specify dynamic LOCKING.
(FILE OPEN ERROR 429)
430
MESSAGE
Dynamic LOCKING was specified on a previous OPEN of this file,
and dynamic LOCKING was not specified on this call to HPFOPEN.
(FILE OPEN ERROR 430)
431
MESSAGE
The FINAL DISPOSITION OPTION (item# 50) is not valid, or a
bounds violation occurred on this option.
(FILE OPEN ERROR 431)
432
MESSAGE
The file name specified begins with a dollar sign ('$') and is
not a valid standard file name. (FILE OPEN ERROR 432)
433
MESSAGE
A back-referenced file equation does not exist.
(FILE OPEN ERROR 433)
434
MESSAGE
The specified syntax option is not currently implemented.
(FILE OPEN ERROR 434)
435
MESSAGE
The switch to COMPATIBILITY MODE FOPEN failed; contact your SE.
(FILE OPEN ERROR 435)
436
MESSAGE
There is an invalid character in the device string.
(FILE OPEN ERROR 436)
437
MESSAGE
$OLDPASS was not passed in for a file.
(FILE OPEN ERROR 437)
438
MESSAGE
The COMPATIBILITY MODE AFT index does not match the NATIVE MODE
PLFD index, implying the use of an AFT without going through the
standard file open mechanism. (FILE OPEN ERROR 438)
439
MESSAGE
The record format specified is not compatible with the device
type or file type specified. (FILE OPEN ERROR 439)
440
MESSAGE
The entry point specified is not valid.
(FILE OPEN ERROR 440)
441
MESSAGE
The creation of the COMPATIBILITY MODE disk file failed.
(FILE OPEN ERROR 441)
442
MESSAGE
The file type field of the FOPTIONS does not contain a
valid file type. (FILE OPEN ERROR 442)
443
MESSAGE
The file system is unable to obtain the COMPATIBILITY MODE
information for a COMPATIBILITY MODE file type.
(FILE OPEN ERROR 443)
444
MESSAGE
A file access rights entry does not exist for the specified
file. (FILE ACCESS RIGHTS ERROR 444)
445
MESSAGE
No more file entries can be added to the FILE ACCESS RIGHTS
TABLE. (FILE ACCESS RIGHTS ERROR 445)
446
MESSAGE
The creation of the FILE ACCESS RIGHTS TABLE failed.
(FILE ACCESS RIGHTS ERROR 446)
447
MESSAGE
The FILE EQUATION STRING OPTION (item# 52) contains an
invalid character. (FILE OPEN ERROR 447)
448
MESSAGE
The FILE EQUATION STRING OPTION (item# 52) is either
inaccessible at the caller's privilege level (bounds violation) or is
missing a delimiter. (FILE OPEN ERROR 448)
449
MESSAGE
The FILE EQUATION STRING option (item# 52) is not in a valid
file equation form. (FILE OPEN ERROR 449)
450
MESSAGE
There is an invalid character in FILE EQUATION STRING OPTION
(item# 52). (FILE OPEN ERROR 450)
451
MESSAGE
The TEMPORARY FILE specified does not exist; the file was not
found. (FILE OPEN ERROR 451)
452
MESSAGE
Both READ and WRITE must be specified as either NOWAIT or WAIT
for this type of file. (FILE OPEN ERROR 452)
453
MESSAGE
The group specified does not exist in the account; the group
was not found. FILE OPEN ERROR 453)
454
MESSAGE
The account specified does not exist on the system; the account
was not found. (FILE OPEN ERROR 454)
455
MESSAGE
The PASCAL XL STRING OPTION (item# 51) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 455)
456
MESSAGE
The file could not be opened because the file is being restored
or stored, the file is already open, or write access is not allowed
because the file is already open in a way which does not allow
subsequent writers. (FILE OPEN ERROR 456)
457
MESSAGE
An unknown error was returned from STORAGE MANAGEMENT.
(FILE OPEN ERROR 457)
458
MESSAGE
There is no more disk space left on the device; out of disk
space. (FILE OPEN ERROR 458)
459
MESSAGE
The specified extent size is not valid.
(FILE OPEN ERROR 459)
460
MESSAGE
A system error has occurred and was backed out with no system
damage. (FILE OPEN ERROR 460)
CAUSE
An ABORTIO occurred while trying to FOPEN a configured,
but non-existent device.
ACTION
Either add the device or use another.
461
MESSAGE
The maximum number of files for the operating system has been
exceeded. (FILE OPEN ERROR 461)
462
MESSAGE
The MAPPING OPTIONS for the file are not correct.
(FILE OPEN ERROR 462)
463
MESSAGE
A privileged file code violation occurred.
(FILE OPEN ERROR 463)
464
MESSAGE
The file's privilege level exceeds the caller's access
privilege level. (FILE OPEN ERROR 464)
465
MESSAGE
The access privilege level exceeds the caller's privilege level.
(FILE OPEN ERROR 465)
466
MESSAGE
EXECUTE access was specified by a nonprivileged caller.
(FILE OPEN ERROR 466)
467
MESSAGE
NOWAIT I/O was requested by a nonprivileged caller.
(FILE OPEN ERROR 467)
468
MESSAGE
The file size exceeds the maximum file size for this type of
file. Current limits are 128GB for STD fixed and KSAM64 files, 2GB for
byte stream files, and 4GB for all other files.
(FILE OPEN ERROR 468)
469
MESSAGE
The specified LOCKWORD does not match the LOCKWORD associated
with the file; this is a LOCKWORD violation.
(FILE OPEN ERROR 469)
470
MESSAGE
PRIVILEGE violation occurred.
(FILE OPEN ERROR 470)
471
MESSAGE
A BOUNDS violation occurred on the status parameter.
(FILE OPEN ERROR 471)
472
MESSAGE
A BOUNDS violation occurred on the file number parameter.
(FILE OPEN ERROR 472)
473
MESSAGE
The file number for "GET THE PLABEL" for a message file
is invalid.
474
MESSAGE
No PLABEL was found; contact your HP Service
Representative.
475
MESSAGE
The RAW OPTION (item# 55) was specified, but the caller was not
executing at the required PRIVILEGE level to use this privileged
feature. (FILE OPEN ERROR 475)
476
MESSAGE
A BOUNDS violation occurred on the RAW OPTION (item# 55).
(FILE OPEN ERROR 476)
477
MESSAGE
The version number in the file label passed with the RAW OPTION
(item# 55) is not correct for this version of the fsle System.
(FILE OPEN ERROR 477)
478
MESSAGE
The file label passed with the RAW OPTION (item# 55) is not a
valid file label. (FILE OPEN ERROR 478)
479
MESSAGE
The CREATE domain can not be used with the RAW OPTION
(item# 55). (FILE OPEN ERROR 479)
480
MESSAGE
The PERMANENT, TEMPORARY, or OLD domains can not be used with
the RAW OPTION (item# 55). (FILE OPEN ERROR 480)
481
MESSAGE
The system-defined file $NULL can not be opened for user-mapped
access. (FILE OPEN ERROR 481)
482
MESSAGE
The specified environment file could not be opened.
(FILE SYSTEM ERROR -482)
CAUSE
The open of the specified environment file failed.
ACTION
Ensure that the environment file is made accessible.
483
MESSAGE
The specified environment file is not a valid printer
environment file. (FILE SYSTEM ERROR -483)
CAUSE
The environment file is not valid.
ACTION
Check the file code and record size.
484
MESSAGE
The specified environment file has not been compiled.
(FILE SYSTEM ERROR -484)
CAUSE
An uncompiled environment file has been specified.
ACTION
Compile the specified environment file.
485
MESSAGE
The header record in the specified environment file is not
valid. (FILE SYSTEM ERROR -485)
CAUSE
The environment file is probably corrupted.
ACTION
Replace the environment file.
486
MESSAGE
An error occurred while reading the specified environment file.
(FILE SYSTEM ERROR -486)
CAUSE
An error occurred while reading the environment file.
ACTION
Copy the environment file to another file and retry the
operation.
487
MESSAGE
An error occurred while closing the specified environment file.
(FILE SYSTEM ERROR -487)
CAUSE
An error occurred while closing the environment file.
ACTION
No action is necessary.
488
MESSAGE
Opening this file by UFID is prohibited.
CAUSE
An attempt was made to open by ufid a file whose parent is a
directory in the hierarchical file system (HFS) or a file which is a
HFS directory itself. This is prohibited to non-system
code software.
ACTION
Either establist the calling software as system
code or do not attempt open by ufid on such files.
490
MESSAGE
The SHORT MAPPED file space used by the process exceeds the
maximum allowed per process. (FILE OPEN ERROR 490)
491
MESSAGE
The OBJECT CLASS OPTION (item# 56) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 491)
492
MESSAGE
The VOLUME NAME specified does not exist in the volume set
associated with the file's group. (FILE OPEN ERROR 492)
493
MESSAGE
A VOLUME MANAGEMENT error occurred.
(FILE OPEN ERROR 493)
494
MESSAGE
The VOLUME SET associated with the file's group does not exist.
(FILE OPEN ERROR 494)
495
MESSAGE
The VOLUME CLASS does not exist in the volume set.
(FILE OPEN ERROR 495)
496
MESSAGE
The specified VOLUME CLASS is not mounted.
(FILE OPEN ERROR 496)
497
MESSAGE
The specified VOLUME is not MOUNTED.
(FILE OPEN ERROR 497)
498
MESSAGE
The specified VOLUME is not defined in the group's volume set.
(FILE OPEN ERROR 498)
499
MESSAGE
The VOLUME SPECIFICATION is not valid; check the VOLUME CLASS
OPTION (item# 22) and/or the VOLUME NAME OPTION (item# 23).
(FILE OPEN ERROR 499)
500
MESSAGE
A DIRECTORY SERVICES ERROR occurred.
(FILE OPEN ERROR 500)
501
MESSAGE
The caller lacks the SAVE FILE (SF) capability.
(FILE OPEN ERROR 501)
502
MESSAGE
An invalid PARAMETER has been detected. This error may also
occur on unimplemented parameter values.
(FILE OPEN ERROR 502)
503
MESSAGE
The PRIVILEGED ACCESS OPTION (item# 29) is not valid, or a
bounds violation occurred on this option.
(FILE OPEN ERROR 503)
504
MESSAGE
The USER NAME does not exist in the directory.
(FILE OPEN ERROR 504)
505
MESSAGE
The VSD does not exist.
506
MESSAGE
You do not have SAVE ACCESS for the specified GROUP.
(FILE OPEN ERROR 506)
507
MESSAGE
You do not have SAVE ACCESS for the specified account.
(FILE OPEN ERROR 507)
508
MESSAGE
The request would exceed the permanent file space limit for the
specified group. (FILE OPEN ERROR 508)
509
MESSAGE
The request would exceed the permanent file space limit for the
specified account. (FILE OPEN ERROR 509)
510
MESSAGE
The FILE PRIVILEGE OPTION (item# 38) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 510)
511
MESSAGE
The volume set specified is closed; the file can not be opened
on the volume set at this time. (FILE OPEN ERROR 511)
512
MESSAGE
The VARIABLE ACCESS RIGHTS OPTION (item# 57) is not valid, or
a bounds violation occurred on this option.
(FILE OPEN ERROR 512)
513
MESSAGE
The specified device name represents a sharable device. The
DEVICE NAME OPTION (item# 20) may be used to specify nonsharable
devices only. (FILE OPEN ERROR 513)
514
MESSAGE
The specified device class represents a sharable device. The
DEVICE CLASS OPTION (item# 42) may be used to specify nonsharable
devices only. (FILE OPEN ERROR 514)
515
MESSAGE
The UNPROTECTED OPTION (item# 58) was specified, but the caller
was not at the required privilege level to use this privileged option.
(FILE OPEN ERROR 515)
516
MESSAGE
The UNPROTECTED OPTION (item# 58) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 516)
517
MESSAGE
The UNPROTECTED OPTION (item# 58) was specified, yet the
previous open of the file did not specify the UNPROTECTED OPTION.
(FILE OPEN ERROR 517)
518
MESSAGE
The UNPROTECTED OPTION (item# 58) was specified on a previous
open of this file, but the option was not specified by the current
accessor of the file. (FILE OPEN ERROR 518)
519
MESSAGE
The PRIVILEGED ACCESS OPTION (item# 29) was specified for an
unprotected file, and the specified access privilege level is greater
than level 1. This is not allowed for unprotected files.
(FILE OPEN ERROR 519)
520
MESSAGE
The SYSTEM OBJECT CLASS OPTION (item# 59) is not valid, or a
bounds violation occurred on this option.
(FILE OPEN ERROR 520)
521
MESSAGE
Both the OBJECT CLASS OPTION (item# 56) and SYSTEM OBJECT
CLASS OPTION (item# 59) were specified; this is a conflict.
(FILE OPEN ERROR 521)
522
MESSAGE
The file size is greater than 4 megabytes for a short mapped
file. (FILE OPEN ERROR 522)
523
MESSAGE
The COMPATIBILITY MODE file could not be created.
(FILE OPEN ERROR 523)
524
MESSAGE
Mountable volumes are not enabled.
(FILE OPEN ERROR 524)
525
MESSAGE
The operator denied access to the private volume; the file
could not be OPENED. (FILE OPEN ERROR 525)
526
MESSAGE
A CLOSE is pending on the volume set; the file can not be
OPENED. (FILE OPEN ERROR 526)
527
MESSAGE
A sharable device specification was expected, but a nonsharable
device was specified. (File Open error 527)
528
MESSAGE
The file system is unable to START a transaction.
529
MESSAGE
The file system is unable to END a transaction.
530
MESSAGE
The VARIABLE ACCESS RIGHTS OPTION (item# 57) was specified by
a caller executing at an incorrect privilege level.
(FILE OPEN ERROR 530)
531
MESSAGE
The FILE PID OPTION (item# 60) was specified by a caller
executing at an incorrect privilege level.
(FILE OPEN ERROR 531)
532
MESSAGE
The ACCESS RIGHTS OPTION (item# 61) was specified by a caller
executing at an incorrect privilege level.
(FILE OPEN ERROR 532)
533
MESSAGE
The FILE PID OPTION (item# 60) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 533)
534
MESSAGE
The ACCESS RIGHTS OPTION (item# 61) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 534)
535
MESSAGE
A MAPPED ACCESS OPTION (item# 18 or 21) was specified along with
the FILE PID OPTION (item# 60); this is not allowed.
(FILE OPEN ERROR 535)
536
MESSAGE
A MAPPED ACCESS OPTION (item# 18 or 21) was specified along with
the VARIABLE ACCESS RIGHTS OPTION (item# 57); this is not allowed.
(FILE OPEN ERROR 536)
537
MESSAGE
Opening a MAPPED ACCESS KSAM file for WRITE access is not
allowed. (FILE OPEN ERROR 537)
538
MESSAGE
Opening a MAPPED ACCESS KSAM file without COPY MODE is not
allowed. (FILE OPEN ERROR 538)
539
MESSAGE
A bounds violation occurred on the KSAM PARMS OPTION (item# 54).
(FILE OPEN ERROR 539)
540
MESSAGE
The REVERSE VT OPTION (item# 48) is not valid, or a bounds
violation occurred on this option. (FILE OPEN ERROR 540)
541
MESSAGE
The group does not exist on the volume set; the group was not
found. (FILE OPEN ERROR 541)
542
MESSAGE
The account does not exist on the volume set; the account was
not found. (FILE OPEN ERROR 542)
543
MESSAGE
Using the specified block factor and record size (plus
overhead), the resultant block size is too big.
(FILE OPEN ERROR 543)
544
MESSAGE
The requested file mapping options conflict with the mapping
options currently in effect for the file which is already open. The
conflict may be in the follo wing options (item numbers): 18, 21, 57,
58, 60, 61. (FILE OPEN ERROR 544)
545
MESSAGE
An unexpected trap was encountered; contact your SE.
(FILE OPEN ERROR 545)
546
MESSAGE
The file system can not open a file for MAPPED and WRITE access
when the file is protected by TRANSACTION MANAGEMENT.
(FILE OPEN ERROR 546)
547
MESSAGE
The UNPROTECTED VARIABLE ACCESS RIGHTS OPTION (item# 62) was
specified by a caller executing at an incorrect privilege level.
(FILE OPEN ERROR 547)
548
MESSAGE
The UNPROTECTED VARIABLE ACCESS RIGHTS OPTION (item# 62) is not
valid, or a bounds violation occurred on this option.
(FILE OPEN ERROR 548)
549
MESSAGE
An error occurred while writing to the file label.
(FILE OPEN ERROR 549)
550
MESSAGE
A portion of the file resides on a volume which is not mounted
or is not accessible by the operating system.
(FILE OPEN ERROR 550)
551
MESSAGE
The caller is not sufficiently privileged to request the must
allocate secondary storage option.
(FILE SYSTEM ERROR -551)
CAUSE
The caller is not privileged enough to specify this option.
ACTION
Acquire the necessary privileges prior to the operation.
552
MESSAGE
The must allocate secondary storage option is not valid.
(FILE SYSTEM ERROR -552)
CAUSE
Either the value is not valid, or a bounds violation
occurred.
ACTION
Supply a legal value for this option.
553
MESSAGE
An attempt was made to decrement the File Open Count Table when
the count had not been incremented.
(FILE SYSTEM ERROR -553)
CAUSE
A coding error exists in the file system.
ACTION
File an SR.
554
MESSAGE
Redirecting a system file to a KSAM file is not allowed.
(PROCESS ERROR 554)
555
MESSAGE
The perm-to-temp final disposition was specified by a caller
that is at an incorrect privilege level.
(FILE OPEN ERROR 555)
556
MESSAGE
An error occurred during the expansion of COMMAND INTERPRETER
variables and expressions in the file name.
(FILE OPEN ERROR 556)
CAUSE
Syntax or logic error in the expressions or missing (undefined)
COMMANDINTERPRETER variables.
557
MESSAGE
The operating system is not in the UP state, yet a COMMAND
INTERPRETER variable or expression was found in the file name. This is
allowed only when MPE/iX has booted completely up.
(FILE OPEN ERROR 557)
558
MESSAGE
For KSAM files, the CREATE domain is allowed only when the Copy
Mode option is enabled. (FILE OPEN ERROR 558)
560
MESSAGE
The caller lacks sufficient privilege to specify the syntax
value provided. (FILE SYSTEM ERROR -560)
CAUSE
A privileged syntax option was specified but the
caller was not privileged.
ACTION
Acquire the necessary privileges, or specify a different
syntax.
561
MESSAGE
The value supplied to the file close privilege option is not
valid. (FILE SYSTEM ERROR -561)
CAUSE
A value outside the legal range of 0..3 was specified.
ACTION
Specify only legal privilege levels.
563
MESSAGE
An internal error has occurred, an invalid attempt has been
made to allocate a direct access device.
(FILE SYSTEM ERROR -563)
CAUSE
An error exists in the file system.
ACTION
File an SR.
568
MESSAGE
The inherit environment option is invalid.
(FILE SYSTEM ERROR -568)
CAUSE
The value is not in the legal range, or a bounds
violation occurred.
ACTION
Specify only legal values for the inherit environment
option.
581
MESSAGE
The link spool file option was specified without the link device
option being specified. (FILE SYSTEM ERROR -581)
CAUSE
The link spool file option and the link device option
must be specified together.
ACTION
Specify both of these options.
592
MESSAGE
The requested operation is not allowed on a read-only volume.
(FILE SYSTEM ERROR -592)
CAUSE
A write operation was requested for an object on
a read-only volume.
ACTION
Move the file to a read/write volume.
593
MESSAGE
The creation of this CM file cannot be made an atomic operation.
(FILE SYSTEM ERROR -593)
CAUSE
The FMAVT SIR could not be acquired.
ACTION
Retry the operation.
594
MESSAGE
CM file opens cannot be restored to normal operation.
(FILE SYSTEM ERROR -594)
CAUSE
The FMAVT SIR could not be released.
ACTION
Take a dump of the system and file an SR.
595
MESSAGE
Files of this file type cannot be created outside the MPE
namespace. (FILE SYSTEM ERROR -595)
CAUSE
An attempt was made to create a file outside the
MPE namespace that is not currently supported.
ACTION
Use an MPE namespace name to create this file.
596
MESSAGE
The specified file code is not valid in this context.
(FILE SYSTEM ERROR -596)
CAUSE
An attempt was made to assign a negative file code
to a file outside an MPE group.
ACTION
Use a positive file code, or create the file in a group.
597
MESSAGE
NEW Domain cannot be specified for named hierarchical file
system files.
CAUSE
Specifying NEW Domain for a named file or specifying TEMPORARY
Domain to open a file whose parent is a directory in the hierarchical
file system (HFS) is prohibited.
ACTION
When opening a file in the NEW Domain in a HFS directory, do not
specify a filename. Files in the TEMPORARY Domain are restricted
to classic MPE/iX groups.
598
MESSAGE
An invalid value was specified for the read format option.
(FILE SYSTEM ERROR -598)
CAUSE
The value of the read format option is not valid.
ACTION
Supply a valid value for the read format option.
599
MESSAGE
Both the file name and the file syntax must be specified with
the raw open option. (FILE SYSTEM ERROR -599)
CAUSE
One or both of the file name and name syntax options
were not specified with the raw open option.
ACTION
Supply both the file name and the name syntax options with
the raw open option.
600
MESSAGE
The procedure detected the end of the file, or no error
detected. (FSERR 0)
601
MESSAGE
The procedure detected an illegal DB register setting.
(FSERR 1)
602
MESSAGE
This is an illegal capability. (FSERR 2)
603
MESSAGE
The required parameter is missing. (FSERR 3)
604
MESSAGE
Disk free space allocation disabled on all disks in domain
(FSERR 604)
CAUSE
A CM error was detected.
ACTION
File an SR.
605
MESSAGE
DRT number > 511 (FSERR 605)
CAUSE
A CM error was detected.
ACTION
File an SR.
606
MESSAGE
Device has no available spare blocks. (FSERR 606)
CAUSE
A CM error was detected.
ACTION
File an SR.
607
MESSAGE
Unformatted or uninitialized media on device.
(FSERR 607)
CAUSE
A CM error was detected.
ACTION
File an SR.
608
MESSAGE
The procedure detected an illegal parameter value.
(FSERR 8)
609
MESSAGE
An invalid file was specified in FOPTIONS.
(FSERR 9)
610
MESSAGE
This is an invalid record size specification.
(FSERR 10)
611
MESSAGE
The procedure detected an invalid blocksize.
(FSERR 11)
612
MESSAGE
Record number out of range (FSERR 612)
CAUSE
A CM error was detected.
ACTION
File an SR.
613
MESSAGE
Can't open file multi-access, out of FMAVT entries
(FSERR 613)
CAUSE
A CM error was detected.
ACTION
File an SR.
615
MESSAGE
EXCEEDED THE MAXIMUM MESSAGE FILE OPENS FOR WRITE ACCESS
(FSERR 615)
CAUSE
A CM error was detected.
ACTION
File an SR.
616
MESSAGE
More than 255 opens of a file occurred.
(FSERR 616)
617
MESSAGE
A magnetic tape runaway occurred. (FSERR 617)
618
MESSAGE
The device powered up. (FSERR 618)
619
MESSAGE
The forms control was reset. (FSERR 619)
620
MESSAGE
This is an invalid operation. (FSERR 620)
621
MESSAGE
A data parity error occurred. (FSERR 621)
622
MESSAGE
A software time out occurred. (FSERR 622)
623
MESSAGE
The procedure detected the end of the tape.
(FSERR 623)
624
MESSAGE
The unit is not ready. (FSERR 624)
625
MESSAGE
There is no WRITE ring on the tape. (FSERR 625)
626
MESSAGE
A transmission error occurred. (FSERR 626)
627
MESSAGE
An I/O time out occurred. (FSERR 627)
628
MESSAGE
A timing error on data overrun occurred.
(FSERR 628)
629
MESSAGE
An SIO failure occurred. (FSERR 629)
630
MESSAGE
A unit failure occurred. (FSERR 630)
631
MESSAGE
The procedure detected the end of the line.
(FSERR 631)
632
MESSAGE
A software abort occurred. (FSERR 632)
633
MESSAGE
Data was lost. (FSERR 633)
634
MESSAGE
The unit is not on line. (FSERR 634)
635
MESSAGE
The data-set is not ready. (FSERR 635)
636
MESSAGE
This is an invalid disk address. (FSERR 636)
637
MESSAGE
This is an invalid memory address. (FSERR 637)
638
MESSAGE
A tape parity error occurred. (FSERR 638)
639
MESSAGE
Recovered tape error occurred. (FSERR 639)
640
MESSAGE
The operation is inconsistent with access type.
(FILE SYSTEM ERROR 640)
641
MESSAGE
The operation is inconsistent with record type.
(FILE SYSTEM ERROR 641)
642
MESSAGE
The operation is inconsistent with device type.
(FILE SYSTEM ERROR 642)
643
MESSAGE
WRITE exceeds record size. (FILE SYSTEM ERROR 643)
644
MESSAGE
Update at record zero. (FILE SYSTEM ERROR 644)
645
MESSAGE
Privileged file violation. (FILE SYSTEM ERROR 645)
646
MESSAGE
Out of disk space. (FILE SYSTEM ERROR 646)
647
MESSAGE
An I/O error on file label occurred.
(FILE SYSTEM ERROR 647)
648
MESSAGE
An invalid operation due to multiple file access.
(FILE SYSTEM ERROR 648)
649
MESSAGE
This in an unimplemented function.
(FILE SYSTEM ERROR 649)
650
MESSAGE
This is a nonexistent account.
(FILE SYSTEM ERROR 650)
651
MESSAGE
This is a nonexistent group.
(FILE SYSTEM ERROR 651)
652
MESSAGE
This is a nonexistent permanent file.
(FILE SYSTEM ERROR 652)
653
MESSAGE
This is a nonexistent temporary file.
(FILE SYSTEM ERROR 653)
654
MESSAGE
Invalid file reference.
(FILE SYSTEM ERROR 654)
655
MESSAGE
Device unavailable.
(FILE SYSTEM ERROR 655)
656
MESSAGE
Invalid device specification.
(FILE SYSTEM ERROR 656)
657
MESSAGE
Out of virtual memory. (FILE SYSTEM ERROR 657)
658
MESSAGE
No passed file. (FILE SYSTEM ERROR 658)
659
MESSAGE
Standard label violation. (FILE SYSTEM ERROR 659)
660
MESSAGE
Global RIN unavailable. (FILE SYSTEM ERROR 660)
661
MESSAGE
Out of group disk space. (FILE SYSTEM ERROR 661)
662
MESSAGE
Out of account disk space. (FILE SYSTEM ERROR 662)
663
MESSAGE
User lacks non-sharable device capability.
(FILE SYSTEM ERROR 663)
664
MESSAGE
User lacks multi-RIN capability.
(FILE SYSTEM ERROR 664)
665
MESSAGE
Punch hopper is empty. (FILE SYSTEM ERROR 665)
666
MESSAGE
Plotter limit switch reached.
(FILE SYSTEM ERROR 666)
667
MESSAGE
Paper tape error. (FILE SYSTEM ERROR 667)
668
MESSAGE
Insufficient system resources.
(FILE SYSTEM ERROR 668)
669
MESSAGE
An I/O error occurred. (FILE SYSTEM ERROR 669)
670
MESSAGE
An I/O error occurred while printing header/trailer.
(FILE SYSTEM ERROR 670)
671
MESSAGE
TOO MANY FILES OPEN (FSERR 71)
CAUSE
A CM error was detected.
ACTION
File an SR.
672
MESSAGE
INVALID FILE NUMBER (FSERR 72)
CAUSE
A CM error was detected.
ACTION
File an SR.
673
MESSAGE
BOUNDS VIOLATION (FSERR 73)
CAUSE
A CM error was detected.
ACTION
File an SR.
674
MESSAGE
No room left in stack segment for another file entry
(FSERR 74)
CAUSE
A CM error was detected.
ACTION
File an SR.
677
MESSAGE
NO-WAIT I/O PENDING (FSERR 77)
CAUSE
A CM error was detected.
ACTION
File an SR.
678
MESSAGE
NO NO-WAIT I/O PENDING FOR ANY FILE (FSERR 78)
CAUSE
A CM error was detected.
ACTION
File an SR.
679
MESSAGE
NO NO-WAIT I/O PENDING FOR SPECIAL FILE (FSERR 79)
CAUSE
A CM error was detected.
ACTION
File an SR.
680
MESSAGE
SPOOFLE SIZE EXCEEDS CONFIGURATION (FSERR 80)
CAUSE
A CM error was detected.
ACTION
File an SR.
681
MESSAGE
NO "SPOOL" CLASS IN SYSTEM (FSERR 81)
CAUSE
A CM error was detected.
ACTION
File an SR.
682
MESSAGE
INSUFFICIENT SPACE FOR SPOOFLE (FSERR 82)
CAUSE
A CM error was detected.
ACTION
File an SR.
683
MESSAGE
I/O ERROR ON SPOOFLE (FSERR 83)
CAUSE
A CM error was detected.
ACTION
File an SR.
684
MESSAGE
DEVICE UNAVAILABLE FOR SPOOFLE (FSERR 84)
CAUSE
A CM error was detected.
ACTION
File an SR.
685
MESSAGE
OPERATION INCONSISTENT WITH SPOOLING (FSERR 85)
CAUSE
A CM error was detected.
ACTION
File an SR.
686
MESSAGE
Spooling internal error (FSERR 86)
CAUSE
A CM error was detected.
ACTION
File an SR.
687
MESSAGE
BAD SPOOFLE BLOCK (FSERR 87)
CAUSE
A CM error was detected.
ACTION
File an SR.
688
MESSAGE
NONEXISTENT SPOOLFILE (FSERR 88)
CAUSE
A CM error was detected.
ACTION
File an SR.
689
MESSAGE
POWER FAILURE (FSERR 89)
CAUSE
A CM error was detected.
ACTION
File an SR.
690
MESSAGE
EXCLUSIVE VIOLATION: FILE BEING ACCESSED
(FSERR 90)
An operation was attempted on a file type that does not support
that operation. (FILE SYSTEM ERROR -939)
CAUSE
The file is probably a CM file, or some other file
with some type of implicit restrictions.
ACTION
Do not attempt this operation with this file.
940
MESSAGE
The caller lacks sufficient privilege to attempt this operation.
(FILE SYSTEM ERROR -940)
CAUSE
The caller is not privileged enough to perform this
function.
ACTION
Acquire a sufficient privilege level.
941
MESSAGE
The read operation was completed due to the break key being
pressed. (FILE SYSTEM ERROR -941)
CAUSE
The user pressed the break key.
ACTION
Retry the read operation.
942
MESSAGE
A soft end of file condition was encountered.
(FILE SYSTEM ERROR -942)
CAUSE
The user typed in a colon (:) as the first character
on $STDIN, or :EOD as the first characters on $STDINX.
ACTION
Reopen the input file if you wish to continue reading.
943
MESSAGE
The IOWAIT type manager layer has requested the intrinsic layer
to retry the IOWAIT. (FILE SYSTEM ERROR -943)
CAUSE
The type manager layer cannot process the I/O that
was found at this time.
ACTION
No action is necessary.
944
MESSAGE
The terminal end of line character has been detected.
(FILE SYSTEM ERROR -944)
CAUSE
The end of line character was typed into the terminal.
ACTION
No action is necessary.
945
MESSAGE
Type manager; ABORT_IOX failed.
946
MESSAGE
Type manager; CONVERT_DST failed.
947
MESSAGE
Type manager; ATTACH_ID failed.
948
MESSAGE
Type manager; The parameter passed was not valid.
949
MESSAGE
The option selected is not valid in this context.
950
MESSAGE
Type manager, a software error has occurred within terminal
I/O software.
951
MESSAGE
Type manager, an offline condition has occurred while doing a
FAST WRITE to a terminal.
952
MESSAGE
Type manager; a FAST WRITE to a terminal failed.
953
MESSAGE
Type manager; JSINFO failed.
954
MESSAGE
Type manager; a DATA MEMORY PROTECT TRAP occurred.
955
MESSAGE
Type manager; a CONDITIONAL TRAP occurred.
956
MESSAGE
Type manager; an OVERFLOW TRAP occurred.
957
MESSAGE
Type manager; the file is busy being stored.
958
MESSAGE
Type manager; this is an access violation.
959
MESSAGE
Type manager; this is a multiple access error.
960
MESSAGE
Type manager-directory purge; the account does not
exist.
961
MESSAGE
Type manager-directory purge; the group does not
exist.
962
MESSAGE
Type manager-directory insert; the account does not
exist.
963
MESSAGE
Type manager-directory insert; the group does not
exist.
964
MESSAGE
Type manager; invalid carriage control.
965
MESSAGE
Type manager; FILE ACCESS RIGHTS TABLE DELETE
failed.
966
MESSAGE
Type manager; user attempted to save temporary file to
existing permanent file.
967
MESSAGE
Type manager directory insert; group does not have SAVE FILE
capability.
968
MESSAGE
Type manager directory insert; account does not have SAVE FILE
capability.
969
MESSAGE
Type manager-directory find; file was not found in the temporary
directory.
970
MESSAGE
Type manager-directory purge; the file was not
found.
971
MESSAGE
Type manager-directory purge; file was not found in the
temporary directory.
972
MESSAGE
Type manager-directory replace; file was not found in the
temporary directory.
973
MESSAGE
Type manager-directory find; file was not found in the temporary
directory.
974
MESSAGE
Type manager-directory purge; the group was not
found.
975
MESSAGE
Type manager directory purge; the temporary file group was not
found.
976
MESSAGE
Type manager-directory replace; the temporary file group was not
found.
977
MESSAGE
Type manager-directory find; the temporary file account was not
found.
978
MESSAGE
Type manager-directory purge; file account was not
found.
979
MESSAGE
Type manager-directory purge; the temporary file account was not
found.
980
MESSAGE
Type manager-directory replace; the temporary file account was
not found.
981
MESSAGE
Type manager-directory insert; there is no group directory disk
space available.
982
MESSAGE
Type manager-directory insert; there is no group disk space
available for temporary file.
983
MESSAGE
Type manager-directory replace; there is no group disk space
available for the temporary file.
984
MESSAGE
Type manager-directory insert; there is no account disk space
available.
985
MESSAGE
Type manager-directory insert; there is no account disk space
available.
986
MESSAGE
Type manager directory replace; there is no account disk space
available.
987
MESSAGE
Type manager-directory insert; this is a duplicate
name.
988
MESSAGE
Type manager-directory insert; this is a temporary file
duplicate name.
989
MESSAGE
Type manager-directory replace; this is a temporary file
duplicate name.
990
MESSAGE
Type manager; a directory I/O error occurred.
991
MESSAGE
Type manager; the directory switch failed.
992
MESSAGE
An error occurred while moving data to or from the user buffer.
(FILE SYSTEM ERROR -992)
CAUSE
A trap occurred while executing a MOVE_FAST.
ACTION
Close the file, reopen and retry the operation.
993
MESSAGE
An error occurred while moving data between two potentially
overlapping areas. (FILE SYSTEM ERROR -993)
CAUSE
A trap occurred while executing a MOVE_L_TO_R.
ACTION
Close the file, reopen and retry the operation.
994
MESSAGE
Type manager; the storage management READ failed.
995
MESSAGE
Type manager; the storage management START READ
failed.
996
MESSAGE
Type manager; the storage management WRITE failed.
997
MESSAGE
Type manager; the storage management START WRITE
failed.
998
MESSAGE
Type manager; the storage management FINISH WRITE
failed.
999
MESSAGE
Type manager; the storage management control
failed.
1000
MESSAGE
Type manager; the storage management close failed.
1001
MESSAGE
Type manager; the record size was exceeded.
1002
MESSAGE
Type manager; the file limit was exceeded.
1003
MESSAGE
Type manager; this is an invalid request.
1004
MESSAGE
Type manager; out of disk space.
1005
MESSAGE
Type Manager; end of user labels.
1006
MESSAGE
Type manager; the user label limit has been
exceeded.
1007
MESSAGE
Type manager; the GDPD reference count is negative.
1008
MESSAGE
Type manager; system is out of GDPDs.
1009
MESSAGE
Type manager; unable to build the GDPD table.
1010
MESSAGE
Type manager; unable to unlink the GDPD.
1011
MESSAGE
Type manager; unable to unlink the PLFD.
1012
MESSAGE
Type manager; unable to deallocate the GDPD.
1013
MESSAGE
Type manager; there is no nowait I/O for this specific
file.
1014
MESSAGE
Type manager; nowait I/O is pending.
1015
MESSAGE
Type manager; the procedure attempted to save this file with
no name.
1016
MESSAGE
Type manager; the control block semaphore initialization
failed.
1017
MESSAGE
Type manager; the procedure was unable to get the
file size.
1018
MESSAGE
Type manager; this is an unimplemented function.
1019
MESSAGE
Type manager; a bad variable record block was
detected.
1020
MESSAGE
Type manager; device type is not valid.
1021
MESSAGE
Type manager; FUPDATE sequence error occurred.
1022
MESSAGE
Type manager; the block size was exceeded.
1023
MESSAGE
Type manager; the end-of-file has been detected.
1024
MESSAGE
An invalid spooling operation was requested.
(FILE SYSTEM ERROR -1024)
CAUSE
The user specified an invalid spooling operation.
ACTION
Do not request this operation.
1025
MESSAGE
The type manager layer was not able to release all resources
that were acquired. (FILE SYSTEM ERROR -1025)
CAUSE
One or more resources could not be returned to the system.
ACTION
File an SR.
1027
MESSAGE
An error occurred while trying to access a file label extension.
(FILE SYSTEM ERROR -1027)
CAUSE
An error occurred on a call to a label management procedure.
ACTION
File an SR.
1028
MESSAGE
An error occurred while trying to access the spool file manager.
(FILE SYSTEM ERROR -1028)
CAUSE
A call to one of the spool file manager service
procedures failed.
ACTION
File an SR.
1029
MESSAGE
The write operation caused the directory disk space limits to
be exceeded. (FILE SYSTEM ERROR -1029)
CAUSE
An extent fault occurred which would require allocation
of more disk space than is allowed.
ACTION
Purge unwanted files, or increase the accounting limits.
1030
MESSAGE
An attempt was made to remove a file on a read-only volume.
(FILE SYSTEM ERROR -1030)
CAUSE
A purge or unlink was done against a file on a read-only
volume.
ACTION
Do not attempt a purge or an unlink on this file.
1031
MESSAGE
An attempt was made to create a file in an object that is not
a directory. (FILE SYSTEM ERROR -1031)
CAUSE
An invalid path specification was provided by the caller.
ACTION
Correct the invalid path specification.
1032
MESSAGE
An attempt was made to purge a file from an object that is not
a directory. (FILE SYSTEM ERROR -1032)
CAUSE
An invalid path specification was provided by the caller.
ACTION
Correct the invalid path specification.
1033
MESSAGE
An invalid directory operation was requested.
(FILE SYSTEM ERROR -1033)
CAUSE
A directory service procedure reported an error.
ACTION
Do not attempt this operation.
1034
MESSAGE
The reserved file for the Current Working Directory has become
corrupted. (FILE SYSTEM ERROR -1034)
CAUSE
The file system could not get a pointer to the CWD reserved
file.
ACTION
Abort and restart the process.
1035
MESSAGE
Directory services encountered a security violation while trying
to traverse the specified path. (FILE SYSTEM ERROR -1035)
CAUSE
The user lacks access to or through one of the directory
nodes.
ACTION
Have the system manager grant the user access to
the offending directory.
1036
MESSAGE
The caller lacks traverse access to one of the HFS path
directory components. (FILE SYSTEM ERROR -1036)
CAUSE
The user is not granted TD access to one or more
of the components in the path.
ACTION
Have the system adminstrator grant TD access to this user.
1037
MESSAGE
The caller lacks the ability to delete entries from the target
directory. (FILE SYSTEM ERROR -1037)'
CAUSE
The user does not have DD access to the parent directory.
ACTION
Have the system adminstrator grant DD access to this user.
1038
MESSAGE
The caller lacks the ability to create entries in the target
directory. (FILE SYSTEM ERROR -1038)
CAUSE
The user lacks CD access to the parent directory
or does not have SF capability.
ACTION
Have the system administrator grant sufficient access.
1039
MESSAGE
The volume set indicated by the directory mount record is not
available. (FILE SYSTEM ERROR -1039)
CAUSE
The volume set is not mounted or the disk drive
is not turned on.
ACTION
Mount the necessary volumes and make sure the drive(s) are
functioning.
1040
MESSAGE
Directory services encountered an error while trying to update
the file label. (FILE SYSTEM ERROR -1040)
CAUSE
An error occurred during a file label update.
ACTION
File an SR.
1041
MESSAGE
An empty path was provided to the directory services.
(FILE SYSTEM ERROR -1041)
CAUSE
The caller provided an empty path.
ACTION
Provide a non-empty path.
1042
MESSAGE
Directory services detected that a component of the path has a
name length which exceeds the maximum for that directory.
(FILE SYSTEM ERROR -1042)
CAUSE
A name exceeds the directory specific name length limit.
ACTION
Provide a shorter name.
1043
MESSAGE
An attempt was made to insert a name greater than 16 characters
into the root, an account, or a group.
(FILE SYSTEM ERROR -1043)
CAUSE
The caller specified a name greater than 16 characters
in an MPE directory component.
ACTION
Provide a name less than or equal to 16 characters.
1044
MESSAGE
An illegal attempt was made to purge a file that was opened by
UFID. (FILE SYSTEM ERROR -1044)
CAUSE
The caller opened the file by UFID, then did an
FCLOSE purge.
ACTION
To purge this file, it must be opened with a name.
1046
MESSAGE
The IOWAIT type manager layer requests the intrinsic layer to
requeue the present I/O and retry the IOWAIT.
(FILE SYSTEM ERROR -1046)
CAUSE
The type manager is unable to process the I/O at this time.
ACTION
No action is necessary.
1047
MESSAGE
Incompatible version of the file.
CAUSE
The FOPEN/HPFOPEN request has been denied because the version of the
file is not compatible with the version of the operating
system.
ACTION
On a 5.0 or later system, copy the KSAM/XL file to another file
specifying DEFBLK to create a compatible version of the file.
Then, copy the newly created file to the pre-5.0 system
1050
MESSAGE
TM_REC_TOO_SHORT: The record specified for writing is too
short.
CAUSE
The record does not have all the keys present.
ACTION
Specify a larger record with all the keys present.
1051
MESSAGE
TM_NONSEQ_WRITE: This error indicates that the current FWRITE
had a primary key which was not in sequential order when compared with
the previous FWRITE.
CAUSE
A write was attempted with the primary key not in sequential
order when compared with the previous write.
ACTION
Change the order in which the records are written
to the file so that the primary key is always in sequential order. Or
rebuild the file and specify the SEQ flag to be false.
1052
MESSAGE
TM_DUP_KEY_DISALLOWED: An attempt was made to insert a duplicate
key to an index which disallows duplicate keys.
CAUSE
One of the indexes in the file has the DUP flag set to false;
however, an attempt was made to insert a key which already
existed in that index.
ACTION
Modify the record so that the key is not a duplicate of a previous
record; or create the file with the index DUP flag set to TRUE.
1054
MESSAGE
TM_KSM_CBLOCK_FAILED: An error was detected while scanning the
B TREE where the information relating to the user specified keys
is kept.
CAUSE
This error is not currently used.
ACTION
Nothing.
1055
MESSAGE
TM_KEY_NOT_FOUND: The user specified key cannot be found in the
index area of the KSAM XL file.
CAUSE
The user may have specified a key that does not
exist in the KSAM XL file.
ACTION
Use a valid key specification.
1056
MESSAGE
TM_PRIM_KEY_CHANGED: An FUPDATE call attempted to modify
the primary key value.
CAUSE
The file was opened for sequential processing and
the primary key was changed while doing an FUPDATE.
ACTION
Check the record to be written to make sure the primary key in not
changed. Compare the buffer that was FREAD from
the file to the buffer that you are passing to FUPDATE.
1057
MESSAGE
TM_KEY_SEARCH_ERROR: An error was detected while scanning the
B TREE where the information relating to the user specified keys is
kept.
CAUSE
The internal B TREE structure is corrupted.
ACTION
Close the KSAM XL file, store it to tape, and contact
your HP Support Representative.
1058
MESSAGE
TM_XM_START_SYS_TRANS_FAILED: A system transaction could not
be started.
CAUSE
This is probably due to an MPE/iX operating system defect.
ACTION
Take a memory dump and contact your HP Support
Representative.
1059
MESSAGE
TM_XM_END_SYS_TRANS_FAILED: A system transaction could not
be terminated.
CAUSE
This is probably due to an MPE/iX operating system defect.
ACTION
Take a memory dump and contact your HP Support
Representative.
1060
MESSAGE
TM_RECORD_DELETED: The particular record in question was
deleted.
CAUSE
An attempt was made to read or update or delete
a record which was deleted.
ACTION
When positioning the data pointer before the read, make sure the
pointer is not positioned to a deleted record.
1061
MESSAGE
TM_BTREE_INTERNAL_ERROR: An error was detected while scanning
the B TREE where the information relating to the user specified keys
is kept.
CAUSE
The internal B TREE sturucture is corrupted.
ACTION
The KSAM XL file is corrupted. Close the KSAM file,
store it to tape, and contact your HP Support Representative.
1062
MESSAGE
TM_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
The B TREE is probably very sparsely filled.
ACTION
FCOPY the KSAM XL file to another KSAM XL file. This should make
more efficient use of the index blocks. If that fails,
build the KSAM XL file with a larger file limit.
1063
MESSAGE
TM_INVALID_KEY_SPECIFIED: The key specification provided by
the user is not a valid one.
CAUSE
The key specified in a procedure such as FREADBYKEY does
not match the one specified in building the file.
ACTION
Check the key specified in the procedure call to FREADBYKEY
or FFINDBYKEY.
1065
MESSAGE
TM_FFIND_FAILED: An FFINDN failed based on the relative record
number specified.
CAUSE
The relative record number specified was greater
than the largest relative record number in the B TREE.
ACTION
Check the second parameter in the call to FFINDN specifying
the relative record number.
1066
MESSAGE
TM_DUP_KEY_FOUND: Duplicate keys were found for the key
currently being specified.
CAUSE
The detection of the existence of duplicate keys is specificaly
performed for COBOL in FREAD and FREADBYKEY intrinsics
called by COBOL.
ACTION
This status will be returned to COBOL programs only.
1067
MESSAGE
TM_KSM_SPACE_FAILED: An error ocurred while doing
FSPACE.
CAUSE
The displacement specified in the FSPACE parameter
is too large or too small.
ACTION
Check the displacement specified in the FSPACE parameter.
1068
MESSAGE
TM_INVALID_INDEX_RRN: An error was detected in a
B TREE entry for location of a data record.
CAUSE
The internal B TREE sturucture is corrupted.
ACTION
Close this file and build a new file. Use FCOPY
specifying KEY=0 to rebuild a new KSAM XL file.
1069
MESSAGE
TM_INVALID_DATA_PTR_CALCULATED: The position of the data pointer
computed is before the first data record or after the end
of file.
CAUSE
The KSAM XL file is corrupted in the data pointer
of the index area.
ACTION
Close the KSAM file, store it to tape, and contact
your HP Support Representative.
1070
MESSAGE
TM_INVALID_REC_NUM: An invalid recnum was specified in the
call to a pointer positioning procedure such as FPOINT,
or FREADDIR.
CAUSE
A relative record number specified is not valid,
either before the first record or beyond the last record.
ACTION
Specify a valid relative record number.
1071
MESSAGE
TM_DPAGE_FIND_FAILED: An error occurred while scanning for a
data page with a vacant slot in it.
CAUSE
All the data pages are used.
ACTION
Close the file, build a new KSAM XL file with similar
characteristics and FREADC from the old file and FWRITE into the
new file.
1072
MESSAGE
TM_KSM_NO_REC: The KSAM XL file is empty, no records in the
file.
CAUSE
An attempt was made to read or modify a KSAM XL
file which has no active records in it.
ACTION
Check the content of the file before accesssing it.
1073
MESSAGE
TM_KSM_XM_ATTACH_FAILED: An error was detected while trying to
attach the file to the XM log.
CAUSE
An internal MPE/iX error occurred.
ACTION
Take a memory dump and call your HP Support Representative.
1074
MESSAGE
TM_KSM_INVALID_DATA_PTR: The logical data pointer is currently
incorrectly positioned.
CAUSE
The logical data pointer is currently position before
the start of the data area or after the end of file.
ACTION
Do an FCLOSE followed by an FOPEN or do FPOINT to reposition
the data pointer.
1075
MESSAGE
TM_KSM_INVALID_CHILD_PTR: An invalid child pointer was detected
in the index part of the file.
CAUSE
The internal B TREE structure is corrupted.
ACTION
Close the KSAM file, store it to tape, and call
your HP Support Representative.
1076
MESSAGE
TM_KSM_CORRUPTED_FILE: During a previous KSAM operation, the
KSAM file was discovered to be corrupt so that FWRITEs, FREMOVEs, and
FUPDATEs are disallowed.
CAUSE
The internal B TREE structure is corrupted.
ACTION
Close the KSAM file, store it to tape, and call
your HP Support Representative.
1077
MESSAGE
The file system was unable to start a user transaction
undertransaction management. (FILE SYSTEM ERROR -1077)
CAUSE
A call to transaction management failed.
ACTION
Make sure the file is attached to XM, otherwise file an SR.
1078
MESSAGE
The file system was unable to end a user transaction under
transaction management. (FILE SYSTEM ERROR -1078)
CAUSE
A call to transaction management failed.
ACTION
File an SR.
1079
MESSAGE
An invalid offset value was provided for a KSAM/XL file.
(FILE SYSTEM ERROR -1079)
CAUSE
The user supplied an invalid file offset.
ACTION
Supply a valid offset value to the intrinsic.
1080
MESSAGE
The KSAM/XL subsystem detected an unknown internal error.
(FILE SYSTEM ERROR -1080)
CAUSE
An internal error was detected.
ACTION
File an SR.
1110
MESSAGE
The file system was unable to create the File I/O State Table.
(FILE SYSTEM ERROR -1110)
CAUSE
The FIOST table could not be created.
ACTION
File an SR.
1111
MESSAGE
The file system was unable to initialize the File I/O State
Table. (FILE SYSTEM ERROR 1111)
CAUSE
The FIOST table could not be initialized.
ACTION
File an SR.
1112
MESSAGE
The file system was unable to create the File I/O State
Semaphore Table. (FILE SYSTEM ERROR -1112)
CAUSE
An error occurred while creating the FIOST Semaphore Table.
ACTION
File an SR.
1113
MESSAGE
The file system was unable to initialize the File I/O State
Semaphore Table. (FILE SYSTEM ERROR -1113)
CAUSE
An error occurred while initializing the FIOST Semaphore
Table.
ACTION
File an SR.
CIERR 1500 - 7199
1500
MESSAGE
An unexpected High-level IO error was encountered while
executing a tape IO request.
CAUSE
Either the IO request was invalid, or the device
is not ready/accessible.
ACTION
Make sure the requested IO operation is a valid
one, and the devcie is accessible for the process.
1501
MESSAGE
An unexpected Low-level IO error was encountered while
executing the tape IO request.
CAUSE
The device encountered an error during IO execution.
It could be a medium, device or hardware error, or a driver internal
error.
ACTION
Make sure the medium and device are in a proper
state. For example, check for device power, tape positioning, medium
misload ... etc... If nothing wrong with the device and medium,
then you should contact Hewlett-Packard for support.
1502
MESSAGE
A tape IO request failed because a write access was
denied.
CAUSE
Either the medium is protected from write access,
or the process does not have write access to the device.
ACTION
Make sure the process has write access to the device
and the medium is not write protected.
1503
MESSAGE
The device is not ready for executing this tape IO
request.
CAUSE
Either the device is not online, or the device is
not in a state ready to execute this IO request.
ACTION
Make sure the device is on line and the medium is
readily positioned.
1504
MESSAGE
A tape IO request failed because the attempted device operation
is not supported by the operating system.
CAUSE
Either the requested device operation is not valid for this device,
or a file system internal error was encountered.
ACTION
Make sure the requested IO operation is valid for
this device. If so, contact Hewlett-Packard for support.
1505
MESSAGE
An attempt to backspace failed because the medium is already
positioned at its beginning.
CAUSE
The device was positioning at the beginning of the medium,
an attempt to backspace the medium could not be performed.
ACTION
Do not try to backspace the medium when it is positioned at
its beginning.
1506
MESSAGE
A tape IO operation failed because the end of the medium was
encountered.
CAUSE
An attempt was made to execute a device operation beyond
the end of the medium.
ACTION
Do not try to access the medium beyond the end of
tape mark. Rewind, mount another tape and try again.
1507
MESSAGE
A tape IO request failed because the device is not available
for access.
CAUSE
The specified device is not a valid one, or the
device is disabled or unconfigured.
ACTION
Check for the accessibility of the device being accessed.
1508
MESSAGE
An internal error occured while processing a tape IO
request.
CAUSE
An unexpected trap occur due to a file system internal
error.
ACTION
Contact Hewlett-Packard for support.
1509
MESSAGE
A bounds violation error was detected while processing a tape
IO request.
CAUSE
The address/parameter passed was inaccessible to the caller.
ACTION
Pass only addresses in accessible spaces.
5000
MESSAGE
A keyword < 0 or > VINFO_MAX_KEYWORD, or = 1 was
specified; such keyword numbers are not currently
supported.
5001
MESSAGE
The keyvalue for the output buffer type is outside of the
allowable range of VINFO_OUTPUT_MIN_PARM to
VINFO_OUTPUT_MAX_PARM.
5002
MESSAGE
The output buffer keyvalue pointed to an invalid range of
memory for the user, or wasn't at least 4 bytes large.
5003
MESSAGE
The keyvalue for the volume range is outside of the allowed
range of VINFO_RANGE_MIN_PARM to VINFO_RANGE_MAX_PARM.
5004
MESSAGE
The keyvalue parameter pointed to an invalid section of
memory.
5005
MESSAGE
The volume name contains invalid characters, or the delimiter
wasn't found within the allowed number of characters.
5006
MESSAGE
The volume class name contained some invalid characters, or
the delimiter was not found within the allowed number of
characters.
5007
MESSAGE
The volume set name contained some invalid characters, or the
delimiter was not found within the allowed number of
characters.
5008
MESSAGE
The specified generation index number was outside of the
range -1..32767.
5009
MESSAGE
No volumes were found in the specified range with the requested
volume set, class, volume names, and the generation index.
5010
MESSAGE
A keyword was specified two or more times in the intrinsic call.
The latest keyword's keyvalue was used, and the previous keyvalues were
ignored.
5011
MESSAGE
The keyword VINFO_OPTION_END_OF_LIST (0) was specified with
some keywords following it in the intrinsic call; the extra parameters
were ignored.
5012
MESSAGE
Neither the output buffer, nor the number of volumes in range
output PARM were specified in the intrinsic call.
5013
MESSAGE
The user tried to access a volume set other than his logon
group's home volume set. Such access is allowed only to those with
SM, OP, or CV capability.
5014
MESSAGE
A volume range of one volume class was specified, but the volume
class name was not specified.
5015
MESSAGE
A particular volume within a given volume class was desired,
and the range was set to one volume. The volume class name was given,
but the particular volume name was not given.
5016
MESSAGE
The user's output buffer was too small to hold all of the
requested data. If the number of volumes in range parameter was
specified, then the number of volumes that were actually accessed
are negative.
5017
MESSAGE
An error occurred during an I/O in some layer under Directory
Services during a DIRECFIND.
5018
MESSAGE
A failure occurred during a switch between CM and NM, or vice
versa. This failure occurred somewhere within Directory
Services.
5019
MESSAGE
Either no GUFD/PLFD was found for the user's logon account
directory, or the logon group's group entry was not found in the
account directory.
5020
MESSAGE
This error should be impossible to return. If it is returned,
then some unexpected error was returned in a DIRECFIND. The exact
MPE/iX error number may be found on the error stack.
5021
MESSAGE
The volume class name was specified as an output parameter when
volume searching was determined to be by volume sets; not by volume
classes.
5022
MESSAGE
The status parameter was pointing to an invalid section of
memory.
5023
MESSAGE
The volume range and volume names specification conflict. Some
of the VNAMES were not needed compared to the range; therefore, the
extra names were ignored.
5024
MESSAGE
The KEYVAlue parameter used to specify the desired units was
outside of the range VINFO_UNITS_MIN_PARM to
VINFO_UNITS_MAX_PARM.
5100
MESSAGE
HPVLMINFO is reserving error numbers 5000 to 5100.
5101
MESSAGE
The PROCESS LOCAL FILE DESCRIPTOR TABLE is full.
5102
MESSAGE
The file number does not reside in the PLFD TABLE.
5103
MESSAGE
The file number specified is not within the range of possible
open files.
6000
MESSAGE
Storage Management SIO is not ready.
(FILE SYSTEM ERROR -6000)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6001
MESSAGE
Storage Management SIO undefined function.
(FILE SYSTEM ERROR -6001)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6002
MESSAGE
Storage Management SIO other function.
(FILE SYSTEM ERROR -6002)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6003
MESSAGE
Storage Management SIO count is too big.
(FILE SYSTEM ERROR -6003)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6004
MESSAGE
Storage Management SIO count is insufficient.
(FILE SYSTEM ERROR -6004)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6008
MESSAGE
Storage Management SIO checksum error occurred.
(FILE SYSTEM ERROR -6008)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6009
MESSAGE
Storage Management SIO invalid form.
(FILE SYSTEM ERROR -6009)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6010
MESSAGE
Storage Management SIO parity error.
(FILE SYSTEM ERROR -6010)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6011
MESSAGE
Storage Managment SIO bad access.
(FILE SYSTEM ERROR -6011)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6012
MESSAGE
Storage Managment SIO bad item.
(FILE SYSTEM ERROR -6012)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6014
MESSAGE
Storage Managment SIO unit is off.
(FILE SYSTEM ERROR -6014)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6015
MESSAGE
Storage Managment SIO deleted record.
(FILE SYSTEM ERROR -6015
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6016
MESSAGE
Storage Managment SIO no spare available.
(FILE SYSTEM ERROR -6016)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6017
MESSAGE
Storage Managment SIO blank media.
(FILE SYSTEM ERROR -6017)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6018
MESSAGE
Storage Managment SIO paper tape error.
(FILE SYSTEM ERROR -6018)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6019
MESSAGE
Storage Managment SIO system error.
(FILE SYSTEM ERROR -6019)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6020
MESSAGE
Storage Managment SIO tape error.
(FILE SYSTEM ERROR -6020)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6021
MESSAGE
Storage Managment SIO invalid disk address.
(FILE SYSTEM ERROR -6021)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6023
MESSAGE
Storage Managment SIO start I/O failure.
(FILE SYSTEM ERROR -6023)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6024
MESSAGE
Storage Managment SIO timer error.
(FILE SYSTEM ERROR -6024)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6027
MESSAGE
Storage Managment SIO vertical form control reset.
(FILE SYSTEM ERROR -6027)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6028
MESSAGE
Storage Managment SIO beginning of tape.
(FILE SYSTEM ERROR -6028)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6030
MESSAGE
Storage Managment SIO broken read.
(FILE SYSTEM ERROR -6030)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6031
MESSAGE
Storage Managment SIO timer overflow.
(FILE SYSTEM ERROR -6031)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6032
MESSAGE
Storage Managment SIO bad escape.
(FILE SYSTEM ERROR -6032)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6033
MESSAGE
Storage Managment SIO plimit.
(FILE SYSTEM ERROR -6033)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6034
MESSAGE
Storage Managment SIO tape runaway.
(FILE SYSTEM ERROR -6034)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6038
MESSAGE
Storage Managment SIO stime.
(FILE SYSTEM ERROR -6038)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6040
MESSAGE
Storage Managment SIO end of file.
(FILE SYSTEM ERROR -6040)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6041
MESSAGE
Storage Managment SIO end of tape.
(FILE SYSTEM ERROR -6041)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6042
MESSAGE
Storage Managment SIO tape error recovery.
(FILE SYSTEM ERROR -6042)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6043
MESSAGE
Storage Managment SIO end of line.
(FILE SYSTEM ERROR -6043)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6044
MESSAGE
Storage Managment SIO invalid operation.
(FILE SYSTEM ERROR -6044)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6100
MESSAGE
Terminal Storage Management read failed.
(FILE SYSTEM ERROR -6100)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6101
MESSAGE
Terminal Storage Management write failed.
(FILE SYSTEM ERROR -6101)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6102
MESSAGE
Terminal Storage Management start read failed.
(FILE SYSTEM ERROR -6102)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6103
MESSAGE
Terminal Storage Management start write failed.
(FILE SYSTEM ERROR -6103)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6104
MESSAGE
Terminal Storage Management control function failed.
(FILE SYSTEM ERROR -6104)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6105
MESSAGE
Terminal Storage Management broken read encountered.
(FILE SYSTEM ERROR -6105)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6200
MESSAGE
Storage Management Native Language I/O dependent error.
(FILE SYSTEM ERROR -6200)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6201
MESSAGE
Storage Management Native Language I/O conversion error.
(FILE SYSTEM ERROR -6201)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6202
MESSAGE
Storage Management Native Language I/O MEA error.
(FILE SYSTEM ERROR -6202)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6203
MESSAGE
Storage Management Native Language I/O judge error.
(FILE SYSTEM ERROR -6203)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
6204
MESSAGE
Storage Management Native Language I/O implementation error.
(FILE SYSTEM ERROR -6204)
CAUSE
A storage management error was detected.
ACTION
Ensure the device is operating properly.
7001
MESSAGE
The generic name translation service could not get access to
CWD information. (FILE SYSTEM ERROR -7001)
CAUSE
The reserved file for CWD has been closed or is corrupted.
ACTION
Abort and restart the process.
7002
MESSAGE
The generic name translation service found a name outside a
group when it was required to be in a group.
(FILE SYSTEM ERROR -7002)
CAUSE
The name was outside of a group.
ACTION
Ensure that the name resolves to being in a group.
7003
MESSAGE
The generic name translation service could not find a component
of the source name path. (FILE SYSTEM ERROR -7003)
CAUSE
A directory is missing in the source name path.
ACTION
Provide a valid name.
7004
MESSAGE
The generic name translation service did not have room in the
target array to return the name.
(FILE SYSTEM ERROR -7004)
CAUSE
The target array length is not large enough.
ACTION
Supply a larger target array.
7005
MESSAGE
The generic name translation service found a remote envorionment
or a system file when it was not allowed.
(FILE SYSTEM ERROR -7005)
CAUSE
Remote environements and system files cannot be translated
into some syntaxes.
ACTION
Remove the remote environment or system file from the
input name.
7006
MESSAGE
The generic name translation service found no source name.
(FILE SYSTEM ERROR -7006)
CAUSE
A source name to translate was not provided.
ACTION
Specify a source name.
7007
MESSAGE
The generic name translation service received a request to
translate into an unsupported syntax.
(FILE SYSTEM ERROR -7007)
CAUSE
An invalid syntax value was specified as the target syntax.
ACTION
Supply a valid target syntax.
7008
MESSAGE
The generic name translation service received a request to
translate into an unknown syntax.
(FILE SYSTEM ERROR -7008)
CAUSE
An invalid syntax value was specified as the target syntax.
ACTION
Supply a valid target syntax.
7009
MESSAGE
The generic name translation service received a request to
translate a name from an unknown syntax.
(FILE SYSTEM ERROR -7009)
CAUSE
An invalid syntax value was specified as the source syntax.
ACTION
Supply a valid source syntax.
7010
MESSAGE
The generic name translation service cannot translate the
source name into the desired syntax.
(FILE SYSTEM ERROR 7010)
CAUSE
The source name cannot be expressed in the target syntax.
ACTION
Pick a different target syntax.
7011
MESSAGE
The generic name translation service cannot parse the source
name. (FILE SYSTEM ERROR -7011)
CAUSE
The generic name parsing service found a syntax
error in the name.
ACTION
Supply a valid source name.
7012
MESSAGE
The generic name translation service was called with invalid
options. (FILE SYSTEM ERROR -7012)
CAUSE
The caller passed a bad value in the options parameter.
ACTION
Supply a valid options parameter.
7101
MESSAGE
UNABLE TO CREATE FLOD DATA STRUCTURE.
CAUSE
An internal file system error occurred.
ACTION
Call your HP Support Representative.
7102
MESSAGE
UNABLE TO CREATE FLOD DATA STRUCTURE.
CAUSE
An internal file system error occurred.
ACTION
Call your HP Support Representative.
7103
MESSAGE
UNABLE TO ISSUE ANOTHER LOCK REQUEST, LIMIT
REACHED.
CAUSE
The maximum number of lock requests for this file has been reached.
No lock requests can be granted until some locks are released.
ACTION
Release unneeded locks.
7104
MESSAGE
INTERNAL HPFLOCK ERROR.
CAUSE
Internal file system error.
ACTION
Call your HP Support Representative.
7105
MESSAGE
FILE WAS OPENED WITH DYNAMIC LOCKING, USE FLOCK.
CAUSE
HPFLOCK is called on a file which was HPFOPENed
with the dynamic locking option.
ACTION
HPFOPEN the file without the dynamic locking option.
7106
MESSAGE
LOCK HELD BY ANOTHER PROCESS, REQUEST DENIED.
CAUSE
An attempt was made to lock without the wait option
a record range already locked by another process.
ACTION
Retry the request later or use the wait option.
7107
MESSAGE
NO FLOD EXISTS, INCOMPATIBLE FILE TYPE.
CAUSE
HPFLOCK does not support this file type.
ACTION
Use FLOCK instead.
7108
MESSAGE
NO SUCH LOCK EXISTS.
CAUSE
HPFLOCKINFO, with a command parameter value of 1, was
issued on a lock request which does not exist.
ACTION
Assume no such lock exists and continue.
7109
MESSAGE
WHENCE PARAMETER OUT OF BOUNDS.
CAUSE
A value other than 0, 1, 2, or 3 was passed in for
the whence parameter.
ACTION
Pass in a legal value.
7110
MESSAGE
LENGTH PARAMETER OUT OF BOUNDS.
CAUSE
A negative value was passed for the the length parameter.
ACTION
Pass in a non-negative number.
7111
MESSAGE
START PARAMETER OUT OF BOUNDS.
CAUSE
The value for the start parameter is beyond the
file limit for the file and is therefore, invalid.
ACTION
Determine the file limit via FFILEINFO and correctly compute
the value for the start parameter.
7112
MESSAGE
INTERNAL HPFLOCK ERROR.
CAUSE
An internal file system error occurred.
ACTION
Call your HP Support Representative.
7113
MESSAGE
LOCK EXTENDS BEYOND THE FILE LIMIT.
CAUSE
The start, length, and whence parameters combine
to refer to a record beyond the file limit.
ACTION
Determine the file limit via FFILEINFO and correctly compute
the values for the start, length, and whence parameters.
7114
MESSAGE
INTERNAL HPFLOCK ERROR, FLOD MARKED INVALID.
CAUSE
An internal file system error occurred. To avoid corruption,
all attempts to HPFLOCK or HPFUNLOCK the file will be denied.
ACTION
Close all instances of the file to release all locks
and allow locking on subsequent HPFLOCKs to occur.
7115
MESSAGE
NO GUFD EXISTS, INCOMPATIBLE FILE TYPE.
CAUSE
HPFLOCK does not support this file type.
ACTION
Use FLOCK instead.
7116
MESSAGE
NO GDPD EXISTS, INCOMPATIBLE FILE TYPE.
CAUSE
HPFLOCK does not support this file type.
ACTION
Use FLOCK instead.
7117
MESSAGE
COMMAND PARAMETER OUT OF BOUNDS.
CAUSE
A value other than 0 or 1 was passed in for the
command parameter to HPFLOCKINFO.
ACTION
Pass in a legal value.
7118
MESSAGE
LOCK PARAMETER OUT OF BOUNDS.
CAUSE
A value other than 0, 1, 2, 3, or 4 was passed in
for the lock parameter to HPFLOCK.
ACTION
Pass in a legal value.
7119
MESSAGE
PIN PARAMETER OUT OF BOUNDS.
CAUSE
An invalid value was passed in the pin parameter to
HPFLOCKINFO.
ACTION
Pass in a legal value.
7120
MESSAGE
INTERRUPT OCCURED WHILE WAITING FOR LOCK.
CAUSE
The process was aborted or an interrupt occurred
while waiting for the lock request. The request was denied.
ACTION
Retry the operation.
7123
MESSAGE
SIZE PARAMETER OUT OF BOUNDS.
CAUSE
An invalid value was passed in for the size parameter
to HPFLOCKINFO.
ACTION
Pass in a positive value.
7124
MESSAGE
INVALID FILE TYPE.
CAUSE
HPFLOCK does not support this file type.
ACTION
Use FLOCK instead.
7125
MESSAGE
LOCK TYPE AND FILE ACCESS INCOMPATIBLE.
CAUSE
A request for a read lock was made on a file not
opened with read access or a request for a write lock was made on a
file not opened with write access.
ACTION
HPFOPEN the file with the appropriate access.
7126
MESSAGE
CONFLICTING READ FORMAT.
CAUSE
The HPFLOCK request has been denied because another lock
request has been granted by a process which has the file opened
with a different read format.
ACTION
Retry the operation later, or reopen the file a
different read format and retry the operation.