DSXchange

Sorry, still looking for a precise description of the problem. What is "not correct" about the output you get from Project B? Can you show us what you get versus what you want / expect?

Explain for us what "not working properly" means.

Funny... almost asked if you had logging enabled in the stage.

Still think it is better as a "pre-process". Run something to check all of the files and if any are zero, send out a alert and don't process any of them since that seems to be your requirement. Or check each before the load and only execute the job if there are records to load, otherwise a...

You posted in the Parallel forum yet marked your Job Type as 'Server'. Not sure it ultimately matters in this case but can you clarify which job type we're talking about?

No possible. Zero records in the source means nothing flows through the job.

It's not correct... note that the input value is "20140225 060253" in both cases and the second value is the time.

I'm assuming you're talking about a generic "start a DataStage job" script / process, yes? We kept ours simple... pretty much just check to make sure the job exists and is in a runnable state and then whatever was needed "post" to determine what happened or to capture whatever yo...

I think Ray meant Prasson, his is the PX specific one. And it just looks like a cross join from the very small sample data posted but I doubt it is - so the Merge stage should be able to handle the two files directly without any shenanigans.

Again, clarify for us any transformations that you are doing. Your source is what, a string? And then you do what with it to convert it to a timestamp?

For that you'd need the parallel version of EReplace, posted here as pxEReplace by (most recently) the user PhilHibbs. However, I seem to recall it being... leaky.

There's an official IBM version but from what I recall, you'd have to upgrade into the 9.x world to get it.

It's not one of theirs. This may help or get you pointed in the right direction:

http://www-01.ibm.com/support/docview.w ... wg21642236

Sorry, I missed the "used to work but started misbehaving today" part. I thought the error started when you added the Execute Command stage.

Why don't you post the contents of the Execute Command stage so we can see your 'settings'?

I prefer the operator over the function, but six of one...

input[1,4]:''-'':input[5,2]:''-'':input[7,2]: <etc>

Opened them.