DSXchange

Or an existing function, since it seems to be expecting a paren?

Sachin - if you have a specific question, please ask it. At the moment, I feel like I'm just repeating myself on the explanation, which I can't imagine is all that helpful. Rather than imagine your job design - build it. Run it. Check the outputs and the logs to see how it behaves with respect to t...

Again, what is unclear? The hashed file is cleared when the job starts and the stage is opened/initialized, not when the first record hits it. So, it gets cleared twice and then the records flow.

Sorry but elaborate on what aspect? What is unclear? Colin may need to be elaborating as well as we don't know the actual job design.

Check the online documentation for 'Macros'. At a high level, just... use it. We'd need more specifics about what exactly you are trying to do to give more specific advice.

Post the other log messages. Reset the aborted job and post any 'From previous run...' message as well.

How can this be what? Working? The 'Clear' happens when a job starts and the stage 'opens' so guessing it is happening twice right up front when it doesn't matter.

If you are looking for a macro, a job can find out what is 'calling' it using the DSJobController macro. Same as via the DSGetJobInfo() function using the DSJ.JOBCONTROLLER Info Type.

Automatically stops? Sounds like you are running this from the Director with a Row Limit of 100. If so, it would log an entry similar to this:

At row 100, link "X"
Run stopped

MattKeevil wrote:The FastTrack software looks like it's a POST development documentation tool

Nope. Pre.

Never mind the fact that there's no indication of a need to delete anything, just detect.

Pretty sure someone has already posted on this issue, but I don't recall if there was anything in the way of a resolution. Curious what IBM Support comes up with.

It should only be 'greyed out' until you select / highlight an object on the right-hand side... like your shared container.

Ack!... that's correct, I always use it to strip characters and forgot how the replace works. You need a string of spaces for the second argument as long as the string of special characters, as it is a one-to-one positional replacement.

I built a routine to leverage the former and call it in the Initial Value of a stage variable. That sets it once and then I can apply it to all records in the load.