DSXchange

Or you could add a dummy "Customer9999" record to your DB and order the result by that column and check for the condition in your transform stage.

You need to look up the deadlock daemon in either the documentation or this forum. With this daemon started your locked jobs will get automatically cleared every {n} minutes. This is far simpler that trying to understand the locking mechanism and to identify the correct locks.

Gateleys,

for your information, although the MATCHES function will work; it uses 32 times more CPU than the INDEX function and that will add up to a lot slower execution or heavier CPU load in a real job.

Ray - thanks for that. I went through the list of functions since I had a nagging memory that something like that existed and I couldn't find it; then I checked the formatting of ICONV/OCONV in case the function was hidden in there. I'm glad you remembered that one, since the one-liner without a rou...

There is a known problem with the properties not opening which is fixed by applying a patch from IBM/Ascential that you need to go through your support provider to get.

That cannot be done directly in DataStage, since when the EOF is reached the job finishes. You can use an after-stage routine in a transform which is executed when the inputs are finished, but there is no way to set a "this is the last row in the file" flag inside the transform itself. Various means...

Do you mean the end of each record? Or the last line of the file?

Guido,

I have marked the post a non-premium so that you can take a look at a simple solution.

It would be sqlStr<1>, i.e. the 1st field (or line) of the output.

Sumit, the question is like asking "what is better, a minivan or a Ferrari"? Both vehicles are built for different purposes, you wouldn't want take your 4 kids to soccer in a Ferrari or race your minivan. The same principle applies to Server and Parallel Extender installations. One is built for spee...

I got 51 matches when I did a quick search for "error in dlopen" so the answer is that yes, others have had and resolved such problems.

(this sounds suspiciously like an interview question) Use a routine when you can't solve an operation without using one. The advantages and disadvantages of using routines are the same as with any programming language. Routines add execution time since they must be called (i.e. pushed onto and then ...

None of the builtin formatting options or other string function can do this in 1 line as would be necessary for a derivation in a transform stage. I would put in a very short Routine that does: Routine MyRoutine(InString) Ans = '' StringLen = LEN(InString) FOR Index = 1 TO StringLen ...

Sumit,

this question has been asked before, see this FAQ post

Your statement is a DataStage SELECT and that will return the selected information to a select list (this defaults to 0). You actually wish to execute a SQL type select, you need to add a ";" to the end of the command and this will force it to be interpreted the way you wish.