DSXchange

XML files? How are you reading them? If you use a Sequential File stage then the CR/LF pairs could be an issue but shouldn't be if you let the XML Input stage read them directly via the URL/File Path option.

From a contrarian point of view, I never saw buffering or leveraging the IPC stages as any kind of Silver Bullet. You'll also find posts here that issue specific cautions on their use (I think from Ernie) as the buffering can introduce some rather... unexpected... results. I've built thousands of Se...

You might try pinging "kcbland" here, not sure otherwise. He used to visit quite regularly but I haven't seen him in these parts in a long time.

Shouldn't dssearch leverage Job Control tab instead of Dependencies tab? Shouldn't everything in the Job Control tab be listed in the Dependancies tab? :wink: It's a bug, as far as I know. Then what do you use to find the names of Sequence which are using a particular Job or another Sequence? My gi...

So... missing a word... couldn't what it? Find? So, it was there and still was not found or it wasn't listed there? I've seen the latter but not the former but I'd be the first to admit I never used dssearch all that much.

It leverages the Dependancies tab on a Sequence when it searches, from what I recall.

You said you already use USERSTATUS in the job, so that's off the table. To write to the log, simply call DSLogInfo().

If what you currently have is working, it may not really be worth the effort to clean out the cobwebs... unless they are really bad and make maintaining/understanding them overly difficult.

The Nested Condition would be the way to go, that and perhaps a Sequencer set to 'Any'. You may be able to make it less 'cob-webby' if you create individual Sequence jobs and conditionally run them from a Master Sequence.

Since you can't use USERSTATUS write it to a file, that or the job's log. File would be easier to retrieve.

Then I wouldn't change anything.

Nagin wrote: Sorry Ray, We have version 8 parallel edition. I don't know how to move the post to parallel edition.

I "moved" it... since it was already in the right forum, all that was needed was an edit of the original post and (fyi) you can always edit your own posts.

Are you starting the jobs from the Director?

Many ways to skin that cat. In a Sequence job, trigger conditions could drive the flow, check for a count > 0 in the flow and it could just end gracefully at that point for a zero count, that or perhaps send an email. Or a Nested Condition stage could do the same and make the check a little more obv...

Interesting... never knew that a browser would show something like an empty tag differently than it was in the source but just confirmed the behaviour for myself. But then it was never my tool of choice to check the validity of xml. Normally all XML parser's can read an empty tag in the format <empt...