DSXchange

It would seem that you've located the source of the problem. I'm not at a datastage client where I can check, but I seem to recall you use the local definition when using a parameter set value within a sequence to pass on the value.

No worries, and tell Rene that I'll do my best

Can you put an "echo" command into the script to ensure that the command line is working? Also, could your default date format be YYYY/DD/MM instead of the expected YYYY/MM/DD?

No, I tried that as well. It is the SQL command which takes the > 4000 character long string and thinks of it as a long and then gives the BIND error message. I finally ended up having to use a BASIC stage with BYTELEN() to make sure that I only sent appropriately sized strings to the Oracle stage. ...

Linda - please edit your post and enclose it in code tags so that the indentation isn't lost. It is returning a 0 because the call to DSDetachJob() is successful. You will need to use the result of DSRunJob() for the return code. Also, instead of the IF-THEN construct, you can do a simple JobHandle ...

I can think of lots of places where I would love to be able to get the unencrypted value of an encrypted parameter; but can't think of a place where I would need to and am pretty happy that the mechanism is secure enough to keep casual programmers such as ourselves from accessing restricted data.

And what about the other questions? Particularly whether you did a VarChar2(4000 CHAR) or a VarChar2(4000) {which implies VarChar2(4000 BYTE)}

If support did their homework then most likely there is little you can do.

Although I haven't heard the term "engine node" before, it would refer to the one node on which the DataStage engine resides. The term "resource node" is used a lot in the documentation and refers to the logical node or nodes where DataStage processes run.

There is no method for viewing the true contents of encrypted columns.

Database speed? Network load?

This would be a runtime error going to a VarChar column and it only occurs when the incoming VarChar data exceeds the 4000 limit; the error is raised during parsing of the insert statement. Even doing a Substr(bigString,1,4000) or a substrb(bigString,1,4000) doesn't help, either.

I have been fighting with the same error message for while, so I'll respond even though you said it was "urgent" ( nothing here is urgent to anyone but the person posting the problem, it is an all-volunteer site). First off, did you explicitly declare the columns are VarChar(4000 CHAR), th...

A Char(10) field cannot have 7 characters. This will only work if your source field is defined as CHAR(7), in which case your derivation will be "In.Char7Field:'AAA'".

Do you want to remove the warning message (job or project level message handler will do that for you) or remove the cause of the problem?