DSXchange

It means that the design specifies that this is a multi-instance job. It can be called several times in parallel. The documentation details how this is done.

I would declare the file as one long string, then count the tabs to get the number of columns. You haven't specified if the first line contains the column names but if it does you can parse those names to see if it matches a list of columns.

In those boxes they would have to be, since it expects string values.

Gokul - this is a different error. Ignore datastage for the moment and read up (or use Google) for SQLSTATE=38553 and -727 to find out why you are getting this. Hint - it has to do with privileges.

There isn't enough information for an answer in that post, unfortunately.

I am unclear on how you see that a link isn't executed - is this via the job log or because hashed files don't get created?

Are you missing the semicolon? (just a guess)

The number of nodes does not have anything directly to do with physical CPUs on the machine! If you don't increase your virtual memory on the machine, then change your configuration file to run with less nodes, that has a very direct impact on the number of processes running and thus on the amount o...

Ray - this is neat new V8 functionality (that ...almost... works)

sumesh - instead of me confirming things, have you thought about actually reading the documentation or help files?

In that case I think you have discovered a limitation; it is unclear from the documentation as to whether or not this is a bug (which means that it probably isn't a bug according to IBM). I would guess that the only workaround is to hard-code the values and create an appropriate DB2 userid with acce...

Can you explain? does that mean you cannot type it in, or that you cannot compile or that it won't run correctly?

If the link contained in /usr/vacpp/bin/xlC_r points to the correct compiler then you should be OK. you can place your source files in whatever directory you like

I would add writing the MQ-Series record to a sequential file so that it isn't lost should the job abort. You cannot restart the sequence without losing data unless you explicitly program storing the interim data.

Have you tried manually entering the parameters, e.g. "#UserId#'?

Tools such as Toad will display partition information in easily read forms, or you can get the data directly from Oracle, see this page for some hints. Once you know your partitioning method you can reflect that in your DataStage jobs and finally, those options will not show up unless you specify "L...