- Article Type: General
- Product: Aleph
- Product Version: 19.01
p_file_02 stops with a particular record. The $alephe_scratch log shows this:
CUT RECORD NUMBER= 000000437; TAG= 5058
CUT RECORD NUMBER= 000000440; TAG= 5058
CUT RECORD NUMBER= 000000449; TAG= 505
Execution error : file '/exlibris/aleph/a19_2/aleph/exe/.gnt'
error code: 114, pc=0, call=11, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
Looking at the MARC input file, it seems the problem is a bad input record from the vendor.
I think this is the offending tag's Directory entry: 505132290053; and the preceding entry is 504005100485. So the 505 displacement should be 00536 rather than 90053. Now the next byte in the Dir is a 6, following the 505's 12 bytes. So I think we are looking at a 13-byte directory entry for the 505. (It should be only 12.)
We will complain to our data supplier. Their solution is going to be to divide their 505 in two so each part has a data length under 9999 bytes.
- Article last edited: 10/8/2013