DSXchange

[quote="maffan76"]Hi, We have recently jumped from Server Version to PX and have to migrate jobs from Server verison to PX. quote] And another thing, you don't have to migrate your jobs from server to PX. You only need to migrate those jobs that need to run faster and would benefit from a ...

This is one of those rare cases where it might be a lot easier (and definitely a lot faster) to read and write the XML using sequential file stages instead of XML Input and XML Output. If you are simply reading a numeric value, changing it and writing it back again the XML parsing within a transform...

DataStage flattens XML complex structures into relational records. If you are talking about dividing your XML file into six files with the same record structure then you are better off doing it outside of DataStage. If you are dividing it into six different record structures then you can do it in Da...

New DataStage users could also benefit from opening up a Transformer and looking at everything available on the right mouse click menu. There are some things on there that even experienced DataStage coders are unaware of.

Normally you want to avoid plucking env variables from within a routine as it breaks good modular coding practices. Kind of like using global variables in Visual Basic code. The project specific environment variables are set as the default values for job parameters, it is possible that someone will ...

The standard web log reader rocks, you could churn through a big web log in no time with all the handy routines that come with the web log import such as URL parsers. It's when you need non-standard browse and click event event information from your web site that you get into trouble.

As a stab in the dark I would say your job is aborting within the transformer due to some incorrect derivation or routine code. When you reset the job you should see a message appear in the long starting with the words "from last run.." which can contain additional debug error messages (retrieved fr...

So how do people feel about large repeating XML files? Seems to me a misuse of the format. An XML file with one million repeating records also holds one million duplicate definitions of those records which take up as much if not more space then the data itself. Is this incorrect use of XML? Should t...

That's the drawback, sequential file processing is fast but it can be hard to support, especially if you need to change or add XML elements.

That link does not work.

The topic or post you requested does not exist

I think your only options are self publishing, which requires a lot of goodwill from Ascential/IBM, or IBM Press. I think IBM Press will want to publish some type of Information Integration book after the Hawk release. You would assume that if IBM Press are taking the book through the normal proposa...

Yep, the XML reader is a dog. It tries to read the entire XML file as a single document in one very big text field. Very large XML files cannot be handled by the XML input stage as they run out of memory. You are better off processing it via a sequential file stage and parsing it in a transformer. Y...

Actually with IBM buying Ascential there is now a MUCH easier way to get a DataStage book published which bypasses all the legal problems. I've been toying with the idea of writing a certification guide for the Hawk release and the mythical Hawk certification exam. If anyone is looking to publish a ...

You can certainly do it through Progress ODBC drivers which should be available from your Progress DBAs. Don't know of any specific Progress plugin that accesses it natively.

Oracle is in an interesting position. They bought these RDBMS independent products such as PeopleSoft but if they want to embed OWB into them they are going to have to make them Oracle dependent, which pisses off a lot of existing customers.