DSXchange

The uvconfig file is used to set the tunables for the DataStage Engine itself, things such as the size of lock tables, the number of dynamic hashed files that can be open simultaneously, the number of publicly-available numbered semaphores, whether NLS is enabled, and so on. There is one uvconfig fi...

... or 19 million TB (approximately), whichever comes first!

Yes, by setting the pathname of .odbc.ini as the value of the $ODBCINI environment variable.

It can't find a db2read function. This almost certainly means that the relevant environment variables for DB2 client (or DB2 Connect or both) have not been set up properly.

Is the message IS being monitored, or MAY BE being monitored? The second of these can occur if any kind of lock on the job exists in the Repository - if the job is open in Monitor, Designer or Monitor, for example.

DataStage EE is currently running in production on at least two grids of which I am aware. It treats the grid as an MPP cluster. The operating system looks after a lot of the distribution of work. I have not seen any official announcement that DS supports grid computing, but at least two sites have ...

Records processed are reported in thousands (K) of rows. 1000K is one million.

A restarted job sequence MUST use all the same parameter values as the prior incomplete run. This is the only way that you can prevent this warning and abort from occurring. (Well, there's one other way, and that's to recompile so that all the checkpoints are lost and to run the entire sequence agai...

Read about this function in DataStage BASIC manual. You may need to add Trans() to DSParams file if you don't like the red colour.

Did you ever resolve this? I have just encountered it on a 7.5.1 system.

Have you set all operation to sequential mode? It would be very difficult for your sys admin to determine otherwise, because your node definitions are identical. You can only determine whether two nodes are used under such a configuration from your logs, or by using the data set management tool or v...

There is no lookup whatsoever in that diagram. Therefore (unless you have a constraint expression in the Transfomer) the expected rows out will be the same as the number of rows in.

This is an example of the powerful string handling functions available in Server. This solves your question: FIELD(In.URL,'/',1,DCOUNT(In.URL,'/')-1) The DCOUNT() function returns the number of fields delimited by '/' and the FIELD(string,delimiter,from[,to]) function gives you all ...

It's HASHED file, dammit, not "hash" file.

There are a couple of SDK routines dealing with 1970-01-01-based dates.