BASIC routine is not cataloged

raju_chvr · Post by **raju_chvr** » Mon Nov 03, 2003 1:53 pm

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.

mfortuna · Post by **mfortuna** » Mon Nov 03, 2003 3:01 pm

I think I saw this when I tried to run a Sequence job and the routine was not compiled, for example when you import the design of a set of jobs/routines.

Try compiling the routine and then running the job.

ray.wurlod · Post by **ray.wurlod** » Mon Nov 03, 2003 3:40 pm

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"?

dickfong · Post by **dickfong** » Tue Nov 04, 2003 12:42 am

If ForceFail is the routine that you've developed and you want to call it in another routine or DS basic code. You should use the DEFFUN function to define it before use.

DF

rdy · Post by **rdy** » Fri May 14, 2004 11:22 am

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.

ray.wurlod · Post by **ray.wurlod** » Fri May 14, 2004 4:29 pm

Yep, that'll do it!
It's like continuing to write the old year in dates for a couple of days into the new year, and we all do that.

DSXchange

BASIC routine is not cataloged

BASIC routine is not cataloged

Further cause