(Sequence) job "silently" fails to get started

Problem

We call a DS job by its but DS does not seem to show even the request. Well, the caller gets an according message but other wise, Directory remains unmoved, logging does not seem to apply. Due to lack of permissions I could not double check it myself but I trust our DS admin.

Causes

a) Calling a sequence job with invocation id that does not allow multiple instances

Well, yeah, DataStage does not allow that for whatever reason.

b) Passing a parameter not specified to a (sequence) job

Again, it seems picky to me.

c) Not passing a parameter specified without default value to a (sequence) job

I did not actually test this (yet), but it seems logic to me that DS must fail.

Solution

a) Remove the respective tick in the general tab of the job properties dialog (probable on the upper left corner).
b) Remove the passing of the parameter (or define the parameter in the job properties and use it - there might be a reason that the parameter gets passed).
c) Pass the parameter (or remove it from the definition in the job properties).

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

Error when checking operator: Could not find input field 'field_name'

Well, you checked and double-checked the existence of respective field and it is there! Yeah, stumbled over it again. And again! Possible solutions You need to compile jobs explicitly. You're done then. Try it. Go! What are you waiting for? If you are really extra sure compiled the job, then double-check the presence of the respective field again, but not in the stage DS tells you but in the very source at the start of the dataflow where this field comes from. It happens that if the column name of your SQL is not identical to the field name propagated. I do absolutely not know why: compilation does not reveal the problem DataStage misses the correct problem location by far
Mehr anzeigen

Missing record delimiter "\n", saw EOF instead

Actually, this warning is quite simple to fix. Apparently, DS expects the last record of a file to terminate with the record delimiter in any case - maybe there is a setting to alter this behaviour but I did not deem worthwhile the effort to look for it. So the solution is just to terminate the file on a single empty line. Obviously, this case is for Unix like line breaks. The others delimiters are handled analogously.
Mehr anzeigen