DSXchange

chulett

It hasn't been running for several days, but rather flagged as running. There are times when jobs can fail and not update the status shown in the Director, which just shows the last known status. If you know for a fact that the job is not running - you've grepped for the job name amongst any phantom...

chulett

The return value of a simple command is its exit status, or 128+n if the command is terminated by signal n. So your script was terminated by signal 13, which is SIGPIPE. Not sure there's anything simple about this, both times I presented it to IBM Support they couldn't tell me where it was coming f...

chulett

Can you please check the timeout setting in the administrator. This issue normally pops up when the time out is set for say 1 hour and the job runs for more than the the timeout set . Don't think this has anything to do with timeouts - at least not in my experience. In my exposure to it, it was hap...

chulett

I can't imagine this isn't documented.

chulett

Sorry, if I had had more to add I would have. I don't have access to 8.x nor PX at the moment, and the 7.x docs don't mentioned anything about using a file that I can see - only an optional job parameter to seed the sequence. And no, you wouldn't use your install path unless that's where your file i...

chulett

If you feel like helping, do so over in the other thread that goutam (properly) opened for this:

http://www.dsxchange.com/viewtopic.php?p=266777

chulett

goutam wrote:Should this file be present in windows drive??

It needs to be local to your DataStage server, regardless of platform. What's in the help is just an example.

chulett

Asked and answered quite a number of times here already. Search for a key portion of your message, say "RPC daemon is not running", for discussions regarding how to debug and determine the problem. Typically, something has the port it needs in use and thus the 'bind bombs'. Problem is, without debug...

chulett

Or create a reference hashed file with the values you are interested in and lookup when rejecting.

chulett

Reported as working with parameter sets.

chulett

Actually, if you've added an Environment Variable as a job parameter and assigned it a non-default value at runtime, then it *is* changed for the duration of the session. So I don't really think it would fail.

Simple enough to test if one felt the urge.

chulett

chulett wrote:Data in but not out of that stage would imply your XPath Expressions couldn't be matched back to the XML.

chulett

Contact your official Support provider.

chulett

AttitudeBaz wrote:I have hundreds of Universe Stages within our datastage jobs to simply store their data between various jobs.

Curious why you chose that route rather than using, say, a sequential file for this task?

chulett

Or seems to me you could just reference it directly in the script - $VariableName or ${VariableName} for example.

DSXchange

Search found 42189 matches

Re: surrogate ket generator stage

Re: Universe read / write performance