Buildop: Dropping component because of a prior component

[bikan]

Hi ,

I have a buildop stage having two i/p fields & one o/p field. The buildop is doing base64 decoding.

input file ---> BuildOp ---> Peek Stage

The decoding logic is working fine and I am getting desired output from the Buildop stage.

But I am getting a warning everytime I run the job.

The warning is like
"Dropping component "XYZ" because of a prior component with the same name."

XYZ is the column which is present in both input as well as output link and the decoding is done on this field.

RCP is disabled in the job.

In Buildop:
1. All column names on the input link and 'input table schema in buildop' are same. Similarly,
2. All column names on the output link and 'output table schema in buildop' are same.

Is this creating problem?
What is the best way to avoid the warning (without suppressing it)?

[sud]

I think you might be using auto transfer of columns, do it programatically in the loop logic.

[chulett]

An exact search for "because of a prior component with the same name" got me 27 hits including your post, did none of them help?

[bikan]

Autotransfer is off and I am moving fields in the program.

Yes, the search did give me some existing results but none of them were of this sort where there is only one input link and one output link and were related to buildop or similar stage.

Please help me resolve this issue.

[srinivas.g]

handle that warning through message handler management in datastage director

[srinivas.g]

handle that warning through message handler management in datastage director

[bikan]

As mentioned earlier, I do not want to handle the warning as it is not comply with the standards here.

Please let me know if there is any other way to remove the warning.

[bikan]

As mentioned earlier, I do not want to handle the warning as it does not comply with the required coding standards given to us.

Please let me know if there is any other way to remove the warning.