DSXchange

Command Output is a dynamic array so there a Field Marks included that are causing your comparison to fail. Try array notation:
Or strip them:
And see if either one works for you.

You'll have to remove the truncation from the target stage itself as there isn't a mechanism there to make it conditional, as far as I know. Perhaps others have dealt with this and can offer more cogent advice, I'm thinking of some kind of a routine call that is only made when the first row passes t...

You can include a job parameter like that in a source query but since it's a job parameter it must be set / passed in as the job is invoked, trying to set it "before job" is too late. One common way to accomplish what you are showing here is to stash the first value in the USERSTATUS area ...

Yes. Anything "before" the stage happens when the stage is opened / initialized / when the database connection is made. It doesn't wait for the first row to arrive before it fires, if that's what you are thinking would happen.

You posted in the wrong forum. The forums here are based on product & job type and this one is for questions specific to the Information Analyzer product.

Question on Parallel jobs belong in the Enterprise Edition forum. I'd move this myself if I had the power but I don't here.

Agreed, that was a bit lame.

I'm locking this, if you want to have a real discussion on "transformer lookup" start a new post.

I have neither the time nor the ability to test anything like that. Interesting point, though.

What does UTILITYRUNJOB return? If it does 1 = Success, 2 = Warnings (etc) then that trigger will not consider that "OK" as it needs to return a 0 for OK.

There is no ability to use wildcards in the actual filename now that I think about it, so that second option comes off the table. As far as I know, it should have worked just fine in the Filter however. If you open up a Cmd window and run your 'type' command from it, does it work correctly, write th...

What kind of not good data?

Thanks... but not really germane to a discuss of the restartability of Sequence jobs.

The square brackets [] are the substring operator. So "YourSample[1,4]" will get you "2004", "YourSample[5,2]" will get you "04", etc etc.

Too slow.

In version 7.x I found the status of "Stopped/Restartable" to be basically a... lie. It isn't restartable. As you've seen, only "Aborted/Restartable" can actually be restarted without Resetting first.

Not sure if that was ever fixed...

No.

Yes.

Un-hijacked. Please start your own posts in the future rather than replying to an old, unrelated post.