DSXchange

No problem. I'm finding I actually do learn a lot by staying on top of the forums here and at Ascential/IBM DeveloperNet. I enjoy being able to answer or help and that has kept me interested in staying involved.

Thanks,
John

To iterate your series objects to correctly call a functional map, you need to use your input series object on an output card's series object. I hope this helps, John I generated a type DBTable --> which has Row(s) e.g., LINTEITEM-->DBTable --->Row(s) --->Column names My Output card is mapped to DB...

Yes, by "series object" I do mean an item that can occur more than once. So I am guessing you have something like this: InputCard InputItems (s) Going into: LineItemDetails LINEITEMS (s) ---> LINEITEM_ID ---> ITEM_NAME ---> ITEM_DESCRIPTION For this you would need to call your functional m...

Is the output card where you are calling the functional map a series object as well? It has to be for the functional map to be called multiple times.

John

With DSTX, it is possible to produce a cartesian product just as in SQL when you do a select and join two tables incorrectly producing large number of rows returned. I guess I don't understand fully what you are trying to produce. Plus, I have not used the DB interfaces as my situation has not allow...

There are a couple of ways to do this. You could right-click on the A.key column and select "Copy". That will put the item in your clipboard. Then paste it into the B.FK_A column. The other way to accomplish this with drag-and-drop is to get the A output card on top and drag the card title...

From a given output card you can not only reference any of the input card, but also any of the preceeding output cards. So in the output card for B's FK reference to A, use the key value from the output card for A.

John

From the Unix shell just do something like this:
That will execute the map with all the settings compiled in the map. You can override many of the settings just as you do with the RUN function.

I suggest taking a look at the Execution Commands Reference Guide PDF.

How would you code something like this in TX ? IF CODE = 1, WRITE A REC OR IF CODE = 2 WRITE B REC OR IF CODE = 3 WRITE C REC OR IF.... ETC DatastageTX's If/Then does not have an ElseIF component common to many traditional languages. Also, it does not have true Case statement. What it does have is ...

Do you have the Restart attribute set in the input Type Tree? If so, then validation wouldn't fail and you could use the reject function to access any bad records.

I agree, more information is needed.

I would suggest removing the Release character for one element and then export the Type Tree. Take a look at how the mts file is formed for that element with the undefined Release character. Then fix the other elements in the same manner.

my $0.02.

I had a similar problem in DSTX 7.51. I submitted a request for assistance and was told there was a bug. They created a patch for us that does work. However, it didn't solve the problem I wanted it to. Not because the patch didn't work, but because I was trying to do something that was abnormal and ...