DSXchange

Are ranges always an integer value? Will you support date ranges? Are ranges inclusive? e.g. is 500, 501, and 502 all part of (500-502) ? Or just 501 ? example broken out by fieldes: LOOKUP rec . INPUT rec 01: 123 . 123 . = 02: % . 167 . = % matches anything 03: NOT50 . 7362 . = 7362 <> 50 04: (200-...

Did you check the error log (C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\.convert.4472)? I looked (on the qs-server machine); no such file. I looked for the msg "produced errpath" , because that is the msg in the log output, and I got hits on these files: ipe_srv.exe qsserv.exe Digging into qsserv...

This is a deploy-only to a remote machine. The job deploys and runs clean when processed 100% locally (e.g. the QSDesigner & QSServer are both installed on this workstation). For our exercise, we're trying to make the same job run on a remote QSServer. QSDesinger running in winxp. QSServer runni...

"What's in a name? That which we call a black-hole
By any other word would yet mightily suck."

eostic wrote:I love threads like this. Especially sweet for Valentines day. Shows how much we all adore this product.



Ernie

You need to look for the use of EventHorizon jobs. These are dangerous because once your project exceeds the critical threshold of complexity, time will begin to slow and eventually come to a complete halt. This often, but not always, includes all aspects of time: development time, run times, debugg...

What kind of error message would you get if the server your shares live on was rebooted? You come in the next day and the H:\ drive looks all happy. And... does "continuously running" mean CPU was working hard? Or the job was hung and just said "Running" in the Directory, but CPU...

The large load ran 100% without aborting, that is over 200 invocations just fine (it used to abort up every few dozen invocations). John G. You must be one happy fellow. :) Ahh, you don't know the half of it :) Each invocation ran about 6 to 8 mintues (closer to 8 or 9 as the target tables had more...

asorrell wrote:If this fixes your problem please post here to confirm...

The large load ran 100% without aborting, that
is over 200 invocations just fine (it used to abort
up every few dozen invocations).
John G.

If this fixes your problem please post here to confirm... So far, so good. I'm running a large batch of records (200,000 main records, each with about 30 to 60 associated helper records in various tables). Anyway, for the last month I would launch this batch to run overnight. It would usually abort...

Thank you. I will plug APT_NO_JOBMON into my dsjobs and let everyone know how things turn out in a few days (we have a big run coming up this weekend!). John G. So on our production system we set APT_NO_JOBMON (I think that is right) to True - to totally disable jobmon on that system. Since then, no...

Can u post the complete log..i got this error many times My SIGKILL has returned. I think this is the "complete" log; with any luck you'll look at this and say "Don't do thing X, that is stupid" and I'll come away from this being smarter. dsjob -logdetail mdirqa flatcols04b 5816...

Manual-anything will tend to suck... both for the volunteers that verify things, and would-be account holders that end up waiting over weeekends, or vacations, or crunch-times to be verified. At account creation time, throw in an image-test ( http://en.wikipedia.org/wiki/CAPTCHA ) in to help weed ou...

pavankvk wrote:Can u post the complete log..i got this error many times

*sigh* no, I've run it since than and auto-clean wiped it.
If it blows up again, I'll do that.
I almost want it to blow up now, it has been 200+ invocations
since the last abort and it is now presenting the illusion of being solid

I mean, how does a program not write an error message if it dies? If it's killed with SIGKILL it may not get the opportunity to. That is a good point... I'm used to SIGKILL coming from humans, e.g. $ kill -9 pid If something external to DataStage is killing children, I need to have a talk with that...

To narrow down, try running the job in a single node config file, so that, you can eliminate lower down the number of processors running for that user. And can confirm, whether its related to number of processor/user limit. I'm hitting SIGKILL problems now, so I'll chime in here. Things run fine fo...