ILArchives..JobControl (@FAILED2): Controller problem: BASIC routine is not cataloged: DSU.ForceFail
The above is the error DS throwing when I tried to execute a Sequencer with an routine embedded to kill the sequencer in case of any error.
Any help on this is appreciated.
BASIC routine is not cataloged
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The "DSU" prefix indicates that ForceFail is a user-written routine of some kind. The error "not cataloged" usually indicates that the routine has not successfully been compiled. If you imported from an export file in which the executable code had not been exported, this is an equivalent situation.
The process of compiling a server Routine also causes an entry to be placed in the "catalog" (actually the VOC file) containing the location of the executable code and, possibly, other information about its mode of execution. If compilation is unsuccessful, the cataloging step does not occur.
Another possibility is mis-spelling or mis-casing. Routine names, like most other things in DataStage (server) are case sensitive. Is the actual name of the Routine "Forcefail"?
The process of compiling a server Routine also causes an entry to be placed in the "catalog" (actually the VOC file) containing the location of the executable code and, possibly, other information about its mode of execution. If compilation is unsuccessful, the cataloging step does not occur.
Another possibility is mis-spelling or mis-casing. Routine names, like most other things in DataStage (server) are case sensitive. Is the actual name of the Routine "Forcefail"?
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.
Further cause
I ran into this same problem, but it seemed unlikely that the routine name was misspelled because I selected it from a drop-down list in a routineActivity stage.
After reading the advice in this thread, I found that I had selected the function from the list, then went and changed the name of the function in my development ....so it didn't exist by that name anymore. I just had to change the routineActivity to point the the newly named routine.
After reading the advice in this thread, I found that I had selected the function from the list, then went and changed the name of the function in my development ....so it didn't exist by that name anymore. I just had to change the routineActivity to point the the newly named routine.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: