IO17917: TDI WILL USE THE VALUES IN THE LIST INSTEAD OF THE LIST ITSELF, BECAUSE THAT IS USUALLY WHAT IS EXPECTED
Fixes are available
Closed as program error.
TDI will use the values in the list instead of the list itself, because that is usually what is expected. But for the special attribute named "$tcb.accumulator" we actually want the list itself. Therefore a code change needs to be resolve. Steps to Duplicate: 1. Create an AL that uses and Assembly Line Function Component and the $tcb.accumulator where the accumulator is a list. Expect to get the list in return. Workaround for the example given. In the data flow of an AL, 1. Create a script component to set the newList attribute. For example: work.setAttribute("newList", java.util.ArrayList()); 2. Create the ALFC component and define the following: Output Map: Component attribute: $tcb.accumulator Assignment: return work.newList; Connection: testAL 3. Create a 2nd script node to view the list returned. if (work.newList) task.logmsg(work.newList); else task.logmsg("newList is null"); For the 2nd AL (named testAL) Create a Feed - File System connector A simple example is a File System connector to a file that contains email addresses. Desired Behavior: list is return from $tbc.accumulator Environment: TDI 7.1 and TDI 7.1.1
Problem with special attritue named "$tcb.accumulator" in TDI
This is bug in TDI code and has been fixed, formal fix will be made available in 7.1.1-TIV-TDI-FP0003.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
Translate this page: