DSXchange

Use the Data Set Management tool to verify that this column is, indeed, in the record schema associated with the Data Set (that is, rather than in the record schema associated with the link with which you are attempting to read from the Data Set).

Why? Job names are unique in the project, so the category name would be entirely superfluous. Source code for dsjob is provided (in the manual) so you can "roll your own" that accepts category name. Though I fail to see how it would provide any benefit. Heck, you could totally rewrite dsjob so that ...

Why? Job names are unique in the project, so the category name would be entirely superfluous.

Check with your support provider to determine whether this is a known issue with this stage type. Also check to see whether you can open the stage type (a) in another job in the same project and (b) in a job in another project, just in case something odd has occurred in the design-time metadata for ...

Please verify that scale is set to 2 everywhere a mention of this column is made.

Do you have the DataStage deadock daemon (dsdlockd) running?

Instead of
Run
Wait
Run
Wait

move the statements around so that you have
Run
Run
Wait
Wait

Try doing an ODBC trace on both to learn how they handle the connection differently.

Try doing an ODBC trace on both to learn how they handle the connection differently.

If DRS can not do "replace existing rows completely" (which means "delete then insert") consider using an ODBC stage, which can.

With exclusive access to the account run DS.CHECKER. This will remove orphaned files associated with any incompletely deleted jobs.

Getting some learning would be best. A ".dsx" file is an export. And the only thing an implementation team could do with a ".dsx" file is to import it into a DataStage project. So your requirement that export should not be used is moot.

Post the exact and entire warning, which should contain information about the data in the record and why it could not successfully be sent to SQL Server.

I don't really have much else to offer. What stage type are you using on the reference link? If it's OCI you might try :1 instead of ? for the parameter marker.