File System (Compatibility Mode)
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| E0701 Volume II | |
| E0300 Volume I ♥ | |
| E0300 Volume II | |
| E0300 Volume III | |
| E0394 Volume I | |
| E0796 Volume II | |
| E0494 Volume III |
- 0
- MESSAGE
END OF FILE (FSERR 0)
- 1
- MESSAGE
ILLEGAL DB REGISTER SETTING (FSERR 1)
- 2
- MESSAGE
ILLEGAL CAPABILITY (FSERR 2)
- 3
- MESSAGE
REQUIRED PARAMETER IS MISSING (FSERR 3)
- 4
- MESSAGE
DISC FREE SPACE ALLOCATION DISABLED ON ALL DISCS IN DOMAIN (FSERR 4)
- 5
- MESSAGE
DRT NUMBER > 511 (FSERR 5)
- 6
- MESSAGE
DEVICE HAS NO AVAILABLE SPARE BLOCKS. (FSERR 6)
- 7
- MESSAGE
UNFORMATTED OR UNINITIALIZED MEDIA ON DEVICE. (FSERR 7)
- 8
- MESSAGE
ILLEGAL PARAMETER VALUE (FSERR 8)
- CAUSE
A call was made to access (open, read, write, lock, append etc.) a file with a parameter value that the file system could not use.
- ACTION
Check values of all parameters in all calls to the file system. If you are not calling the file system directly, but instead are relying on a generated call (such as a call to HPFOPEN generated by a language compiler rather than a call to HPFOPEN that you coded directly) check all call parameter values and all code that would influence parameter values. Also, because file system call parameter values can be overidden by file equations, be sure the parameters in every file equation correctly match the file to be accessed.
- 9
- MESSAGE
INVALID FILE TYPE SPECIFIED IN FOPTIONS (FSERR 9)
- 10
- MESSAGE
INVALID RECORD SIZE SPECIFICATION (FSERR 10)
- 11
- MESSAGE
INVALID RESULTANT BLOCK SIZE (FSERR 11)
- 12
- MESSAGE
RECORD NUMBER OUT OF RANGE (FSERR 12)
- 13
- MESSAGE
CAN'T OPEN FILE MULTI-ACCESS, OUT OF FMAVT ENTRIES (FSERR 13)
- 15
- MESSAGE
EXCEEDED THE MAXIMUM MESSAGE FILE OPENS FOR WRITE ACCESS (FSERR 15)
- 16
- MESSAGE
MORE THAN 255 OPENS OF A FILE (FSERR 16)
- 17
- MESSAGE
MAGNETIC TAPE RUNAWAY (FSERR 17)
- 18
- MESSAGE
DEVICE POWERED UP (FSERR 18)
- 19
- MESSAGE
FORMS CONTROL WAS RESET (FSERR 19)
- 20
- MESSAGE
INVALID OPERATION (FSERR 20)
- 21
- MESSAGE
DATA PARITY ERROR (FSERR 21)
- 22
- MESSAGE
SOFTWARE TIME-OUT (FSERR 22)
- 23
- MESSAGE
END OF TAPE (FSERR 23)
- 24
- MESSAGE
UNIT NOT READY (FSERR 24)
- 25
- MESSAGE
NO WRITE-RING ON TAPE (FSERR 25)
- 26
- MESSAGE
TRANSMISSION ERROR (FSERR 26)
- 27
- MESSAGE
I/O TIME-OUT (FSERR 27)
- 28
- MESSAGE
TIMING ERROR OR DATA OVERRUN (FSERR 28)
- 29
- MESSAGE
SIO FAILURE (FSERR 29)
- 30
- MESSAGE
UNIT FAILURE (FSERR 30)
- 31
- MESSAGE
END OF LINE (FSERR 31)
- 32
- MESSAGE
SOFTWARE ABORT (FSERR 32)
- 33
- MESSAGE
DATA LOST (FSERR 33)
- 34
- MESSAGE
UNIT NOT ON-LINE (FSERR 34)
- 35
- MESSAGE
DATA-SET NOT READY (FSERR 35)
- 36
- MESSAGE
INVALID DISC ADDRESS (FSERR 36)
- 37
- MESSAGE
INVALID MEMORY ADDRESS (FSERR 37)
- 38
- MESSAGE
TAPE PARITY ERROR (FSERR 38)
- 39
- MESSAGE
RECOVERED TAPE ERROR (FSERR 39)
- 40
- MESSAGE
OPERATION INCONSISTENT WITH ACCESS TYPE (FSERR 40
- 41
- MESSAGE
OPERATION INCONSISTENT WITH RECORD TYPE (FSERR 41)
- 42
- MESSAGE
OPERATION INCONSISTENT WITH DEVICE TYPE (FSERR 42)
- 43
- MESSAGE
WRITE EXCEEDS RECORD SIZE (FSERR 43)
- 44
- MESSAGE
UPDATE AT RECORD ZERO (FSERR 44)
- 45
- MESSAGE
PRIVILEGED FILE VIOLATION (FSERR 45)
- 46
- MESSAGE
OUT OF DISC SPACE (FSERR 46)
- 47
- MESSAGE
I/O ERROR ON FILE LABEL (FSERR 47)
- 48
- MESSAGE
INVALID OPERATION DUE TO MULTIPLE FILE ACCESS (FSERR 48)
- 49
- MESSAGE
UNIMPLEMENTED FUNCTION (FSERR 49)
- 50
- MESSAGE
NONEXISTENT ACCOUNT (FSERR 50)
- 51
- MESSAGE
NONEXISTENT GROUP (FSERR 51)
- 52
- MESSAGE
NONEXISTENT PERMANENT FILE (FSERR 52)
- 53
- MESSAGE
NONEXISTENT TEMPORARY FILE (FSERR 53)
- 54
- MESSAGE
INVALID FILE REFERENCE (FSERR 54)
- 55
- MESSAGE
DEVICE UNAVAILABLE (FSERR 55)
- 56
- MESSAGE
INVALID DEVICE SPECIFICATION (FSERR 56)
- 57
- MESSAGE
OUT OF VIRTUAL MEMORY (FSERR 57)
- 58
- MESSAGE
NO PASSED FILE (FSERR 58)
- 59
- MESSAGE
STANDARD LABEL VIOLATION (FSERR 59)
- 60
- MESSAGE
GLOBAL RIN UNAVAILABLE (FSERR 60)
- 61
- MESSAGE
OUT OF GROUP DISC SPACE (FSERR 61)
- 62
- MESSAGE
OUT OF ACCOUNT DISC SPACE (FSERR 62)
- 63
- MESSAGE
USER LACKS NON-SHARABLE DEVICE CAPABILITY (FSERR 63)
- 64
- MESSAGE
PROGRAM NOT PREPPED WITH MULTI-RIN CAPABILITY (FSERR 64)
- 65
- MESSAGE
PUNCH HOPPER EMPTY (FSERR 65)
- 66
- MESSAGE
PLOTTER LIMIT SWITCH REACHED (FSERR 66)
- 67
- MESSAGE
PAPER TAPE ERROR (FSERR 67)
- 68
- MESSAGE
INSUFFICIENT SYSTEM RESOURCES (FSERR 68)
- 69
- MESSAGE
I/O ERROR (FSERR 69)
- 70
- MESSAGE
I/O ERROR WHILE PRINTING HEADER/TRAILER (FSERR 70)
- 71
- MESSAGE
TOO MANY FILES OPEN (FSERR 71)
- 72
- MESSAGE
INVALID FILE NUMBER (FSERR 72)
- 73
- MESSAGE
BOUNDS VIOLATION (FSERR 73)
- 74
- MESSAGE
NO ROOM LEFT IN STACK SEGMENT FOR ANOTHER FILE ENTRY (FSERR 74)
- 77
- MESSAGE
NO-WAIT I/O PENDING (FSERR 77)
- 78
- MESSAGE
NO NO-WAIT I/O PENDING FOR ANY FILE (FSERR 78)
- 79
- MESSAGE
NO NO-WAIT I/O PENDING FOR SPECIAL FILE (FSERR 79)
- 80
- MESSAGE
SPOOFLE SIZE EXCEEDS CONFIGURATION (FSERR 80)
- 81
- MESSAGE
NO "SPOOL" CLASS IN SYSTEM (FSERR 81)
- 82
- MESSAGE
INSUFFICIENT SPACE FOR SPOOFLE (FSERR 82)
- 83
- MESSAGE
I/O ERROR ON SPOOFLE (FSERR 83)
- 84
- MESSAGE
DEVICE UNAVAILABLE FOR SPOOFLE (FSERR 84)
- 85
- MESSAGE
OPERATION INCONSISTENT WITH SPOOLING (FSERR 85)
- 86
- MESSAGE
Spooling internal error (FSERR 86)
- 87
- MESSAGE
BAD SPOOFLE BLOCK (FSERR 87)
- 88
- MESSAGE
NONEXISTENT SPOOLFILE (FSERR 88)
- 89
- MESSAGE
POWER FAILURE (FSERR 89)
- 90
- MESSAGE
EXCLUSIVE VIOLATION: FILE BEING ACCESSED (FSERR 90)
- 91
- MESSAGE
EXCLUSIVE VIOLATION: FILE ACCESSED EXCLUSIVELY (FSERR 91)
- 92
- MESSAGE
LOCKWORD VIOLATION (FSERR 92)
- 93
- MESSAGE
SECURITY VIOLATION (FSERR 93)
- 94
- MESSAGE
USER IS NOT CREATOR (FSERR 94)
- 95
- MESSAGE
READ COMPLETED DUE TO BREAK (FSERR 95)
- 96
- MESSAGE
DISC I/O ERROR (FSERR 96)
- 97
- MESSAGE
NO CONTROL Y PIN (FSERR 97)
- 98
- MESSAGE
READ TIME OVERFLOW (FSERR 98)
- 99
- MESSAGE
BOT AND BACKSPACE TAPE (FSERR 99)
- 100
- MESSAGE
DUPLICATE PERMANENT FILE NAME (FSERR 100)
- 101
- MESSAGE
DUPLICATE TEMPORARY FILE NAME (FSERR 101)
- 102
- MESSAGE
I/O ERROR ON DIRECTORY (FSERR 102)
- 103
- MESSAGE
PERMANENT FILE DIRECTORY OVERFLOW (FSERR 103)
- 104
- MESSAGE
TEMPORARY FILE DIRECTORY OVERFLOW (FSERR 104)
- 105
- MESSAGE
BAD VARIABLE BLOCK STRUCTURE (FSERR 105)
- 106
- MESSAGE
EXTENT SIZE EXCEEDS MAXIMUM (FSERR 106)
- 107
- MESSAGE
INSUFFICIENT SPACE FOR USER LABELS (FSERR 107)
- 108
- MESSAGE
INVALID FILE LABEL (FSERR 108)
- 109
- MESSAGE
INVALID CARRIAGE CONTROL (FSERR 109)
- 110
- MESSAGE
ATTEMPT TO SAVE PERMANENT FILE AS TEMPORARY (FSERR 110)
- 111
- MESSAGE
USER LACKS SAVE FILES (SF) CAPABILITY (FSERR 111)
- 112
- MESSAGE
USER LACKS PRIVATE VOLUMES (UV) CAPABILITY (FSERR 112)
- 113
- MESSAGE
VOLUME SET NOT MOUNTED - MOUNT PROBLEM (FSERR 113)
- 114
- MESSAGE
VOLUME SET NOT DISMOUNTED - DISMOUNT PROBLEM (FSERR 114)
- 115
- MESSAGE
ATTEMPTED RENAME ACROSS VOLUME SETS - REJECTED (FSERR 115)
- 116
- MESSAGE
INVALID TAPE LABEL FOPEN PARAMETERS (FSERR 116)
- 117
- MESSAGE
ATTEMPT TO WRITE ON AN UNEXPIRED TAPE FILE (FSERR 117)
- 118
- MESSAGE
INVALID HEADER OR TRAILER TAPE LABEL (FSERR 118)
- 119
- MESSAGE
I/O ERROR POSITIONING TAPE FOR TAPE LABELS (FSERR 119)
- 120
- MESSAGE
ATTEMPT TO WRITE IBM STANDARD TAPE LABEL (FSERR 120)
- 121
- MESSAGE
TAPE LABEL LOCKWORD VIOLATION (FSERR 121)
- 122
- MESSAGE
TAPE LABEL TABLE OVERFLOW (FSERR 122)
- 123
- MESSAGE
END OF TAPE VOLUME SET (FSERR 123)
- 124
- MESSAGE
ATTEMPT TO APPEND LABELED TAPE (FSERR 124)
- 125
- MESSAGE
EXPIRATION DATE CAN'T BE LATER THAN PRECEDING FILE'S (FSERR 125)
- 126
- MESSAGE
CHARACTER SET NUMBER MUST BE BETWEEN 0 AND 31. (FSERR 126)
- 127
- MESSAGE
FORM NUMBER MUST BE BETWEEN 0 AND 31. (FSERR 127)
- 128
- MESSAGE
LOGICAL PAGE NUMBER MUST BE BETWEEN 0 AND 31. (FSERR 128)
- 129
- MESSAGE
VERTICAL FORMAT NUMBER MUST BE BETWEEN 0 AND 31. (FSERR 129)
- 130
- MESSAGE
NUMBER OF COPIES MUST BE BETWEEN 1 AND 32767. (FSERR 130)
- 131
- MESSAGE
NUMBER OF OVERLAYS MUST BE BETWEEN 1 AND 8. (FSERR 131)
- 132
- MESSAGE
PAGE LENGTH PARM MUST BE BETWEEN 12 (=3") AND 68 (=17"). (FSERR 132)
- 133
- MESSAGE
PICTURE NUMBER MUST BE BETWEEN 0 AND 31. (FSERR 133)
- 134
- MESSAGE
EXTENDED CAPABILITY PARM MUST BE 0 (OFF) OR 1 (ON). (FSERR 134)
- 135
- MESSAGE
UNRECOVERED MEDIA ERROR. (FSERR 135)
- 137
- MESSAGE
DEFECTIVE TRACK ON FOREIGN DISC (FSERR 137)
- 138
- MESSAGE
TRACK DOES NOT EXIST ON FOREIGN DISC (FSERR 138)
- 139
- MESSAGE
DELETED RECORD ON IBM DISKETTE (FSERR 139)
- 148
- MESSAGE
INACTIVE RIO RECORD (FSERR 148)
- 149
- MESSAGE
MISSING ITEM NUMBER OR RETURN-VARIABLE (FSERR 149)
- 150
- MESSAGE
INVALID ITEM NUMBER (FSERR 150)
- 151
- MESSAGE
CURRENT RECORD WAS LAST RECORD WRITTEN BEFORE SYSTEM CRASHED (FSERR 151)
- 152
- MESSAGE
UNRECOGNIZED KEYWORD IN FOPEN DEVICE PARAMETER (FSERR 152)
- 153
- MESSAGE
EXPECTED ";" OR CARRIAGE RETURN IN DEVICE PARAMETER (FSERR 153)
- 154
- MESSAGE
ENVIRONMENT FILE OPEN ERROR (FSERR 154)
- 155
- MESSAGE
NOT ENVIRONMENT FILE. CHECK FILE CODE OR RECORD SIZE. (FSERR 155)
- 156
- MESSAGE
ENVIRONMENT HEADER RECORD INCORRECT (FSERR 156)
- 157
- MESSAGE
UNCOMPILED ENVIRONMENT FILE (FSERR 157)
- 158
- MESSAGE
ERROR READING ENVIRONMENT FILE (FSERR 158)
- 159
- MESSAGE
ERROR CLOSING ENVIRONMENT FILE (FSERR 159)
- 160
- MESSAGE
ERROR DOING FDEVICECONTROL FROM ENVIRONMENT FILE (FSERR 160)
- 161
- MESSAGE
TOO MANY PARAMETERS IN DEVICE STRING - OVERFLOW (FSERR 161)
- 162
- MESSAGE
EXPECTED "=" AFTER KEYWORD IN DEVICE PARAMETER (FSERR 162)
- 163
- MESSAGE
"ENV" BACK REFERENCE IN FILE EQUATION INCORRECT (FSERR 163)
- 164
- MESSAGE
DEVICE PARAMETER TOO LARGE OR MISSING CARRIAGE RETURN (FSERR 164)
- 165
- MESSAGE
INVALID DENSITY SPECIFICATION (FSERR 165)
- 166
- MESSAGE
FFILEINFO FAILED IN ACCESSING REMOTE SPOOL FILE. (FSERR 166)
- 167
- MESSAGE
SPOOL FILE LABEL ERROR, CAN'T INSERT ENV FILE NAME. (FSERR 167)
- 168
- MESSAGE
ITEM NOT SUPPORTED ON REMOTE SYSTEM. (FSERR 168)
- 170
- MESSAGE
RECORD IS MARKED FOR DELETION (FSERR 170)
- 171
- MESSAGE
DUPLICATE KEY VALUE (FSERR 171)
- 172
- MESSAGE
NO SUCH KEY (FSERR 172)
- 173
- MESSAGE
TCOUNT PARAMETER LARGER THAN RECORD SIZE (FSERR 173)
- CAUSE
There is a discrepancy between the number of bytes that the system has transferred (or is attempting to transfer) and the number of bytes specified in a buffer or record size.
- ACTION
Check all calls to intrinsics where a buffer or record size is specified which may not match data transfer size. In particular, check calls to intrinsics such as FREAD or FREADBACKWARD, which have a TRANSFERCOUNT parameter which is returned by the system. A possible cause is that the system has (or is attempting to) set the TRANSFERCOUNT to a value which exceeds the buffer length specified in the call. Another possible cause is a LENGTH parameter which exceeds the record size in a call to FWRITE without the NOBUF option. Also, a call to FWRITE with a LENGTH parameter which exceeds the physical record size may produce this message unless the MULTIRECORD AOPTION is used.
- 174
- MESSAGE
CAN NOT GET EXTRA DATA SEGMENT (FSERR 174)
- 175
- MESSAGE
KSAM INTERNAL ERROR (FSERR 175)
- 176
- MESSAGE
ILLEGAL EXTRA DATA SEGMENT LENGTH (FSERR 176)
- 177
- MESSAGE
TOO MANY EXTRA DATA SEGMENTS FOR THIS PROCESS (FSERR 177)
- 178
- MESSAGE
NOT ENOUGH VIRTUAL MEMORY FOR EXTRA DATA SEGMENT (FSERR 178)
- 179
- MESSAGE
THE FILE MUST BE LOCKED BEFORE ISSUING THIS INTRINSIC (FSERR 179)
- 180
- MESSAGE
KSAM FILE MUST BE REBUILT (FSERR 180)
- 181
- MESSAGE
INVALID KEY STARTING POSITION (FSERR 181)
- 182
- MESSAGE
FILE IS EMPTY (FSERR 182)
- 183
- MESSAGE
RECORD DOES NOT CONTAIN ALL KEYS (FSERR 183)
- 184
- MESSAGE
INVALID RECORD NUMBER (FFINDN INTRINSIC) (FSERR 184)
- 185
- MESSAGE
SEQUENCE ERROR IN PRIMARY KEY (FSERR 185)
- 186
- MESSAGE
INVALID KEY LENGTH (FSERR 186)
- 187
- MESSAGE
INVALID KEY SPECIFICATION (FSERR 187)
- 188
- MESSAGE
INVALID DEVICE SPECIFICATION (FSERR 188)
- 189
- MESSAGE
INVALID RECORD FORMAT (FSERR 189)
- 190
- MESSAGE
INVALID KEY BLOCKING FACTOR VALUE (FSERR 190)
- 191
- MESSAGE
RECORD DOES NOT CONTAIN SEARCH KEY SPECIFIED FOR DELETION (FSERR 191)
- 192
- MESSAGE
SYSTEM FAILURE OCCURRED WHILE THE KSAM FILE WAS OPENED (FSERR 192)
- 193
- MESSAGE
$STDIN/$STDLIST CANNOT BE REDIRECTED TO KSAM FILES (FSERR 193)
- 194
- MESSAGE
KSAM files not allowed for global AFT's (FSERR 194)
- 195
- MESSAGE
Global files cannot be remote files (FSERR 195)
- 196
- MESSAGE
LANGUAGE NOT SUPPORTED (FSERR 196)
- 197
- MESSAGE
NATIVE LANGUAGE INTERNAL ERROR (FSERR 197)
- 198
- MESSAGE
INVALID VERSION NUMBER IN KSAM FILE (FSERR 198)
- 199
- MESSAGE
UNABLE TO SWITCH THE LOCKING MODE (FSERR 199)
- 300
- MESSAGE
NO. OF OPENS FOR FILE EXCEEDS 255 (FSERR 300)
- 301
- MESSAGE
FREE SPACE TABLE FOR LDEV ! IS FULL, RUN VINIT -COND (FSERR 301)
- 302
- MESSAGE
INVALID ITEM NUMBER FOR FDEVICECONTROL (FSERR 302)
- 303
- MESSAGE
INVALID ACCESS FOR ITEM NUMBER TO FDEVICECONTROL (FSERR 303)
- 304
- MESSAGE
ATTEMPT TO CHANGE TERMINAL PARITY IN 8 BIT MODE (FSERR 304)
- 305
- MESSAGE
INVALID FORMAT IN TERMINAL CONFIGURATION FILE (FSERR 305)
- 306
- MESSAGE
CHECKSUM ERROR IN TERMINAL CONFIGURATION FILE (FSERR 306)
- 307
- MESSAGE
PASSED VALUE TO FDEVICECONTROL LESS THAN MIN (FSERR 307)
- 308
- MESSAGE
PASSED VALUE TO FDEVICECONTROL GREATER THAN MAX (FSERR 308)
- 309
- MESSAGE
PASSED VALUE TO FDEVICECONTROL IS UNSUPPORTED (FSERR 309)
- 310
- MESSAGE
COUNT TO FDEVICECONTROL INSUFFICIENT TO RETURN INFO (FSERR 310)
- 311
- MESSAGE
COUNT TO FDEVCNT GREATER THAN AVAILABLE TO STORE INFO (FSERR 311)
- 312
- MESSAGE
PASSED SPECIAL CHARACTER HAS PREVIOUSLY DEFINED FUNCTION (FSERR 312)
- 350
- MESSAGE
KSAM LOCK TABLE FULL (FSERR 350)
- 351
- MESSAGE
TOO MANY RECORD LOCKS IN ONE PROCESS (FSERR 351)
- 352
- MESSAGE
RECORD WAS LOCKED ALREADY (FSERR 352)
- 353
- MESSAGE
FILE MUST BE UNLOCKED BEFORE ISSUING THIS INTRINSIC (FSERR 353)
- 354
- MESSAGE
DATA INTEGRITY VIOLATION (FSERR 354)
- 355
- MESSAGE
FILE IS LOCKED BY ANOTHER PROCESS (FSERR 355)
- 356
- MESSAGE
LOCK REQUEST REJECTED DUE TO POTENTIAL DEADLOCK (FSERR 356)
- 357
- MESSAGE
DATA MAY BE INVALID BECAUSE FILE IS LOCKED BY OTHERS (FSERR 357)
|
Chapter 5 Error Messages |
Eagle A-mux Device Manager (Subsystem 198) |