DSXchange

You can use the mnemonic DSJ.ME in both the before and after job subroutines. You cannot pass a stage variable into the routine.

Sorry, my mistake.

Don't you just have one data output column called "Payload", which comprises all the column data, to which you write? The template for this is in Table Definitions -> Real Time -> WebSphere MQ Connector -> MQMessage.

No uvconfig changes will affect the multiinstance behaviour. The "compteur" variable use is quite odd, particularly adding the internal date (days since Dec 31 1967) and internal time (seconds since midnight). Wait a second, I recall issues when using numeric instance numbers. Is that the case for y...

Have you tried using the MQ Connector stage? We are using MQ from mainframe with very long and variable message sizes with no issues.

Which did you install first, DS or the dot.net update? Have you tried re-installing DS?

In the first reply on this thread, Ray detailed how to start the deadlock daemon. Do you have this running?

You either have not installed, or not correctly installed, your c++ compiler in the 2nd environment.

Maybe this person was thinking of the PX virtual datasets and applied it (incorrectly) to server hashed files.

The "telnet localhost" works only if your client and server machines are the same. Try "telnet {ds-server-name}".

Turn on the dsdlockd process so that locks are automatically cleared every 15 minutes.

I expected rejects, not correct records... What about putting a transform stage between source and target, putting in a second output link to a peek stage with a constraint of only sending records where the value of a column is null. That way you could see if the problem is happening on the read or ...

The message with teh UV.ACCOUNT points to file access issues. Do you have any security software installed? Can you globally change access rights to the DataStage server and project directories (temporarily, to see if it makes a difference)? If you execute "telnet localhost" from the server, do you g...

This would seem to point to the error occuring in the TRANSform stage. Both your changes and link to DSP.Open reflect that. Address 574 in the program (assuming you have the same release 8.0.1 that I do) is a call to "$DSP.Open" routine that has been cataloged in memory. Assuming you had no installa...

Use "C:\Temp" instead of "C:\Temp\" and see if that makes a difference.

There are job design methods you can use to control memory (i.e. not cacheing hashed lookups will use less memory, but work slower) and a couple of the uvconfig settings also affect memory use. But you need to know that by doing so you are going to seriously slow down DS processing and it is much ch...