p_file_20 error: z305_expiry_date is wrong

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

Description:
p_file_20 creates three z305 records for a particular patron: ALEPH, ABC50, MSVU.

For matched records, the ABC50 local record was updated with the new expiry date included in the input file 20080930.

For new records, the ABC50 record was created BUT with the default expiry date from the tab31 entry 20110730. Why?

Resolution:
This is what I see in the input file:

USER-REC
ACTION........... A
MATCH-ID-TYPE.... 02
MATCH-ID......... 0349659
...
NAME............. Corman, Rebecca
...

BOR-REC # 02
ACTION...... A
SUB-LIBRARY. MSVU
TYPE........
STATUS...... 01
EXPIRY-DATE. 20080930
REG-DATE....

BOR-REC # 03
ACTION...... A
SUB-LIBRARY. ABC50
TYPE........
STATUS...... 01
EXPIRY-DATE. 20110730
REG-DATE....

Thus, though the MSVU record has an expiry date of 20080930, the ABC50 record has 20110730. That is why we see that value in the record the PLIF creates.

See KB 8192-8455 for complete info on PLIF updating of the z305.

• Article last edited: 10/8/2013