DSXchange

That's because the flat file isn't your problem. It's either network congestion or your source query needs to be tuned more better. Or both.

Sorry, I meant the source code for the ExecDOS routine, not your wrapper code. Odd that it has a DSU prefix, that means it is a User written routine so someone told it to log the command line. You could also switch to using DSExecute() directly, that doesn't log anything like the ExecXX wrapper does...

Gives up?

You can't use wildcards there. You either need to cat all the files together pre-job or investigate the use of the Filter option in the Sequential File stage. You can use it to cat all of the files to standard out and then the stage reads that as its input stream as if they were all one large file.

Add a parameterized constraint to skip the first X records where this time X = 100. And please don't post in all bold, it makes the baby jesus cry.

I don't have a Windows server so don't have ExecDOS. Post the routine code, wrapped in [code] tags and we'll see what we can do.

No kidding. What happens if you do not delete the indexes? How many deletes are we talking about here?

Which doesn't help all that much as you really want to select the NEXTVAL so it gets incremented properly.

Great! Please mark the thread as Resolved using the big button at the top of the screen.

Then create one. Copy the existing routine and change it so it doesn't log the information you don't want to see in the log.

np. If you have any more questions on this topic, be sure to come back and ask.

Mind posting that code? Did you look to see if there is an ExecDOSSilent available? For UNIX there is an ExecSHSilent, hence the question.

Sorry, typo. ExecDOS which does exist, btw. How are you executing this now - Sequence job? Custom code before/after job?

HP-UX?

FMT should work fine for your zero fill needs, it's just that you'll need to 'manually' prefix the sign on the amount. Creating a separate field for the sign is one simple way to accomplish this.