Hi everybody
I am new to the Datastage and tried to get started with TX jobs but have no idea where to get the basic information about TX Jobs
Things like where do we use TX jobs , How different is it from Server jobs etc .
Also I tried to search in this forum but could not find basic information, although I found many related topics on TX .
Any pointers from your side will be great 1
Thanks in advance
TX Jobs
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Not sure if this will help you... To make your decision you'll really need to determine what you are trying to accomplish.
"How different is it from Server jobs etc" Can't really say. I used to go to some of the Ascential dev group meeting in the area. It seemed to me that they were very similar. The big diffs were DS is much better dealing with bulk loads to DBs, TX is better for event based transactions.
TX is designed as a data transformation tool. Changing non-proprietary data formats to proprietaty; X12 to flat file or DB; or vise versa. We use it to transform inbound data to standardized data formats so other non-TX code gets a consistant file to work with. We also load data to temp-tables so it can be processed into production tables by java code or SPs. Finally we use it to transform outbound data to trading partner friendly formats.
In our case we also use it to process real time queries relates to member benefits, claims etc. You type tree definitions inforce structural constraints and your map rules will inforce other data constriants.
Hope that helps...
"How different is it from Server jobs etc" Can't really say. I used to go to some of the Ascential dev group meeting in the area. It seemed to me that they were very similar. The big diffs were DS is much better dealing with bulk loads to DBs, TX is better for event based transactions.
TX is designed as a data transformation tool. Changing non-proprietary data formats to proprietaty; X12 to flat file or DB; or vise versa. We use it to transform inbound data to standardized data formats so other non-TX code gets a consistant file to work with. We also load data to temp-tables so it can be processed into production tables by java code or SPs. Finally we use it to transform outbound data to trading partner friendly formats.
In our case we also use it to process real time queries relates to member benefits, claims etc. You type tree definitions inforce structural constraints and your map rules will inforce other data constriants.
Hope that helps...