Using KSAM/XL and KSAM 64 (32650-90886)

230 AppendixB
BASIC/V Intrinsics
Status Parameter
23 Invalid key; No record found —
An attempt was made to locate a record by a key value with BKSTART or
BKREADBYKEY and the record cannot be found.
24
Invalid key; Boundary violation —
An attempt was made with BKWRITE to write beyond the externally defined
boundaries of the file; that is, to write past the end-of-file.
71
Request denied; File already locked —
An attempt was made to lock a file with BKLOCK and the file is already
locked.
81
Invalid call; Invalid number of parameters —
Too many or too few parameters were specified in the procedure call just
made.
82
Invalid call; Invalid parameter —
The specified parameter is not the correct type. For example, a string
variable was selected where only a numeric variable or expression is
allowed.
83
Invalid call; Insufficient internal buffer space —
The data specified in the
parameterlist to be read or written will not fit
into the configured internal buffer space. You may need to have certain
operating system parameters revalued.
9xxx
File system error —
An MPE file system error occurred for which the three-character value,
xxx is the error code. You can call procedure BKERROR to convert the error
code returned here to a printable message.
The value of status can be tested as a whole, or the first character can be tested separately
from the remaining characters. For example:
10 DIM S$(4)
.
.
.
50 IF S$(1;1) = "0" THEN PRINT "SUCCESS"
60 ELSE PRINT "ERRORCODE=";S$
.
.
.
100 IF S$(1;1)= "9" THEN DO
110 PRINT "FILE ERROR=";S$(2)
120 DOEND
.
.
.
200 IFS$ = "22" THEN DO
210 PRINT "DUPLICATE KEY ERROR"