p_manage_21: "File xxx does not exist" when the file *does* exist
- Article Type: General
- Product: Aleph
- Product Version: 20
Description:
I submitted p_manage_21 with an input file "newABC_MATY_records".
The $alephe_scratch/abc60_p_manage_21.00082 job log has these lines at the end:
Param Errors Found:
F01: File /exlibris/aleph/u18_2/alephe/scratch/new does not exist.
Param Initialization Failure, Exiting !!!
But the file newABC_MATY_records *does* exist. Is it looking for a file with just the name "new"?
Resolution:
The reason the input file newABC_MATY_records is not being found is that the submission process changes uppercase characters in the filename to lowercase and looks for a file with that name.
Renaming the file in $alephe_scratch to all lowercase ("new_abc_maty_records") corrected this problem.
Though there may be some cases where this is not a problem, as a general rule, you should *not* use uppercase letters in file names: use lowercase letters only.
Only the first 40 characters of the file name appear in the error message, so the full name is not appearing.
Additional Information
As described in Article 000042121 ( manage-18: "I/O error: ... File not found" ), checking the "Read From / PrintToAdm" checkbox can cause a Cataloging service to look for the input file in the ADM library's $data_scratch rather than the bib library's.
- Article last edited: 11/14/2013