DSXchange

I don't have DB2 here but don't recall it using numbered parameter markers, I thought that was strictly an Oracle thing. Are you sure that :1 shouldn't be a ? instead?

mydsworld wrote:So, does 'Wait for file' waits for the receipt of the file in full?

No, it simply checks for existence.

As noted, the typical solution is the use of a zero byte 'flag' or 'semaphore' file sent after the main file. When it is received, you know it is safe to go get the main file.

I would just bite the bullet and do this through the GUI, it's not really that bad and it will be over before you know it.

You could also export the jobs in question and use an editor on the .dsx file to make the changes noted.

opdas wrote:how do I exit from the loop? using terminator activity? but this would abort the sequence. Can I exit grace fully without aborting the sequence.

Just do a conditional branch to something 'outside' the loop, past the End Loop stage, to get out early and gracefully.

Then perhaps that's a PX restriction, what you've done would work just fine in Server. It matches the columns in the link to the parameter markers in your sql, it doesn't give a hoot how many column names you mention.

Stop by my house some time. I think I found the earliest mention that I recall making here when discussing generating test data. It was then extended to solve this situation where you read and update a hashed file in the same job... and yah it's quite cool when the light-bulb goes off in your head a...

A search for that error message would turn up quite a number of hits, I'd wager. And most would lay out the steps needed to check what code is causing the problem. For example, this one from yesterday:

http://www.dsxchange.com/viewtopic.php?t=118656

Post the complete error message, it should state a TRANS file and line number where the phantom error is occurring.

Sounds like you still have both columns in the output link.

Where / how often do you call this? Seems to me you may be able to leave it as and call it from a Sequence job, depending on the answer.

You need to check the individual job logs that had the warnings, you can't get those details from the Sequence's log.

Manually, month by month.

pravin1581 wrote:When we run any DS job from the designer, where is the executable file of that job is created and what is the format of that file.

Ok, I'll bite... why seek this knowledge, Grasshopper?

I don't see how you can expect a patch to fix a problem on an unsupported platform, but it can't hurt to ask.

We've documented this technique before here. And all you need for the constraint is @FALSE as no rows need to be processed simply to create or clear the existing hashed file, the link just needs to be 'opened'.