- Article Type: General
- Product: Aleph
- Product Version: 18.01
Noting the document "How to use the Patron Loader Interface" v18, I see the command line entry for running this is defined. However, before I try, can you confirm that it is not necessary to specify whether it is xml or sequential?
PLIF 18 document, page 18, section "Running PLIF from the command line" should be updated to include the eighth parameter "input file type". This issue is currently with the Documentation team.
Running p_file_20 from the Command Line
For the purpose of these instructions, assume that the input PLIF file is called
To run p_file_20 from the Command Line:
1. Copy the PLIF file to the $data_scratch directory of the ADM library whose
patrons you want to update (for example, USM50). The name of the file must be
in lowercase. For example:
cp /wherever/patrons.plif .
2. Enter the following command to run p_file_20:
csh -f $aleph_proc/p_file_20 USM50,patrons.plif,patron_update.rpt,Y,%,+,,XML > & patron_update.log &
The job takes eight parameters, separated by commas.
1 – Library in which to do patron update (for example, USM50)
2 – Name of PLIF file, which should be in the $data_scratch directory (for
3 – Report file for update, which is left in the $data_scratch directory (for
4 – Y to update the database, N to not change the database and only produce a
5 – Spaces character (overwrite-with-blanks character). If this character is in the
input file, a space is written to the ALEPH field
6 – Ignore character (null character). If this character is in the input file, the
ALEPH field is protected.
7 – In version 16 and up there is an optional seventh parameter, character
8 – Input file type: XML or ALEPH_SEQ.
This issue is still open and was escalated to Second line support for further analysis <2007-09-23 01:00:05>.
This issue is still open and was escalated to Development for further investigation <2007-11-18 01:00:04>.
PLIF command line Input file type XML ALEPH_SEQ
- Article last edited: 10/8/2013