DSXchange

Right, that would be the typical reason for that message - someone "viewing" the log messages via the Direcor.

Unless you play some games and contain everything within a single stage, data will "flow between" the ETL Server and the DB Server in all cases. And with both source and target db connections in the job, data will flow "back and forth".

What have you tried? Oddly enough, the Stored Procedure stage would be the first thing to try.

So, what was the resolution?

"Code" tags preserve whitespace. Here is a overview of the Sequence job. Loop Companies (General Job Processing) Loop Project Files for Companies (General Processing) Check if File is Empty (Nested Condition ) if not empty then process otherwise go to sequencer Loop Projects ...

Our resident XML Guru Ernie Ostic has posted the details in his blog, everything should be there:

http://dsrealtime.wordpress.com/2007/12 ... -a-source/

Basically you use it to do an "ls" to capture what the XML stage needs and then tell that stage where to find the file.

That's kind of overkill, one or the other should work but the basics are sound. The output is a dynamic array and what you are not seeing (or taking into account) are the Field Marks between the elements. Either remove them or just check the first element. Some examples below, not an exhaustive list...

No, anything at that level would be too late. That would abort the Sequence itself and possibly any currently running jobs as well, not the one that ended with warnings.

Yes, it's a Boolean function so it either returns true or false and the Not() function reverses the results. The other is a Link Variable Boolean and is automatically set for the lookup. And all I was saying was that I prefer using it (anywhere) to check for hashed file lookup success/failure rather...

IsNull(Field) = 0 is the same as Not(IsNull(Field)) as zero is false and any non-zero value is true. Nulls are always returned from a failed hashed file lookup.

I prefer using the NOTFOUND link variable nowadays.

Since you are on a Windows server, the ODBC stage is your man. I'd suggest searching for "ODBC Excel" as this has been discussed here in the past. A lot.

There is this, I assume it is still valid:

http://www.dsxchange.com/viewtopic.php?t=106971

Sequence level would be too late, so you need to handle it "in job". Several ways, some off the top of my head... Set the warning level when the job runs very low. Send problems down a reject link set to abort on the first record. Check the JOBINTERIMSTATUS after job and abort the job if is says it'...

Oh, so the issue is the one that ended with warnings does not rerun? Your jobs need to Abort as well, so you'll need to ensure it aborts as well whenever there are any warnings in it.

I assumed (perhaps inappropriately) that it was mounted in some fashion to the UNIX server - NFS, Samba, whatever.