ue_17 is running but doesn't handle any messages

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

Description:
customer has problems with ue_17.
It is a multi-ADM site and when a borrow request is created by one ILL library it is elaborated and Sent to Supplier and the APDU message is successfully created in ILLSV but its status remains NEW.
The ue_17 procedure simply doesn’t seem to handle the message.
Restarting ue_17 doesn't help.

Resolution:
Daemone ue_17 is using direct index STS (Z11) to find new ILLSV records.

In ILLSV on the customer server for any reason z11_id did not exist:

Enter Table Name : z11

Defined in file_list:
__________________________________________________________
IND z11_id 100K 0K ts1
IND z11_id1 100K 0K ts1
__________________________________________________________

Exist in the Database:
INDEX_NAME STATUS INDEX_TYPE UNIQUENESS COLUMN_NAME
--------------- ------- ---------- ----------- --------------------
Z11_ID1 VALID NORMAL NONUNIQUE Z11_DOC_NUMBER

This explains that ue_17 does not pick up any ILLSV-record.

Creation of the index did not work as there are already duplicate keys in Z11_REC_KEY.

So Z11 had to be rebuild using p_manage_05 (this only took few minutes as ILLSV is very small):

m505@maya(a20_2) ILLSVu>ap
m505@maya(a20_2) ILLSVu> csh -f p_manage_05 ILLSV,1

Now z11_id index is there.

After restart of ue_17 the daemon is correctly handling all ILLSV records.