DSXchange

I'll always keep an open mind (which is different from a hole in the head). Sure there will be exceptions to every "rule", and Arnd has highlighted a good one. I probably would have gone the same way there, or I may have split the task to load into a single local source (text file would do, and fixe...

Metadata must be loaded statically into DataStage jobs. End of story.

You can use dynamic SQL, but the columns involved must exactly match the columns defined in the link properties.

If you select the base job in Director and choose Clear Log from the job menu it ought to clear all instances. Have not tested this recently, but that's how it used to work.

The worst site I've ever worked was succinctly described by the account manager who contracted me. "You don't have to worry about the goal posts shifting - they haven't even figured out what game they're playing." Prophetic words, alas. Phase 1 delivered six months late, with some parts of it shifte...

Data are sent to the job monitor (JobAppMon) through named pipes. If something goes wrong with that mechanism, then job monitoring is disabled, but does not prevent the job from continuing to execute. This is the first warning you posted. This may or may not be related to the waitForWriteSignal() fa...

Without having given it a lot of (unpaid) thought, I would tend to plan along the following lines. There is a small number of different input file layouts. I would design a separate job for each of these then, in a job sequence, make the decision about which of these ought to be used based upon the ...

One particular case. 8 because of 10 but, really, the cause of failure was the ill-advised decision to try to deliver everything (including loading of archival/historical data) in phase 1. It couldn't be delivered on time, and what was delivered had not been properly tested because of time pressures...

The invocation ID macro can not be used directly as a parameter reference in a file name. You must create a job parameter, populate it with the value of the invocation ID (or anything else you please). Job parameter references can be used in file names.

DataStage is driven by metadata, and therefore does not have "dynamic metadata" as you desire.

However, if you search the forum, you will find solutions to this question, for example loading partial or even entire SQL statements into job parameters.

About a month ago an Ascential pre-sales support person ran a demo from DataStage EE (parallel job) that fired off a Multiload script from each node in the job - that is, multiple instances of Multiload into the same table. There were no issues with locks, as the partitions contained independent set...

Does it reliably happen with the first job, or only once or rarely? The message indicated that there was a problem with a pipe; such errors are typically rare and intermittent.

Isn't this requirement exactly fulfilled by a Switch stage?

changes made by an engineer without a spec to make the change

Looks a bit like a root cause to me!

is there any way to parameterise the "Interface> Input" in buildop stage,so that we can give different retailers schema file at runtime) Alas, no, which is going to make your task rather difficult. You will need to design an approach the uses a standard schema, but which allows for columns to be mi...

I do not like to use Link Partitioners to achieve partition parallelism (see Chapter 2 of Parallel Job Developer's Guide ) in server jobs. A job that uses a link partitioner presumably splits one stream of data for multiple processing. And a link collector has to gather them all back together into a...