DSXchange

I can't comment on deadlines and effort involved, but I cannot understand how a customer or dba can recommend against doing an "update" on data and prefers doing a "delete" and then "insert" while not allowing bulk loads. Since the type of primary keys and constraints a...

A "delete" followed by an "insert" is going to be considerably slower than an "update". How about doing a join to your output table in order to determine which records exists and which don't, then perform 2 distinct DB2 stage outputs - one an "insert" and the ...

Try passing "drop nothing" as the parameter.

Instead of typing "dscmdexport ...", type "C:\Program Files\IBM\InformationServer\Clients\Classic\dscmdexport ..."

Stage variables will help here. Sort the data on ID and Seq. svLastC3 = IF (In.ID=svLastID) THEN NullToValue(In.C3,svLastC3) ELSE NullToValue(In.C3,"") svLastC4 = IF (In.ID=svLastID) THEN NullToValue(In.C4,svLastC4) ELSE NullToValue(In.C4,"") etc. svLastID = In.ID Pass all rows o...

Could you give an example of what the parameter looks like?

What error are you getting? Your attach-point shouldn't make a difference if you specify the full path to the .exe or if that directory is in your $PATH.

Could you give an example of what the parameter looks like? Perhaps you might need to add a dummy modify stage action such as dropping a non-existant column.

Patel, the answer is to specify the null value as "\&\#" so that the characters are escaped and not parsed. I found it strange, since by specifying "##" or "&&" it worked without a problem but with your "&#" I got the same error message. Intern...

the "dscmdimport.exe" and "dscdexport.exe" are client-side windows programs and not server-side ones, thus they cannot be run under UNIX.

Unfortunately the string "Rating "A" Note" is not well-formed and cannot be parsed using the column definition of quoted strings. Unless you can make the party creating the quoted string do this correctly, i.e. create a string "Rating ""A"" Note" , t...

I'm not sure what you mean by your question, could you perhaps explain in a bit more detail what "all records at a time" means? Datasets are easily defined and copied in DataStage jobs. Do you want to copy the contents at the OS level, without a job?

I see the problem on the command line, the "@ID >= COUNT.SUP" is missing a number before the COUNT.SUP, i.e. "@ID >= 40 COUNT.SUP". You have specified some sort of a filter. Go to your Director -> View -> Filter. "From" should have oldest selected "To" should ...

Could you please also cut-and-paste your error message to this thread?

If you save a copy of your job and compile and run that copy do you get the same error? Does this message occur for any other jobs in your project? Are you 100% certain that you deleted the original job (which will delete the defective log file)?