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...
Job is not calling the routine...
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 27
- Joined: Thu Jun 26, 2008 6:13 am
- Location: chennai
Job is not calling the routine...
ramkarthik
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 27
- Joined: Thu Jun 26, 2008 6:13 am
- Location: chennai
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..
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..
ramkarthik
-
- Participant
- Posts: 597
- Joined: Fri Apr 29, 2005 6:19 am
- Location: Singapore