DSXchange

It wasn't clear from your original post whether all rows being delivered to the ORABULK stage were being written to the DAT file. By how many are they different? Two? (My guess is based on two logged "non-numeric where numeric required" messages.) Would it be difficult to determine which rows were n...

In quick summary, "static" hashed files are pre-sized when they are created. The creator selects appropriate group size, hashing algorithm and number of groups (modulo) depending on the amount of data to be stored. These values do not change except through manual intervention. "Dynamic" hashed files...

In a Transformer stage the following is the sequence of execution. 1. Any before-stage subroutine is executed. If ErrorCode is non-zero, the job aborts. 2. A row is obtained from the stream input link. 3. For each reference input link, in the specified execution order: (a) the reference key ...

That message usually means that a non-numeric value has been found in the data being supplied, where a numeric value was expected. Because the ORABULK stage is written in DataStage BASIC, it replaces that non-numeric value with zero, and issues a warning. This may not be what you require! Check the ...

If you just want the first line, you may find it more convenient to use the UNIX head command. If you invoke this using DSExecute(), the result is in the third argument (as a string) and the exit status in the fourth. Shell = "UNIX" Command = "head -1 " : FileName Output = "...

There is no hash file solution if your key exceeds 768 or the 2048 characters. You're faced with using either a UV/ODBC stage where the current key column is just an attribute or doing the lookup in a relational table. Not a UV stage, because this is still a hashed file under the covers, and still ...

Or, even better, construct a DataStage job to do it for you, and run that - with as many parameters as you wish, from your code. The job can move data to and from sequential or hashed file(s), both of which are readily manipulated - without licensing - by DataStage BASIC.

Your requirement is precisely what the Merge stage does. How large are the files? If they are very large, there may be a more performant solution available, as the Merge stage has to use memory to load at least one of your two files, perhaps both.

Must be time to give Parameter Manager a plug. While it doesn't directly address the OP's question, PM does provide for management of parameters between environments, in a sense offering the capability of having "global" parameters that can be loaded into jobs with different (project-wide) default v...

Just to rub it in... Even if you got everything right from Ken's post, you still have to fix any required entries in the system tables (such as UV.ACCOUNT and the SQL Catalog tables). Therefore, while technically it can be done - if you know what you're doing at every step - why would you bother, gi...

I think what you're seeing is an artifact of the GUI refresh interval and not much more. Maybe, even, the GUI refreshes "right to left" (in the same way that active stages are closed "right to left", which you can see in the job logs). Since you're on version 7, and probably have row buffering enabl...

(Whistling the 1812 Overture...)

This is number 1812 for me.

That fact will disappear into history once my points count increments, so I just felt like recording it in a persistent fashion.

Sorry for the interruption.

There is no DataStage limit to the number of instances that may be started. Technically there is a limit, because the job ifentifier is a character string literal, and the maximum length of one of these is 255 characters. Therefore the DataStage limit on the maximum number of instances of a multi-i...

It depends. Which database? There is a set of functions within DataStage BASIC collectively known as the BASIC SQL Client Interface (or BCI) that allow your DataStage BASIC code to act as a client to the database. However, access is via an ODBC driver, so that you must have an appropriate ODBC drive...

By default the maximum size of a hashed file key is 768 characters in version 7.x, 255 characters in earlier versions. This can be increased using the MAXKEYSIZE tunable, up to 2048 characters. However there may be implications for other hashed file tunables if you do this; for example, at 2048 char...