DSXchange

A good measurement there is to use dump_score and look at the T-type stages (i.e. a modify stage or a transform). As an example, if you have a 2-node configuration and they are at only 80% CPU usage and when you run it with a 4-node configuration they are at 45% you are getting the same throughput b...

Kumar, that is not necessarily the case. Here with a 24CPU P-Series it turns out that a 1-node configuration is fastest for many of the jobs. Just as an example, take outputting to a database that resides on a remote machine. If the bandwidth between the DataStage server and the DataBase server is l...

Check pages 6-578 through 6-582 of the Ascential Datastage BASIC Guide

In most PX jobs the best performance may well be with 1-node configurations. The process overhead of starting and coordinating many parallel process usually outweighs the performance benefits for jobs that only process thousands instead of millions of records. As a rule of thumb I would default all ...

Craig - I hang my head in shame and won't make any more whacko, off-the-wall and unrealistic suggestions for several thousand more milliseconds...

Is this a job sequence or does it have Job Control code? It seems to be issuing a call to DSWaitForjob() that is returning the error.

The reason that kumar_s asked is that you have the following error message:

Toolkit\mksnt\sh.exe: Toolkit\mksnt\sh.exe: not found

You need to correctly install the MKS toolkit in order for this work.

The way to test this is to ... test it! I usually use several million loop iterations and store the value of SYSTEM(9) before and subtract that from the value after the loop. This value is milliseconds of CPU so if you can make your baseline conversion run for about 5 or 10 minutes then the results ...

What method were you using to load the data to Oracle? Normally the table will not have an exclusive lock taken against it. And a normal termination will commit or rollback automagically.

Were you using the bulk loader?

Unlikely that this is a bug, as it seems to be at the core of the external call. I have the same version (on AIX) and am getting a valid an correct string value returned in the command stage's $CommandOutput variable. I just did a very simple 3 stage job. In the first command stage I executed "cat" ...

I usually end up using "localhost" for the server address instead of the name - plus logging in with a userid and a password.

I don't think that the DSSetParam() is called as part of the Command execution. Your error message points to your Job_Activity_94 stage. Try doing a simple new job with just the command activity (do a simple one without a script call) and get that to work, then change the command for your script and...

Could your dataset or lookup fileset be from an older version? You can try to get some information on the file from the Tools->Dataset Management or from the UNIX command line "orchadmin describe {FilePath}"

I just tested a small script to make sure that the value of "{Execute_Command_Stage}.$CommandOutput" does work. Can you modify your execute command to do a simple "ls -al | wc -l" and see if you get a return code of 0 and some value? If this works then you need to look at your script and what it act...

The "patch" is an Ascential one and the tip did not come from me (I was the one looking for help) but from Klaus Schaefer. Click here for the link