DSXchange

As I'm sure you're aware, without any kind of diagnostic information it's going to be hard for anyone to help unless they've seen the exact same nebulous message before. Have you checked some of the things it might possibly be - tablespace, unique index, constraint issues, etc etc? If nothing really...

Poor old ClickPack, we miss her.

Hackery, Gentlemen, I cry Hackery! Sorry. :wink: You would use that Masked Decimal conversion with OConv if you had data without a decimal point that you needed to add one. And I believe that with IConv the opposite would be true, that it would remove them. However, don't have access to a system rig...

Sorry but that's not the way things work here. :? First of all, the convention is one post per question or issue so dumping fifteen in all at once is a definite no-no. But the biggest problem is the nature of the questions - we do not provide answers to what are patently interview questions. While y...

Can you post the complete, unedited error message(s) please?

All of those error codes are documented in the dsapi.h header file in the $DSHOME/include directory, from what I recall. FYI. Perhaps in the online help as well.

That doesn't make much sense and I have no idea how a downstream Join stage would cause that kind of error in an upstream SP stage.

Unless someone else has anything, I'd take this to your official support provider and see what they think is going on.

What exactly do you mean by 'not functioning' or 'not in action'?

From what I recall, this: Job Aborted after Fatal Error logged. Program "DSD.WriteLog": Line 315, Abort. Is the result of a call to the DSLogFatal function, a conditional user controlled abort and unrelated to the 'zero length string used' informational message or anything else we've been ...

Hmmm... I thought for a moment you meant mine was.

Another common technique is to write it out with a static name and then rename it 'after job' using O/S commands to include the date and time if required.

Do you have a timezone issue?

Command Output is a dynamic array rather than a single value, with returns being converted to Field Marks. Remove them then check:
Or reference just the first array element:

Not quite sure what 'work like this' means. Are you certain that your triggers are firing like you think they should? Meaning, in Seq2 whether or not Seq1 finishes correctly it sounds like it may always be taking the Otherwise link. Have you added any 'logging text' to each stage to know which path ...

That seems a little... over-engineered to me. Why all the extra user status shenanigans? You should be able to do this using 'regular' job status checks.