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

Description:
We are running p_serial_13 and it seems to be hung. ps -ef claims it is running:

ps -ef | grep p_serial_13
aleph 307406 880822 0 12:39:10 pts/0 0:00 grep p_serial_13
aleph 356576 2523276 0 Nov 10 - 0:00 csh -f /exlibris/aleph/a18_1/aleph/proc/p_serial_13 ABC50,mbw_olse,mbw_olse20081110,20091231,N,00,

But the temp file in alephe/scratch has not grown for the past hour:

bash-3.00$ ls -l abc50_p_serial_13*
-rw-rw-r-- 1 aleph aleph 260961 Nov 10 11:08 abc50_p_serial_13.05736
-rw-rw-r-- 1 aleph aleph 0 Nov 10 10:57 abc50_p_serial_13.05736.lock

In addtion, nothing else in the batch queue is running, as if the entire lib batch is hung.

Why would p_serial_13 have hung?

Resolution:
[From Jerry:] I see the following at the end of the $alephe_scratch/abc50_p_serial_13.05736 log file:

Start handling DOC NO: 000644482
End handling DOC NO: 000644482
Start handling DOC NO: 000645192
End handling DOC NO: 000645192
Start handling DOC NO: 000645194
End handling DOC NO: 000645194
Start handling DOC NO: 000645255 <----

And a tail of the abc50 $data_scratch/serial_13_1 work file confirms that 000645194 was the last record successfully processed.

Please run it again, with 000645255 omitted.

[From site:]

The job ran with 645255 omitted from the input file. #645255 is for a weekly, 46 issues per year. The pattern looks like this:

853
$$a v.
$$b no.
$$u 46
$$v r
$$i (year)
$$j (month)
$$k( day)
$$w w
$$y od0707,0721,0804,0818,0901,1229

853X
$$9 00101
$$a 50
$$b 1
$$i 2009
$$j 01
$$3 20090105

So the $$k value in the 853X (which should be specifying the day, corresponding to to the caption "(day)" in 853 $$k) is missing, and I suspect that's what's causing the problem. (In fact, even when trying to access this via the serials GUI, Aleph can't display the "Level-X"
portion of the pattern--the display just hangs.) We will fix it manually.

• Article last edited: 10/8/2013