DSXchange

I know I can get this done in a server job using file2 as a hash file and a transform stage with 2 or 3 stage variables. Does anyone know how I can get this done in a server job? This confuseth me. Did you mean for the first "can" to be a "can't"? Still, you can get this done putting file2 in a has...

I would think you would be able to do this with a Merge stage, provided it exists in the 6.x release. Otherwise, load it into your db of choice and 'join' there.

The syntax has been posted here and Vincent (of course) has a blog on the subject. Check this post to get you started:

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

To answer your question, a post can only be deleted if it has not been replied to.

Welcome! :D

Is this the same problem as posted here?

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

Sounds like you may have a metadata mismatch at work here.

RudreshEswarappa wrote:Please can anyone help.

The short answer here is - run fewer jobs at the same time. Simple as that.

How exactly does one run an infinite number of jobs at the same time? Did you miss the Mr Rollie Eyes icon signifying... well, sarcasm?

You can 'pass' parameter sets from the command line with dsjob much the same as individual parameters.

How about some details... details are always good and we seem to be severely lacking in them.

What is the definition of the PUB.poel field in the Progress database? Same for the Oracle field you are sourcing from. And lastly, what is the metadata for each field in the job?

The message is pretty clear, did you check to find records where the length of that field won't fit in the Progress database?

Column proddesc in table PUB.poel has value exceeding its max length or precision

No, but you can create a lower-case version of the string and compare it to the original to see if they match.

ps. Strings are not 'case sensitive' but comparisons can be. Do you mean you need to ensure a string is in all upper case? Or not entirely lower case?

And? What have you tried?

A Sequence job would solve this problem easily along with a routine that captures that parameter value.

As I noted earlier, and completely irrespective of DataStage, that leading dot your posted message showed is indeed invalid. You either need to ensure the schema is there before the dot, which makes it an 'absolute path' in a manner of speaking or you need to not have the dot. That would make it equ...

Please be more specific in your requirements, there is obvious confusion here. Are you looking to generate a record per day for that given month and year?