DSXchange

How long after the job finishes are the processes still consuming 100% CPU? If you get the pid numbers and do a "truss -p {pid}" what kind of activity are they doing?

The "Maximum Message Length" is a Queue setup parameter - perhaps that is set too small in your queue?

The c++ compiler isn't used in seqeuences, just in Parallel jobs that use transformer stages.

Can you post the "LIST.READU EVERY" result? (use the code tags so we can see the formatting, please). I haven't checked a V8 Windows installation, but prior to this version DS always installed it's own minimal telnet listener which routed through to the TCL, I am surprised that this isn't working. B...

The point that I was trying to make is that your error has nothing to do with the DateToString() function.

If you make the derivation just "SetNull()" then I am fairly certain the error will still be there. I think it has to do with your column name.

And after you finish thinking about Ray's questions, think about Parameter Sets and Shared Containers.

The reason that it works for you in Windows is because your host and client systems are on the same box.

But the export is client-side (Windows) only, so it won't work as you expect on a UNIX system.

That is a nasty problem - this happens at V8 when your user doesn't have admin rights. The files are created by someone with Admin privileges on your PC and don't give you sufficient privileges on the file. Have the admin grant you RW rights on that xml file.

Set "start=1". It will start automagically next time you bounce the DataStage server, or use Ray's method at the beginning of the thread to start it immediately.

swapnilverma - I am ready to be proven worng, so please try it. As far as I know, you can only pass certain values to the parameters, and stage variables values are certainly not among the possibilities.

Yes, you will need to concatenate the fields to one; you can use a transform stage or a column export stage to effect this.

I just noticed Ray mentioned how to start the daemon, you will also need to edit the $DHSOME/dsdlockd.config text file and enable the daemon.

The Search can be used to find the many threads in DSXChange that discuss this. I think that the documentation is very weak, the only mention is in the BASIC guide, Deadlocks Deadlocks occur when two users who acquire locks incrementally try to acquire a lock that the other user owns, and the existi...

It is a warning, telling you that the table has become quite large. If you know, understand and expect this you can think about deprecating the warning to an informational one.