DSXchange

SURA wrote:I have enabled it and mentioned it in my post.

Actually no, no you didn't, at least not clearly. You did mention the word 'microseconds' one time and say something about 'enabled to timestamp' but that doesn't exactly clear it all up for us.

I would have asked the same question.

I don't know... they use the word 'append' in a pretty generic sense which leads me to believe they are not equivalent: by default the IBM InfoSphere DataStage appends to existing tables, you can also decide to create a new table, replace an existing table, or keep existing table details but replace...

I'm not aware of any way for auto-generated queries to include hints.

Ah... so it was specific to SQL Server. Good thing it was a known issue with a patch available for it.

Ah yes, was going to chime in a little earlier that it seemed a bit... nonsensical.

Just guessing here, but if that uses standard Windows functionality you should be able to shift-click to select a range or control-click to select multiple individual entries. Any chance that works?

There isn't one, you'll need to build your own or call a service, something of that nature. Never mind the fact that conversion rates can change frequently so trying to build one yourself is pretty much out of the question, I would imagine.

Rounding afterwards is straight-forward.

So for whatever reason it seems it was corrupt. Marking as resolved.

All that being said, what are you trying to return? Is 'x' some kind of value or values or is it just the status of the procedure run?

Oh, I completely agree... just answering the question as asked. :wink: I've advocated here before several times your same approach, disconnect any status or stats gathering from the jobs themselves and do it all as a 'post' process. I don't want failures in that gathering effort to interrupt the loa...

When I use in the job a stored procedure stage, it have two output fields ProcCode , ProcMess How can I populate those two variables from the Stored Procedure. Do you actually mean two input fields? If they are output fields, the procedure is already populating them, I would assume. Also, when I do...

In all honesty, no. I don't see how DataStage could possibly override what happens inside the stored procedure and if it is coded to do work in 'chunks' and issue intermediate commits, I don't really see how DataStage running it would be any different from you running it. All the stage does is wrap ...

Since we don't know how you are running these jobs, it's hard to make good suggestions. At this point I would say a Sequence could do all that. Your after-job script is never going to know anything other than the job is still RUNNING, as you've found. :idea: Your script could be run by an after-job ...

Sorry, forgot you said you were calling a script. I assume you are using dsjob -jobinfo to get the information you are after? Unfortunately it doesn't show the interim status. I'm curious, what does the script do once it has the information that it needs, write it to a file perhaps? You'd need to wr...

As I said:

DSJ.JOBINTERIMSTATUS Returns the status of a job after it has run all stages and controlled jobs, but before it has attempted to run an after-job subroutine. (Designed to be used by an after-job subroutine to get the status of the current job).