DSXchange

COBOL has a COMP-3 attribute that can be applied to numbers. Instead of storing them as ASCII digits the COMP-3 type used BCD (binary coded decimal) to store two digits per byte. This routine just changes that binary type back into digit form.

If the number of columns and number of data bytes are similar in the slow load and the fast load I really would look in Oracle to see if you might have slow triggers.

I'm not at a DataStage machine so I can't check, but it sounds like a cobol type conversion routine as part of the sdk. Actually, it looks more like a datatype and not a routine - where did you see this? If it is in the routines tree then you can always open up the routine and look at the source, th...

Hello Arvind and welcome to DSXchange.

You need to have the correct c++ compiler installed on your system. Most stages don't use the compiler, but the transformer stage does.

Hello and welcome to DSXchange. You will find that you get better answers when you post in the correct forum; in addition this problem has been discussed numerous times before, use the search button above. In your case you can go to the designer, save your job under another name, delete the original...

This is case of thinking of using a hashed file to store the lookup table and, with luck, having that lookup fit into memory. If that works out you might be back to almost your original speeds.

Yes, exactly. There is only one physical unique key; if you specify multiple keys in a job it combines them to one string internally.

lol - those names and paths look awfully familiar!

the scp format for you is user:password@node

Abu - that is a good thought, but unfortunately it doesn't work that way. Multiple key definitions in DataStage actually go into just one key. Hashed files have one and only one key and it must be unique.

lokesh - how often does this need repeating? Using "auto" partitioning will not guarantee that a job will work correctly! Let's take a very simple example. The source file has 2 columns, a numeric sequential row number and a numeric Employee number. Let us assume the default "auto" partitioning is d...

The tagline of the World Community Grid is "You can help change the world" and I think that it is a worthwhile endeavour indeed. The project makes use of grid computing to effectively weld together a supercomputer by scavenging free CPU cycles on user's PCs. Any time that the Windows backstop proces...

That means that the generated code in a Job Sequence doesn't contain the "INCLUDE DSINCLUDE JOBCONTROL.H" statement, and you won't be able to use these routines. You will have to write a small routine (or get someone to e-mail you the routine listed earlier in this thread) that calls DSAttachJob(), ...

I posted a full routine, but you would need to join as a premium member to use it. Lookup up DSAttachJob() in the docs, it has 2 parameters.

I just re-checked my test program and I just realized that the PEEK stage output lists the last column first so I got my +s and -s reversed.

Mea Culpa - you are right. Use -1 to subtract a day.

Good try JoshGeorge, but wrong. I stand by my original post :D

(But I did do a quick check by writing a test job to make sure I wasn't wrong before posting)