Hi,
I want to know what are the info which are carried by a link from one stage to the next?
In one of my jobs, I have a link from Transformer stage to a DB2/UDB API stage. DB2 stage is a target stage. Now when I replaced the existing DB2 stage with a new one, the link carried the Table name also. For example, my previous DB2 stage was pointing to a table "XYZ", now this new DB2 stage automatically pointing to the same table "XYZ". As far as I know, the links carry only the columns info (column names, derivation logic, datatypes,..) and NOT the Tablename. This is a property to be set in DB2 stage. May be I am going wrong as I don't have much experience on DS.
Can somebody explain me?
Thanks!
Information carried by a link
Moderators: chulett, rschirm, roy
Information carried by a link
Nitin Jain | India
If everything seems to be going well, you have obviously overlooked something.
If everything seems to be going well, you have obviously overlooked something.
If you used the canvas and added a new DB/2 stage and dragged the link across then the stage information will also be transferred over; this is different from the link information. If you were to drag your link to a dataset and then drag it back to the DB/2 stage your table and DB/2 connection information will have been lost.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Charter Member
- Posts: 166
- Joined: Wed Mar 16, 2005 6:52 am
- Location: Mumbai, India
As a general rule:
All info entered in the stage Page are associated with and stored as a property of the stage.
All Info entered in the <input/Output>/<LinkName> pages are associated and stored as a property of the link.
Each link will store 2 such sets of properties. 1 at the input and 1 at the output (Try setting input properties of a link and then flipping it around so that it becomes to output link to that stage instead of the input. Then flip it around again).
As Arnd mentioned above,post-disconnection, a link will remember its previous set of properties until they are overridden by connecting it to another stage.
All info entered in the stage Page are associated with and stored as a property of the stage.
All Info entered in the <input/Output>/<LinkName> pages are associated and stored as a property of the link.
Each link will store 2 such sets of properties. 1 at the input and 1 at the output (Try setting input properties of a link and then flipping it around so that it becomes to output link to that stage instead of the input. Then flip it around again).
As Arnd mentioned above,post-disconnection, a link will remember its previous set of properties until they are overridden by connecting it to another stage.
Amey Vaidya<i>
I am rarely happier than when spending an entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.</i>
<i>- Douglas Adams</i>
I am rarely happier than when spending an entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.</i>
<i>- Douglas Adams</i>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Under the covers the design information is stored as jobs, containers, stages and "pins".
A "pin" is a connection between a link and a stage. Every link in a complete job is represented by two pin records.
The analogy is from electronic circuit boards, where the links are drawn on the board and components (such as integrated circuit chips) are connected to the links via pins.
A "pin" is a connection between a link and a stage. Every link in a complete job is represented by two pin records.
The analogy is from electronic circuit boards, where the links are drawn on the board and components (such as integrated circuit chips) are connected to the links via pins.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.