DSXchange

That's called a 'vertical pivot' - search the forums for discussions on the techniques needed to accomplish that.

Welcome. :D sqlldr isn't in your path on the remote system, hence it cannot be found. And there's no log file because you never launched sqlldr... unless you mean whatever Func_Log_Writer is supposed to do. If so, don't see how anyone can comment on that with no source. So it seems you'll need to en...

I don't know about anyone else, but man am I ever satisfied! [ahhhh]

New in the 8.x release.

Thanks for posting that, Ernie. Bookmarked your blog.

Hard to tell from your description what exactly you are doing. Shell variable? Meaning, you've got this command in a shell script and have passed the parameter to the script? If that's the case, then use $1 (assuming the first parameter) rather than $catg_name. Environment variable? If that's what ...

The comparison itself would be valid regardless of how the input is sorted, however you are correct in that most people would use it with sorted input.

How? 'PART1' is neither numeric nor a number but rather alphanumeric and thus a string it must be.

But that particular handle has been released, so how can the code that follows actually run the job again?

Unless there's some magic snippage in there, critical pieces of code that we are missing...

The XML Input stage needs an input link. Since there is no PX folder stage, the Sequential File stage will have to take its place and luckily it supports wildcard pattern matching so it can 'read' multiple files much like the folder stage. It can also be set to capture and pass just the filename, wh...

That's because the 'subsequence' didn't abort, I'd wager. That must happen first, then depending on the main Sequence design it could abort as well and all be restartable.

No, there's nothing automatic about invocations. You will need to control that, probably simplest by incrementing a number each time.

Specifically, when you attach to the job: hJob1 = DSAttachJob(JobName.InvocationID, DSJ.ERRWARN) I'm somewhat surprised that the next chunk of code actually works, that you could attach using the old handle again and not the job name: * Release the handle for the Job ErrCode = DSDetachJob...

Really? Scroll back up to the top, to the first post you made. Should be obvious.

Hmmm... assumed that was what you were already doing and the issue lay elsewhere.