DSXchange

Best to start from the Project directory itself and issue the 'dssh' from there (bonus - no LOGTO needed), otherwise make sure you say 'NO' when it asks you to setup the bin directory for DataStage access.

The variable shouldn't matter... sounds like you could have a permissions problem. Check the DSParams file in the project.

And it could simply be actual data that is too large when compared to the target field, something that isn't enforced until it goes to the database. Is your message from DataStage or from the target database? The former means the job noticed the data was larger than the metadata and didn't even send...

Well, to be fair I did say 'get you started' rather than solve your problem.

Have you posed this question to your official support provider? See what suggestions they have?

I don't see any need to replace stages. If you can't get any joy from your DBAs and your network people (you have involved them as well, yes?) then get your official support provider involved.

No, if you only run Server jobs you'll be fine without one.

It won't. You'll need to check if the AIX server has a supported C++ compiler on it and if not, purchase one.

Sure seems like you did. I know there's a way to copy that verb back into this project from another but don't know the syntax off the top of my head and don't have any DataStage access. Someone will be along and supply it, I would imagine... that and help correct your hashed VOC delete issue.

So... are we resolved?

Or alternately:
Where the value of the parameter is "/opt/BI".

I'm not sure just how possible that would be, especially when complicated by having to 'check the email' and the attachment as well. Have you done any searching here? An exact search for 'Lotus Notes' turned up 35 other topics, something there might help at least get you started.

Is the Server CAPITALS transform (aka 'MCT') smart enough to change "sam smith-jones" to "Sam Smith-Jones"? I thought it was strictly whitespace reliant and thus you'd end up with "Sam Smith-jones".

There's no "if-then-else" needed here. You have two output links and always fully populate both sets of columns with the same data. The key is the constraint so that only one or the other 'fires' for each record and the constraint can make use of the Key Change column.

You already posted this. Seeing as how this is the wrong forum for your question, I moved the first one and you've already had a couple of replies:

viewtopic.php?t=139585

Locking this one.

Nope, not clear at all.

Can you draw a 'picture' of the job?