DSXchange

Or you could just refer to the documentation that tells you that BLOB is not supported.

You can encrypt any string you like. I typically only encrypt passwords. While I have not used it with dsjob, I have used it successfully with other commands including istool and importexportmanager.

You can also use "dot notation" for example

If you think for a moment about what's happening inside the Join stage, there's nothing that would affect the sorted order of the rows passing through it.

Of course, if the next downstream stage forced a re-partition or a collection, you could well lose your sorted order because of that.

Is the Copy stage doing anything, such as dropping or renaming columns?

You can encrypt values using encrypt.sh (in the bin directory of ASBNode or ASBServer) and use these (for example {iisenc}s8dwdS#sf9wd1f3ssfre--) in your command line. The encrypt.sh utility uses AES-128 encryption by default (you can choose something else).

You have it the wrong way around. You need RAWTOHEX in the SELECT.

Read my post again. Carefully.

For example, you could use an Execute Command activity in a sequence executing an echo command and a redirection operator to overwrite the file. In the Parameters field include literal text and job parameter reference(s).

HEXTORAW() or equivalent function in the target INSERT or UPDATE statement.

What Roland said. I have in the past created generic jobs of this kind to move data from Oracle to MySQL. Five jobs for 837 tables. I read the metadata from Oracle system tables (you could use DESCRIBE) to determine which of the five generic jobs to use. The one that handled BLOB had the functions I...

DataStage should resolve it if the query is in a stage. Make sure that the spelling and casing of the job parameter reference in your SQL query exactly match those of the actual job parameter defined in the Job Properties Parameters page. Also make sure that the value provided for that parameter is ...

Note that options -wait and -jobstatus are mutually exclusive. If you use -wait you will need to remove it to use -jobstatus option.

Disabling NLS won't really affect performance. The fact that NLS is installed means that characters are processed using multi-byte-capable techniques. Installing without NLS is a "pure (extended) ASCII" environment, single-byte character set only. That would perform better than with NLS in...

I never put password in .odbc.ini, and rarely username.