DSXchange

Ahh, I understand now. I thought that it was only one time at bat. Maybe the cricket here is rubbing off on me.

Is your disk that the hashed file resides on filling up to 100%?

If not, try making your derivation for the key into OCONV(KeyColumn,'MCP') to replace unprintable characters with a '.' and see if that makes a difference.

I get that part, but if people steal bases doesn't that give a maximum of 4 (same as for that home-run-with-bases-loaded)?

How can you do that? Do Australian rules allow 2 runners per base?

-Arnd.

Since the export checks for locked jobs I assume that it also takes and holds locks, so two jobs running concurrently might lock each other out of jobs - but I haven't tried it either. Any jobs in the export file should be OK, though.

Rafidwh - did you actually read my post? Please look into your BASIC programming PDF file and search for the MCN conversion and that will answer your question on what can technically be done with alphabetic characters in a numeric string. Nobody here can answer what needs to be done according to you...

There are no hard rules for this, each implementation starts off with different conditions that are company dependant. The most important part of best practices and standards is that they are created early and are adhered to. It helps if they are simple and clear as well. Creating a good set of nami...

A transform stage call must be to a function, so create your own function and put the call the DSLogFatal() in there.

I still think you have RCP turned on in the flow of your job, it is the explanation for your error message. Perhaps you are specifying the columns in your user-written SQL somewhere; what would happen if you try to write to a dataset instead of your database -- does the dataset schema contain the 2 ...

You changed your metadata since the first post. Instead of my 2 stage variables, just use your two columns, otherwise the solution is the same.

Check to see that you have turned off RCP (runtime column propagation)

If your CHARacter field contains only digits then you do not need to perform any explicit conversions, see the example I gave in the previous post. If your CHAR fields contains mixed numeric and text then you will need to provide some conversion code to make sure that DataStage interprets this field...

Ajit, the sequence then has nothing to do with your question. Once a job has finished with a status of "warnings" you cannot change it to "aborted". There are a couple of threads active at the moment about how to make a job abort when it has warnings. The easiest method is to have the job abort when...

Ajit,
I am not sure what you now want to do. If a job finishes with warnings do you want to change that from the sequence so that it shows that the job aborted? Or is the real question on how to make a job abort when now it is just giving warnings?

I understand that. In order to answer your question it might be a good idea to answer mine.