DSXchange

If you are in a production environment then I would schedule for the additional work that a new install entails and do that. Particularly at V8 with the new repository structures I feel more comfortable starting with a clean slate. If you are still in development only then I'd start off with an upda...

That's a pretty compelling argument, in my opinion!

The second job will run once it gets it's input file, only it will wait for job A to complete if job A is already running, ditto for job A - it will wait for job B to complete if that is running.

One cannot convert from one CRC result to another, the algorithms don't work that way. You could either program your own CRC-16 in BASIC or use a UNIX level CRC-16 program and call that from your job for each value to be computed.

If one environment work and the other doesn't because a function cannot be found, then the likely cause is in your LIB or LIBPATH values (also set through the dsenv script). Can you compare the two environment values to locate discrepancies?

Job Sequences have the "Wait for File Activity", which is perfect for doing what you wish. Let us call the files A and B; then you would have a WFF(appear, file A) -> WFF(disappear, controlfile B) -> PX Job file A. Unconnected to that stream you would have a WFF(appear, file B) -> WFF(disa...

You do have external source stages to work with. I assume that by NDM you mean network data mover, and if it has a command line interface and write the data to stdout then the external source stage would solve your problems.

This would be a good place to use the source level debugger available in server jobs; with it you can stop execution in a given stage for a given condition, then view the values of the relevant columns and variables and perhaps figure out what could be causing the error. I can't see anything from wh...

First thought is that either of your 2 stage variables are causing the discrepancies, how are they being calculated?

You don't have much choice, create a 8 node configuration file and use that for jobs that load to your 8-way partitioned database. It will be quite efficient.

I'm not going to touch upon the subject of compatible versions of WAS for DataStage but want to give some food for thought. First of all, DataStage Server barely uses the WAS application. At 8.1 the default location of log files is in the XMETA repository and authentication runs the WAS, but otherwi...

The Parallel Job Developer Guide describes the

DateFromDaysSince() function, which returns a date with a date input and an integer (number of days) input.

Odd. Even though it shouldn't make a difference, are both client machines in the same subnetwork (2nd to last group in the IP address)?

The SQLSTATE=22005 means an error in assignment so your assumption that the conversion is causing the problem is probably correct.
What is your output datatype to DB2 in the stage and what does your conversion call look like?

What is your runtime value for NLS_LANG (check the director log)? This affects how the values are extracted from Oracle and sent to DataStage and this setting is not used for the ODBC connection.