DSXchange

Yes, Server BASIC routines can be used in a PX "BASIC Transformer" with all of the caveats they bring to the table. Or, better yet, write them in C++.

I'm tempted to just say "yes", however... write or use? And of what routines do you speak of?

Silently in what sense... ignore any errors? What happens now when there is one? I use "dscmdexport", it creates a log file of issues and doesn't stop but I have no clue how dsexport handles problems.

If you're good now, please mark the post as Resolved using the button at the top of the screen.

If you don't want to (or can't) substring, then yes you need both to go from one external representation to another.

What did you try? Can you post what is causing your compiler errors? The formats are all in the online help, for example find IConv function (BASIC) in the Index, go there, scroll down to the Date Conversions section and then click on the "D" for a detailed description of that code and how...

Cool.

Ah... someone needs a good smack upside the head.

First IConv() with a mask matching your input format, then OConv() on that result with a mask matching your desired ouput format.

You'd have to reference the expression (again) in your where clause rather than the alias.

If there is a source issue job should not ran earlier, but it has ran earlier. Not a very good assumption. :wink: Seems pretty obvious you've got something different in your 'actual' data than you ever saw in your test data, something that it causing the job to implode. What that difference is I ca...

When your original design with buffering on gives you a problem and that problem goes away with buffering off, then yes I'd say it was a "problem of buffering". Of course, you'd have to specifically test that and let us know.

Should also be possible to query those separate field in such a manner as to get only records which have changed in the last 30 days. Might be a little goofy looking but I would think it could be done. Or maybe (YEAR*10000)+(MONTH*100)+DAY to build the date? With some way to ensure the month and day...

Depends on the stage writer. Won't be random but it could be the first, could be the last, may log a warning or may not... varies from stage to stage from what I've seen.

So... a Datacom sql question rather than a DataStage question. Afraid I don't know squat about Datacom, is there anyone you work with that can help with that?

Or you can just assemble the date inside your job.