p_print_03: "Existing 001 field for record ... is not a valid Aleph format"
- Article Type: General
- Product: Aleph
- Product Version: 16.02
Description:
When we run p_print_03 and the record already has an 001 field, we get the message: "Error. Existing 001 field for record XXXXXXXXX is not a valid Aleph format".
Is there a way to force p_print_03 to do an 001 overwrite?
Resolution:
You can have it execute a fix_doc_do_file_08 before the fix_doc_001_sysno. Like this:.
EXPT fix_doc_do_file_08 delete_001.fix
EXPT fix_doc_001_sysno
Then you would have an abc01/tab/import/delete_001.fix file like this:.
1 001## DELETE-FIELD
Note: there is an indication that this doesn't work in certain versions. If not, you will need to do one of two things:
1. Use the p_print_03 input file as input to the p_manage_37 "fix doc records" job, specifying a label in tab_fix which has the as the fix_doc_do_file_08 as the fix routine to execute. This will update the records in place, deleting the 001. Or
2. Use the p_print_03 input file as input to the p_manage_21 global change, specifying 001 as a "Delete Field".
In either case, be sure to specify the appropriate input file.
Then you will be able to run p_print_03 with fix_doc_001_sysno OK.
Additional Information
faq
- Article last edited: 10/8/2013