 |
» |
|
|
|
|  | |
| | | |  | NOTE: This chapter includes KSAM error messages. | | | | |
- -90
- MESSAGE
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.
- 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.
|
