DSXchange

Not really any different from your other post discussing this data type I'm afraid.

At this very moment? I'm afraid not. Can you clarify a couple of things, please? What 8.x version are you running and is this the 'new' XML stage? I'm guessing it's not but thought I would ask to be sure.

Sorry, got nothing to add except to note your interesting use of literally white whitespace.

Why would it sometimes fail? Sounds like the proper solution to me.

That's too bad about the lack of the diagnostic message, that will complicate trouble-shooting this. Let's see if anyone else has any words of wisdom. In the meantime, perhaps it might help to post the contents of your dsenv file as that's where your shared library statement would be set.

If the job runs fine with the parameters in place and the only issue is with View Data, then in your shoes I'd be looking for a patch. Work with your official support provider or check on Fix Central.

Verify with your official support provider.

Are you enclosing the parameter name in hash marks - #DB_CONN1# - and have you ensured that the parameter name exactly matches to the name defined for the job, including case? Couldn't tell from your post, hence the question.

Hard to say. If you Reset the aborted job, is an entry added to the log saying "From previous run..."? If so, post the contents.

You'd need to create a custom routine and then run that in the Sequence job and that means writing it in BASIC. I think you'll find Ray has some prebuilt that he gives away on his site that do "date math"... let's see what he says when he wanders by. :wink: Once you have computed this peri...

Or I assume the proc could have been changed to issue the commit.

Regardless, nice find.

ExecCommand tab Command: echo <activitystagename>.$CommandOutput<3> Parameters: <pathtosequentialfile> Triggers tab Expression: $CommandOutput<3> = 'Y' If you go this route... no, that command would not be correct. You echo the contents of the file and then as you correctly noted, use the result in...

iq_etl wrote:With the Execute Command stage having it's own trigger tab, do I even need a Nested Condition?

Need? No, which is why I noted you could do all this with or without that stage.

I don't think "$CommandOutput<3> = 'Y'" is an expression. It certainly is... it evaluates to true or false. Use the helper to build the expression, even if you have to edit it later to complete it. As I noted, you need to include the name of the stage in the variable so it knows which Com...

Looks like Andy was assuming you'd be getting two separate counts (or simply counting two files) via two Execute Command stages and then the Nested Condition stage would be the one doing the 'evaluating' of the results, deciding if they matched or not. If you've got everything in one file with three...