DSXchange

I say, use stage variables and keep concatenating the inputs. Use field() function to parse the fields you require. Your output will be a single column. Other way that I can think of is by using awk.

chulett wrote:Precision and Scale.

Hehe. I meant actually the value that is supposed to be.
Is it really (38,10) ? How do you know the scale is 10 ?

Stick to the supported api's or command line dsjob commands with the right argument. Utilizing the parsing power of shell scripts and other unix utilities like awk, sed etc.
These will still exist even in 8.0 but the sql might change.

chulett wrote:Do I pass?

Looking at Ray's reply, I say you pass

Go for Craig's second solution. Execute the stored proc. in a .bat or .cmd file using osql and redirect the output to a file. Read the flat file in your datastage job.

What is x and y supposed to be in Decimal(x,y) ???

Does your id have load permissions to the table? Extracting data just means you have select permissioins, not necessarily insert/update permissions. Verify it from your dba.

The best way to find out is to try it out. Run , say 10 instances at the same time. If you are satisfied, start incrementing the number of simultaneous instances. Stop at a point where you find that the process is struggling. Experiment it out. No one can tell you as only you know your system best.

Import the metadata with orchbutil. That is more accurate. Before that, change the scale to 0 and see if that helps.

Its similar to passing values between jobs. Write your value to a flat file and in the sequence job activity, define a parameter to the job that needs to read that value. In the derivations you can call a small routine that cats the file and reads its contents using DSExecute().

Decimal by property will save the leading space. So you will have to process it somehow, somewhere to get rid of it. Unless you explicitly change the data type and trim the space.

Madhusv wrote:There are routines KeyMgtGetNextValue and KeyMgtGetNextValueConcurrent, You can use this to genrate sequence in server jobs

The routines mentioned above will help you if you are on server edition.
If px, the follow Craig's advice. As both the advices are specific to the edition your working on.

Yea, I didnt get the question either

Let me give you an example: Few records come in with keys 1 and 2, 1, 3 you do a lookup on your hashed file, it loads 1 and 2, now for 1 it will see that its already present hence it will be updated. Isnt that what you originally wanted. Commit each record, read and do comparison. Tell us why you wa...

An insert update to a table is the same as writing to a hashed file. If the key does not exist, it will be inserted, if it exists, it will be overwritten (update). So whats the matter.