So let me see if I understand this. As far as the actual processing that takes place in a job, Data Element has *no* effect. If I specify a column on a UniVerse stage as SQL type INTEGER and the Data Element as String, the INTEGER specification controls what gets stored in that field and the String specification is ignored. (Other than by human readers coming into the project later who would then think I was an idiot ).
So unless you are playing with the MetaData repository by some other means, you can always just ignore the columns Data Element, or eliminate it entirely with no effect on processing.
Correct?
Regards,
Clif
Wednesday, May 09, 2001, 7:53:45 PM, you wrote:
> Data Elements are a really nifty idea that never really took of or is
> used in DataStage.
> The
> reality is these are rarely if ever used but are kind of nifty.
Data Elements - whats the use :-)
If you apply data elements to a table columns, there is a corresponding data element definition when you create transforms. I believe the thought here is match which transforms would/should be applicable to what columns. Since this is not usually defined or practiced I would say your assessment is be pretty much accurate.
Regards,
Allen
----- Original Message -----
From: "Moderator"
To:
Sent: Thursday, May 10, 2001 7:49 AM
Subject: Data Elements - whats the use
>
> So let me see if I understand this. As far as the actual processing
> that takes place in a job, Data Element has *no* effect. If I specify
> a column on a UniVerse stage as SQL type INTEGER and the Data Element
> as String, the INTEGER specification controls what gets stored in that
> field and the String specification is ignored. (Other than by human
> readers coming into the project later who would then think I was an
> idiot ).
>
> So unless you are playing with the MetaData repository by some other
> means, you can always just ignore the columns Data Element, or
> eliminate it entirely with no effect on processing.
>
> Correct?
>
> Regards,
>
> Clif
>
> Wednesday, May 09, 2001, 7:53:45 PM, you wrote:
>
> > Data Elements are a really nifty idea that never really took of or
> > is
used
> > in DataStage.
>
>
> > The
> > reality is these are rarely if ever used but are kind of nifty.
>
>
Regards,
Allen
----- Original Message -----
From: "Moderator"
To:
Sent: Thursday, May 10, 2001 7:49 AM
Subject: Data Elements - whats the use
>
> So let me see if I understand this. As far as the actual processing
> that takes place in a job, Data Element has *no* effect. If I specify
> a column on a UniVerse stage as SQL type INTEGER and the Data Element
> as String, the INTEGER specification controls what gets stored in that
> field and the String specification is ignored. (Other than by human
> readers coming into the project later who would then think I was an
> idiot ).
>
> So unless you are playing with the MetaData repository by some other
> means, you can always just ignore the columns Data Element, or
> eliminate it entirely with no effect on processing.
>
> Correct?
>
> Regards,
>
> Clif
>
> Wednesday, May 09, 2001, 7:53:45 PM, you wrote:
>
> > Data Elements are a really nifty idea that never really took of or
> > is
used
> > in DataStage.
>
>
> > The
> > reality is these are rarely if ever used but are kind of nifty.
>
>