DSXchange

OK, I was assuming a standard 'looking up from the same hashed file being updated' scenario, all from one transformer. You can't do the normal creation / clearing in the write link as the reference lookup happens first. Now that I've reread your original posts and see the job design, I don't see any...

Yah, yah Mr Henry... give me Perl or give me death.

Check with your support provider, that's a known issue with a patch available.

Right... and no need for a separate job, I always add that link to the using job, connected to the lookup hashed file. And most importantly - left trouser leg.

Or push the button in the Designer that looks like the IE icon, it will generate an HTML document with everything in the job.

Then you're chock full o' bugs... better get patching.

Then it's time to mark this post as Resolved using the button at the top of the screen, it seems.

AFAIK, you'll need to compute that yourself from the elapsed time of the job run and your count.

Ray has some pre-built Server date handling routines he loves to give away. As they say 'Why reinvent the wheel?'

Then please mark the post as Resolved using the button at the top of the screen.

Ah... my Parallel docs are 7.5 vintage.

The needful is documented in the online help. Read about the 'D' code for OConv() with the format option WA to get the full weekday name.

Perhaps "does not provide an example of" doesn't mean the docs are bad but rather that it doesn't exist. Where did you find a reference to %mmmm? As noted, it's nowhere to be found in the pdf docs. Guys, how does one convert that '01' in the example date to 'January' rather than 'Jan'? You...

Hmmm... I've done CLEAR.FILE on overblown corrupted logs and don't recall it every having a problem. But then perhaps I just got lucky. Or my memory is shot.

Or that.