DSXchange

The only way to avoid creating an empty file as output is to not run the job when your input would produce zero output rows. Perform some sort of preprocessing step to check.

Kumar need to fix his link to not include the 'sid' (search id) information.

You do this every week?

I don't recall ever needing to do anything like this unless SHGVVW - Something Had Gone Very, Very Wrong.

Or load a second copy of the table and when the load completes, swap it in for the original.

Keep in mind the fact that Example #1 is using an OCI stage to do a reference lookup... and that it will fire once for each row through the job. I would imagine the overhead of doing parallel queries on these singleton selects explains the increased execution times.

If your 'timestamp' comes in in a consistent format, both pieces can simply be sub-stringed out.

You will need to make sure that this job can run in parallel by yourself - for instance by checking to see that any output or interim sequential files have a unique name by instance. As Arnd notes, there's more to it than just checking off a box. I wanted to highlight this sentence because it is cr...

Actually, Arnd meant: You could do it from the command line using...

... and you better select as many fields in your query as you have columns in the stage, and do so in the same order.

Ok... I'm going to take a step back from this. For some stoopy reason I thought we were discussing Oracle and now I see it's DB2. Doh! I'm not certified for solo flight in a DB2.

A series of 'If then else' checks, starting from the 'back'. Or check into the Oracle 'COALESE' function if you have that available, it may help.

No.

Actually, my point was around the issue of the 'default value' blocking sending that value in 'normally'... it doesn't. I have no idea why you can't send your 'high nines' time in directly but then you've never specified the actual error you get when you try to do so - or what your derivation or SQL...

Define the 'different results' you see in a transformer. And if you're going this route to the summit, I suggest a slight modification: Ans = 0 UnixCommand = "wc -l ":Arg1 Call DSExecute ("UNIX",UnixCommand,Output,SystemReturnCode) Ans = trim(Output<1>)

ArndW wrote:You are going from CHAR(1) to CHAR(2). Use explicit padding of one space in your derivation...

Isn't that... completely unnecessary? Since when will char fields be right justified? Just map one to the other, no extra who-ha needed.

Ok... you've never been able to 'multi-run' jobs like that that I've ever seen. What would be so wrong with starting them one after another in quick succession I wonder? Or what's so horrible about the 'put both jobs in a Sequence job' idea?