DSXchange

Welcome aboard! :D What this message appears to be telling you is that you have specified X partitions in your query but Y partitions in your PX configuration file for the job. And that the rule is that X must equal Y. The only remedy is to make sure that the rule is obeyed. You can change either or...

Can you post a few rows from each file? Sometimes actually inspecting the data can give inspiration as to what the problem may be. Is there any conversion (say from "" to NULL) specified in the Format properties as these files are being read? Perhaps add an extra output link to the Transformer stage...

The engineering philosophy of DataStage is to log warnings wherever something occurs that does - or even might - cause errors in data. I guess in this way they indemnify the software from being blamed when these errors occur. There is no mechanism to prevent these warnings from being generated and l...

The engineering philosophy of DataStage is to log warnings wherever something occurs that does - or even might - cause errors in data. I guess in this way they indemnify the software from being blamed when these errors occur. There is no mechanism to prevent these warnings from being generated and l...

Not really. Ascential can provide on-site training (very expensive for one person, but cost effective at about four people). If you enrol in the class, they may be prepared to consider sending you your copy of the class notes earlier so you can pre-read them, if you ask nicely. If you're REALLY keen...

You can verify whether or not changes to uvconfig have taken effect by executing the command CONFIG DATA either through the Administrator client command window or at the TCL prompt on the server. You can verify the value of any environment variable using the echo command, for example echo $DS_MMAPPA...

You can indeed do what you desire. But it may be more fruitful, if you're not a confident DataStage BASIC programmer, to realise that a Job Activity can start a Job Sequence as easily as it can start a parallel or server job. That is, you can build a hierarchy of Job Sequences, with condition testin...

The first component of the version number is not for you to use. It's a number used by DataStage to indicate the specific version of the product at which the job was most recently saved. Among other things, this provides protection against trying to load a version 6.x job on a version 5.x system, wh...

No, that's how it works in my experience too. You're not doing anything wrong. If you Oconv("27:00","MT") it's the same result as Iconv("03:00","MT"). Originally the idea was to make measuring intervals that ran through midnight easier. Add a range test on the hour component. FUNCTION CheckTime(...

This is only true if certain restrictions are not violated. The restrictions are documented in the Parallel Job Developer's Guide.

Are you using a Custom trigger? If so, "OK" will need to be quoted.

The DataStage Server Unix Survival Guide I wrote is about an 8 page document that points out all of the touch points the Server product has in the unix environment. I wasn't trying to show proprietary information such as how the product is written, just simple things like how to identify job proces...

Unfortunately the answer is (definitely) no. Further, the readme for 7.1 (or 7.5, not 100% sure) states that there will be no further development of the Documentation Tool (so we'll never see it picking up Job Sequences, for example); Ascential want you to buy MetaStage to generate the same reports.

First of all, it's not new. Until 7.5 Version Control had to be installed as a separate client, but it was all there on the CD. Its function is to promote DataStage components (in named and described batches) from development to test and production environments, automatically managing version number...

Thank you for that.