DSXchange

More partitions, provided that your current configuration is leaving spare capacity on the server engine(s).

Make sure that your lookup table (dimension table) is not empty.

I understand BR to mean British Rail. That said, "propagate" in an ETL context usually means "pass through unchanged". This is what Runtime Column Propagation achieves - the columns are passed through a stage without you needing to code explicitly for it.

Note that there is no default disk pool for scratchdisk in the configuration file that Craig posted. Perhaps there should be. It depends what DataStage is being asked to do.

Did you Search DSXchange? I'm pretty certain this exact question has been answered more than once in the past.

Welcome aboard. Does your VARTEXT column need to be one character longer?

That said, using Information Server Manager and the Eclipse plug-in for SubVersion you can quite easily set up "proper" source code control for DataStage. But there is, as Vincent suggested, an education/management component to it as well - experienced DataStage users will need to be convi...

You can get the underlying service names from the WebSphere Application Server console, but why do you want them?

Not possible using just roles. Even the lowly Operator role can run and reset jobs. You might be able to manage it using file system permissions (for example no write access to RT_LOGxxx/DATA.30) but, in this case, they could still request a job run only to have it fail. Not quite the same thing as ...

3) Many people do but it's technically incorrect. It's the "DataStage server engine". Usually the process that runs is dssh (DataStage shell) and it in turn runs some DataStage BASIC code such as DSD.RUN (for server jobs) or DSD.StageRun (for server Transformer stages). 4) IA jobs run as D...

1) No.
2) It's osh all the way. IA jobs run as DataStage jobs.

The Epoch property sets the lowest (earliest) date that will be generated. The Limit property sets the highest, which is that many days after the epoch date.
For example to generate dates in the nineties, set Epoch to 1989-12-31 and limit to 36503 (there were three leap years in that decade).

1) All osh processes run as osh 2) QualityStage runs DataStage jobs. 3) The Engine is the machine on which the DataStage software is installed. 4) Information Analyzer can use the same Engine or a different one. FastTrack does not use an Engine tier at all (until generating a DataStage job).

The parallel Sequential File stage is intolerant of field delimiters occurring within fields, even if they're quoted.

Best workaround is to use a server Sequential File stage within a server Shared Container in your parallel job.

What bridge were you using before?