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

Description:
As described in KB 31482 our p_manage_01 failed in p_manage_01_e. I am following the steps in "How_To_Run_Index_Jobs_2009_Nov_02_js.doc" to restart the run of p_manage_01 at the "e" stage.

I dropped and recreated z98 and dropped z98_id.

Here is the command I ran:

csh -f $aleph_proc/p_manage_01_e ABC01,1,000000000,999999999,,8 p_manage_01 > & $alephe_scratch/abc01_p_manage_01_e.jma.log &

Here is what is in the log:
ALEPH/SUN_OS_2, Copyright Ex Libris.
version 20 revision 01 copy 1, 13-Feb-2009
p_lng: Undefined variable

My preliminary preparations included moving all the *log and *cycle files from the earlier phase to a different directory (../abc01/scratch/p_manage_01_Dec2010), i.e., e and a cycle files, and log files for a, c, d, d1, e, e1).

It appears p_lng needs to be set somewhere, what do you suggest?

Resolution:
The csh command needs to be preceded by:

> setenv p_lng ""

(that is, two double quotation marks right next to each other). The re-run was successful. The "How To Run Index Jobs" will be updated to indicate the need for this setenv.

Technical explanation:

p_lng parameter derives from start_p_proc file which is "sourced" by p_manage_01 process.
The p_manage_01_e process "sources" start_p_sub_proc instead, which does not know the p_lng parameter.
When the process p_manage_01_e checks the value of p_lng it fails, because it was not defined within environment in which the p_manage_01_e runs.

To make p_manage_01_e process to "know" the p_lng variable it can be defined prior to execution of the process by setting its value to "" (NULL - which is the value that is set to it when start_p_proc is activated from p_manage_01.

• Article last edited: 10/8/2013