p_manage_18 truncating record but not issuing a message
- Article Type: General
- Product: Aleph
- Product Version: 18.01
Description:
MARC record has been converted to aleph seq format with p_file_01 / p_file_02.
1. p_file_02 log showed: Record length 000062000 truncated + number of tags 1157 truncated to 1000
Output file: "hol-trunc-converted" (/exlibris1/nyu60/scratch)
Total: 1002 lines
2. File "hol-trunc-converted" (truncated by p_file_02) was loaded to ABC60 with p_manage_18
Result: record loaded by p_manage_18 contains fewer tags than the input record (the record output by p_file_02)
File name: "hol-trunc-converted-loaded"
Total: 806 lines vs. 1002 lines in "hol-trunc-converted"
Why does p_manage_18 truncate additional fields from a record that has been already truncated by p_file_02?
Resolution:
We see that the length of loaded doc is 44998:
>> s+ abc60
SQL-ABC60>> select Z00_DATA_LEN from z00 where Z00_DOC_NUMBER='003554569';
Z00_DATA_LEN
------------
44998
The length of 44998 is only two bytes short of the doc record size limit of 45000.
It seems that p_file_02 is not truncating enough fields to avoid this problem.
It seems to me that when p_manage_18 does this truncation it should be producing a message.
In any case, you need to either delete fields from the input record or split it into multiple records.
(Keywords: p-file-01 file_01 p-file-02 file_02 p-manage-18 manage_18)
- Article last edited: 10/8/2013