DSXchange

Ascential Software acquired Torrent Systems, and the name of Orchestrate was changed, initially as a marketing exercise, to Parallel Extender (or PX). So, yes, it's the same engine. And you can refer to your Orchestrate documentation - in some areas it's more accurate than the PX documentation. In v...

I would suggest that 2.2 was a tolerably stable release, sounds like you all bypassed it. 2.5 was the first version with NLS enabled (in the USA you would definitely have bypassed this ), exactly imitating the functionality in 2.2 and, curiously for mathematicians, came out after version 3.0! There ...

You can certainly discover what's out there, if it's any of the known database types, or even if you can establish an ODBC connection to the data. A tool like AuditStage will help you to determine what structure the data have. Somehow, somewhere, though, you will need some form of documentation abou...

The idea of this Forum is to be a sharing place. If your hunch proves to be correct, please post the details of your solution so that others may benefit. I'm sure you'll post again if your hunch turns out not to be correct!

Review the code generated by compiling the sequence. You will find it on the Job Control tab in the job properties window. See whether there's anything there that might introduce such a delay. Check, too, whether the controlled job has anything that might cause its status reporting to be delayed. Wh...

Please do report back whether that fixes your problem. You can help the next person who bumps into that problem.

There are several restrictions on when you can encapsulate server jobs in shared containers to use in parallel jobs - and let me note in passing that this is not the same as converting server jobs to parallel jobs. The restrictions are documented on pages 2-19 and 2-20 of the version 7 DataStage Ent...

When has a DataStage developer ever used the long description field? Who has time for that? It's one of the aspects that differentiates the best developers. Not only do I use the short and long descriptions, I also use comprehensive annotations. Once I leave a client's site, any work I've done - ev...

If you're performing a lookup against a hashed file, you're getting the only match. Not the first, not the last, the only match. Create an index on the UV table underlying the UV stage, on the key column(s). If there are any other constrained columns, index these too. Get to a TCL prompt (or use the...

Your original post specified parallel job. It is this that confused us. If you're doing inner joins between the five tables based on the primary keys, you should not get duplicates (because primary key columns should have a uniqueness, or at least joint-uniqueness, property). Can you explain exactly...

Even that may be too many, there are times, for example when the database server (on the same machine) also needs CPUs, or you are doing some really intensive processing in your ETL, that you'd configure maybe one processing node per two CPUs.

Q. Can I create a sequential file on the fly?
A. You could make the sequential file name (or pathname) a job parameter, and use that parameter in the Sequential File stage.

Can you please explain how that DataStage BASIC code can allow a parallel job to create a dynamically-named sequential file?

Parallel jobs require a completely different mind set from server jobs. Read through the first section of the Parallel Job Developer's Guide to get a feel for what is needed. Forget techniques you used in server jobs. Learn how to do it with parallel jobs. There is no hashed file available. There ar...

The separate links attempt to open separate cursors into the table. Whichever operates first manages to set an exclusive update lock on the table until the COMMIT arrives, which means that the other can not. An even better approach is not to insert or update rows at all, but to create two separate d...