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

Description:
We have a problem with the custom jobs. Take for example p_priv_01. It runs fine, and the sql generates a printout, but the batch never shows completion. The batch log (abc50_p_priv_01.00053) for job 2336 in ABC50 (ABCSUPER/ACPSUPER20, port 6515) on hickory server shows it still running although a finished print report shows up in the ABC50 print folder (test-priv01-srf).

The log shows "end" at the bottom, but I notice in comparing to standard Aleph job batch logs, I don't see the "Wrote Z100 record with rec-key: ######" at the bottom. Would that cause the batch to hang up and never show success? Do we have to include a reference to that process in the custom batch?

Resolution:
Does the job continue to show up in util c/1? and in ps -ef | grep priv_01 ?

p_priv_01 ends with these lines:

ex_p_priv_01:
bl_end
rm_f_symbol
exit

while p_com_02 ends with these:

ex_p_com_02:
end_p_proc
exit

I suggest that, as a test, you replace the last three lines in p_priv_01 with the two shown above from p_com_02.

[From site:] This worked.

• Article last edited: 10/8/2013