DSXchange

If your topic is Resolved, please mark it as such. Thanks!

Welcome aboard, Paddy. :D Before we go any further with this, can we verify your 'particulars' that you marked your post with, please? There is no 6.x version of EE where parallel (PX) jobs will run on a Windows server, so could you let us know what those values should really be? Thanks. It will hel...

'Error 0' is kind of a catch-all unknown error on some systems, from what I recall. Still, as you said, not very informative.

Is your problem the fact that you can no longer 'compile' jobs? If so, why don't you explain the problem you are having rather than asking about logs and timestamps?

Only jobs with Transformer stages actually invoke the C++ compiler during compilation, otherwise you are generating OSH script.

That happens when you rebuild the indexes and you are not alone in the project. Yes, it can be rather disconcerting to go from a relatively small problem to what appears to be a huge one (OMG, all of the jobs are gone now!) but it should be easy to fix. Ensure no other clients are connected, jobs ar...

(I suspect, but have not proven, that the lock is released when processing of that row is completed.) Not in my experience. I was trouble-shooting another person's job and ran an unusually high number of records through it. It wreaked all kinds of havoc and every other DataStage process on the serv...

Ah... not wonder you couldn't check for a return value of 88. These kind of details are important to disclose up front. Have you looked at the source code for the ExecSHSilent routine? It returns a zero on success or a 1 for any failure. So your script may pass back an '88' but the routine you used ...

Yes. Yes. Been there, done that. *

I typically don't bother locking for update, don't really see the point, so just leave it 'un-cached'. Be willing to learn the errors of my ways if there's a good reason for the option...

ps. *Entire engine ground to a halt, not just my pitiful little job.

du supports the -k option as well, if you'd rather deal with sizes in 'K' (1024 byte) blocks than 512 byte blocks.

A Custom trigger expects an Expression there, something that evaluates to true or false. You know, like "X = 1" or some such. Having a singleton value - like DSJS.RUNWARN, which is a "2" by the way - means your expression is just "2". And since a zero is false and a non-zero value is true, that "exp...

I was wondering when you were going to figure that out.

What trigger are you using? Still this?

kaps wrote:In Routine1's trigger I am using custom(conditional) and expression as DSJS.RUNWARN.

ray.wurlod wrote:Get some more knowledgable friends.

Dang, beat me to it.

vsi wrote:or am i making mess of the design

That's a whole 'nuther question.

I don't know about 'quite common' but it *is* perfectly valid.

Link to another Routine Activity stage that calls UtilityAbortToLog.