DSXchange

An SMP configuration has the same fastname for all nodes mentioned in the configuration file. Provided that the default configuration file has two or more nodes it will be good for training in parallel jobs.

Dynamic RDBMS stage is nothing more than a wrapper - the DBMS type determines whether an ODBC driver, an OCI function, a Sybase OC function, etc., gets called. It will never be faster than the equivalent native interface because it is nothing more than an additional layer of software. But it's more ...

None of which I am aware. Others may educate us.

It would never be the ...SEQ statements. These are for accessing text files (etc.) in a sequential fashion. Read using the hashing algorithm uses READ statement. The hashed file needs to have been opened with OPEN or OPENPATH and closed (if required) with CLOSE. For better performance, though, open ...

IBM documentation (somewhere, I can't recall where) specifies that at most one DataStage server version 8.0 can be installed on any one machine. It can be co-resident with an earlier version server, however, if the latter is an -itag install - that is, does not use default shared memory keys.

You could always use a server Sequential File stage in a server shared container in your parallel job.

Look in the Editor's Blog forum.

Let me explain. He's from Barcelona.

Does each ODBC Enterprise stage refer to a separate table?

Although the DataStage BASIC compiler does its work as an operating system command (nbasic), this command is undocumented, and there is no way to run that code at the operating system level - it is designed to run inside the DataStage run machine (think of that as a "virtual machine" if yo...

My guess would be some or all of the environment variables in the Compiler group.

Ought not the output column length be 19 if you're not converting fractional seconds?

I take it that this single-CPU server can deliver an infinite amount of processing, memory and disk I/O resources?

Are the strings in which the newline characters appear quoted?

This problem can be caused simply by having the log view for the job open in Director.

Log view sets a lock that prevents the job from being changed while the log is being viewed - a reasonable precaution, if you think about it.