DSXchange

# and $ sign are reserved signs in DataStage, so maybe it is possible to use the internal representation of the signs in your select statement? Tried that but still no luck it shows the same error Can you show us exactly what you tried? Did you notice that there are two underscores on each side of ...

Just wanted to let you know I split this out into your own topic - so you have control over its fate - and linked back to the 2005 topic for you.

Perhaps this 'junk' is in your source data?

You should be asking that question to whomever administers that system. They should be controlling the actual mechanism you use to perform the delete and handling the permissions required.

Food for thought - with no mechanism to control if the after-sql fires another path might be a link to an aggregator set to Last that you direct to the status table. Link ordering can ensure it arrives after the main data and thus should only commit if the main data flow is successful. FWIW.

I don't recall that running a job would lock it but I'm sure someone will be along to correct me if my recollection is faulty. Editing the job certainly locks it and we had lock issue with people who couldn't be bothered to log off at night or who broke their connections and left orphaned locks. Loc...

Not that I recall. You'll have more issues with locked jobs than running jobs, I do believe.

prasad v wrote:As per my concern, this should be sequence number as i am maintaing max sequence number in a file. if we have gaps in seq.numbers. We will get duplicates sequene numbers second run

I don't see how you get there from here. Gaps = duplicates? No.

That or go back to the 8.3 pathnames that are under the so called "long pathnames" nowadays. Program Files would typically be Progra~1.

Sounds like your dataset is corrupt.

Let's get this out of the way first. Surrogate values have no derived meaning or intelligence behind them, they just 'take the place' of the business key. Because of that, having 'gaps' in the sequence is meaningless and not something you should be worrying about.

I don't think so...

Apparently. I think they're just there to show what has been done as the links expire after a certain amount of time as they are to the actual live webinar. Perhaps, if they have been archived in some manner, they could be redirected to the archive. An email to the Editor (editor@dsxchange.com) migh...

Out of curiousity, what exactly are you doing 'after sql'?

Correct... unless you can conditionally make the call. I've done something similar in the past where I call it once when the first record comes through and then never again as I know it would be a waste of time. To do this on the last record, however, would be a little more problematic unless you ar...