DSXchange

I agree, templates feels like a piece of functionality that is only partially there. On large projects it is easier to use then copy job but requires some organisation to set up. The thing about copy job is knowing which job to copy, having that job in your project and then having to remove all the ...

Everyone who starts developing in parallel jobs gets a truck load of warning messages, especially when you throw sequential files and transformers into the mix. It's just a matter of experience, training, learning and experimentation that makes it easier to avoid them.

Of course T42 once made the observation that he could make all warnings go away through good development! Have you tried putting a copy stage between the transformer and the sequential file and then playing with the partition settings of that copy stage?

You have to keep in mind that stage variables are executed in the order they appear. A stage variable that does the comparison should appear before a stage variable that holds the value from the previous row. svNewValue: input.custid svCustidIsChanged: svNewValue <> svOldValue svOldValue: input.cust...

Unfortunately when Ascential released the message handler functionality they did not provide any guidance as to when or why it should be used. Here is how I use it: No message handlers in development, unit testing, functional testing or user acceptance testing. Testers get to see the jobs run warts ...

There is a message in the FAQ forum for setting up a parallel job message handler. Because parallel jobs are chronic whingers it is almost mandatory to add a message handler to any production environment (recommend not adding one to development) to remove trivial warnings so that the job finishes wi...

Have you tried saving it to a parallel job and exporting and importing it that way? I wonder whether it is failing to import because it is a shared container or because it contains a stage type that your target project cannot handle.

I was told by Ascential support that it was a known defect in the XML Input stage on Solaris and we could just ignore it. Posted this same message some months back when someone else asked the same question. Doesn't cause any harm to your data, it's just a nuisance that may result in your support sta...

What exactly are you merging? If you take the example where you have an entire project dsx checked in and you want to merge in a single job dsx to overwrite the existing. The merge should work if it can correctly locate the start and end job statements for that job. The danger is if the merge lost t...

Record keeping and collaboration for DataStage projects is part of the next release, DataStage Hawk, which goes into beta testing soon. DataStage has previously not been very strong on team collaboration, apart from a robust client/server design, but the next release promises to improve things.

CDC is quite straight forward, your delta data is the "After" view and your dimension is the "Before" view. CDC will output your rows with the change data code that will indicate which rows are modified and which are new. Make sure you drop off unchanged rows and delete rows and you are good to go. ...

I always felt you were better off doing surrogate key lookup first and then doing change data capture on the rows that already exist and sending the new rows directly down an insert path. A surrogate key lookup only retrieves a couple columns from the database while CDC returns every column. So look...

I've always felt ProfileStage and QualityStage are the two GUIs that were the most difficult to use. Which is probably why they both get completely rewritten in the next releases. ProfileStage is a good profiling tool for a project team due to the controls over the stages in profiling. If you are af...

I think that's the way view data works. When I view data on a database table with no rows I also get an error with the option to view more details, the attached log shows a row limiter hit error. Should be okay when you actually run the job.

Maybe it's trying to create the dstmp.050825.093754A as a log file but cannot get write access to the engine directory. Assume you are logged in as the DataStage admin user (eg. dsadm), have you tried creating the dstmp file in that location manually?