Job is not calling the routine...

ramkarthik · Post by **ramkarthik** » Wed Mar 14, 2012 10:54 am

Hi,

We have a "Transform function" server routine that we can compile and test. But, when we were trying to run the same from a server job<job control>, we could not execute it because of the following error message...

Attempting to Cleanup after ABORT raised in stage <Jobname>.JobControl

It was recently migrated from Production environment to dev for testing.

We tried running other routines in the development environment to check for setup issues. They ran fine...

Please advise with root cause and solution for this...

Thanks in advance...

Kryt0n · Post by **Kryt0n** » Wed Mar 14, 2012 3:28 pm

Think you're the one who needs to determine root cause...

Have a look at the "Summary of sequence run" log message, it may contain more information for you to identify cause

ray.wurlod · Post by **ray.wurlod** » Wed Mar 14, 2012 3:34 pm

Did you migrate the routine's executable (or compile the routine in production)? What other error messages were logged? When you reset the job, is there a "from previous run..." event logged and, if so, what does it reveal?

ramkarthik · Post by **ramkarthik** » Wed Mar 14, 2012 4:07 pm

We are using a server job to run the routine. we are not calling the routine from sequence.

We migrated the routine from prod (in compiled state) and compiled in dev after migration - we are able to test it...

We could not see any more error messages apart from
"Attempting to Cleanup after ABORT raised in stage <Jobname>.JobControl"

I think we missed exporting job executables.. will reexport and check

Thanks for the response..

kandyshandy · Post by **kandyshandy** » Wed Mar 14, 2012 9:03 pm

You can very well compile the job in DEV environment rather than doing any export/import again.

Anyways, tell us what your routine is doing?