Warnings using Change Capture Stage

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
SBSA_DW3
Premium Member
Premium Member
Posts: 2
Joined: Fri Jul 25, 2008 1:31 am
Location: Johannesburg

Warnings using Change Capture Stage

Post by SBSA_DW3 »

I am using a Change Capture Stage in a job and get the following waring:

CCP_01: When checking operator: Defaulting "Party_Class_Start_Dt_File" in transfer from "beforeRec" to "outputRec".

Could any one please suggest what settinngs can be changed to get rid of these warnings.

Thanks!
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Welcome! :D

First suggestion is to search before posting as more than likely you're not the first person to have any particular problem. For example, when I did an Exact search for "in transfer from" I got 37 hits, many of which seem to be identical to yours. See if they help, then post back if you still have questions.
-craig

"You can never have too many knives" -- Logan Nine Fingers
mahendrasoni1983
Participant
Posts: 2
Joined: Thu May 17, 2007 6:43 am
Location: hyderabad

Solution

Post by mahendrasoni1983 »

go to the stage property of Change capture stage ->option->change mode->choose explicit key,all vaues->ok->compile the job n rerun it
mahendrasoni1983
Participant
Posts: 2
Joined: Thu May 17, 2007 6:43 am
Location: hyderabad

Solution

Post by mahendrasoni1983 »

go to the stage property of Change capture stage ->option->change mode->choose explicit key,all vaues->ok->compile the job n rerun it
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Please explain the logic behind this suggestion, and why you believe that doing what you suggest will eliminate the particular warning.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply