DSXchange

There is no general answer to your question, which is similar to "How long is a piece of string?".

You need to start with measuring your system so that you know what your resource usage is.

The project directory has a text file called "DSParams" which contains these values. Since editing the file with incorrect values could corrupt the project, I would sugges t you just look at it but don't edit it.

"dd" or "od" can be used to view EBCDIC files directly on UNIX (use Google to get the syntax and description). If you would post the PL1 definitions or an excerpt to this thread we could go through the different datatypes but they will most likely be those you already know - inte...

What do you mean by "can't" in your post? If you removed it you can add it again via the administrator, but only in the user section.

I didn't even know that categories can be created with embedded spaces. When you execute the command with quotes, what is the dssearch output?

The FTP Stage transfers data on a row-by-row basis without landing the data; unlike the FTP command which copies a whole to/from disk in one go.

From your description the FTP stage sounds like what you need.

What have your tried so far and with what sort of success?

The textual description sounds viable. What is your problem - is it runtime? If so, replace your database write with a peek stage and re-run the job. If the rows-per-second goes up then your bottleneck is in the output stage and you can look into tuning that.

Have you tried quoting?

Could you post the whole error message? Also, did you clear the log file (i.e. ensure that it was not broken prior to the job run)?

PIC S9(16) COMP-3 is stored in 9 bytes, not 16. COMP-3 stores one digit in 4 bits, plus it needs 4 bits for the sign, thus 16 digits / 2 = 8 plus sign and rounded up to the next 8-byte boundary.

0% idle can be a cause for jobs to fail due to timeouts or overloaded resources.
But all of this is pure guesswork until you have a nerror message of some type.

It would seem that you haven't read the Please read before posting here and haven't realized that this is an all-volunteer forum and that posting threads with "urgent", "ASAP" or similar terms usually results in getting a slower answer than you normally would get. If it is urgent...

The first field in your string is "" empty (left of the first '/')

Then you have reached an impasse. Either reduce the number and size of messages or, better yet, don't log them in the job log but elsewhere. This heavy I/O to the log file is most certainly slowing your job down as well.

Reset your job in the director and then post the new message "From previous run..." to this thread.