DSXchange

meet_deb85 wrote:

ArndW wrote:Please post the complete error message that you get at runtime.

when i run a job it dont give any error messabe but with fatal it gets aborts.....

Please just post the contents of the fatal message in the log, otherwise everyone here would just be guessing as to what your problem might be.

Using 100% of CPU is not necessarily a bad thing. In this case the question that I would have is if your database is also on the same system. If yes, then 100% means that the system is doing as much as possible given the CPU it has and if the CPU were made faster or you went to more CPUs the process...

Please post the complete error message that you get at runtime.

InInteger would be the input argument. perhaps you can change the default "Arg1" to "InInteger".

The Mainframe product has to licensed separately and is not cheap. I posted some server code several days ago that outputs COMP-3.

I'm not at a DS pc right now, but seem to recall that the CFF stage in Server is only for reading, but on PX it can be used for both reading and writing. Have you tried to write to the stage?

The Transform function of "CONVERT(Char(10),'*',In.TextColumn)" will convert the <lf> to a "*" both in server and PX.

How about calling a shell script from the after-job - this script checks the size of the output file and if it is 0 then it either adds the one line or copies a prepared 1-line long file into the location of the empty file.

In the before-job call execute a "ulimit -a" to see what the process' values are, which might be different from your shell's settings.

A constraint of "@OUTROWNUM<100001' on the last transform would do the trick.

What sort of data target do you have? I would use an after-job call to check the number of rows processed and, if 0, write the one record to the target. Sequential and Hashed files would be the easiest.

I don't know why your are getting that - usually the SIGTERM should be enough, but for some reason it timed out and a SIGKILL was sent to terminate the process. Does this happen all the time or just once?

I thought that the poster meant it took 25 minutes before the first row arrives in DataStage - but perhaps I misunderstood.

Deinstall the patch - losing logs is less critical than your other errors. Then talk to your support organization about the other problems. When you talk about parameter transfer problems is that using Parameter Sets?

How busy was the machine at the time? If it was very busy and slow that would explain the message.