DSXchange

Interesting... and only a partial answer. Searching for 'EndOfTransmission block' even without the 'block' part only returns this post out of the bajillions here over the years, so not exactly in common use. While I could guess what an EOT block might be, I'd settle for an explanation from the Maste...

Huh... hadn't noticed that, what pray tell does that one do?

Good guesses, you may very well be right on both counts.

KT?

viewtopic.php?t=135401

Ahhh... revisionist history is a wonderful thing.

Yup!

Yes, do that as soon as you are done with the handle, so typically just before the exit point.

And you need to not enable the 'Disable BBCode in this post' option if you want tags (like the quote tags you used) to work properly. I fixed your post, so just FYI at this point.

"Matches" has been there basically forever, I do believe.

So use two stages.

First pointer? An exact search here for "Parallel job reports failure (code 134)" to see if anyone else who has seen this error has any helpful information in their post.

Being a fat client, distance kills speed as you've noticed. Something like a Citrix server, as suggested, would solve that problem for you.

Index()

Where's your detach of the handle?

Sure, why not? Once in a great while you'll find things done in a proc that are difficult to do in a job but otherwise it should all be perfectly feasible and make them (typically) much easier to maintain... or at least you can pawn it off on the ETL folks afterwards rather than having to bother the...

Sorry, never know when to mention that and generally make the assumption that people know you should be targeting active stages, which principally means transformers in the Server world.