DSXchange

OK, then... green stage?

So... no indication from IBM of a bug or possible bug in that version of the stage? Are they at least still working it with you?

Scroll down to the Index function in the URL below for the syntax. You'll need to copy/paste the whole thing as it is not clickable here, unfortunately. Something like this perhaps, adjust as you see fit: If Index(lnk_Cast.BASEBALL," ",1) = 0 then <space not found logic> else <space found ...

No, that's not what the Field() function does, best to recheck the docs for it. Why not shows us the Index() syntax you used? That should be the most straight-forward test to make.

The Index() function. A non-zero return value = success in this case.

That makes zero sense to me. In your shoes, I would involve support.

Using all UPPERCASE it doesn't surprise me no rows are returned unless you also do the same to the field being tested, that's an old trick for a 'case-insensitive' match.

Sorry but... Blue stage? Green stage? Can we use their proper names, please.

JKenklies wrote:I'll check the -jobinfo option next week. Thanks for that idea!

You will need to parse it out of the output from the command but it's very straight forward... grep / cut or something similar.

First I'd suggest you not worry about the Sequence job and its phantoms at the moment. It is waiting for the Parallel job to complete so that's normal behaviour. Concentrate on the Parallel job... and my first suspicion would fall on the webservice call, especially since it seems to be volume relate...

Welcome! First I want to note that I've edited your post to replace all occurrences of "sequential job" with "sequence job" as that is the proper terminology. Secondly, which part of the process "stalls" - the parallel job? What do you do in that case, kill it? And does...

And still no answer to a simple yes/no question... guessing that means no.

More than once you've been asked if you've contacted support on this issue... have you?

To be honest, while I used USERSTATUS more than my fair share in the past, I never leveraged the "-userstatus" option from dsjob. I would suggest going back to the normal "-jobstatus" so you can know what happened to the job, did it end gracefully or not. If it did RUN_OK and you...

It's just a lookup table which lends itself to the Convert() function rather nicely. Or you could code something in C++ or even BASIC and use a Server job. All kinds of ways. :idea: And there's absolutely no need to quote everything each time you reply, there's a perfectly lovely Reply to topic 'but...