DSXchange

There is a DataStage NLS manual in the standard documentation set. Among other things this will guide you into getting NLS character maps built and installed when DataStage starts, so that they are available for use.

Is it in the Stage Types branch of the Repository? If so, you can drag it from there to customize your Palette.

The "bad state" means that the job is not in a runnable state. If attempting to run it in reset mode returns this status, it suggests that the job was not even in a resettable state. This can mean that the job is currently running, has not been compiled, or perhaps is crashed. Determine the job stat...

For some reason the VOC entry does not include the pathname of the file dictionary for job log. Take a look at any of the other job log entries (maybe RT_LOG805) to see what I mean. The fix is

DataStage is a 32-bit application. The database can be either 32-bit or 64-bit, but DataStage must find the 32-bit libraries for accessing the database; that is, the 32-bit libraries must occur before the 64-bit libraries in the shared library search path (e.g. LD_LIBRARY_PATH) for DataStage users/p...

Are you sure you completely deleted all the 7.5.1A objects before restoring from backup?

satadru.kar wrote:I am not sure about the version u r talking about.. but u can run px jobs in windows enviornmrnt if .net framework is installed in your system.

You are in India. English is one of the official languages of India. Please use it here.

Can you open the original job successfully? If yes, something has gone wrong with the copy - delete it and try again. Make sure that the job is not open in any client and not running when you make the copy.

dsjob is the utility. You need to retrieve the "job started" event (find the newest log ID of type "started" using -lognewest option). Among other things, this reports the parameter values that were used for that run. Read the detail of that event using -logdetail option.

Are the business rules already written in Java? If not, why is "using a Java class" part of your specification? It's probably more efficient if the business rules are checked "in line" in the DataStage job.

You can not read and write the same file. Actually you can, and that's your problem. You read one line, positioning the pointer at the beginning of line #2. You then write a line, overwriting some or all of line #2. Your next read goes from the end that write to the next line terminator. In short yo...

Don't worry too much about the UNIX-like pathnames; DataStage EE on Windows uses MKS Toolkit for most of its execution. MKS Toolkit, as you may be aware, is a UNIX emulation. But it is still essential that you specify correct names and locations for the compiler and linker. The correct values depend...

DPF used to be called DB2 EEE and is an environment that supports partitioned tables. Without it, none of the DB2 partitioning stuff is accessible, and DataStage certainly could not employ the DB2 partitioning algorithm. Given that you can still select the DB2 partitioning algorithm when the write m...

In the downstream activity, click on the helper tool (which might be labelled something like Insert Job Parameter) or - if using the Expression Editor - choose Activity Variable. You will get a list of all activity variables from upstream activities, including your Routine activity's $ReturnValue, d...

That is true for write mode Load. You must check the log (and maybe bad) file from sqlldr.

However, the OP is using Upsert mode, and bemoans the fact that there's no Insert only option with that.