DSXchange

"1006":"1011" :"1012" is the same as "100610111012" which probably isn't the pattern you had in mind. I daresay you were looking for something like "1006" : VM : "1011" : @VM : "1012" as your pattern in the first case. But it all seems unnecessarily unwieldy. You have t...

Hashed files can, if 64-bit addressing is used, be much bigger than 2GB if required. Check whether "they" have any processes that are removing the .Type30 files, perhaps because the files are zero-length. If they do, oblige them to change the behaviour so as not to delete files called .Type30 becaus...

Is this a parallel job (as indicated in the original post) or a server job (as indicated by the forum in which you posted it)?

Also not all UNIX operating systems/emulators support positive arguments for the tail command.

It's not a bug, it's how it works. The warning comes from the fact that DataStage uses an IEEE standard for implementing storage of floating point numbers that has limits to its precision - eleven bits are used for the exponent (which is offset by a constant, 1023 if I recall correctly) and 51 bits ...

You would need a BASIC Transformer to use Oconv() or Iconv() in a parallel job. But your output isn't hex - it appears to be binary. Oconv() can do that too. Please specify your exact requirements. Hex can be managed with "MX" or "MX0C" or "MY" conversion, binary with "MB" or "MB0C").

No, these are the buffers inserted by DataStage possibly due to a "force" buffering setting. The problem appears to be with network protocol rather than memory. Are you in a single machine or multiple machine environment? If the latter, are all the rsh and tcp protocols set correctly?

Vijay Kumar wrote:Is there any way I can avoid these warning messages without doing any transformation for null handling?

No. The warning messages will always be generated in this case, because you need to be aware of the situation.

Either provide null handling or implement a message handler.

IBM have a class called DataStage Essentials for Mainframe(code DX134) that you can take.

No.

(Unless you can find something really obscure in Pattern Action Language that I have not been able to find.)

One of my benchmarks that I was able to sustain for years (2 x Craig's posts) has gone out the window. Maybe if I unplug his keyboard for a while...

It's DEFFUN that's really needed.

If the appropriate DEFFUN declaration exists in a header file then you can $INCLUDE that header file.

Read about DEFFUN and $INCLUDE In the DataStage BASIC manual or in on-line help.

Is the final line in the file properly terminated?

Did you search? Did you find this answer?