DSXchange

So the same error again, this time with a "C" rather than a "D". I don't have time right now for more trouble-shooting but I'll ponder this.

Yes, it does... that why I posed it more as a question. I thought that might be ok since you are considering a looping sequence. And you didn't miss anything significant so I unmarked it.

You'd have to post the error.

UserStatus only holds a single 'record' or element. Are you able to use UtilityRunJob for this? Meaning rather than the Server job writing the name of the job to run out it actually runs it instead.

eostic wrote:There are a lot of us 'ol server types around.

<raises hand>

That wasn't a question. If your scheduler creates a ticket when the threshold is passed, why not have it also stop the job?

Not sure, my DOS days are way behind me. First thing that jumps out at me though is I don't believe there is a /D option for FIND command, so it assumes it must be a file.

Trying to remember what we ended up using after job - XML Beans, perhaps?

You could probably leverage the Field() function, one stage run referenced twice where the first takes field 1 and the second field 2.

Have your scheduling tool issue the stop request from the command line.

Do you have the MKSToolkit installed on your server? You should nowadays. If so you can use UNIX commands which are a wee bit easier on the eyes:

wc -l D:\APP_DATA\VBS\PAS\CIA\REJECTS\SOURCE\ALISSourceRejects.csv

First question - why format it at all? It's not anything needed and if you want to see it formatted open it in something like IE. To pursue this, in your shoes I'd look into something like a 'pretty printing' utility you could call from the command line as a post-process that would output a formatte...

That could just be trigger expressions. After you count the file (Execute Command stage most likely) then two triggers from it could evaluate the output and branch to either a Job Activity stage or a Notification stage.

What have you tried so far?

Right, BO moves what it can into the database and anything it can't gets processed in the engine like normal. And if pure SQL means SQL rather than something like PL/SQL then yes, that's my understanding.

"Balanced Optimization approach is comparable to ODI ELT architecture." How true is that statement? I would think "comparable" is a decent choice of words. Balanced Optimization is also known as Push Down Optimization and moves applicable processing into the target database, ess...