DSXchange

Funny, but Chris here seems to look an awful lot like adams06. Why post this again under a different name?

ps. Asked and answered in this post. If you feel like you need to add something to the conversation, add it there.

This is more complex as it seems. In case 2, there is a missing value, so two delimiters are required. Not according to the OP: 2. OUTPUT TWO I NEED TO FORMAT TO D - F WHICH I HAVE DONE IT BY USING "CHANGE FUNCTION" In all cases, it seems like there should be a single dash between any non-null fiel...

Actually - technically - protected is different from read only. Regardless, neither should be the cause of the issue or cause any changes in job behaviour. Unless 'protected' here means something other than 'running in a Protected project'...

If you'll always have a FIELD1, that simplifies things. In any case, the concatenation is the dash and the field in question, if the field is non-null. If FIELD1 can be null, then you need to track the first non-null field - that one doesn't get a dash. Any non-null fields after the first non-null g...

Keep in mind the fact that the before and after tabs are completely isolated from the 'main' processing the stage does. Just because you are deleting from the right place 'before' and inserting to the right place 'after' has no bearing on what goes on in the stage. Other than the fact that they all ...

Then perhaps they loaded somewhere other than where you expected?

What does the job's log show? Warnings?

You are correct in that it is 'enforced' when transferring to a passive stage like an RDBMS stage. In my experience, the warnings noted in the original post are generated by DataStage because the size declared in the job is smaller than the actual data. DataStage then truncates the data so as to not...

Typically because you've defined your metadata as having a size of 1.

For a little less... terse... example of the technique, check this FAQ posting on the same subject.

The 'today and tomorrow' options which cause your error use the at function to do the actual scheduling. You can see that in the error message. The other less troubling ones use cron. As a guess - since you've never verified if you have checked this after several mentions - is your userid has permis...

I don't really see the point of using ExecTCL over the ExecSH I assume you were using before that, but I'll leave that between you two. I'm also wondering why you need to do this after stage ? I don't really know if this would help but the more 'traditional' approach would be to call the sqlplus scr...

As noted early, please post your actual question over in the appropriate forum.

I'm curious why you'd think that Ascential would provide a core routine for several years now that had such a obvious fatal flaw in it? And while the routine will certainly get called several thousand times in a normal operation, you'll see if you look at the code that the hashed file it leverages i...

Actually, it is possible from a Job Activity stage. After building the noted routine to return the InvocationID of the master Sequence job, use the dreaded three-dotted External Parameter Helper (yes, I know they are called 'ellipses' but that's a scary word) to put that returned value into any down...