DSXchange

Doesn't really answer the question. What character sets are involved here, source and target?

What exact 7.x version are you running? Attachments were not supported until 'later', I think with 7.5. And you need to use the routine rather than the Notification Activity stage, yes?

And is your actual syntax more like TRIM(Link1.ColumnName,'0',"L") and what stage are you doing this in?

Multi-byte character set?

First off, what makes you think it is not working? What is your target field after the trim, another varchar or a decimal?

Actually, they are $PROJDEF and $ENV (plus others) and oddly enough they are documented. Don't take this the wrong way but rather than ask people to regurgitate portions of the manuals for you here, why not take a stab at looking it up yourself first?

Hmmm... that's got more to do with Universe than anything else and the multi-valued fields it supports. May be best to search here for 'Rocket Software' who own that product now and see about downloading the Universe manuals they have.

Yes, all versions will. Still a 32bit application but should run just fine.

Sounds like you need a precursor job to determine "if FACT_PRODUCT contains already certain records", whatever certain records means. Then a Sequence job could determine what to run next.

The one you were writing to with the write cached enabled, looks like "/home/migration/X"? I've seen similar things happen to job log files when they get hammered by a bazillion warning messages. I'm wondering if simply waiting would have allowed it to clear itself up on its own? May have ...

Then you've "set" it and it will be properly in your environment if you source the dsenv file in your .profile or manually before executing the orchadmin commands.

That search also found 15 matches, several of which were marked as Resolved. None of them helped you?

I don't see how 'nodes' play a role in how a Sequence job passes parameters, neither it nor the Routine Activity have any parallel processing in them. Sounds like it's now time to get into the gory details of your routine. Can you post the code here now, please? And you really need to include more l...

Searching here for "This Key is already associated with an element of this collection", apparently you have faced this problem before.

Out of curiousity, what user is the job that failed running under, something other than dsadm? Have you confirmed permissions not just on the file but on the entire path to it?