DSXchange

"All requirements"? Including anything people could possibly think up after a feature has been released? Ok. Have you tried it in conjunction with the 'Automatically handle activities that fail' option? That is how it typically is leveraged. Only define 'Ok' triggers in your job and then let the Seq...

More of a database than a DataStage question. If I was in your shoes, I'd start by chatting up my DBA. Or posting this question in some kind of a DB2 support forum. And posting here, of course, someone will probably know. I'm guessing you could also write your own, incorporate it into the job itself.

Congrats Chuck! Err... Jules! Err... what in the heck *is* your name?

Nice... a first post with no narrative, no "how-de-do", no "here's what I checked", nada - just the generated orchestrate errors, waiting to be rescued. In the wrong forum, no less.

I'd be wondering, too. Never heard of it.

I'm sure there is, but you should give a better explanation of what 'based on Id1 and Id2' means to get more accurate advice. This would typically involve stage variables, doing a little 'group change detection' dance and constraining the output to 11 max per group. Actually, that's a Server answer ...

Actually, it works just fine. Ensure that any database warnings abort your jobs, there are several ways to do that.

Or write your own more smarter mechanism tailored to your specific requirements.

That too.

Have you read the help on the filter option? You can't do things like that there. You need to execute a command that writes to standard out and optionally also reads from standard in. The output of the command is streamed into the stage and read as if it were a 'virtual sequential file' so to speak...

Ok... I'm still questioning the need to do things like this on a weekly basis, it just seems total overkill to me. Am I missing something here? Is this something that other people do?

Check sud's post... he was asking where you were actually running the job and showed some code to do so. Basically, a controlling job or 'batch' would need to read in your parameter file, attach to the job in question, set the parameters values and then run and monitor the actual job. If you are run...

This error does not give in only in one job, gives to all that one has select and one insert. These jobs functioned before, only that I migrei they stops another environment, and started to give these errors. So, since they functioned before and now no longer do, my note does not apply. You'll need...

This error can occur if you are sourcing/targeting CLOB (or other large) fields and you don't declare them properly.

Stopping not equal failing. The job must abort in order for the checkpoint restart to pick up from that failure point.

I call this routnie in beforeJob subroutine and in Input Value : /home/abc/filename.txt Is this the right way to pass teh values or some other way. No... and this is what I was worried was going on when I read the first post. You cannot set the parameter values of a running job, which is what you a...