- Article Type: General
- Product: Aleph
- Product Version: 18.01
Rep Change 410 (a few NCIP Enhancements) indicates we are to add RID to the xxx50/tab/tab11_ind. Until now, each of our 28 xxx50/tab/tab11_ind have been blank. Our experience is with tab11 in the FCC01, and that is typically indexed.
1. Do we have to run p_manage_05 in each xxx50?
2. What is the Z37-REQUEST-IDENTIFIER field? We don't see this in the Collected Oracle tables documentation or with a "desc" in SQLPlus.
It turns out that the text for rep change 410 mixed up the changes made for v.18 and v.19. Here is clarification regarding what was done for v.18 and the implications of the changes:
When a request is created by an NCIP message (RequestItem or AcceptItem), the NCIP message may include a request identifier. That request identifier may be later used by the NCIP client to cancel that specific request. It is therefore essential that the identifier be stored in the request that ALEPH creates in response to the message.
In ver. 18:
ID is stored in the Z37-NOTE-2, and in a “RID” field on the ADM document (Z00). If the correct request is to be fetched when a cancel request comes in with this ID, the RID field has to be indexed in the ADM library. That’s what the tab11_ind instructions are about. It will not be relevant for ver. 19.
In ver. 19:
In version 19 the identifier is stored in the new Z37-REQUEST-IDENTIFIER field. The Z37-REQUEST-IDENTIFIER field is indexed and is used to fetch the correct request if a cancel message comes in with an ID.
So, the Z37-REQUEST-IDENTIFIER field does not exist in v.18, but will in v.19.
On the other hand, the new RID field in the ADM library record will require an index and thus an indexing job. My own take on this would be that if you know that the source of your NCIP messages will not be using the request identifier field, you should be able to skip this entire part of the process. Presumably, the RID field would never get created and thus indexing it should not be important. If you are unsure about the use of the request identifier field from your NCIP message source, you may need to set this up.
- Article last edited: 10/8/2013