Hi guys,
I get this error everytime I try to compile a job.
The error relates to a transformer stage.
I have checked EVERYTHING (constraints, variables,...). I have even written trivial derivations (with no routines involved, just mapping directly from input fields)
I have even tried to rebuild the transformer in case the internal code was corrupted, but nothing.
The "More" button returns
Compiling: Source = 'RT_BP1776/JOB.1876606699.DT.1411563621.TRANS1', Object = 'RT_BP1776.O/JOB.1876606699.DT.1411563621.TRANS1'
*************************************************************
Compilation Complete.
(PRUEBAS_Obj_4_1_3_ObjectL_Mapping.Transformer_xculero)
However, Director states that the job status is "not compiled"
Any suggestion you may have can be of great help...
Cheers!
Error compiling generated subroutine for stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 15
- Joined: Wed Mar 29, 2006 1:55 am
-
- Participant
- Posts: 15
- Joined: Wed Mar 29, 2006 1:55 am
-
- Participant
- Posts: 15
- Joined: Wed Mar 29, 2006 1:55 am
Yup, as you reckon I have tried by "rebuilding" the same job. It was not hard to do since there is almost no code involved, as I said the derivations are direct copies of input links.
I have just noticed that the same issue comes up for other jobs in the same folder... And they are pretty simple too...
I have read a similar post and the guy managed to solve it, this was his final post:
"The issue is there is no enough space in the unix box and also i rebuild the repository indexes using DS.TOOLS and now it's working fine. "
Do you think this is the issue? If yes, how can I do that?
I have just noticed that the same issue comes up for other jobs in the same folder... And they are pretty simple too...
I have read a similar post and the guy managed to solve it, this was his final post:
"The issue is there is no enough space in the unix box and also i rebuild the repository indexes using DS.TOOLS and now it's working fine. "
Do you think this is the issue? If yes, how can I do that?
-
- Participant
- Posts: 15
- Joined: Wed Mar 29, 2006 1:55 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If this error ever recurs, try clearing the job's status file (Tools menu in Director, or DS.TOOLS menu on server). I'm guessing that the status record for the job somehow got "stuck" (there are a few possibilities, which I will not canvas now, since the problem is resolved).
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.