1. Parallel_words in versions 18, 19 and 20
Yoel Kortick

2. parallel_words. Yoel Kortick
Introduction
A new option of using parallel_words has been added in versions 18, 19 and 20.
In versions 18 and 19 it is used by adding a parameter to aleph_start.
In version 20 it is the only way to build words via ue_01 so there is no parameter needed.
This was originally done for customers 01HVD and 49BVB
In version 18 it has been added via rep_change 1961 and in version 19 it has been added via rep_change 563.
parallel_words. Yoel Kortick

3. parallel_words. Yoel Kortick
Purpose
The main purpose of using parallel_words is to improve performance (decrease the amount of time needed) when indexing words via the ue_01 daemon.
In this brief presentation we will not involve ourselves with program changes, only with the actual effect of the parallel_words.
Note that the parallel_words comes to replace a previous option of using “accumulative” words.
parallel_words. Yoel Kortick

4. parallel_words. Yoel Kortick
Purpose
Here is the description from rep_change 1961 (v. 18) rep_change 563 (v. 19):
Description: in order to improve the performance of the ongoing indexing (done by the doc index daemon - ue-01), the building of the words has been defined in parallel to other indexes. For this, the following must be defined in aleph_start.private: setenv parallel_words "Y". If the new environment variable is not defined, the daemon continues to work as before.
parallel_words. Yoel Kortick

5. parallel_words. Yoel Kortick
When to use?
From now on we recommend to anyone who has experienced the overall performance of ue_01 being too slow to use this new option.
If, on the other hand, a library has not experienced a situation that the ue_01 overall performance is too slow then there is no need to do anything.
Technical note: In this change we have improved the overall performance of ue_01 by building the words in parallel to other indexes, rather than being one of a queue of indexes.
parallel_words. Yoel Kortick

6. parallel_words. Yoel Kortick
When is this relevant?
This is, as stated in the rep_change, relevant only for ue_01 daemon and therefore not relevant for manage_01.
The online update and batch jobs which use the ue_01 daemon are effected (manage_18, manage_33 and manage_40 for example).
Manage_01 does not use the ue_01 daemon and therefore is not effected.
parallel_words. Yoel Kortick

7. Implementation
For libraries wishing to use this option in versions 18 and 19 the following must be added to $alephe_root/aleph_start.private: 
setenv parallel_words "Y"
parallel_words. Yoel Kortick

8. parallel_words. Yoel Kortick
Implementation
Here is the implementation note:
Implementation Notes:
To activate the functionality add the following line to aleph_start.private
setenv parallel_words "Y"
After making the change you should do
source $alephe_root/aleph_start
source $alephe_root/aleph_start
You should also restart the ue_01 daemon and the pc_server.
parallel_words. Yoel Kortick

9. Viewing the new ue_01 process
After implementing the new option we have this (when view the ue_01 processes via UTIL C 1)
5979 ? S :05 /exlibris/aleph/a18_1/aleph/exe/rts32 ue_01_a USM01.a18_1
5981 ? S :06 /exlibris/aleph/a18_1/aleph/exe/rts32 ue_01_z0102_index USM01.a18_1
5983 ? S :06 /exlibris/aleph/a18_1/aleph/exe/rts32 ue_01_word_parallel USM01.a18_1
Before implementing the new option we have this (when view the ue_01 processes via UTIL C 1)
20005 ? S :11 /exlibris/aleph/a18_2/aleph/exe/rts32 ue_01_a USM01.a18_2
20006 ? S :04 /exlibris/aleph/a18_2/aleph/exe/rts32 ue_01_z0102_index USM01.a18_2
20007 ? S :03 /exlibris/aleph/a18_2/aleph/exe/rts32 ue_01_word_index USM01.a18_2
parallel_words. Yoel Kortick