DSXchange

You could use:



I believe it always wants to add a delimiter to the date. This uses a Transform to strip out all non-numeric characters.

Exactly. That and a big stick. Helps with the 'enforced' part.

Um... how do you know, Tony?

The downsides? Mostly what I've seen is either the buggy way it was implemented or just the fact that it is the nature of the beast. This impression may also change from version to version. Heck, Ascential sent of a big alert yesterday for anyone using the 7.5 Enterprise Edition to download 7.5a ASA...

Or what Ray said.

datastage wrote:The function is a simple as:
Call DSLogWarn(JobName, "Sequencer called jobs with warnings")
Ans = ''

You've got the arguments backwards.

Sit down. Have a cookie.

Well, that explains that! Places I've been have always used a single userid for the running of the jobs.

You need to use single quotes around the job number.

Not that I am aware of, as the check it does is a fundamental part of the engine as far as I know. Others may know better, however.

Kind of funny, but I've been doing this since 1998 and I've never seen that message.

Ahhh... then they're not really duplicates, are they?

I agree with and understand your basic premise, just having some fun with ya, V.

I think you are correct, Mike. The "Fully Generated Query" option is to be avoided, in my opinion. It's only there because they needed to say they could provide that functionality, even though it is a PITA to use. As you said, you can't simply modify a portion of your query, you have to rebuild the ...

First row, I believe. The only 'workaround' at this point in time is to use one of the two stages that support that functionality - the ODBC or UV stages.

Vincent, a 'union' by definition removes all duplicates. You have to specifically say 'union all' to retain them.

It was introduced in 7.1, which is why you don't see it - yet. Take a peek at this post where we discussed how it is meant to be used and I posted an introductory snippet from the 7.1 readme.