DSXchange

I believe that "clear table" implies "DELETE FROM table;" which can be hugely slow if there are lots of referential integrity constraints. If these are made into a single transaction nothing at all will appear to occur until the COMMIT is transmitted.

MetaStage (and Manager Usage Analysis) don't work if table names are job parameters. It seems happy enough if user ID, password and even schema are job parameter references, however.

2006 - So far we've managed to postpone Orwell's predictions for 22 years and are still running. You just haven't been paying attention, have you? On New Year's Day in Sydney the temperature was 44C (111F) - it was literally too hot to run my laptops! Not what the population needed to get over a hu...

It's obliging two processes to be created for each stage operating in parallel mode. Presumably to force the use of two CPUs, even though they're sharing not only memory but also disk and scratch disk resources.

Aaarrggh!! The whole rationale behind being able to import table definitions then load them into jobs, fully or partially, using mouse clicks is that they remain untouched by human hands, and therefore error-free. This maximizes your chances of creating a working job first time. While the other post...

Please post the actual error(s) thrown by the compiler, let us contemplate whether or not it is helpful in diagnosing the problem.

Do you refuse to tell your doctor your symptoms when you visit, dismissing them as unhelpful?

Welcome aboard! :D There are three special tokens that can be used as the default value for an environment variable set up via the Administrator client. $PROJDEF picks the value up from what was set in the Administrator client. $ENV picks the value up from the executing user's environment. $UNSET ex...

1. Trim() never results in a zero-length string.

2. A zero length string ("") has a known value. Null is unknown. You can never claim that they are equal (or even unequal).

My misunderstanding - this used to be called pre-compilation; it's the phase where the code generator does a "sanity check" of the design before attempting to generate code. This style of message usually arises when there is some mandatory property missing, such as a file or table name. Mainframe jo...

Welcome aboard! :D The second logged message in any job log (in Director) shows all environment variables that are set for the job. Please check there to see whether the environment variables are being picked up. How are you setting them? Sometimes you have to re-boot a Windows machine before new/ch...

You're almost certainly going to need something custom here, because there's nothing out of the box to add date/time data.

Be aware that you need to handle situations like the result not being on the same day as the original date/time, and possibly a negative time to add.

OK, I now see that you mean "two identically defined processing nodes". Though unusual, and not optimally efficient, this is legal and not the source of your problem. It appears that the virtual Data Set on the link between the srcSeqFile stage and the Surrogate Key Generator stage contains some kin...

It might be a dedicated link, but with how many others are you sharing the bandwidth? Have they been watching the cricket (Australia v South Africa) in real time? TCP/IP is the preferred protocol between client and server for DataStage. In theory you can use LAN Manager (to a Windows server only), b...

If it's a mainframe job you can't validate it - you can only push the COBOL and JCL files to the mainframe for compilation and execution.
Please confirm whether this is a mainframe job or a server job.

The data type on one side of a Transformer stage for one or more columns is incompatible with the data type of the derived column. For example, you may be trying to map a PIC X(20) into a PIC X(16), or a PIC 9(9)V99 into a PIC 9(6) or even - shock, horror!, a PIC X into a PIC 9. You need to investig...