DSXchange

I believe the OP is also asking about stage status. This can be waiting (yellow link), running (blue link), finished (green link), aborted (red link). Unless you've customized the colours.

Is there any formula or heuristic for determining a new value, other than trial and error?

There is nothing out of the box. You could write a plug-in stage, but it's probably not worth the effort, particularly if you already have a custom MDX. It might also be worth checking on what has been asserted by the "MS guy"; after all, if the product supports a CREATE CUBE statement, then surely ...

Do you get the same error for both locations?
Is this the pathname of your master projects directory in your run profile?
Do you have write permission in the target folder?
Is this error occurring when deploying a job? If not, when?

There is a compilation option for job sequences that requires a warning message to be logged if a job under control finishes with a status other than OK - look on the job properties tab. Yes, I believe Kim is referring to a message handler. There will be a paper or video on DSXchange early next year...

Solutions given thus far do not verify that xyz at the beginning of the address and to the left of the @ symbol is the same as the xyz immediately to the right of the @ symbol. Is this, in fact, part of the requirement?

Why do you think one of his job titles is "analyst"? He could (should?) have pointed out that what's postulated is not even possible in a sequencer. It is, of course, possible in a job sequence. The only thing you can do in a sequencer is fire its output trigger(s) if any or all of its inputs have f...

If the source is a database where NOT NULL constraints are enforced, then you do not need to check. If the source is, say, a text file (where NOT NULL constraints are meaningless) then you do need to check. It's not a lame question - it's a good question, and highlights the fact that DataStage serve...

This design will not open the file for reading until it has been written to and closed by the writer, therefore the Transformer stage will wait. -----> SeqFileStage -----> TransformerStage -----> But a modular design in which one job creates the file and another reads it, is easier to maintain. And ...

Read my last sentence again. Are you really being concerned about the "removing printer shared memory segment" message, or about something else? I see nothing untoward in the output of uv -admin -info in your post. You can install DataStage server wherever you like (except the root directory); that ...

If you can specify under exactly what conditions you want an abort to occur, then you could create another job (Job Control code) that polled for those conditions and issued appropriate DSStopJob() calls. Have you investigated a Terminator activity in a job sequence? That does much the same thing, b...

Prevent the abnormal terminations from occurring - train your developers to disconnect properly. As you may know, this message is informative - it's only a warning because it's an "unusual" event - does not occur every time. You will ALWAYS get this message from the uv -admin -info command if there ...

You would also find it in the Server Job Developer's Guide because a job sequence is just a special case of a server job (and that's the main reason that server jobs aren't going away any time soon).

Might be worth asking your local SAP experts or SAP support provider.

What Vincent suggested can be accomplished by removing duplicates from the reference Data Set. Of course it is sometimes legitimate to return multiple values (and thereby to generate more output rows than you have stream input rows), for example when performing a range lookup or a lookup against a s...