DSXchange

Well then, post your "expressions" or script. How do you expect people to help you if all you basically say is "something is wrong"?

Then as Ray would say - time to mark your post as Resolved then?

What the heck does that mean? Everything is fine now? We need to start over?

If I'm following... add 1 to your "last highest value" before you pass it to the job / stage.

Project not found? I don't see the connection as you don't "path" the project when using dsjob. Post your syntax, please.

Before the end of which day?

It would help to state the actual problem you are having or errors you are getting. That should work 'fine' as long as there are only three columns defined in the stage and you fix the problem Minhajuddin noted.

There's no magic parameter. You need to determine where the 'bottleneck' is. Break off the first stage from the job into a new one and write to a sequential file with an @FALSE constraint. How long does it take? Add another stage, move the constraint down. Lather, rinse, repeat. At what step do you ...

Apparently what you have not done is read the docs.

Uncheck the 'formatted output' option.

To eradicate this the only possible way is to uncheck those two default settings. Incorrect. As I noted, the documentation tells you what you need to do. Bring up the online help, switch to the Index tab and search for Job Properties. At the bottom of the Help page, click on General on the Sequence...

I find that a strange problem as well, remembering the dsx files that I've edited being pretty much 80 character records. Or so.

It is considered to have failed if the 'Automatically handle activities that fail' option is enabled, yes. Simply enough to 'fix', however - the documentation clearly states how you can handle it so the 'automatically' part doesn't kick in. In other words, it only handles it if it thinks you haven't.

jdmiceli wrote:Return codes are:
0 = positive row count greater than zero was found
1 = zero row count was found
-1 = error condition of some sort was found

I don't see where this is happening in your code. Without intervention, you get the actual count returned, not simply a zero or a one.

We know, we've seen your other post. Have you run this by your Oracle DBA, see if they can shed any light on the issue?