DSXchange

ogmios wrote:on the client side you have the application xml2dsx which will allow you to convert DataStage xml to dsx files.

Which is run automatically when you import an xml export. This step can be rather painful for your pc to run, hence my comment.

Do yourself a favor and Google up an ASCII chart as a reference. There are a ton out there, one here for example.

Ditto what Kim said. I use the dsx format for backups and import/export. On occasion, I'll pull a full xml export and stash it away somewhere on my UNIX server and use it to search for metadata, typically grepping for tablenames or routines when I want to find out which jobs they are used in. The fi...

The simple way? Upgrade to 7.5 where they've added an attachment option to the Notification Activity stage. Otherwise, the answer is 'no' from a Sequencer standpoint without a custom routine. If you want to use attachments in a prior version, you'll need to write your own routine or job control code...

Both stages work in a similar fashion, but are configured using different mechanisms. Both use a DSN - a Data Source Name - which is simply a marker or label for a set of configuration information. The DSN can bear absolutely no resemblance to what it actually connects to, but are generally made the...

In other words, not really all that different from testing anything else. There's nothing magical about it just because it's a DataStage job.

Not really... you'd still have to buy ODBC drivers, unless you already have. The drivers that ship with DataStage are only licensed for use within jobs, not via the BCI functions.

Besides, you don't really think that the programmers are the ones writing the documentation, do you?

Couple of things... Did you verify that you have the telnet prompts properly configured so that it knows how many there are and the keyword in the stage will be matched? If that area isn't setup properly then you'll never get to the actual execution of the command part. Try turning on tracing for th...

More than likely, yes. However, it's hard to say what is wrong without seeing both your metadata and your data. I'm a little concerned that you had to "align the data to the length that I specified in the meta data", usually it's the other way 'round. Is this just something you are playing with, so ...

First of all, I would like to know if we are using fixed width when importing metadata, the column name must be the same as the width that we specified? Assuming you are talking about the header record in the file, then yes - or at least no longer than. However, fixed width files generally do not h...

Tony - how are you managing your Phantom directory? I've found that you can see issues like this when there are a large number of entries in the &PH& directory under any given project. You can try a couple of things. Short term - With no jobs running, log on to the Administrator and issue a CLEAR.FI...

Any chance you are running 7.5? That version adds two new Sequencer stages to allow "looping" in the GUI. Before that you are typically talking a fair amount of hand coded job control to accomplish this.

Yuck! BCI functions, ODBC and the need to buy licensed drivers. Do it in a DataStage job instead. Why do you think you "need" to do this in a routine?

Probably memory / resource related. There are definitely limits to the amount of un-ordered data the Aggregator can handle on any given system, but I don't know of any hard-and-fast rules on how to determine what that limit might be. Any chance you can sort the incoming data to support your aggegati...