• Article Type: General
• Product: Aleph
• Product Version: 17.01

Description:
The patron loader report generates an enormous amount of data which often is not needed. How do we get just the errors, if possible?

Resolution:
The $alephe_scratch p_file_20 log file lists specific errors.

Looking at the abc50_p_file_20.05393 file, I see following seven different errors:

Z303-ILL-LIBRARY is not valid (check tab_sub_library)
Z303-HOME-LIBRARY is invalid (check tab_sub_library)
Z305-EXPIRY-DATE is not correct
Z305-PHOTO-CHARGE should be "C" or "F"
Z305-SUB-LIBRARY is not valid (check tab_sub_library)
conflict between Z305-SUB-LIBRARY and Z305-BOR-STATUS (check tab31)
Z303-PROXY-ID is not valid

We see the following in the util f/2/5/1 student_ads.txt file for input patrons 24 and 110:

ILL-LIBRARY...... LAW
HOME-LIBRARY..... LAW

Per tab_sub_library, "LAW" is not a valid sublibrary.

Similarly, the presence of LAW as the sublibrary in the BOR-REC causes the Z305 errors for input patrons 24 and 110:

BOR-REC # 04
ACTION...... A
SUB-LIBRARY. LAW
TYPE........ 00
STATUS...... 22
EXPIRY-DATE.
REG-DATE....

This "conflict between Z305-SUB-LIBRARY ..." error can occur in v18-up when you have a BOR-REC "SUB-LIBRARY ... ALEPH" record in your input file, and just one ADM library and USER-SHARING=N. In this case you do *not* need or want an ALEPH BOR-REC (you need an xxx50 BOR-REC). The ALEPH BOR-REC should be removed from your PLIF input file.

• Article last edited: 10/8/2013