DSXchange

Deep thoughts Kim, deep thoughts. Well said, well written, deeply motivated, or shall I say, excellent. I agree with whatever you have to say, especially in your last para. Folks like Ray, Ken, Arulan, Craig and yourself are true gurus in the field of DataStage and DW, have a keen eye on excellence ...

sylvan_rydes wrote:Hi Craig,

Suppose the number is 5489275482321009. Then what will be the equivalent char to this number. Isn't it simple?

Sylvan

I still did not get what you wanted
Do you want that number to be represented in words? Kinda lost with your terminology.

Give us an example. What it looks like and what you want? If you want a number to be converted to words, then clickhereto get the routine Craig is talking about.

chulett wrote:Me thinks the young Padawan means DSLogWarn, DSLogEvent is used to do the equivalent in a different job from the current job.

My fault in mis-interpretting your statement there. But as you said, all aspects are covered

MetaData mismatches are often the result of "Human" entered metadata, which is, usually, the case with flat files and datasets. For databases, we import. And hence my hunch that its either a dataset or a flat file.
No mention about it by the OP.

Or simply check JOBINTERIMSTATUS rather than JOBSTATUS. From the online help: 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 sta...

select A.col1, A.col2, A.col3 From myTable A Inner Join (select col1, Max(col3) As MaxCol3 from myTable group by col3) As Temp ON A.col1 = Temp.col1 AND A.col3 = Temp.MaxCol3 Pass the above query in your database stage. Depending upon what database it is, the syntax might vary, but ...

Dont datasets support rejected links. So do sequential files. You dont need to check for it inside the transformer. The reject links will take care of it. As far as I know.

For the current job yes, but Log a warning in the log of another job, no. That was because we were guessing if the warning was to be launched for only the current job or all the job at the "same level" as per the OP's question. If the latter was to be done, it would not have been possible from with...

DSLogEvent() was to be wrapped in a routine. But no need, UtilityWarningToLog() is what you needed. You can mark the post as "Resolved" now.
I know Ray, me a grasshopper

ray.wurlod wrote:UtilityWarningToLog() is doable from the current job.

For the current job yes, but Log a warning in the log of another job, no.

chulett wrote:Me thinks the young Padawan means DSLogWarn, DSLogEvent is used to do the equivalent in a different job from the current job.

That wont be do-able from the current job. What is do-able is to log a warning using DSLogEvent() and leverage the execution at the sequence level. Right?

Look into DSLogEvent().

ray.wurlod wrote:Then clearly you must demand that Microsoft and IBM get their act together so that you can!

If only we were in wonderland [sigh]

gup wrote: IBM stated it is possible -

Is that all that IBM said? Is that all you accepted from IBM?