DSXchange

DateFromDaysSince() function should do it for you. The days offset can be negative.

You may have quite a wait until U logs in again; he hasn't posted in a while (but may still be lurking). Why do you specifically want U to help in any case? U's profile shows only beginner level.

And is plz somewhere in eastern Europe or the Balkans?

Create (probably as a constant in an upstream Transformer stage)

and include that in the pivot.

If EMP_ID can be null from source you must handle this explicitly. Functions such as Alpha() and Num() can not accept null arguments. Calculate stage variable svEmpIdTest as follows. If IsNull(InLink.EMP_ID) Then -1 Else If Alpha(InLink.EMP_ID[6,1]) And Num(InLink.EMP_ID[5,1])...

To work from a lookup you need a WHERE clause that mentions the Key column(s) bound to parameters. SELECT whatever FROM wherever WHERE KeyCol = :1 You could have reference to a sequence in the SELECT clause I suppose, though I struggle to think of a good reason when you can add one to a variable in ...

You never know with exec. Could be the address of a pointer to a cursor structure, or something. Try something simpler, like SELECT COUNT(*) FROM DUAL and build up from there. It's more usual to use CALL with ODBC to execute stored procedures. Try that instead of EXEC. Otherwise investigate using SQ...

Yes, but not elegantly. The only "pull" solution is regular polling, as you have identified.

That suggests that the old job is not in a properly deleted state. Did you rename it before importing? If so, delete the renamed job (using a DataStage client too). This will delete all the "support files" properly.

No!!!!!

You don't know which they all are, and you would still leave the VOC entries that point to them in place.

Run the command DS.CHECKER, whose task it is to clean up such orphaned files.

One of the support engineers at VMARK (who is still with IBM support, so shall remain nameless) suggested two additions to the CPU instruction set that would be useful in this circumstance.

HCF (halt and catch fire)

HEK (halt and electrify keyboard)

Now them's real warrior words!

The elegant way is to have the other application trigger a DataStage job that is set up as a web service, once its computations are completed.

That is the strangest definition of mantissa that I have ever encountered, and I believe it to be wrong. If the field is a string, use Field(InLink.TheField, ".", 2, 1) to identify that component following the decimal placeholder ("." assumed) and compare that against zero. If the field is a decimal...

Even then thousands of log messages may already be buffered for writing. You need to find a quiet point, then clear the log (which you can do from Director). You clearly also need to correct your job logic to avoid committing the constraint violations. Use a "look before you leap" strategy: perform ...

Oconv(InLink.GivenDate, "D-YM[4,2]") : "-01" is the first day of its month if GivenDate is in internal format. If it is not, apply an approriate Iconv() to GivenDate within the Oconv() function.

The function I have already given is the first day of the current month.

The rest is arithmetic.

And, of course, pass invocation ID fully down the chain of controlled jobs and job sequences.

Incidentially, the term is "sequence", not "sequencer". As you will see on the Palette, a Sequencer is a component that you can use in a Sequence.