Modify stage

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
premupdate
Participant
Posts: 47
Joined: Thu Oct 04, 2007 3:37 am
Location: chennai

Modify stage

Post by premupdate »

Hi Everyone,

I was struggling with an error which states that
TGT_CL_FNC_MKT_IMT_TP: When checking operator: When binding output schema variable "outRec": When binding output interface field "CL_CODE" to field "CL_CODE": Implicit conversion; from source type "string" to result type "string[20]": Possible truncation of variable length string
.

This job comprises of lookup stage and three datasets

Code: Select all


                                   dataset2
                                     |
                                     |     
                                     |
        dataset1-----------------lookup-------------------dataset3
|
I had checked the datatype for the column "CL_CODE" in dataset 1 and dataset 2 through dataset manangement,there is the difference.
Dataset 2--->string
dataset 1---->string[20]

Dataset 2 comes as the output from another job from modify stage.
The column "CL_CODE" has the datatype string[20] before modify stage.

we are in need to trim the values.so we included

CL_CODE = String_Trim[" "](CL_CODE)
as the specification.

So after this the datatype for CL_CODE column changes to "string". This is the cause for the warnings in the second job.Please help me to rectify this.
Cheers,
prem
mdbatra
Premium Member
Premium Member
Posts: 175
Joined: Wed Oct 22, 2008 10:01 am
Location: City of London

Post by mdbatra »

Try applying Modify Stage Prior to Look Up Stage & perform the same operation on CL_Code what u did in Job 1.
Rgds,
MB
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Moderator: please move to parallel forum
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