DSXchange

I counsel... patience. See if someone with any ideas (which is not me, btw) wanders by.

Best to open a support case while you're waiting for help... if you haven't done so already.

Pete - there's a forum dedicated for issues like this (amongst other things) and I've moved you there. As in here. And as noted in other discussions, emails are not the way to go, please text our Editor: I don't want to suggest that Andy didn't reach out but I am really only a phone call away. Pleas...

It is a "built-in routine", specifically part of the Server SDK library. Sounds to me like you were exploiting a bug in the earlier release, something corrected in the (many) years since 7.5 hit the streets. I don't recall them shipping with source code but could be wrong. Whatever you end...

Pete, split you into your own topic.

Original discussion is here.

qt_ky wrote:Not normal!

Abby... something.

No worries, let me get you moved into the correct forum.

So... you've said "dataset" now... does that mean this is actually a Parallel job?

Well, that sucks. Guess we'll need to see who wanders by next with some words of wisdom. I no longer have any way to test or play around with anything DataStage, unfortunately.

From what I recall, yes. I'd suggest you put just the "cat" in the command property and the rest in the parameters property so that when it builds what it needs to run it knows there might be a parameter to evaluate.

If I'm following what you are doing here, you should be able to use the DSJobInvocationId macro for that.

I put the word masking in quotes for basically the same reason, wondering what exactly it meant here. We've had several conversations over the years here when people were mixing it up with other techniques like redaction and even encryption at times.

Whatever you are thinking should be matching up to the :1 bind variable needs to be marked as a key and it doesn't sound like it is. If it is, we'd need to know how your columns are configured in the lookup, in and out.

Docs don't specify. You should be able to tell from the output column, is it a 32 character string? That would tell you it's MD5.

Well, that would certainly do it.

Thanks for posting your resolution.