ABORT raised when attempting to execute routine... sometimes

[pnpmarques]

Hello,
In my sequence I have a routine activity which goal is to search for a specific string in job log entries using "dsjob -logdetail..." command.
Sometimes, in testing environment, the sequence ends with only the follownig error message:
Attempting to Cleanup after ABORT raised in job <jobname>..JobControl

Our suggestion to Datastage administrator has always been importing routine again and compile sequence, which worked, but we are afraid these situations will happen again for no apparent reason.

Has anyone experienced this before?

Best regards.

[pandeesh]

Please post the entire messages you are getting.

[pnpmarques]

(...)
<sequence_job>..JobControl (DSWaitForJob): Job <parallel_job> has finished, status = 1 (Finished OK)
<sequence_job>..JobControl (@Job_15): Checkpointed run of job <parallel_job>
Attempting to Cleanup after ABORT raised in job <sequence_job>..JobControl
(<sequence_job>) <- <sequence_job>: Job under control finished.

That's it, no information at all.
Next step is the routine activity I mentioned before. It's odd that I have to compile this routine so that the sequence finishes ok.

[chulett]

If you reset the aborted job, is there a "From previous run..." message added to the log? If so, please post the contents.

[pnpmarques]

Finally I got it:
From previous run
DataStage Job 675 Phantom 538
Program "DSRunJob": Line 403, Variable "TempName" previously undefined. Empty string used.
Subroutine "DSU.RtSearchStringInJobLog" called with 3 arguments, 0 were expected"
Program "JOB.1188344055.DT.1592358232": Line 1144, Unable to load subroutine.
Attempting to Cleanup after ABORT raised in job <job_name>..JobControl

DataStage Phantom Aborting with @ABORT.CODE = 3

I found this information:
http://www-01.ibm.com/support/docview.w ... wg1JR39860

I am going to test if declaring this variable in the routine is the solution.

[pnpmarques]

So far it has been running good. I am declaring this topic as Resolved.