DSXchange

It would be much simpler if you just "upgrade in place". For a new server - yes, you will need to export and import all projects. That and transfer all existing data/hashed/etc files you'll need to persist.

Did you turn off the "View / Show Categories" option as noted?

Check that?

Ok, confusing. You still haven't stated upgrading from 7.5.1 to what? And what "new datastage server" are you talking about - are you building a completely new box for this upgrade to be installed on?

You just went out and unlocked ALL jobs? Bad Idea. If you can't see the job listed in the Director then your project has become corrupted, possibly from your overzealous use of the UNLOCK verb. You'll probably as a first effort need to try and REINDEX the project, search the forum for that word or D...

ps. You're not having a problem, a DATE is a DATE regardless of the format some tool displays it in.

There's an option in the stage to "Include comment". Disable that.

Check the length and compare the first X characters where X is the length of the smaller of the two.

ps. That's not "backward compatibility". More like "forward"... and everything should always be forward compatible.

Describe your job design. Explain in detail what "no records has been transferred" means.

Double-click on the function itself in the Manager (Routines\sdk\RowProc) - it is "explained clearly" in the Long Description, as are all supplied routines.

Every time? No. I suppose if you change the input or output format you would, but not for just an internal code change. Unless that's a new "feature" of 8.x.

I suggested you open a case with your official support provider, not read the release notes. Although that wasn't a bad idea but it certainly isn't the only thing to do.

Then it seems you may need to trim a 'newline' directly - CHAR(10) rather than @FM.